WO2011035638A1 - 接入网关控制功能用户呼叫转接业务的实现方法及系统 - Google Patents

接入网关控制功能用户呼叫转接业务的实现方法及系统 Download PDF

Info

Publication number
WO2011035638A1
WO2011035638A1 PCT/CN2010/075235 CN2010075235W WO2011035638A1 WO 2011035638 A1 WO2011035638 A1 WO 2011035638A1 CN 2010075235 W CN2010075235 W CN 2010075235W WO 2011035638 A1 WO2011035638 A1 WO 2011035638A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
agcf
sends
call
message
Prior art date
Application number
PCT/CN2010/075235
Other languages
English (en)
French (fr)
Inventor
杨强
王忱
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to AU2010297787A priority Critical patent/AU2010297787B2/en
Priority to EP10818332.8A priority patent/EP2466819B1/en
Priority to RU2012112486/08A priority patent/RU2491740C1/ru
Priority to MX2012003429A priority patent/MX2012003429A/es
Priority to BR112012006349A priority patent/BR112012006349A2/pt
Priority to IN2275DEN2012 priority patent/IN2012DN02275A/en
Priority to US13/258,376 priority patent/US8559613B2/en
Publication of WO2011035638A1 publication Critical patent/WO2011035638A1/zh
Priority to HK12109405.6A priority patent/HK1168702A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/54Arrangements for diverting calls for one subscriber to another predetermined subscriber
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/102Gateways
    • H04L65/1023Media gateways
    • H04L65/103Media gateways in the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/102Gateways
    • H04L65/1033Signalling gateways
    • H04L65/104Signalling gateways in the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/1046Call controllers; Call servers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/1063Application servers providing network services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M7/00Arrangements for interconnection between switching centres
    • H04M7/12Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
    • H04M7/1205Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
    • H04M7/126Interworking of session control protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/16Communication-related supplementary services, e.g. call-transfer or call-hold

Definitions

  • the present invention relates to the field of communications, and in particular to a call forwarding service for a user carried by an access gateway control function (AGCF) in a network of a public switched telephone network/integrated service digital network (PES, PSTN/ISDN Emulation Subsystem) Implementation method and system.
  • AGCF access gateway control function
  • the Internet Protocol Multimedia Subsystem is an Internet Protocol (IP)-based network architecture proposed by the 3rd Generation Partnership Project (3GPP), which builds a network architecture.
  • IP Internet Protocol
  • 3GPP 3rd Generation Partnership Project
  • PES IP-based network architecture proposed by the traditional terminal to access the IMS network by Telecommunications and Internet converged services and protocols (TISPAN).
  • ETSI 183 043 The development of ETSI 183 043 is based on solving the above problems. However, the current ETSI 183 043 describes only the traditional services of H248 users such as three-party, call waiting, etc. Two implementations are tightly coupled, and the relevant procedures are also described in the appendix of ETSI 183 043. There is currently no specification for how to implement the call forwarding service for users carrying AGCF, and there is no corresponding technology to explain. Summary of the invention
  • the main purpose of the present invention is to provide a method and system for implementing an AGCF subscriber call forwarding service, and implementing a call forwarding service for a user carried by the AGCF.
  • An implementation method for an access gateway control function user call transfer service comprising: an access gateway control function (AGCF) user accessing a public switched telephone network/integrated service digital network emulation subsystem (PES) through an AGCF
  • AGCF access gateway control function
  • PES public switched telephone network/integrated service digital network emulation subsystem
  • AS application server
  • the call forwarding service is implemented by using the tightly coupled manner and the manner of the AS master control, including:
  • the AGCF After the AGCF user hangs up, the AGCF sends a release call message to the AS in the conversation between the AGCF user and the non-AGCF user, and triggers the use of the tight coupling between the AGCF and the AS to implement the interaction;
  • the AS triggers the mode of the AS master by sending a modify media request message to the non-AGCF user.
  • the non-AGCF user implements media negotiation in the AS master mode and implements the call between the non-AGCF users.
  • the AGCF user is the user A
  • the non-AGCF user is the user B and the user C.
  • the implementation of the call forwarding service further includes:
  • AGCF sends a release call message to AS in conversation between user A and user B, user A and user C; AS is in user A and user After the user C picks up the phone and sends the response response message to the AS, the AS sends a modify media request message to the user C.
  • the user C sends a modify media response message to the AS.
  • the AS sends a modify media request message to the user B.
  • the user B sends the modified media to the AS.
  • the response message; the AS sends a modify media request message to the user C; the user C sends a modify media response message to the AS; and implements a call between the user B and the user C;
  • the AGCF user is the user A
  • the non-AGCF user is the user B and the user C.
  • the implementation of the call forwarding service further includes:
  • the AS sends a modify media request message to the user C; the user C sends a modify media response message to the AS; the AS sends a modify media request message to the user B; the user B sends a modify media response message to the AS; and the AS sends a modify media request message to the user C; User C sends a modify media response message to the AS; implements a call between user B and user C.
  • the implementing the call forwarding service by using the tightly coupled manner and the end-to-end control manner includes:
  • the AGCF After the AGCF user hangs up, the AGCF sends a release call message to the AS in the conversation between the AGCF user and the non-AGCF user, and triggers the use of the tight coupling between the AGCF and the AS to implement the interaction;
  • the AS triggers the end-to-end control by sending a replacement call request message to the non-AGCF user.
  • the non-AGCF user implements media negotiation in an end-to-end control mode and implements a call between non-AGCF users.
  • the AGCF user is the user A
  • the non-AGCF user is the user B and the user C.
  • the implementation of the call forwarding service further includes: User C picks up the phone and sends an acknowledgement message to the AS. After the user A hangs up, the AGCF releases the A terminal.
  • the AGCF sends a release call message to the AS in the dialog between the user A and the user B and the user A and the user C.
  • a release response message is sent to the AGCF in the conversation between the user A and the user B, and the user A and the user C respectively;
  • the AS sends a replacement call request message to the user B; the user B sends a replacement call request reception message to the AS; the user B sends a replacement call start message to the AS; the user B sends a session invitation message to the AS; the AS sends a session invitation message to the user C; C sends an acknowledgement response message to the AS; the AS sends an acknowledgement response message to the user B; and implements a call between the user B and the user C;
  • the AGCF user is the user A
  • the non-AGCF user is the user B and the user C.
  • the implementation of the call forwarding service further includes:
  • the user A hangs up, the AGCF releases the A terminal; the AGCF sends a release call message to the AS in the conversation between the user A and the user B, and the user A and the user C; the AS picks up the call at the user A and the user C, and sends a response to the AS.
  • the AS sends a replacement call request message to the user B; the user B sends a replacement call request reception message to the AS; the user B sends a replacement call start message to the AS; the user B sends a session invitation message to the AS; the AS sends a session to the user C.
  • the invitation message is sent by the user C to the AS; the AS sends an answer response message to the user B; and the call between the user B and the user C is implemented.
  • the call forwarding service is implemented by using the loosely coupled manner and the manner of the AS master control, including:
  • the AGCF After the AGCF user hangs up, the AGCF sends a replacement call request message to the AS to trigger the interaction between the AGCF and the AS in a loosely coupled manner.
  • the AS sends a modify media request message to the non-AGCF user to trigger the mode that is controlled by the AS.
  • the non-AGCF user implements media negotiation in the AS master mode and implements the call between the non-AGCF users.
  • the AGCF user is the user A
  • the non-AGCF user is the user B and the user C.
  • the implementation of the call forwarding service further includes:
  • the AGCF sends a change call request message to the AS.
  • the AS sends a change call start message to the AGCF.
  • the AS sends a change call success message to the AGCF.
  • the release call message is sent to the AGCF; the AGCF sends a release call message to the AS in the call between the user A and the user B;
  • the AS sends a modify media request message to the user C; the user C sends a modify media response message to the AS; the AS sends a modify media request message to the user B; the user B sends a modify media response message to the AS; and the AS sends a modify media request message to the user C; User C sends a modify media response message to the AS; implements a call between user B and user C;
  • the AGCF user is the user A
  • the non-AGCF user is the user B and the user C.
  • the implementation of the call forwarding service further includes:
  • AGCF sends a change call request message to AS; AS sends change call request receiving message to AGCF; AS sends replacement call start message to AGCF; AS sends replacement call success message to AGCF; AS is at user A In the call with the user C, the release call message is sent to the AGCF; the AGCF sends a release call message to the AS in the call between the user A and the user B;
  • the AS sends a modify media request message to the user C.
  • the user C sends a modify media response message to the AS.
  • the AS sends a modify media request message to the user B.
  • the user B sends the modified media to the AS.
  • the response message; the AS sends a modify media request message to the user C; the user C sends a modify media response message to the AS; and implements a call between the user B and the user C.
  • the implementing the call forwarding service by using the method of coupling and the end-to-end control includes: After the AGCF user hangs up, the AGCF sends a replacement call request message to the AS to trigger the interaction between the AGCF and the AS in a loosely coupled manner.
  • the AS triggers the end-to-end control by sending a replacement call request message to the non-AGCF user.
  • the non-AGCF user implements media negotiation in an end-to-end control mode and implements a call between non-AGCF users.
  • the AGCF user is the user A
  • the non-AGCF user is the user B and the user C.
  • the call forwarding service further includes:
  • AGCF sends a change call request message to AS
  • AS sends a change call request receiving message to AGCF
  • AS sends a change call start message to AGCF
  • the AS sends a release call message to the AGCF in the call between the user A and the user C
  • the AS sends a replacement call success message to the AGCF
  • the AGCF sends a release call message to the AS in the call between the user A and the user B;
  • the AS sends a replacement call request message to the user B; the user B sends a replacement call request reception message to the AS; the user B sends a replacement call start message to the AS; the user B sends a session invitation message to the AS; the AS sends a session invitation message to the user C; C sends an acknowledgement response message to the AS; the AS sends an acknowledgement response message to the user B; and implements a call between the user B and the user C;
  • the AGCF user is the user A
  • the non-AGCF user is the user B and the user C.
  • the implementation of the call forwarding service further includes:
  • AGCF sends a change call request message to AS; AS sends change call request receiving message to AGCF; AS sends change call start message to AGCF; AS calls between user A and user C, Sending a release call message to the AGCF; the AS sends a replacement call success message to the AGCF; the AGCF sends a release call message to the AS in the call between the user A and the user B;
  • the AS After user C picks up the phone and sends an answer response message to the AS, the AS sends a replacement call to user B.
  • the AS sends an acknowledgement message to User B; implements a call between User B and User C.
  • An access gateway control function user call transfer service implementation system includes: a call transfer implementation unit, configured for an AGCF user to access the PES through the AGCF, and between the AGCF and the AS, using a tightly coupled manner/ Loosely coupled mode; between the AS and non-AGCF users, the AS master mode/end-to-end control mode is used to implement the call forwarding service of the AGCF user.
  • the call forwarding implementation unit is further configured to use the tightly coupled manner and the AS master control mode, after the AGCF user hangs up, the AGCF in the conversation between the AGCF user and the non-AGCF user, to the AS Sending a release call message, and triggering an interaction between the AGCF and the AS by using a tight coupling;
  • the AS triggers the mode of the AS master by sending a modify media request message to the non-AGCF user.
  • the non-AGCF user implements media negotiation in the AS master mode and implements the call between the non-AGCF users.
  • the call forwarding implementation unit is further configured to use the tightly coupled manner and the end-to-end control mode, after the AGCF user hangs up, the AGCF in the conversation between the AGCF user and the non-AGCF user
  • the AS sends a release call message, and triggers an interaction between the AGCF and the AS by using a tight coupling manner
  • the AS triggers the end-to-end control by sending a replacement call request message to the non-AGCF user.
  • the non-AGCF user implements media negotiation in an end-to-end control mode and implements a call between non-AGCF users.
  • the call forwarding implementation unit is further configured to: in the loosely coupled manner and the AS master control mode, after the AGCF user hangs up, the AGCF sends an exchange call request message to the AS, triggering the AGCF and the AS Interacting in a loosely coupled manner;
  • the AS sends a modify media request message to the non-AGCF user to trigger the mode that is controlled by the AS.
  • the non-AGCF user implements media negotiation in the AS master mode and implements the call between the non-AGCF users.
  • the call forwarding implementation unit is further configured to: in the loosely coupled manner and the end-to-end control mode, after the AGCF user hangs up, the AGCF sends an exchange call request message to the AS, triggering the AGCF and the Inter-AS uses a loosely coupled way to achieve interaction;
  • the AS triggers the end-to-end control by sending a replacement call request message to the non-AGCF user.
  • the non-AGCF user implements media negotiation in an end-to-end control mode and implements a call between non-AGCF users.
  • the AGCF and the application server use a tightly coupled/loosely coupled manner; between the AS and the non-AGCF user,
  • the AS master control mode/end-to-end control mode implements the call forwarding service of the AGCF user.
  • the traditional fixed network user can continue to normally use the call forwarding service including the ringing state transfer and the call state transfer after accessing the PES network through the AGCF. In terms of usage habits, it is the same as before accessing the PES network.
  • the present invention provides a loose coupling and a tight coupling implementation for the call forwarding service, and provides an end-to-end and AS control implementation between the AS and the non-AGCF user to implement the AGCF. The user's call forwarding service.
  • Embodiment 1 is a schematic flowchart of an implementation process of Embodiment 1 of the method of the present invention
  • Embodiment 2 is a schematic flowchart of an implementation process of Embodiment 2 of the method according to the present invention
  • Embodiment 3 is a schematic flowchart of an implementation process of Embodiment 3 of the method of the present invention.
  • Embodiment 4 is a schematic flowchart of an implementation process of Embodiment 4 of the method of the present invention.
  • FIG. 5 is a schematic diagram of an implementation process of Embodiment 5 of the method according to the present invention
  • FIG. 6 is a schematic diagram of an implementation process of Embodiment 6 of the method according to the present invention.
  • the basic idea of the present invention is: After the AGCF user accesses the PES through the AGCF, the AGCF and the AS are in a tightly coupled manner/loosely coupled manner; between the AS and the non-AGCF users, the AS is controlled by the AS. The way / by end-to-end control, the call forwarding service of the AGCF user is realized.
  • An implementation method of an AGCF user call forwarding service includes: after an AGCF user accesses a PES through an AGCF, and uses a tightly coupled/loosely coupled manner between the AGCF and the AS; and in the AS and the non-AGCF Between the users, the AS master mode/end-to-end control mode is used to implement the call forwarding service of the AGCF user.
  • the end-to-end control mode is: The way of non-AGCF user end-to-end control.
  • the end-to-end control method is equivalent to the control method of the peer relationship;
  • the AS master control mode is equivalent to the master-slave relationship control mode.
  • the first scenario ⁇ Use a tightly coupled approach and a scenario in which the AS is mastered.
  • the implementation of the call forwarding service specifically includes the following contents:
  • the AGCF sends a release call message to the AS in the conversation between the AGCF user and the non-AGCF user, and triggers the use of the AGCF and the AS.
  • the coupling method implements the interaction.
  • the AS sends the modify media request message to the non-AGCF user to trigger the AS master control mode.
  • the non-AGCF user implements the media in the AS master control mode.
  • Negotiate and implement calls between non-AGCF users Two scenarios are included in this scenario, which are explained below.
  • the AGCF user is specifically user A
  • the non-AGCF user is specifically user B and user C; in the case of ringing state transfer.
  • the implementation of the call forwarding service further includes the following:
  • the user A hangs up and the AGCF releases the A terminal; the AGCF sends a release call message to the AS in the conversation between the user A and the user B, the user A and the user C respectively.
  • the AS sends a release response message to the AGCF in the conversation between User A and User B, User A and User C, respectively.
  • the AS sends a modify media request message to the user C.
  • the user C sends a modified media response to the AS.
  • the message is sent by the AS to the user B; the user B sends a modify media response message to the AS; the AS sends a modify media request message to the user C; the user C sends a modify media response message to the AS; Call.
  • the implementation of the call forwarding service further includes the following:
  • the AGCF For the method of tightly coupling between the AGCF and the AS, after the user C picks up the phone and sends an acknowledgement message to the AS, the user A hangs up, the AGCF releases the A terminal, and the AGCF is at the user A and the user B, the user A and the user.
  • the release call message is sent to the AS in the conversation between the Cs respectively; the AS sends a release response message to the AGCF in the conversation between the user A and the user B, the user A and the user C, respectively.
  • the AS sends a modify media request message to the user C; the user C sends a modify media response message to the AS; the AS sends a modify media request message to the user B; B sends a modify media response message to the AS; the AS sends a modify media request message to the user C; the user C sends a modify media response message to the AS; Now the call between user B and user C.
  • the second scenario A scenario that uses a tightly coupled approach and end-to-end control.
  • the implementation of the call forwarding service specifically includes the following contents:
  • the AGCF sends a release call message to the AS in the conversation between the AGCF user and the non-AGCF user, and triggers the use of the AGCF and the AS.
  • the coupling method implements the interaction.
  • the AS triggers the end-to-end control by sending a replacement call request message to the non-AGCF user; the non-AGCF user is in the end-to-end control mode.
  • Media negotiation is implemented and calls between non-AGCF users are implemented.
  • the AGCF user is specifically user A, and the non-AGCF user is specifically user B and user C; in the case of call state transfer.
  • the implementation of the call forwarding service further includes the following:
  • the AGCF For the method of tightly coupling between the AGCF and the AS, after the user C picks up the phone and sends an acknowledgement message to the AS, the user A hangs up, the AGCF releases the A terminal, and the AGCF is at the user A and the user B, the user A and the user.
  • the release call message is sent to the AS in the conversation between the Cs respectively; the AS sends a release response message to the AGCF in the conversation between the user A and the user B, the user A and the user C, respectively.
  • the AS sends a change call request message to the user B; the user B sends a change call request reception message to the AS; and the user B sends a change call start message to the AS.
  • the user B sends a session invitation message to the AS; the AS sends a session invitation message to the user C; the user C sends an answer response message to the AS; the AS sends an answer response message to the user B; and the call between the user B and the user C is implemented.
  • the implementation of the call forwarding service further includes the following:
  • the user A hangs up and the AGCF releases the A terminal; the AGCF sends a release call message to the AS in the conversation between the user A and the user B, the user A and the user C respectively.
  • the AS sends a release response message to the AGCF in the conversation between User A and User B, User A and User C, respectively.
  • the AS sends a change call request message to the user B; the user B sends a change call to the AS. Requesting to receive a message; User B sends a Change Call Start message to the AS; User B sends a Session Invite message to the AS; AS sends a Session Invite message to User C; User C sends an Answer Response message to AS; AS sends an Answer Response message to User B; Implement a call between User B and User C.
  • the third scenario Use the coupled mode and the scene of the AS master mode.
  • the implementation of the call forwarding service specifically includes the following contents:
  • the AGCF sends a replacement call request message to the AS to trigger the interaction between the AGCF and the AS in a loosely coupled manner.
  • the AS sends a modify media request message to the non-AGCF user to trigger the mode controlled by the AS.
  • the non-AGCF user implements media negotiation in the AS master mode and implements non-AGCF users. Call.
  • user C picks up the phone and sends an acknowledgement message to the AS.
  • AGCF releases A terminal; AGCF sends a replacement call request to AS.
  • the AS sends a replacement call start message to the AGCF; the AS sends a replacement call success message to the AGCF; the AS sends a release call message to the AGCF in the call between the user A and the user C; the AGCF is between the user A and the user B.
  • a release call message is sent to the AS.
  • the AS sends a modify media request message to the user C; the user C sends a modify media response message to the AS; the AS sends a modify media request message to the user B; the user B sends a modify media response message to the AS; Sending a modify media request message to user C; user C sends a modify media response message to the AS; and implements a call between user B and user C.
  • the implementation of the call forwarding service further includes the following:
  • AGCF For the loose coupling, user A hangs up, AGCF releases A terminal; AGCF sends a replacement call request message to AS; AS sends change call request receiving message to AGCF; AS sends replacement call start message to AGCF; AS to AGCF Sending a replacement call success message; the AS sends a release call message to the AGCF in the call between the user A and the user C; the AGCF sends a release call message to the AS in the call between the user A and the user B.
  • the user C picks up the phone and sends an acknowledgement response message to the AS.
  • the AS sends a modify media request message to the user C.
  • the user C sends a modify media response message to the AS.
  • the AS sends a modify media request to the user B.
  • the user B sends a modify media response message to the AS;
  • the AS sends a modify media request message to the user C;
  • the user C sends a modify media response message to the AS; and implements a call between the user B and the user C.
  • the fourth scenario A scenario that uses a loosely coupled approach and end-to-end control.
  • the implementation of the call forwarding service specifically includes the following contents:
  • the AGCF sends a replacement call request message to the AS to trigger the interaction between the AGCF and the AS in a loosely coupled manner.
  • the AS sends a replacement call to the non-AGCF user.
  • Request message trigger end-to-end control mode;
  • Non-AGCF users implement media negotiation in end-to-end control mode and implement calls between non-AGCF users.
  • the AS sends a change call request message to the user B; the user B sends a change call request receiving message to the AS; the user B sends a change call start message to the AS; and the user B sends a session invite message to the AS;
  • the AS sends a session invitation message to the user C; the user C sends an answer response message to the AS; the AS sends an answer response message to the user B; and the call between the user B and the user C is implemented.
  • the implementation of the call forwarding service further includes the following:
  • AGCF For the loose coupling, user A hangs up, AGCF releases A terminal; AGCF sends a replacement call request message to AS; AS sends change call request receiving message to AGCF; AS sends replacement call start message to AGCF; AS is in user In the call between A and user C, a release call message is sent to the AGCF; the AS sends a replacement call success message to the AGCF; the AGCF sends a release call message to the AS in the call between the user A and the user B.
  • the AS For the end-to-end control mode, after the user C picks up the phone and sends an answer response message to the AS, the AS sends a change call request message to the user B.
  • the user B sends a change call request receiving message to the AS; the user B sends the replacement call to the AS.
  • the call start message the user B sends a session invitation message to the AS; the AS sends a session invitation message to the user C; the user C sends an answer response message to the AS; the AS sends a response response message to the user B; and the call between the user B and the user C is implemented.
  • the invention is illustrated by way of example below.
  • Embodiment 1 The case of the ring state transfer of the AS-controlled tightly coupled mode. As shown in FIG. 1, the implementation process of this embodiment includes the following steps:
  • Step 101 User A and user B of the AGCF have established a call according to the prior art.
  • User B is not required to be an AGCF user, and may be a non-AGCF user.
  • the descriptions of the user B referred to in the following embodiments are also the meanings herein, and are not described below.
  • Step 102 User A flashes the hook and sends a confirmation (NOTIFY) message to the AGCF.
  • Step 103 The AGCF creates a new call for the hook event of the user A, and initiates a call to the AS.
  • the call is specifically a session invite message in the SIP protocol.
  • Step 104 The AS sends a media request message to the opposite end of the user A, that is, the user B, sets an appropriate media state, and holds the user B.
  • the message is specifically a re-invite message in the SIP protocol.
  • the AS may control the media server to put a dial tone to the user A, and let the user A input the number of the user C; or the AS may return the failure response message of the incomplete number to the AGCF, and let the AGCF control the media server to give the user A a dial tone. Let User A enter the number of User C and create a new call.
  • Step 105 The AS initiates a call to the user C, which is an invite message in the SIP protocol.
  • Steps 106-107 User C returns a ringing response message to the user through the AS, which is an 18x message in the SIP protocol. User A will hear a ringback tone or other beep.
  • the response message is released, which is a 200 OK message in the SIP protocol.
  • the AS can let the user B listen to the ring back tone or other prompt tone according to its own logic and the needs of different clients, and wait for receiving the response response of the user C through media negotiation or the like.
  • Step 112 The C user picks up the phone and sends a response message to the AS, which is a 200 OK message in the SIP protocol.
  • Steps 113-118, user B and user C implement media negotiation under the control of the AS, and implement a call between user B and user C.
  • Embodiment 2 The end-to-end tight coupling mode of the call state transfer. As shown in FIG. 2, the implementation process of this embodiment includes the following steps:
  • Step 201 User A and user B of the AGCF have established a call according to the prior art.
  • Step 202 User A flashes the hook and sends a NOTIFY message to the AGCF.
  • Step 203 The AGCF creates a new call for the hook event of the user A, and initiates a call to the AS.
  • the call is specifically an invite message in the SIP protocol.
  • Step 204 The AS sends a media request message to the opposite end of the user A, that is, the user B, sets an appropriate media state, and holds the user B.
  • This message is a re-invite message in the SIP protocol.
  • the AS may control the media server to put a dial tone to the user A, and let the user A input the number of the user C; or the AS may return the failure response message of the incomplete number to the AGCF, and let the AGCF control the media server to give the user A a dial tone. Let User A enter the number of User C and create a new call.
  • Step 205 The AS initiates a call to the user C, which is an invite message in the SIP protocol.
  • Steps 206-207 user C picks up the phone, and other temporary responses are ignored here, and the AS sends an acknowledgement response message to the AGCF, which is a 200 OK message in the SIP protocol.
  • User A and User C implement the call.
  • Steps 208-209 user A hangs up, and the AGCF releases the A terminal.
  • Steps 210-211 The AGCF sends a call message to the AS in the user A-user B and the user A-user C session, which is a BYE message in the SIP protocol, and the AS is in the user A-user B, and the user A-user C talks.
  • the response message is released, which is a 200 OK message in the SIP protocol.
  • Step 212 The AS sends a replacement call request message to the user B, which is a REFER message in the SIP protocol.
  • Step 213 User B returns a call request receiving message to the AS, which is a type 200 message in the SIP protocol, such as 202.
  • Step 214 User B sends a replacement call start message to the AS, which is a NOTIFY message in the SIP protocol, and carries a 100 trying instruction.
  • the AS will give User B a 200 OK response, which is omitted from the flowchart.
  • Steps 215-216 User B sends a session invitation message to user C through the AS, which is an invite message in the SIP protocol.
  • Step 219 After receiving the response response confirmation message, the user C sends a user A-user C conversation message to the AS, which is a BYE message in the SIP protocol, and releases the user A-user C conversation.
  • Step 220 After receiving the response response message, the user B sends a replacement call success message to the AS, which is a NOTIFY message of the SIP protocol, and carries a 200 OK indication.
  • Step 221 After receiving the message of replacing the call success, the AS sends a call release request message to the user B in the user A-user B session.
  • Embodiment 3 The case of the call state transfer of the AS-controlled coupling mode. As shown in FIG. 3, the implementation process of this embodiment includes the following steps:
  • Step 301 User A and User B of the AGCF have established a call according to the prior art.
  • Step 302 User A flashes the hook and sends a NOTIFY message to the AGCF.
  • the response message 200 OK of re-invite is omitted in the flowchart.
  • Steps 305-306 the AGCF gives the user A a dialing tone, and the user A inputs the number of the user C.
  • Steps 307-308 the AGCF creates a new call for the user A, and calls the user C through the AS, which is an invite message in the SIP protocol.
  • Steps 309-310 the user C picks up the phone, sends an response message to the user A through the AS, and is a 200 OK message in the SIP protocol, so that the user A and the user C talk. There may be some temporary response messages before, which are ignored here.
  • Step 311-312 User A hangs up, and AGCF releases A terminal.
  • Step 313 The AGCF sends a replacement call request message to the AS, which is a REFER message in the SIP protocol.
  • Step 314 The AS sends a call change start message to the AGCF, which is a NOTIFY message in the SIP protocol, and carries a 100 trying indication.
  • AGCF a NOTIFY message in the SIP protocol
  • 200 types of messages in the SIP protocol, such as 202, are omitted in the flowchart.
  • Steps 315-320 the AS initiates media negotiation between user B and user C, and user B communicates with user C.
  • Step 321 The AS notifies the AGCF that the call forwarding service has been successfully implemented, and the NOTIFY message in the SIP protocol carries the 200 OK indication.
  • Step 322 The AS sends a BYE to the AGCF in the user A-user C call, releasing the user.
  • Step 323 The AGCF sends a BYE to the AS in the user A-user B call, and releases the conversation between the user A and the user B.
  • 200 OK is omitted in the flowchart.
  • Embodiment 4 The end-to-end loosely coupled mode of call state transfer. As shown in Figure 4, The implementation process of this embodiment includes the following steps:
  • Step 401 User A and user B of the AGCF have established a call according to the prior art.
  • Step 402 User A flashes the hook and sends a NOTIFY message to the AGCF.
  • Steps 403-404 The AGCF maintains the peer end of the user A, that is, the user B, as the re-invite message of the SIP protocol.
  • the response message of re-invite 200 OK is omitted in the flowchart.
  • Steps 405-406 the AGCF gives the user A a dialing tone, and the user A inputs the number of the user C.
  • Steps 407-408 the AGCF creates a new call for the user A, and calls the user C through the AS, which is an invite message in the SIP protocol.
  • Steps 409-410 user C picks up the phone, sends an response message to user B through the AS,
  • the 200 OK message in the SIP protocol implements the user B-user C call. There may be some temporary response messages before, which are ignored here.
  • Step 411-412 User A hangs up, and AGCF releases A terminal.
  • Step 413 The AGCF sends a replacement call request message to the AS, which is a REFER message in the SIP protocol.
  • Step 414 The AS sends a replacement call request message to the user B, which is a REFER message in the SIP protocol.
  • Steps 415-416 User B returns a call request acceptance message to the AGCF through the AS. It is 200 types of messages in the SIP protocol, such as 202.
  • Step 417-418 User B sends a call change start message to the AGCF through the AS, which is a NOTIFY message in the SIP protocol, and carries a 100 trying indication.
  • the AGCF will return a 200 OK response to the user B through the AS, which is omitted in the flowchart.
  • Step 419-420 User B sends a session invitation message to user C through the AS, which is an invite message in the SIP protocol.
  • Steps 421-422 the user C sends an response message to the user B through the AS, which is a SIP protocol.
  • the 200 OK message in the middle implements the user B-user C call.
  • Step 423-424 After receiving the response response confirmation message, the user C sends a user A-user C conversation message to the AGCF through the AS, and releases the user A-user C conversation for the BYE message in the SIP protocol.
  • Steps 425-426 after receiving the response message, the user B sends a replacement call success message to the AGCF through the AS, which is a NOTIFY message of the SIP protocol, which carries a 200 OK indication.
  • Steps 427-428 after receiving the message of replacing the call success, the AGCF sends a call release request message to the user B through the AS in the user A-user B session.
  • Embodiment 5 The case of the ringing state of the loosely coupled mode controlled by the AS. As shown in FIG. 5, the implementation process of this embodiment includes the following steps:
  • Step 501 User A and User B of the AGCF have established a call according to the prior art.
  • Step 502 User A flashes the hook and sends a NOTIFY message to the AGCF.
  • Steps 503-504 The AGCF maintains the peer end of the user A, that is, the user B, as a re-invite message of the SIP protocol.
  • the response message of re-invite 200 OK is omitted in the flowchart.
  • Step 509-510 User C returns a ringing response message to the user through the AS, which is an 18x message in the SIP protocol. User A will hear a ringback tone or other beep.
  • Step 511-512 User A hangs up, and AGCF releases A terminal.
  • Step 513 User A hangs up, and the AGCF sends a replacement call request message to the AS, which is a REFER message in the SIP protocol.
  • Step 514 The AS sends a replacement call request receiving message to the AGCF, which is a type 200 message in the SIP protocol, for example, 202 message. Thereafter, the AS can be based on its own logic and the needs of different customers.
  • User B listens to ring back tone or other prompt tone through media negotiation, etc., and waits to receive user C's response response.
  • Step 515 User C picks up the phone and sends an response message to the AS, which is a 200 OK message in the SIP protocol.
  • Step 516 The AS sends a replacement call start message to the AGCF, which is a NOTIFY message in the SIP protocol, and carries a 100 trying indication.
  • Steps 517-522 The AS initiates media negotiation between user B and user C to implement a call between user B and user C.
  • Step 523 The AS notifies the AGCF that the call forwarding service has been successfully implemented, and the NOTIFY message in the SIP protocol carries the 200 OK indication.
  • Step 524 The AS sends a BYE to the AGCF in the user A-user C call, and releases the conversation between the user A and the user B.
  • 200 OK is omitted in the flowchart.
  • Step 525 The AGCF sends a BYE to the AS in the user A-user B call, and releases the dialogue between the user A and the user C.
  • 200 OK is omitted in the flowchart.
  • Embodiment 6 The end-to-end loosely coupled mode of the ringing state transition. As shown in FIG. 6, the implementation process of this embodiment includes the following steps:
  • Step 601 User A and user B of the AGCF have established a call according to the prior art.
  • Step 602 User A flashes the hook and sends a NOTIFY message to the AGCF.
  • Steps 603-604 the AGCF maintains the peer end of the user A, that is, the user B, through the AS, as
  • Steps 605-606 the AGCF gives the user A a dialing tone, and the user A inputs the number of the user C.
  • Steps 607-608 the AGCF creates a new call for the user A, and calls the user C through the AS as an invite message in the SIP protocol. Steps 609-610, the user C returns a ringing response message to the user through the AS, which is an 18x message in the SIP protocol. User A will hear a ringback tone or other tone.
  • Step 611-612 User A hangs up, and AGCF releases A terminal.
  • Step 613 User A hangs up, and the AGCF sends a replacement call request message to the AS, which is a REFER message in the SIP protocol.
  • Step 614 The AS sends a replacement call request receiving message to the AGCF, which is a type 200 message in the SIP protocol, for example, a 202 message. Thereafter, the AS can let the user B listen to the ring back tone or other prompt tone according to its own logic and the needs of different customers, and wait for receiving the response response of the user C through media negotiation or the like.
  • AGCF a type 200 message in the SIP protocol
  • the AS can let the user B listen to the ring back tone or other prompt tone according to its own logic and the needs of different customers, and wait for receiving the response response of the user C through media negotiation or the like.
  • Step 615 User C picks up the phone and sends an response message to the AS, which is a 200 OK message in the SIP protocol.
  • Step 616 The AS sends a replacement call request message to the user B, which is a REFER message in the SIP protocol.
  • Step 617 User B returns a call request acceptance message to AS AGCF. It is 200 types of messages in the SIP protocol, such as 202.
  • Step 618-619 User B sends a call change start message to the AGCF through the AS, which is a NOTIFY message in the SIP protocol, and carries a 100 trying indication.
  • the AGCF will send a 200 OK response to User B through the AS, which is omitted in the flowchart.
  • Steps 620-621 User B sends a session invitation message to user C through the AS, which is an INVITE message in the SIP protocol.
  • Steps 622-623 the user C sends an response message to the B through the AS, which is a 200 OK message in the SIP protocol, and implements the user B-user C call.
  • Steps 624-625 After receiving the response response confirmation message, the user C sends an AC conversation message to the AGCF through the AS, which is a BYE message in the SIP protocol, and releases the user A-user C conversation.
  • Steps 626-627 After receiving the response response message, the user B sends a replacement call success message to the AGCF through the AS, which is a NOTIFY message of the SIP protocol, and carries a 200 OK indication.
  • Steps 628-629 After receiving the message of replacing the call success, the AGCF sends a call release request message to the user B through the AS in the user A-user B session.
  • the flow in the embodiment is merely a schematic flow.
  • the AGCF, the AS network element and the messages between them in the embodiment are mainly for clearly expressing the idea of implementing the AGCF user call forwarding service. In a specific implementation, it is not limited to these network elements and messages.
  • the CSCF referred to in Figure 3 and Figure 5 refers to the call session control function.
  • the English name is: Call Session Control Function 0.
  • the AGCF user referred to in the text refers to: The user carried by the AGCF is The non-AGCF user involved in the call refers to: The non-AGCF user involved in the call is not required to be the user of the AGCF, but also the user carried by the AGCF, or the PES network. Any user.
  • An AGCF user call forwarding service implementation system includes: a call forwarding implementation unit, configured for an AGCF user to access the PES through the AGCF, and between the AGCF and the AS, using a tightly coupled manner/loosely coupled manner ; between AS and non-AGCF users, use AS master
  • the control mode/end-to-end control mode implements the call forwarding service of the AGCF user.
  • the specific implementation of the call forwarding implementation unit in different scenarios is different, which are respectively explained below.
  • the first specific implementation In the scenario of the tightly coupled mode and the AS master mode, the call forwarding implementation unit is further used for the AGCF user to hang up, the AGCF in the conversation between the AGCF user and the non-AGCF user, to the AS The release of the call message is sent, and the interaction between the AGCF and the AS is triggered by tight coupling.
  • the AS triggers the mode of the AS master by sending a modify media request message to the non-AGCF user.
  • the non-AGCF user implements the media negotiation in the AS master mode and implements the call between the non-AGCF users.
  • the call forwarding implementation unit is further used for the AGCF user to hang up, the AGCF in the conversation between the AGCF user and the non-AGCF user,
  • the AS sends a release call message and triggers the interaction between the AGCF and the AS in a tightly coupled manner.
  • the AS triggers end-to-end control by sending a call change request message to a non-AGCF user.
  • the non-AGCF user implements media negotiation in an end-to-end control mode and implements a call between non-AGCF users.
  • the call forwarding implementation unit is further used for the AGCF to hang up, and the AGCF sends the replacement call request message to the AS to trigger the AGCF and the AS.
  • the interaction is achieved in a loosely coupled manner.
  • the AS sends a modify media request message to the non-AGCF user to trigger the mode that is controlled by the AS.
  • the non-AGCF user implements media negotiation in the AS master mode and implements the call between the non-AGCF users.
  • the call forwarding implementation unit is further used by the AGCF to hang up after the AGCF sends a replacement call request message to the AS, triggering the AGCF and The ASs interact in a loosely coupled manner.
  • the AS triggers the end-to-end control mode by sending a replacement call request message to the non-AGCF user.
  • the non-AGCF user implements media negotiation in the end-to-end control mode and implements the non-AGCF user. The call between.

Landscapes

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

Abstract

本发明公开了一种接入网关控制功能用户呼叫转接业务的实现方法,该方法包括:在接入网关控制功能(AGCF)与应用服务器(AS)之间,采用紧耦合的方式/松耦合的方式;在AS与非AGCF用户之间,采用AS主控的方式/端到端控制的方式,实现AGCF用户的呼叫转接业务。本发明还公开了一种接入网关控制功能用户呼叫转接业务的实现系统,系统中,呼叫转接实现单元用于在AGCF与AS之间,采用紧耦合的方式/松耦合的方式;在AS与非AGCF用户之间,采用AS主控的方式/端到端控制的方式,实现AGCF用户的呼叫转接业务。采用本发明的方法及系统,实现了AGCF所带用户的呼叫转接业务。

Description

接入网关控制功能用户呼叫转接业务的实现方法及系统 技术领域
本发明涉及通信领域, 尤其涉及一种公用交换电话网 /综合业务数字网 的仿真子系统(PES, PSTN/ISDN Emulation Subsystem )网络中接入网关控 制功能(AGCF )所带用户的呼叫转接业务的实现方法及系统。 背景技术
网际协议多媒体子系统( IMS , IP Multimedia Core Network Subsystem ) 是由第三代合作伙伴计划 ( 3 GPP, 3rd Generation Partnership Project )组织 提出的一种基于网际协议( IP )的网络架构, 其构建了一个开放而灵活的业 务环境, 支持多媒体应用, 并为用户提供丰富的多媒体业务。 PES 则是电 信和互联网融合业务及高级网络协议 (TISPAN , Telecommunications and Internet converged Services and Protocols for Advanced Networking )将传统终 端接入 IMS网络提出的一种基于 IP的网络架构。
现有技术中, 目前已经有在 IMS架构中实现会话初始协议( SIP )终端 的转接业务, 包括盲转接和询问转接; 也有厂家借用该技术在 AGCF实现 传统 H248终端的盲转接和询问转接, 企图以这两个业务来替换传统 H248 终端的转接业务。 然而, 现有技术存在的问题是: 需要为用户登记盲转接 和询问转接两个业务; 用户在实现转接时需要确定到底是要盲转还是询问 转, 一旦选定, 就不可更改; 用户的体验也不同, 比如业务用户在发起转 接后, 将听不到回铃音; 现有的 AGCF用户盲转和询问转业务, 目前还没 有紧耦合的实现方法。
ETSI 183 043的制定立足于解决以上问题, 然而, 目前的 ETSI 183 043 仅对于 H248用户的传统业务比如三方、呼叫等待等业务, 描述了^^耦合和 紧耦合两种实现方式, 而且 ETSI 183 043的附录中对相关的流程也作了描 述。 对于如何实现 AGCF所带用户的呼叫转接业务目前还没有规范, 也没 有相应的技术给予说明。 发明内容
有鉴于此, 本发明的主要目的在于提供一种 AGCF用户呼叫转接业务 的实现方法及系统, 实现了 AGCF所带用户的呼叫转接业务。
为达到上述目的, 本发明的技术方案是这样实现的:
一种接入网关控制功能用户呼叫转接业务的实现方法, 该方法包括: 接入网关控制功能(AGCF )用户通过 AGCF接入公用交换电话网 /综合业 务数字网的仿真子系统(PES )后, 在 AGCF与应用服务器(AS )之间, 釆用紧耦合的方式 /松耦合的方式; 在 AS与非 AGCF用户之间, 釆用 AS 主控的方式 /端到端控制的方式, 实现 AGCF用户的呼叫转接业务。
其中,釆用所述紧耦合的方式和所述 AS主控的方式实现所述呼叫转接 业务包括:
AGCF用户挂机后, AGCF在 AGCF用户与非 AGCF用户的对话中, 向 AS发送释放呼叫消息,并触发 AGCF与 AS之间釆用紧耦合的方式实现 交互;
AS通过向非 AGCF用户发送修改媒体请求消息,触发 AS主控的方式; 非 AGCF用户在 AS主控的方式下实现媒体协商, 并实现非 AGCF用户之 间的通话。
其中, AGCF用户为用户 A, 非 AGCF用户为用户 B和用户 C; 在振 铃态转接的情况下, 实现所述呼叫转接业务进一步包括:
用户 A挂机, AGCF释放 A终端; AGCF在用户 A与用户 B、 用户 A 与用户 C之间的对话中分别向 AS发送释放呼叫消息; AS在用户 A与用户 用户 C摘机, 向 AS发送应答响应消息后, AS向用户 C发送修改媒体 请求消息; 用户 C向 AS发送修改媒体响应消息; AS向用户 B发送修改媒 体请求消息; 用户 B向 AS发送修改媒体响应消息; AS向用户 C发送修改 媒体请求消息; 用户 C向 AS发送修改媒体响应消息; 实现用户 B与用户 C之间的通话;
或者, AGCF用户为用户 A, 非 AGCF用户为用户 B和用户 C; 在通 话态转接的情况下, 实现所述呼叫转接业务进一步包括:
用户 C摘机, 向 AS发送应答响应消息后, 用户 A挂机, AGCF释放 A终端; AGCF在用户 A与用户 B、 用户 A与用户 C之间的对话中分别向 AS发送释放呼叫消息; AS在用户 A与用户 B、 用户 A与用户 C之间的对 话中分别向 AGCF发送释放响应消息;
AS向用户 C发送修改媒体请求消息; 用户 C向 AS发送修改媒体响应 消息; AS向用户 B发送修改媒体请求消息; 用户 B向 AS发送修改媒体响 应消息; AS向用户 C发送修改媒体请求消息; 用户 C向 AS发送修改媒体 响应消息; 实现用户 B与用户 C之间的通话。
其中, 釆用所述紧耦合的方式和所述端到端控制的方式实现所述呼叫 转接业务包括:
AGCF用户挂机后, AGCF在 AGCF用户与非 AGCF用户的对话中, 向 AS发送释放呼叫消息,并触发 AGCF与 AS之间釆用紧耦合的方式实现 交互;
AS通过向非 AGCF用户发送更换呼叫请求消息,触发端到端控制的方 式; 非 AGCF用户在端到端控制的方式下实现媒体协商, 并实现非 AGCF 用户之间的通话。
其中, AGCF用户为用户 A, 非 AGCF用户为用户 B和用户 C; 在通 话态转接的情况下, 实现所述呼叫转接业务进一步包括: 用户 C摘机, 向 AS发送应答响应消息后, 用户 A挂机, AGCF释放 A终端; AGCF在用户 A与用户 B、 用户 A与用户 C之间的对话中分别向 AS发送释放呼叫消息; AS在用户 A与用户 B、 用户 A与用户 C之间的对 话中分别向 AGCF发送释放响应消息;
AS向用户 B发送更换呼叫请求消息; 用户 B向 AS发送更换呼叫请求 接收消息; 用户 B向 AS发送更换呼叫开始消息; 用户 B向 AS发送会话邀 请消息; AS向用户 C发送会话邀请消息;用户 C向 AS发送应答响应消息; AS向用户 B发送应答响应消息; 实现用户 B与用户 C之间的通话;
或者, AGCF用户为用户 A, 非 AGCF用户为用户 B和用户 C; 在振 铃态转接的情况下, 实现所述呼叫转接业务进一步包括:
用户 A挂机, AGCF释放 A终端; AGCF在用户 A与用户 B、 用户 A 与用户 C之间的对话中分别向 AS发送释放呼叫消息; AS在用户 A与用户 用户 C摘机, 向 AS发送应答响应消息后, AS向用户 B发送更换呼叫 请求消息; 用户 B向 AS发送更换呼叫请求接收消息; 用户 B向 AS发送更 换呼叫开始消息; 用户 B向 AS发送会话邀请消息; AS向用户 C发送会话 邀请消息; 用户 C向 AS发送应答响应消息; AS向用户 B发送应答响应消 息; 实现用户 B与用户 C之间的通话。
其中,釆用所述松耦合的方式和所述 AS主控的方式实现所述呼叫转接 业务包括:
AGCF用户挂机后, AGCF通过向 AS发送更换呼叫请求消息, 触发 AGCF与 AS之间釆用松耦合的方式实现交互;
AS通过向非 AGCF用户发送修改媒体请求消息, 触发由 AS主控的方 式; 非 AGCF用户在 AS主控的方式下实现媒体协商, 并实现非 AGCF用 户之间的通话。 其中, AGCF用户为用户 A, 非 AGCF用户为用户 B和用户 C; 在通 话态转接的情况下, 实现所述呼叫转接业务进一步包括:
用户 C摘机, 向 AS发送应答响应消息后, 用户 A挂机, AGCF释放 A终端; AGCF向 AS发送更换呼叫请求消息; AS向 AGCF发送更换呼叫 开始消息; AS向 AGCF发送更换呼叫成功消息; AS在用户 A与用户 C之 间的呼叫中, 向 AGCF发送释放呼叫消息; AGCF在用户 A与用户 B之间 的呼叫中, 向 AS发送释放呼叫消息;
AS向用户 C发送修改媒体请求消息; 用户 C向 AS发送修改媒体响应 消息; AS向用户 B发送修改媒体请求消息; 用户 B向 AS发送修改媒体响 应消息; AS向用户 C发送修改媒体请求消息; 用户 C向 AS发送修改媒体 响应消息; 实现用户 B与用户 C之间的通话;
或者, AGCF用户为用户 A, 非 AGCF用户为用户 B和用户 C; 在振 铃态转接的情况下, 实现所述呼叫转接业务进一步包括:
用户 A挂机, AGCF释放 A终端; AGCF向 AS发送更换呼叫请求消 息; AS向 AGCF发送更换呼叫请求接收消息; AS向 AGCF发送更换呼叫 开始消息; AS向 AGCF发送更换呼叫成功消息; AS在用户 A与用户 C之 间的呼叫中, 向 AGCF发送释放呼叫消息; AGCF在用户 A与用户 B之间 的呼叫中, 向 AS发送释放呼叫消息;
用户 C摘机, 向 AS发送应答响应消息后, AS向用户 C发送修改媒体 请求消息; 用户 C向 AS发送修改媒体响应消息; AS向用户 B发送修改媒 体请求消息; 用户 B向 AS发送修改媒体响应消息; AS向用户 C发送修改 媒体请求消息; 用户 C向 AS发送修改媒体响应消息; 实现用户 B与用户 C之间的通话。
其中, 釆用所述 ^耦合的方式和所述端到端控制的方式实现所述呼叫 转接业务包括: AGCF用户挂机后, AGCF通过向 AS发送更换呼叫请求消息, 触发 AGCF与 AS之间釆用松耦合的方式实现交互;
AS通过向非 AGCF用户发送更换呼叫请求消息,触发端到端控制的方 式; 非 AGCF用户在端到端控制的方式下实现媒体协商, 并实现非 AGCF 用户之间的通话。
其中, AGCF用户为用户 A, 非 AGCF用户为用户 B和用户 C; 在通 话态转接的情况下, 实现所述呼叫转接业务进一步包括:
用户 C摘机, 向 AS发送应答响应消息后, 用户 A挂机, AGCF释放 A终端; AGCF向 AS发送更换呼叫请求消息; AS向 AGCF发送更换呼叫 请求接收消息; AS向 AGCF发送更换呼叫开始消息; AS在用户 A与用户 C之间的呼叫中, 向 AGCF发送释放呼叫消息; AS向 AGCF发送更换呼叫 成功消息; AGCF在用户 A与用户 B之间的呼叫中, 向 AS发送释放呼叫 消息;
AS向用户 B发送更换呼叫请求消息; 用户 B向 AS发送更换呼叫请求 接收消息; 用户 B向 AS发送更换呼叫开始消息; 用户 B向 AS发送会话邀 请消息; AS向用户 C发送会话邀请消息;用户 C向 AS发送应答响应消息; AS向用户 B发送应答响应消息; 实现用户 B与用户 C之间的通话;
或者, AGCF用户为用户 A, 非 AGCF用户为用户 B和用户 C; 在振 铃态转接的情况下, 实现所述呼叫转接业务进一步包括:
用户 A挂机, AGCF释放 A终端; AGCF向 AS发送更换呼叫请求消 息; AS向 AGCF发送更换呼叫请求接收消息; AS向 AGCF发送更换呼叫 开始消息; AS在用户 A与用户 C之间的呼叫中, 向 AGCF发送释放呼叫 消息; AS向 AGCF发送更换呼叫成功消息; AGCF在用户 A与用户 B之 间的呼叫中, 向 AS发送释放呼叫消息;
用户 C摘机, 向 AS发送应答响应消息后, AS向用户 B发送更换呼叫 请求消息; 用户 B向 AS发送更换呼叫请求接收消息; 用户 B向 AS发送更 换呼叫开始消息; 用户 B向 AS发送会话邀请消息; AS向用户 C发送会话 邀请消息; 用户 C向 AS发送应答响应消息; AS向用户 B发送应答响应消 息; 实现用户 B与用户 C之间的通话。
一种接入网关控制功能用户呼叫转接业务的实现系统, 该系统包括: 呼叫转接实现单元, 用于 AGCF用户通过 AGCF接入 PES, 在 AGCF与 AS之间, 釆用紧耦合的方式 /松耦合的方式; 在 AS与非 AGCF用户之间, 釆用 AS主控的方式 /端到端控制的方式,实现 AGCF用户的呼叫转接业务。
其中, 所述呼叫转接实现单元, 进一步用于釆用所述紧耦合的方式和 所述 AS主控的方式下, AGCF用户挂机后, AGCF在 AGCF用户与非 AGCF 用户的对话中, 向 AS发送释放呼叫消息, 并触发 AGCF与 AS之间釆用紧 耦合的方式实现交互;
AS通过向非 AGCF用户发送修改媒体请求消息,触发 AS主控的方式; 非 AGCF用户在 AS主控的方式下实现媒体协商, 并实现非 AGCF用户之 间的通话。
其中, 所述呼叫转接实现单元, 进一步用于釆用所述紧耦合的方式和 所述端到端控制的方式下, AGCF用户挂机后, AGCF在 AGCF用户与非 AGCF用户的对话中, 向 AS发送释放呼叫消息, 并触发 AGCF与 AS之间 釆用紧耦合的方式实现交互;
AS通过向非 AGCF用户发送更换呼叫请求消息,触发端到端控制的方 式; 非 AGCF用户在端到端控制的方式下实现媒体协商, 并实现非 AGCF 用户之间的通话。
其中, 所述呼叫转接实现单元, 进一步用于釆用所述松耦合的方式和 所述 AS主控的方式下, AGCF用户挂机后, AGCF通过向 AS发送更换呼 叫请求消息, 触发 AGCF与 AS之间釆用松耦合的方式实现交互; AS通过向非 AGCF用户发送修改媒体请求消息, 触发由 AS主控的方 式; 非 AGCF用户在 AS主控的方式下实现媒体协商, 并实现非 AGCF用 户之间的通话。
其中, 所述呼叫转接实现单元, 进一步用于釆用所述松耦合的方式和 所述端到端控制的方式下, AGCF用户挂机后, AGCF通过向 AS发送更换 呼叫请求消息, 触发 AGCF与 AS之间釆用松耦合的方式实现交互;
AS通过向非 AGCF用户发送更换呼叫请求消息,触发端到端控制的方 式; 非 AGCF用户在端到端控制的方式下实现媒体协商, 并实现非 AGCF 用户之间的通话。
本发明的 AGCF用户通过 AGCF接入 PES后,在 AGCF与应用服务器 ( AS , Application Server )之间, 釆用紧耦合的方式 /松耦合的方式; 在 AS 与非 AGCF用户之间, 釆用由 AS主控的方式 /由端到端控制的方式, 实现 AGCF用户的呼叫转接业务。
釆用本发明, 让传统固网用户在通过 AGCF接入到 PES网络之后, 能 够继续正常使用其包含振铃态转接和通话态转接在内的呼叫转接业务。 在 使用习惯上, 也与接入 PES网络之前相同。 在 AGCF与 AS之间, 本发明 为呼叫转接业务提供了松耦合和紧耦合两种实现方式, 在 AS 与非 AGCF 用户之间提供了端到端和 AS控制实现方式, 来实现 AGCF所带用户的呼 叫转接业务。 附图说明
图 1为本发明方法的实施例一的实现流程示意图;
图 2为本发明方法的实施例二的实现流程示意图;
图 3为本发明方法的实施例三的实现流程示意图;
图 4为本发明方法的实施例四的实现流程示意图;
图 5为本发明方法的实施例五的实现流程示意图; 图 6为本发明方法的实施例六的实现流程示意图。 具体实施方式
本发明的基本思想是: AGCF用户通过 AGCF接入 PES后, 在 AGCF 与 AS之间, 釆用紧耦合的方式 /松耦合的方式; 在 AS与非 AGCF用户之 间, 釆用由 AS主控的方式 /由端到端控制的方式, 实现 AGCF用户的呼叫 转接业务。
下面结合附图对技术方案的实施作进一步的详细描述。
一种 AGCF用户呼叫转接业务的实现方法, 该方法包括: AGCF用户 通过 AGCF接入 PES后, 在 AGCF与 AS之间, 釆用紧耦合的方式 /松耦合 的方式; 以及在 AS与非 AGCF用户之间, 釆用 AS主控的方式 /端到端控 制的方式, 实现 AGCF用户的呼叫转接业务。
其中, 端到端控制的方式即为: 非 AGCF用户的端到端控制的方式。 端到端控制的方式相当于对等关系的控制方式;而 AS主控的方式相当于主 从关系的控制方式。
以下, 对釆用紧耦合的方式、 松耦合的方式、 釆用 AS主控的方式、 端 到端控制的方式不同组合的场景下, 实现 AGCF用户呼叫转接业务的具体 处理过程分别阐述。
第一种场景: 釆用紧耦合的方式和 AS主控的方式的场景。
此时, 实现呼叫转接业务具体包括以下内容:
针对在 AGCF与 AS之间釆用紧耦合的方式而言, AGCF用户挂机后, AGCF在 AGCF用户与非 AGCF用户的对话中, 向 AS发送释放呼叫消息, 并触发 AGCF与 AS之间釆用紧耦合的方式实现交互。
针对在 AS与非 AGCF用户之间釆用 AS主控的方式而言, AS通过向 非 AGCF用户发送修改媒体请求消息, 触发 AS主控的方式; 非 AGCF用 户在 AS主控的方式下实现媒体协商, 并实现非 AGCF用户之间的通话。 在这种场景下包括两种情况, 以下分别阐述。
第一种情况: AGCF用户具体为用户 A, 非 AGCF用户具体为用户 B 和用户 C; 在振铃态转接的情况。 此时, 实现呼叫转接业务进一步包括以 下内容:
针对在 AGCF与 AS之间釆用紧耦合的方式而言,用户 A挂机, AGCF 释放 A终端; AGCF在用户 A与用户 B、 用户 A与用户 C之间的对话中分 别向 AS发送释放呼叫消息; AS在用户 A与用户 B、用户 A与用户 C之间 的对话中分别向 AGCF发送释放响应消息。
针对在 AS与非 AGCF用户之间釆用 AS主控的方式而言,用户 C摘机, 向 AS发送应答响应消息后, AS向用户 C发送修改媒体请求消息; 用户 C 向 AS发送修改媒体响应消息; AS向用户 B发送修改媒体请求消息; 用户 B向 AS发送修改媒体响应消息; AS向用户 C发送修改媒体请求消息; 用 户 C向 AS发送修改媒体响应消息; 实现用户 B与用户 C之间的通话。
第二种情况: AGCF用户具体为用户 A, 非 AGCF用户具体为用户 B 和用户 C; 在通话态转接的情况。 此时, 实现呼叫转接业务进一步包括以 下内容:
针对在 AGCF与 AS之间釆用紧耦合的方式而言, 用户 C摘机, 向 AS 发送应答响应消息后, 用户 A挂机, AGCF释放 A终端; AGCF在用户 A 与用户 B、 用户 A与用户 C之间的对话中分别向 AS发送释放呼叫消息; AS在用户 A与用户 B、 用户 A与用户 C之间的对话中分别向 AGCF发送 释放响应消息。
针对在 AS与非 AGCF用户之间釆用 AS主控的方式而言, AS向用户 C发送修改媒体请求消息; 用户 C向 AS发送修改媒体响应消息; AS向用 户 B发送修改媒体请求消息; 用户 B向 AS发送修改媒体响应消息; AS向 用户 C发送修改媒体请求消息; 用户 C向 AS发送修改媒体响应消息; 实 现用户 B与用户 C之间的通话。
第二种场景: 釆用紧耦合的方式和端到端控制的方式的场景。
此时, 实现呼叫转接业务具体包括以下内容:
针对在 AGCF与 AS之间釆用紧耦合的方式而言, AGCF用户挂机后, AGCF在 AGCF用户与非 AGCF用户的对话中, 向 AS发送释放呼叫消息, 并触发 AGCF与 AS之间釆用紧耦合的方式实现交互。
针对在 AS与非 AGCF用户之间釆用端到端控制的方式而言, AS通过 向非 AGCF用户发送更换呼叫请求消息,触发端到端控制的方式;非 AGCF 用户在端到端控制的方式下实现媒体协商, 并实现非 AGCF用户之间的通 话。
在这种场景下包括两种情况, 以下分别阐述。
第一种情况: AGCF用户具体为用户 A, 非 AGCF用户具体为用户 B 和用户 C; 在通话态转接的情况。 此时, 实现呼叫转接业务进一步包括以 下内容:
针对在 AGCF与 AS之间釆用紧耦合的方式而言, 用户 C摘机, 向 AS 发送应答响应消息后, 用户 A挂机, AGCF释放 A终端; AGCF在用户 A 与用户 B、 用户 A与用户 C之间的对话中分别向 AS发送释放呼叫消息; AS在用户 A与用户 B、 用户 A与用户 C之间的对话中分别向 AGCF发送 释放响应消息。
针对在 AS与非 AGCF用户之间釆用端到端控制的方式而言, AS向用 户 B发送更换呼叫请求消息; 用户 B向 AS发送更换呼叫请求接收消息; 用户 B向 AS发送更换呼叫开始消息; 用户 B向 AS发送会话邀请消息; AS向用户 C发送会话邀请消息; 用户 C向 AS发送应答响应消息; AS向 用户 B发送应答响应消息; 实现用户 B与用户 C之间的通话。
第二种情况: AGCF用户具体为用户 A, 非 AGCF用户具体为用户 B 和用户 c; 在振铃态转接的情况。 此时, 实现呼叫转接业务进一步包括以 下内容:
针对在 AGCF与 AS之间釆用紧耦合的方式而言,用户 A挂机, AGCF 释放 A终端; AGCF在用户 A与用户 B、 用户 A与用户 C之间的对话中分 别向 AS发送释放呼叫消息; AS在用户 A与用户 B、用户 A与用户 C之间 的对话中分别向 AGCF发送释放响应消息。
针对在 AS与非 AGCF用户之间釆用端到端控制的方式而言, 用户 C 摘机, 向 AS发送应答响应消息后, AS向用户 B发送更换呼叫请求消息; 用户 B向 AS发送更换呼叫请求接收消息;用户 B向 AS发送更换呼叫开始 消息; 用户 B向 AS发送会话邀请消息; AS向用户 C发送会话邀请消息; 用户 C向 AS发送应答响应消息; AS向用户 B发送应答响应消息; 实现用 户 B与用户 C之间的通话。
第三种场景: 釆用 耦合的方式和 AS主控的方式的场景。
此时, 实现呼叫转接业务具体包括以下内容:
针对釆用松耦合的方式而言, AGCF用户挂机后 , AGCF通过向 AS发 送更换呼叫请求消息, 触发 AGCF与 AS之间釆用松耦合的方式实现交互。
针对 AS主控的方式而言, AS通过向非 AGCF用户发送修改媒体请求 消息, 触发由 AS主控的方式; 非 AGCF用户在 AS主控的方式下实现媒体 协商, 并实现非 AGCF用户之间的通话。
在这种场景下包括两种情况, 以下分别阐述。
第一种情况: AGCF用户具体为用户 A, 非 AGCF用户具体为用户 B 和用户 C; 通话态转接的情况。 此时, 实现呼叫转接业务进一步包括以下 内容:
针对釆用松耦合的方式而言, 用户 C摘机, 向 AS发送应答响应消息 后, 用户 A挂机, AGCF释放 A终端; AGCF向 AS发送更换呼叫请求消 息; AS向 AGCF发送更换呼叫开始消息; AS向 AGCF发送更换呼叫成功 消息; AS在用户 A与用户 C之间的呼叫中, 向 AGCF发送释放呼叫消息; AGCF在用户 A与用户 B之间的呼叫中, 向 AS发送释放呼叫消息。
针对 AS主控的方式而言, AS向用户 C发送修改媒体请求消息; 用户 C向 AS发送修改媒体响应消息; AS向用户 B发送修改媒体请求消息; 用 户 B向 AS发送修改媒体响应消息; AS向用户 C发送修改媒体请求消息; 用户 C向 AS发送修改媒体响应消息; 实现用户 B与用户 C之间的通话。
第二种情况: AGCF用户具体为用户 A, 非 AGCF用户具体为用户 B 和用户 C; 振铃态转接的情况。 此时, 实现呼叫转接业务进一步包括以下 内容:
针对釆用松耦合的方式而言,用户 A挂机, AGCF释放 A终端; AGCF 向 AS发送更换呼叫请求消息; AS向 AGCF发送更换呼叫请求接收消息; AS向 AGCF发送更换呼叫开始消息; AS向 AGCF发送更换呼叫成功消息; AS在用户 A与用户 C之间的呼叫中, 向 AGCF发送释放呼叫消息; AGCF 在用户 A与用户 B之间的呼叫中, 向 AS发送释放呼叫消息。
针对 AS主控的方式而言, 用户 C摘机, 向 AS发送应答响应消息后, AS向用户 C发送修改媒体请求消息;用户 C向 AS发送修改媒体响应消息; AS向用户 B发送修改媒体请求消息;用户 B向 AS发送修改媒体响应消息; AS向用户 C发送修改媒体请求消息;用户 C向 AS发送修改媒体响应消息; 实现用户 B与用户 C之间的通话。
第四种场景: 釆用松耦合的方式和端到端控制的方式的场景。
此时, 实现呼叫转接业务具体包括以下内容:
针对釆用松耦合的方式而言, AGCF用户挂机后 , AGCF通过向 AS发 送更换呼叫请求消息, 触发 AGCF与 AS之间釆用松耦合的方式实现交互。
针对端到端控制的方式而言, AS通过向非 AGCF用户发送更换呼叫请 求消息, 触发端到端控制的方式; 非 AGCF用户在端到端控制的方式下实 现媒体协商, 并实现非 AGCF用户之间的通话。
在这种场景下包括两种情况, 以下分别阐述。
第一种情况: AGCF用户具体为用户 A, 非 AGCF用户具体为用户 B 和用户 C; 通话态转接的情况。 此时, 实现呼叫转接业务进一步包括以下 内容:
针对釆用松耦合的方式而言, 用户 C摘机, 向 AS发送应答响应消息 后, 用户 A挂机, AGCF释放 A终端; AGCF向 AS发送更换呼叫请求消 息; AS向 AGCF发送更换呼叫请求接收消息; AS向 AGCF发送更换呼叫 开始消息; AS在用户 A与用户 C之间的呼叫中, 向 AGCF发送释放呼叫 消息; AS向 AGCF发送更换呼叫成功消息; AGCF在用户 A与用户 B之 间的呼叫中, 向 AS发送释放呼叫消息。
针对端到端控制的方式而言, AS向用户 B发送更换呼叫请求消息; 用 户 B向 AS发送更换呼叫请求接收消息;用户 B向 AS发送更换呼叫开始消 息; 用户 B向 AS发送会话邀请消息; AS向用户 C发送会话邀请消息; 用 户 C向 AS发送应答响应消息; AS向用户 B发送应答响应消息; 实现用户 B与用户 C之间的通话。
第二种情况: AGCF用户具体为用户 A, 非 AGCF用户具体为用户 B 和用户 C; 振铃态转接的情况。 此时, 实现呼叫转接业务进一步包括以下 内容:
针对釆用松耦合的方式而言,用户 A挂机, AGCF释放 A终端; AGCF 向 AS发送更换呼叫请求消息; AS向 AGCF发送更换呼叫请求接收消息; AS向 AGCF发送更换呼叫开始消息; AS在用户 A与用户 C之间的呼叫中, 向 AGCF发送释放呼叫消息; AS向 AGCF发送更换呼叫成功消息; AGCF 在用户 A与用户 B之间的呼叫中, 向 AS发送释放呼叫消息。 针对端到端控制的方式而言, 用户 C摘机, 向 AS发送应答响应消息 后, AS向用户 B发送更换呼叫请求消息; 用户 B向 AS发送更换呼叫请求 接收消息; 用户 B向 AS发送更换呼叫开始消息; 用户 B向 AS发送会话邀 请消息; AS向用户 C发送会话邀请消息;用户 C向 AS发送应答响应消息; AS向用户 B发送应答响应消息; 实现用户 B与用户 C之间的通话。
以下对本发明举例阐述。
实施例一: AS控制的紧耦合方式的振铃态转接的情况。 如图 1所示, 本实施例的实现流程包括以下步骤:
步骤 101、 AGCF的用户 A与用户 B按现有技术已经建立通话。
这里, 用户 B不要求为 AGCF用户, 可以为非 AGCF用户。 以下各实 施例涉及到的有关用户 B的描述也是这里的意思, 以下不做赞述。
步骤 102、 用户 A拍叉簧, 给 AGCF发确认(NOTIFY ) 消息。
步骤 103、 AGCF为用户 A的叉簧事件创建新的呼叫,向 AS发起呼叫。 该呼叫具体为 SIP协议中的会话邀请 ( invite ) 消息。
步骤 104、 AS向用户 A的对端, 即用户 B发修改媒体请求消息, 设置 合适的媒体状态, 将用户 B保持。 该消息具体为 SIP协议中的 re-invite消 息。
此后, 可以由 AS控制媒体服务器给用户 A放拨号音, 让用户 A输入 用户 C的号码;也可以由 AS给 AGCF回号码不全的失败响应消息,让 AGCF 控制媒体服务器给用户 A放拨号音, 让用户 A输入用户 C的号码, 并创建 新的呼叫。
步骤 105、 AS向用户 C发起呼叫, 为 SIP协议中的 invite消息。
步骤 106-107、 用户 C通过 AS给用户回振铃响应消息, 为 SIP协议中 的 18x消息。 用户 A会听到回铃音或其它提示音。
步骤 108-109、 用户 A挂机, AGCF释放 A终端。 步骤 110-111、 AGCF在用户 A-用户 B, 用户 A-用户 C对话中分别向 AS发释放呼叫消息, 为 SIP协议中的 BYE消息, AS在用户 A-用户 B, 用 户 A-用户 C对话中会释放响应消息, 为 SIP协议中的 200 OK消息。 此后, AS可以根据自身逻辑和不同客户的需要,通过媒体协商等方式让用户 B听 回铃音或其它提示音, 并等待接收用户 C的应答响应。
步骤 112、 C用户摘机,向 AS发应答响应消息,为 SIP协议中的 200 OK 消息。
步骤 113-118、 用户 B和用户 C在 AS的控制下实现媒体协商, 并实现 用户 B和用户 C的通话。
实施例二: 端到端的紧耦合方式的通话态转接的情况。 如图 2 所示, 本实施例的实现流程包括以下步骤:
步骤 201、 AGCF的用户 A与用户 B按现有技术已经建立通话。
步骤 202、 用户 A拍叉簧, 给 AGCF发 NOTIFY消息。
步骤 203、 AGCF为用户 A的叉簧事件创建新的呼叫,向 AS发起呼叫。 该呼叫具体为 SIP协议中的 invite消息。
步骤 204、 AS向用户 A的对端, 即用户 B发修改媒体请求消息, 设置 合适的媒体状态, 将用户 B保持。 该消息为 SIP协议中的 re-invite消息。
此后, 可以由 AS控制媒体服务器给用户 A放拨号音, 让用户 A输入 用户 C的号码;也可以由 AS给 AGCF回号码不全的失败响应消息,让 AGCF 控制媒体服务器给用户 A放拨号音, 让用户 A输入用户 C的号码, 并创建 新的呼叫。
步骤 205、 AS向用户 C发起呼叫, 为 SIP协议中的 invite消息。
步骤 206-207、用户 C摘机,其它临时响应在此忽略,通过 AS给 AGCF 发应答响应消息, 为 SIP协议中的 200 OK消息。 用户 A和用户 C实现通 话。 步骤 208-209、 用户 A挂机, AGCF释放 A终端。
步骤 210-211、 AGCF在用户 A-用户 B, 用户 A-用户 C对话中分别向 AS发释放呼叫消息, 为 SIP协议中的 BYE消息, AS在用户 A-用户 B, 用 户 A-用户 C对话中会释放响应消息, 为 SIP协议中的 200 OK消息。
步骤 212、 AS给用户 B发更换呼叫请求消息 , 为 SIP协议中的 REFER 消息。
步骤 213、用户 B给 AS回更换呼叫请求接收消息,为 SIP协议中的 200 类消息, 比如 202等。
步骤 214、用户 B给 AS发更换呼叫开始消息,为 SIP协议中的 NOTIFY 消息, 里面携带 100 trying指示。 AS会给用户 B回 200 OK响应, 在流程 图中省略。
步骤 215-216、 用户 B通过 AS向用户 C发会话邀请消息, 为 SIP协议 中的 invite消息。
步骤 217-218、 用户 C通过 AS向 B发应答响应消息, 为 SIP协议中的 200 OK消息, 实现 B-C通话。
步骤 219、 用户 C在收到应答响应确认消息后, 向 AS发释放用户 A- 用户 C对话消息, 为 SIP协议中的 BYE消息, 释放用户 A-用户 C对话。
步骤 220、用户 B在收到应答响应消息后,向 AS发更换呼叫成功消息, 为 SIP协议的 NOTIFY消息, 里面携带 200 OK指示。
步骤 221、 AS在收到更换呼叫成功消息后, 在用户 A-用户 B对话中, 向用户 B发释放呼叫请求消息。
实施例三: AS控制的 耦合方式的通话态转接的情况。 如图 3所示, 本实施例的实现流程包括以下步骤:
步骤 301、 AGCF的用户 A与用户 B按现有技术已经建立通话。
步骤 302、 用户 A拍叉簧, 给 AGCF发 NOTIFY消息。 步骤 303-304、 AGCF通过 AS, 将用户 A的对端, 即用户 B保持, 为 SIP协议的 re-invite消息。 re-invite的响应消息 200 OK在流程图中省略。
步骤 305-306、 AGCF给用户 A放拨号提示音, 用户 A输入用户 C的 号码。
步骤 307-308、 AGCF为用户 A创建新的呼叫, 通过 AS呼叫用户 C , 为 SIP协议中的 invite消息。
步骤 309-310、 用户 C摘机, 通过 AS向用户 A发应答响应消息, 为 SIP协议中的 200 OK消息, 实现用户 A与用户 C通话。此前可能会有一些 临时响应消息, 在此忽略。
步骤 311-312、 用户 A挂机, AGCF释放 A终端。
步骤 313、 AGCF给 AS发更换呼叫请求消息, 为 SIP协议中的 REFER 消息。
步骤 314、AS给 AGCF发更换呼叫开始消息,为 SIP协议中的 NOTIFY 消息, 携带 100 trying指示。 至于 AS回的更换呼叫请求接收消息, 为 SIP 协议中的 200类消息, 比如 202等, 在流程图中省略。
步骤 315-320、 AS发起用户 B和用户 C的媒体协商, 实现用户 B与用 户 C通话。
步骤 321、 AS通知 AGCF, 已经成功实现呼叫转接业务, 为 SIP协议 中的 NOTIFY消息, 携带 200 OK指示。
步骤 322、 AS在用户 A-用户 C呼叫中, 向 AGCF发 BYE, 释放用户
A与用户 C之间的对话。 至于 AGCF回的响应消息 200 OK在流程图中省 略。
步骤 323、 AGCF在用户 A-用户 B呼叫中, 向 AS发 BYE, 释放用户 A与用户 B之间的对话。 至于 AS回的响应消息 200 OK在流程图中省略。
实施例四: 端到端的松耦合方式的通话态转接的情况。 如图 4所示, 本实施例的实现流程包括以下步骤:
步骤 401、 AGCF的用户 A与用户 B按现有技术已经建立通话。
步骤 402、 用户 A拍叉簧, 给 AGCF发 NOTIFY消息。
步骤 403-404、 AGCF通过 AS, 将用户 A的对端, 即用户 B保持, 为 SIP协议的 re-invite消息。 re-invite的响应消息 200 OK在流程图中省略。
步骤 405-406、 AGCF给用户 A放拨号提示音, 用户 A输入用户 C的 号码。
步骤 407-408、 AGCF为用户 A创建新的呼叫 , 通过 AS呼叫用户 C , 为 SIP协议中的 invite消息。
步骤 409-410、 用户 C摘机, 通过 AS向用户 B发应答响应消息, 为
SIP协议中的 200 OK消息, 实现用户 B-用户 C通话。此前可能会有一些临 时响应消息, 在此忽略。
步骤 411-412、 用户 A挂机, AGCF释放 A终端。
步骤 413、 AGCF给 AS发更换呼叫请求消息 , 为 SIP协议中的 REFER 消息。
步骤 414、 AS给用户 B发更换呼叫请求消息, 为 SIP协议中的 REFER 消息。
步骤 415-416、 用户 B通过 AS向 AGCF回更换呼叫请求接受消息。 为 SIP协议中的 200类消息, 比如 202等。
步骤 417-418、 用户 B通过 AS向 AGCF发更换呼叫开始消息, 为 SIP 协议中的 NOTIFY消息, 里面携带 100 trying指示。 AGCF会通过 AS给用 户 B回 200 OK响应, 在流程图中省略。
步骤 419-420、 用户 B通过 AS向用户 C发会话邀请消息, 为 SIP协议 中的 invite消息。
步骤 421 -422、 用户 C通过 AS向用户 B发应答响应消息, 为 SIP协议 中的 200 OK消息, 实现用户 B-用户 C通话。
步骤 423-424、 用户 C在收到应答响应确认消息后, 通过 AS向 AGCF 发释放用户 A-用户 C对话消息, 为 SIP协议中的 BYE消息, 释放用户 A- 用户 C对话。
步骤 425-426、 用户 B在收到应答响应消息后, 会通过 AS给 AGCF发 更换呼叫成功消息, 为 SIP协议的 NOTIFY消息, 里面携带 200 OK指示。
步骤 427-428、 AGCF在收到更换呼叫成功消息后, 在用户 A-用户 B 对话中, 通过 AS向用户 B发释放呼叫请求消息。
实施例五: AS控制的松耦合方式的振铃态转接的情况。 如图 5所示, 本实施例的实现流程包括以下步骤:
步骤 501、 AGCF的用户 A与用户 B按现有技术已经建立通话。
步骤 502、 用户 A拍叉簧, 给 AGCF发 NOTIFY消息。
步骤 503-504、 AGCF通过 AS, 将用户 A的对端, 即用户 B保持, 为 SIP协议的 re-invite消息。 re-invite的响应消息 200 OK在流程图中省略。
步骤 505-506、 AGCF给用户 A放拨号提示音, 用户 A输入用户 C的 号码。
步骤 507-508、 AGCF为用户 A创建新的呼叫, 通过 AS呼叫用户 C , 为 SIP协议中的 invite消息。
步骤 509-510、 用户 C通过 AS给用户回振铃响应消息, 为 SIP协议中 的 18x消息。 用户 A会听到回铃音或其它提示音。
步骤 511-512、 用户 A挂机, AGCF释放 A终端。
步骤 513、 用户 A挂机, AGCF给 AS发更换呼叫请求消息, 为 SIP协 议中的 REFER消息。
步骤 514、 AS给 AGCF发更换呼叫请求接收消息,为 SIP协议中的 200 类消息, 比如 202消息。 此后, AS可以根据自身逻辑和不同客户的需要, 通过媒体协商等方式让用户 B听回铃音或其它提示音, 并等待接收用户 C 的应答响应。
步骤 515、用户 C摘机,向 AS发应答响应消息,为 SIP协议中的 200 OK 消息。
步骤 516、 AS给 AGCF发更换呼叫开始消息,为 SIP协议中的 NOTIFY 消息, 携带 100 trying指示。
步骤 517-522、 AS发起用户 B和用户 C的媒体协商, 实现用户 B与用 户 C之间的通话。
步骤 523、 AS通知 AGCF, 已经成功实现呼叫转接业务, 为 SIP协议 中的 NOTIFY消息, 携带 200 OK指示。
步骤 524、 AS在用户 A-用户 C呼叫中, 向 AGCF发 BYE, 释放用户 A与用户 B之间的对话。 至于 AGCF回的响应消息 200 OK在流程图中省 略。
步骤 525、 AGCF在用户 A-用户 B呼叫中, 向 AS发 BYE, 释放用户 A与用户 C之间的对话。 至于 AS回的响应消息 200 OK在流程图中省略。
实施例六: 端到端的松耦合方式的振铃态转接的情况。 如图 6所示, 本实施例的实现流程包括以下步骤:
步骤 601、 AGCF的用户 A与用户 B按现有技术已经建立通话。
步骤 602、 用户 A拍叉簧, 给 AGCF发 NOTIFY消息。
步骤 603-604、 AGCF通过 AS, 将用户 A的对端, 即用户 B保持, 为
SIP协议的 re-invite消息。 re-invite的响应消息 200 OK在流程图中省略。
步骤 605-606、 AGCF给用户 A放拨号提示音, 用户 A输入用户 C的 号码。
步骤 607-608、 AGCF为用户 A创建新的呼叫, 通过 AS呼叫用户 C , 为 SIP协议中的 invite消息。 步骤 609-610、 用户 C通过 AS给用户回振铃响应消息, 为 SIP协议中 的 18x消息。 用户 A会听到回铃音或其它提示音。
步骤 611-612、 用户 A挂机, AGCF释放 A终端。
步骤 613、 用户 A挂机, AGCF给 AS发更换呼叫请求消息, 为 SIP协 议中的 REFER消息。
步骤 614、 AS给 AGCF发更换呼叫请求接收消息,为 SIP协议中的 200 类消息, 比如 202消息。 此后, AS可以根据自身逻辑和不同客户的需要, 通过媒体协商等方式让用户 B听回铃音或其它提示音, 并等待接收用户 C 的应答响应。
步骤 615、用户 C摘机,向 AS发应答响应消息,为 SIP协议中的 200 OK 消息。
步骤 616、 AS给用户 B发更换呼叫请求消息, 为 SIP协议中的 REFER 消息。
步骤 617、用户 B 向 AS AGCF回更换呼叫请求接受消息。 为 SIP协议 中的 200类消息, 比如 202等。
步骤 618-619、 用户 B通过 AS向 AGCF发更换呼叫开始消息, 为 SIP 协议中的 NOTIFY消息, 里面携带 100 trying指示。 AGCF会通过 AS会给 用户 B回 200 OK响应, 在流程图中省略。
步骤 620-621、 用户 B通过 AS向用户 C发会话邀请消息, 为 SIP协议 中的 INVITE消息。
步骤 622-623、 用户 C通过 AS向 B发应答响应消息, 为 SIP协议中的 200 OK消息, 实现用户 B-用户 C通话。
步骤 624-625、 用户 C在收到应答响应确认消息后, 通过 AS向 AGCF 发释放 A-C对话消息, 为 SIP协议中的 BYE消息, 释放用户 A-用户 C对 话。 步骤 626-627、 用户 B在收到应答响应消息后, 会通过 AS给 AGCF发 更换呼叫成功消息, 为 SIP协议的 NOTIFY消息, 里面携带 200 OK指示。
步骤 628-629、 AGCF在收到更换呼叫成功消息后, 在用户 A-用户 B 对话中, 通过 AS向用户 B发释放呼叫请求消息。
这里需要说明的是, 上述仅为本发明的原理性说明, 所以:
一、 实施例中的流程仅仅为示意流程。
二、 实施例中的 AGCF、 AS网元及它们之间的消息, 主要是为了清楚 的表示实现 AGCF用户呼叫转接业务的思想。 在具体的实现中, 不局限于 这些网元和消息。
三、 对于各种流程中出现的异常流程或情况、 在可以的情况下某些消 息的先后顺序、 网元内部的具体实现并不做具体的限制。
四、本发明实施例中给出了端到端和 AS控制两种实现方式,但本不排 斥其它实现方式。
五、 本发明实施例中没有对呼叫中可能会涉及到的资源预留 ( precondition )、 媒体编解码格式转换 ( transcoding )、 早媒体授权 ( P-Early-Media )、 早媒体 ( early session )等给予描述, 在实际实现中应给 予相应考虑。
图 3、 图 5中涉及的 CSCF指呼叫会话控制功能, 其英文全称为: Call Session Control Function0 另, 需要指出的是: 文中多次涉及到的 AGCF用 户指: AGCF 所带的用户, 为转接呼叫的业务用户; 而涉及到的非 AGCF 用户指: 为转接呼叫的非业务用户, 不要求必须为 AGCF所带的用户, 当 然也可以为 AGCF所带的用户, 还可以为 PES网络中的任何用户。
一种 AGCF用户呼叫转接业务的实现系统, 该系统包括: 呼叫转接实 现单元, 用于 AGCF用户通过 AGCF接入 PES , 在 AGCF与 AS之间, 釆 用紧耦合的方式 /松耦合的方式; 在 AS与非 AGCF用户之间, 釆用 AS主 控的方式 /端到端控制的方式, 实现 AGCF用户的呼叫转接业务。 这里, 呼叫转接实现单元在不同场景下的具体实现不同, 以下分别阐 述。
第一种具体实现: 釆用紧耦合的方式和 AS主控的方式的场景下, 呼叫 转接实现单元, 进一步用于 AGCF用户挂机后, AGCF在 AGCF用户与非 AGCF用户的对话中, 向 AS发送释放呼叫消息, 并触发 AGCF与 AS之间 釆用紧耦合的方式实现交互。 AS通过向非 AGCF用户发送修改媒体请求消 息,触发 AS主控的方式;非 AGCF用户在 AS主控的方式下实现媒体协商, 并实现非 AGCF用户之间的通话。
第二种具体实现: 釆用紧耦合的方式和端到端控制的方式的场景下, 呼叫转接实现单元, 进一步用于 AGCF用户挂机后, AGCF在 AGCF用户 与非 AGCF用户的对话中, 向 AS发送释放呼叫消息, 并触发 AGCF与 AS 之间釆用紧耦合的方式实现交互。 AS通过向非 AGCF用户发送更换呼叫请 求消息, 触发端到端控制的方式; 非 AGCF用户在端到端控制的方式下实 现媒体协商, 并实现非 AGCF用户之间的通话。
第三种具体实现: 釆用^耦合的方式和 AS主控的方式的场景下, 呼叫 转接实现单元,进一步用于 AGCF用户挂机后, AGCF通过向 AS发送更换 呼叫请求消息, 触发 AGCF与 AS之间釆用松耦合的方式实现交互。 AS通 过向非 AGCF用户发送修改媒体请求消息,触发由 AS主控的方式;非 AGCF 用户在 AS主控的方式下实现媒体协商, 并实现非 AGCF用户之间的通话。
第四种具体实现: 釆用 ^耦合的方式和端到端控制的方式的场景下, 呼叫转接实现单元,进一步用于 AGCF用户挂机后, AGCF通过向 AS发送 更换呼叫请求消息, 触发 AGCF与 AS之间釆用松耦合的方式实现交互。 AS通过向非 AGCF用户发送更换呼叫请求消息, 触发端到端控制的方式; 非 AGCF用户在端到端控制的方式下实现媒体协商, 并实现非 AGCF用户 之间的通话。
以上所述, 仅为本发明的较佳实施例而已, 并非用于限定本发明的保 护范围。

Claims

权利要求书
1、一种接入网关控制功能用户呼叫转接业务的实现方法,其特征在于, 该方法包括: 接入网关控制功能( AGCF )用户通过 AGCF接入公用交换电 话网 /综合业务数字网的仿真子系统( PES )后,在 AGCF与应用服务器( AS ) 之间, 釆用紧耦合的方式 /松耦合的方式; 在 AS与非 AGCF用户之间, 釆 用 AS主控的方式 /端到端控制的方式, 实现 AGCF用户的呼叫转接业务。
2、 根据权利要求 1所述的方法, 其特征在于, 釆用所述紧耦合的方式 和所述 AS主控的方式实现所述呼叫转接业务包括:
AGCF用户挂机后, AGCF在 AGCF用户与非 AGCF用户的对话中, 向 AS发送释放呼叫消息,并触发 AGCF与 AS之间釆用紧耦合的方式实现 交互;
AS通过向非 AGCF用户发送修改媒体请求消息,触发 AS主控的方式; 非 AGCF用户在 AS主控的方式下实现媒体协商, 并实现非 AGCF用户之 间的通话。
3、 根据权利要求 2所述的方法, 其特征在于, AGCF用户为用户 A, 非 AGCF用户为用户 B和用户 C; 在振铃态转接的情况下, 实现所述呼叫 转接业务进一步包括:
用户 A挂机, AGCF释放 A终端; AGCF在用户 A与用户 B、 用户 A 与用户 C之间的对话中分别向 AS发送释放呼叫消息; AS在用户 A与用户 用户 C摘机, 向 AS发送应答响应消息后, AS向用户 C发送修改媒体 请求消息; 用户 C向 AS发送修改媒体响应消息; AS向用户 B发送修改媒 体请求消息; 用户 B向 AS发送修改媒体响应消息; AS向用户 C发送修改 媒体请求消息; 用户 C向 AS发送修改媒体响应消息; 实现用户 B与用户 C之间的通话; 或者, AGCF用户为用户 A, 非 AGCF用户为用户 B和用户 C; 在通 话态转接的情况下, 实现所述呼叫转接业务进一步包括:
用户 C摘机, 向 AS发送应答响应消息后, 用户 A挂机, AGCF释放 A终端; AGCF在用户 A与用户 B、 用户 A与用户 C之间的对话中分别向 AS发送释放呼叫消息; AS在用户 A与用户 B、 用户 A与用户 C之间的对 话中分别向 AGCF发送释放响应消息;
AS向用户 C发送修改媒体请求消息; 用户 C向 AS发送修改媒体响应 消息; AS向用户 B发送修改媒体请求消息; 用户 B向 AS发送修改媒体响 应消息; AS向用户 C发送修改媒体请求消息; 用户 C向 AS发送修改媒体 响应消息; 实现用户 B与用户 C之间的通话。
4、 根据权利要求 1所述的方法, 其特征在于, 釆用所述紧耦合的方式 和所述端到端控制的方式实现所述呼叫转接业务包括:
AGCF用户挂机后, AGCF在 AGCF用户与非 AGCF用户的对话中, 向 AS发送释放呼叫消息,并触发 AGCF与 AS之间釆用紧耦合的方式实现 交互;
AS通过向非 AGCF用户发送更换呼叫请求消息,触发端到端控制的方 式; 非 AGCF用户在端到端控制的方式下实现媒体协商, 并实现非 AGCF 用户之间的通话。
5、 根据权利要求 4所述的方法, 其特征在于, AGCF用户为用户 A, 非 AGCF用户为用户 B和用户 C; 在通话态转接的情况下, 实现所述呼叫 转接业务进一步包括:
用户 C摘机, 向 AS发送应答响应消息后, 用户 A挂机, AGCF释放 A终端; AGCF在用户 A与用户 B、 用户 A与用户 C之间的对话中分别向 AS发送释放呼叫消息; AS在用户 A与用户 B、 用户 A与用户 C之间的对 话中分别向 AGCF发送释放响应消息; AS向用户 B发送更换呼叫请求消息; 用户 B向 AS发送更换呼叫请求 接收消息; 用户 B向 AS发送更换呼叫开始消息; 用户 B向 AS发送会话邀 请消息; AS向用户 C发送会话邀请消息;用户 C向 AS发送应答响应消息; AS向用户 B发送应答响应消息; 实现用户 B与用户 C之间的通话;
或者, AGCF用户为用户 A, 非 AGCF用户为用户 B和用户 C; 在振 铃态转接的情况下, 实现所述呼叫转接业务进一步包括:
用户 A挂机, AGCF释放 A终端; AGCF在用户 A与用户 B、 用户 A 与用户 C之间的对话中分别向 AS发送释放呼叫消息; AS在用户 A与用户 用户 C摘机, 向 AS发送应答响应消息后, AS向用户 B发送更换呼叫 请求消息; 用户 B向 AS发送更换呼叫请求接收消息; 用户 B向 AS发送更 换呼叫开始消息; 用户 B向 AS发送会话邀请消息; AS向用户 C发送会话 邀请消息; 用户 C向 AS发送应答响应消息; AS向用户 B发送应答响应消 息; 实现用户 B与用户 C之间的通话。
6、 根据权利要求 1所述的方法, 其特征在于, 釆用所述松耦合的方式 和所述 AS主控的方式实现所述呼叫转接业务包括:
AGCF用户挂机后, AGCF通过向 AS发送更换呼叫请求消息, 触发 AGCF与 AS之间釆用松耦合的方式实现交互;
AS通过向非 AGCF用户发送修改媒体请求消息, 触发由 AS主控的方 式; 非 AGCF用户在 AS主控的方式下实现媒体协商, 并实现非 AGCF用 户之间的通话。
7、 根据权利要求 6所述的方法, 其特征在于, AGCF用户为用户 A, 非 AGCF用户为用户 B和用户 C; 在通话态转接的情况下, 实现所述呼叫 转接业务进一步包括:
用户 C摘机, 向 AS发送应答响应消息后, 用户 A挂机, AGCF释放 A终端; AGCF向 AS发送更换呼叫请求消息; AS向 AGCF发送更换呼叫 开始消息; AS向 AGCF发送更换呼叫成功消息; AS在用户 A与用户 C之 间的呼叫中, 向 AGCF发送释放呼叫消息; AGCF在用户 A与用户 B之间 的呼叫中, 向 AS发送释放呼叫消息;
AS向用户 C发送修改媒体请求消息; 用户 C向 AS发送修改媒体响应 消息; AS向用户 B发送修改媒体请求消息; 用户 B向 AS发送修改媒体响 应消息; AS向用户 C发送修改媒体请求消息; 用户 C向 AS发送修改媒体 响应消息; 实现用户 B与用户 C之间的通话;
或者, AGCF用户为用户 A, 非 AGCF用户为用户 B和用户 C; 在振 铃态转接的情况下, 实现所述呼叫转接业务进一步包括:
用户 A挂机, AGCF释放 A终端; AGCF向 AS发送更换呼叫请求消 息; AS向 AGCF发送更换呼叫请求接收消息; AS向 AGCF发送更换呼叫 开始消息; AS向 AGCF发送更换呼叫成功消息; AS在用户 A与用户 C之 间的呼叫中, 向 AGCF发送释放呼叫消息; AGCF在用户 A与用户 B之间 的呼叫中, 向 AS发送释放呼叫消息;
用户 C摘机, 向 AS发送应答响应消息后, AS向用户 C发送修改媒体 请求消息; 用户 C向 AS发送修改媒体响应消息; AS向用户 B发送修改媒 体请求消息; 用户 B向 AS发送修改媒体响应消息; AS向用户 C发送修改 媒体请求消息; 用户 C向 AS发送修改媒体响应消息; 实现用户 B与用户 C之间的通话。
8、 根据权利要求 1所述的方法, 其特征在于, 釆用所述松耦合的方式 和所述端到端控制的方式实现所述呼叫转接业务包括:
AGCF用户挂机后, AGCF通过向 AS发送更换呼叫请求消息, 触发 AGCF与 AS之间釆用松耦合的方式实现交互;
AS通过向非 AGCF用户发送更换呼叫请求消息,触发端到端控制的方 式; 非 AGCF用户在端到端控制的方式下实现媒体协商, 并实现非 AGCF 用户之间的通话。
9、 根据权利要求 8所述的方法, 其特征在于, AGCF用户为用户 A, 非 AGCF用户为用户 B和用户 C; 在通话态转接的情况下, 实现所述呼叫 转接业务进一步包括:
用户 C摘机, 向 AS发送应答响应消息后, 用户 A挂机, AGCF释放 A终端; AGCF向 AS发送更换呼叫请求消息; AS向 AGCF发送更换呼叫 请求接收消息; AS向 AGCF发送更换呼叫开始消息; AS在用户 A与用户 C之间的呼叫中, 向 AGCF发送释放呼叫消息; AS向 AGCF发送更换呼叫 成功消息; AGCF在用户 A与用户 B之间的呼叫中, 向 AS发送释放呼叫 消息;
AS向用户 B发送更换呼叫请求消息; 用户 B向 AS发送更换呼叫请求 接收消息; 用户 B向 AS发送更换呼叫开始消息; 用户 B向 AS发送会话邀 请消息; AS向用户 C发送会话邀请消息;用户 C向 AS发送应答响应消息; AS向用户 B发送应答响应消息; 实现用户 B与用户 C之间的通话;
或者, AGCF用户为用户 A, 非 AGCF用户为用户 B和用户 C; 在振 铃态转接的情况下, 实现所述呼叫转接业务进一步包括:
用户 A挂机, AGCF释放 A终端; AGCF向 AS发送更换呼叫请求消 息; AS向 AGCF发送更换呼叫请求接收消息; AS向 AGCF发送更换呼叫 开始消息; AS在用户 A与用户 C之间的呼叫中, 向 AGCF发送释放呼叫 消息; AS向 AGCF发送更换呼叫成功消息; AGCF在用户 A与用户 B之 间的呼叫中, 向 AS发送释放呼叫消息;
用户 C摘机, 向 AS发送应答响应消息后, AS向用户 B发送更换呼叫 请求消息; 用户 B向 AS发送更换呼叫请求接收消息; 用户 B向 AS发送更 换呼叫开始消息; 用户 B向 AS发送会话邀请消息; AS向用户 C发送会话 邀请消息; 用户 C向 AS发送应答响应消息; AS向用户 B发送应答响应消 息; 实现用户 B与用户 C之间的通话。
10、 一种接入网关控制功能用户呼叫转接业务的实现系统, 其特征在 于,该系统包括:呼叫转接实现单元,用于 AGCF用户通过 AGCF接入 PES , 在 AGCF与 AS之间,釆用紧耦合的方式 /松耦合的方式;在 AS与非 AGCF 用户之间, 釆用 AS主控的方式 /端到端控制的方式, 实现 AGCF用户的呼 叫转接业务。
11、 根据权利要求 10所述的系统, 其特征在于, 所述呼叫转接实现单 元, 进一步用于釆用所述紧耦合的方式和所述 AS主控的方式下, AGCF用 户挂机后, AGCF在 AGCF用户与非 AGCF用户的对话中, 向 AS发送释 放呼叫消息, 并触发 AGCF与 AS之间釆用紧耦合的方式实现交互;
AS通过向非 AGCF用户发送修改媒体请求消息,触发 AS主控的方式; 非 AGCF用户在 AS主控的方式下实现媒体协商, 并实现非 AGCF用户之 间的通话。
12、 根据权利要求 10所述的系统, 其特征在于, 所述呼叫转接实现单 元, 进一步用于所述釆用紧耦合的方式和所述端到端控制的方式下, AGCF 用户挂机后, AGCF在 AGCF用户与非 AGCF用户的对话中, 向 AS发送 释放呼叫消息, 并触发 AGCF与 AS之间釆用紧耦合的方式实现交互;
AS通过向非 AGCF用户发送更换呼叫请求消息,触发端到端控制的方 式; 非 AGCF用户在端到端控制的方式下实现媒体协商, 并实现非 AGCF 用户之间的通话。
13、 根据权利要求 10所述的系统, 其特征在于, 所述呼叫转接实现单 元, 进一步用于釆用所述松耦合的方式和所述 AS主控的方式下, AGCF用 户挂机后, AGCF通过向 AS发送更换呼叫请求消息, 触发 AGCF与 AS之 间釆用^ ^耦合的方式实现交互; AS通过向非 AGCF用户发送修改媒体请求消息, 触发由 AS主控的方 式; 非 AGCF用户在 AS主控的方式下实现媒体协商, 并实现非 AGCF用 户之间的通话。
14、 根据权利要求 10所述的系统, 其特征在于, 所述呼叫转接实现单 元, 进一步用于釆用所述^^耦合的方式和所述端到端控制的方式下, AGCF 用户挂机后, AGCF通过向 AS发送更换呼叫请求消息, 触发 AGCF与 AS 之间釆用松耦合的方式实现交互;
AS通过向非 AGCF用户发送更换呼叫请求消息,触发端到端控制的方 式; 非 AGCF用户在端到端控制的方式下实现媒体协商, 并实现非 AGCF 用户之间的通话。
PCT/CN2010/075235 2009-09-22 2010-07-19 接入网关控制功能用户呼叫转接业务的实现方法及系统 WO2011035638A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
AU2010297787A AU2010297787B2 (en) 2009-09-22 2010-07-19 Implementation method and system of call forwarding service for access gateway control function users
EP10818332.8A EP2466819B1 (en) 2009-09-22 2010-07-19 Implementation method and system of call forwarding service for access gateway control function users
RU2012112486/08A RU2491740C1 (ru) 2009-09-22 2010-07-19 Способ и система предоставления услуги передачи вызова для абонента функции управления шлюзом доступа
MX2012003429A MX2012003429A (es) 2009-09-22 2010-07-19 Metodo y sistema para realizar servicio de transferencia de comunicaciones para usuario de funcion de control de portal de acceso.
BR112012006349A BR112012006349A2 (pt) 2009-09-22 2010-07-19 método para executar um serviço de transferência de comunicação para um usuário de função de controle de porta de acesso (agcf - access gateway control function) e sistema para executar um serviço de transferencia de comunicação para um usuário da função de controle de porta de acesso
IN2275DEN2012 IN2012DN02275A (zh) 2009-09-22 2010-07-19
US13/258,376 US8559613B2 (en) 2009-09-22 2010-07-19 Method and system for performing communication transfer service for access gateway control function user
HK12109405.6A HK1168702A1 (zh) 2009-09-22 2012-09-24 接入網關控制功能用戶呼叫轉接業務的實現方法及系統

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910093867.5A CN102025686B (zh) 2009-09-22 2009-09-22 接入网关控制功能用户呼叫转接业务的实现方法及系统
CN200910093867.5 2009-09-22

Publications (1)

Publication Number Publication Date
WO2011035638A1 true WO2011035638A1 (zh) 2011-03-31

Family

ID=43795362

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/075235 WO2011035638A1 (zh) 2009-09-22 2010-07-19 接入网关控制功能用户呼叫转接业务的实现方法及系统

Country Status (10)

Country Link
US (1) US8559613B2 (zh)
EP (1) EP2466819B1 (zh)
CN (1) CN102025686B (zh)
AU (1) AU2010297787B2 (zh)
BR (1) BR112012006349A2 (zh)
HK (1) HK1168702A1 (zh)
IN (1) IN2012DN02275A (zh)
MX (1) MX2012003429A (zh)
RU (1) RU2491740C1 (zh)
WO (1) WO2011035638A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102761929B (zh) * 2012-07-09 2017-12-29 中兴通讯股份有限公司 Ims会话切换实现方法和接入切换控制功能装置
CN103475648B (zh) * 2013-08-29 2017-12-19 上海斐讯数据通信技术有限公司 基于sip协议的呼叫盲转方法及呼叫盲转系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070177603A1 (en) * 2006-02-02 2007-08-02 Calme James A Flexible SIP profile for mixed networks
CN101217600A (zh) * 2007-01-05 2008-07-09 中兴通讯股份有限公司 询问转接业务方法和装置

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1387589A1 (de) 2002-07-29 2004-02-04 Siemens Aktiengesellschaft Media Gateway zur Bereitstellung der PSTN/ISDN Dienste in Netzwerken der nächsten Generation
CN100531194C (zh) * 2004-09-07 2009-08-19 华为技术有限公司 分组域业务信号处理系统及其方法
CN100379316C (zh) 2005-07-05 2008-04-02 华为技术有限公司 传统终端用户接入ims域的实现方法及系统
CN100426825C (zh) * 2005-08-04 2008-10-15 华为技术有限公司 实现紧急业务检测的方法、系统及接入控制功能实体
CN100450207C (zh) 2005-09-30 2009-01-07 华为技术有限公司 电路域用户接入ims域的方法及通信系统
CN100428755C (zh) * 2006-01-24 2008-10-22 华为技术有限公司 一种电路域终端实现业务自助的方法及实体
US20080049648A1 (en) 2006-08-28 2008-02-28 Motorola, Inc. Method and apparatus for policy management for an internet protocol multimedia subsystem based wireless communication system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070177603A1 (en) * 2006-02-02 2007-08-02 Calme James A Flexible SIP profile for mixed networks
CN101217600A (zh) * 2007-01-05 2008-07-09 中兴通讯股份有限公司 询问转接业务方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ETSITS 183 043 V2.3.1 (ETSI), 31 March 2009 (2009-03-31), XP014044342 *

Also Published As

Publication number Publication date
IN2012DN02275A (zh) 2015-08-21
RU2491740C1 (ru) 2013-08-27
AU2010297787B2 (en) 2013-09-26
HK1168702A1 (zh) 2013-01-04
CN102025686B (zh) 2014-06-11
BR112012006349A2 (pt) 2017-07-25
US8559613B2 (en) 2013-10-15
EP2466819A4 (en) 2013-09-11
EP2466819A1 (en) 2012-06-20
AU2010297787A1 (en) 2012-04-19
EP2466819B1 (en) 2014-09-24
MX2012003429A (es) 2012-04-30
CN102025686A (zh) 2011-04-20
US20120201369A1 (en) 2012-08-09

Similar Documents

Publication Publication Date Title
WO2009059559A1 (fr) Procédé de commande d'appel de session multimédia et serveur d'application
EP1965592A1 (en) Call continuity among user terminals
WO2006128356A1 (fr) Procede d'ecoute par le terminal utilisateur appelant du signal du terminal utilisateur appele en cas d'interconnexion
WO2012113237A1 (zh) 一种实现多媒体彩铃业务的方法、系统及装置
WO2011017889A1 (zh) 一种多媒体会议的实现方法及系统
WO2012113193A1 (zh) 一种多方通话业务的实现方法和系统
JP5551786B2 (ja) 会話期間中にマルチメディア呼出し音を再生する方法、サーバおよび端末デバイス
WO2009155824A1 (zh) 一种彩铃、彩像业务的实现方法及系统
JP5593304B2 (ja) 呼を終了する方法及びボイスオーバーip端末
WO2009086758A1 (zh) 一种在线彩铃或彩像业务的实现方法
EP1959608A1 (en) A method, a application server and a system for implementing the third party control service
WO2007093116A1 (fr) Procédé et système de fourniture de service de simulation et entité adaptative de signalisation d'accès
WO2009124512A1 (zh) 控制早媒体播放的实现方法
WO2011153752A1 (zh) 在ctd业务中实现呼叫转接的方法、系统及应用服务器
WO2010091567A1 (zh) 一种点击拨号业务到多媒体会议业务的切换系统及方法
JP2011526441A (ja) Imsネットワーク内でカスタマイズされたビデオサービスを実現するための方法およびネットワークユニット
CN101448046B (zh) 一种实现单对话彩铃业务的呼叫建立方法
WO2011035638A1 (zh) 接入网关控制功能用户呼叫转接业务的实现方法及系统
WO2011023041A1 (zh) 一种指示终端媒体类型的呼叫方法及系统
EP2544473B1 (en) Service control method and apparatus
CN101459872B (zh) 单对话彩铃彩像业务在应答后更新媒体的方法
WO2013091310A1 (zh) 终端实现呼叫等待的方法、装置和系统
WO2017000481A1 (zh) 语音通话的拨号方法和装置
WO2008049371A1 (fr) Procédé et système pour transférer un événement de service
CN101459665A (zh) 早媒体信息播放控制方法

Legal Events

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

Ref document number: 10818332

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 13258376

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2010818332

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2275/DELNP/2012

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2010297787

Country of ref document: AU

Ref document number: MX/A/2012/003429

Country of ref document: MX

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2012112486

Country of ref document: RU

ENP Entry into the national phase

Ref document number: 2010297787

Country of ref document: AU

Date of ref document: 20100719

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: A20120558

Country of ref document: BY

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112012006349

Country of ref document: BR

REG Reference to national code

Ref country code: BR

Ref legal event code: B01E

Ref document number: 112012006349

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112012006349

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20120321