WO2009018752A1 - Procédé et dispositif de réalisation d'un service de rappel - Google Patents

Procédé et dispositif de réalisation d'un service de rappel Download PDF

Info

Publication number
WO2009018752A1
WO2009018752A1 PCT/CN2008/071800 CN2008071800W WO2009018752A1 WO 2009018752 A1 WO2009018752 A1 WO 2009018752A1 CN 2008071800 W CN2008071800 W CN 2008071800W WO 2009018752 A1 WO2009018752 A1 WO 2009018752A1
Authority
WO
WIPO (PCT)
Prior art keywords
callback
callback service
service
user
called
Prior art date
Application number
PCT/CN2008/071800
Other languages
English (en)
Chinese (zh)
Inventor
Youzhu Shi
Qing Zhou
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2009018752A1 publication Critical patent/WO2009018752A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42195—Arrangements for calling back a calling subscriber
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/12—Arrangements 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/1205—Arrangements 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/1225—Details of core network interconnection arrangements
    • H04M7/123—Details of core network interconnection arrangements where the packet-switched network is an Internet Protocol Multimedia System-type network

Definitions

  • the present invention relates to the field of network communication technologies, and in particular, to a technology for implementing a callback service.
  • the network in addition to providing call services to users, can also provide supplementary service services in the call service process, and the corresponding supplementary service services include Completion of
  • CCBS Busy Callback Service
  • CCNR Call Completion on No
  • SIP Session Initiation Protocol
  • the callback service is specifically used to complete the call after the call is unsuccessful.
  • the CCBS can make the called user busy and receive the call in the called user state. It becomes unsatisfactory to complete the call connection without the calling user re-initiating a new call; the CCNR enables the called user to receive the call after the called user is activated, and the call is completed after the called user activates. To avoid re-initiating a new call.
  • the callback service such as CCBS and CCNR is specifically implemented in the calling network where the calling user is located, that is, the triggering of the callback service is performed by the network device close to the calling user.
  • Implement callback service is specifically implemented in the calling network where the calling user is located, that is, the triggering of the callback service is performed by the network device close to the calling user.
  • the embodiment of the present invention provides a method and apparatus for implementing a callback service, so that the implementation of the callback service can be controlled by the called network, thereby expanding the scenario in which the callback service can be applied.
  • An embodiment of the present invention provides a method for implementing a callback service, including:
  • the callback service is activated to establish communication between the calling user and the called user.
  • An embodiment of the present invention provides an apparatus for implementing a callback service, including:
  • the device includes a callback service control unit, and the unit is configured to determine, according to the callback service triggering policy, if the communication with the called user cannot be connected after receiving the call initiated by the calling user. After the callback condition is invoked, the callback service is started; after the callback activation policy is determined according to the callback service triggering policy, the callback service is activated to establish communication between the calling user and the called user; The device that implements the callback service exists in the called network where the called user is located.
  • the implementation process of the callback service is controlled by the device in the called network where the called user is located, and The device in the called network can more easily obtain more comprehensive information of the called user, so that the applicable scenario of the corresponding callback service is greatly increased.
  • the embodiment of the present invention can effectively improve the call completion rate, improve the user experience, and increase user satisfaction.
  • FIG. 1 is a schematic structural diagram of an implementation of an apparatus according to an embodiment of the present disclosure
  • FIG. 2 is a schematic structural diagram of a callback service control unit in an apparatus according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a process of processing a callback service according to an embodiment of the present invention.
  • the embodiment of the present invention provides a callback service implementation scheme for controlling and managing a callback service in a called network where a called user is located, so that the callback service can be busy, no answer, and shut down at the called user.
  • the network is inaccessible or triggered by any situation such as roaming to actively limit incoming calls, thereby expanding the range in which the callback service can be applied.
  • the corresponding process of implementing the callback service may include: First, after the called network where the called user is located receives the call initiated by the calling user, if the called user cannot be connected and the called user The communication between the callbacks is started after the callback initiation condition is determined according to the callback service triggering policy; after the callback network determines that the callback activation condition is met according to the callback service triggering policy, the communication is activated.
  • the callback service establishes communication between the calling user and the called user. Therefore, the implementation of the callback service can be controlled and managed in the called network, and the performance of the callback service is improved.
  • the callback service triggering policy includes a user subscription status and a callback service triggering condition
  • the user subscription status specifically includes the data signed by the user, and determines whether the callback service is activated for the user according to the data signed by the user.
  • the called network may provide a default subscription to open the callback service by default, or The user opens the callback service to the business hall, or opens the corresponding callback service by telephone or network;
  • the callback service may include at least one of the following: busy callback service, no answer callback service, shutdown ⁇ callback service (ie, unregistered callback service), roaming/callback service, terminal unavailable callback service or presence status callback service;
  • the callback service trigger condition includes at least one of the following: a default callback service trigger condition, and a configured callback service trigger condition, where:
  • the default callback service triggering condition is a callback service triggering condition that is directly generated by the user after the signing of the contract, and may specifically but not limited to include one or more of the following:
  • Busy callback when the called user's status is busy, the callback service is started, and the called user is turned from busy to idle, and the callback is activated.
  • the presence status callback when the called user's presence status enters a specific presentation state, receives the call, initiates a callback service, and activates the callback after the called user migrates out of the specific presentation state;
  • the configured callback service triggering condition is a callback service triggering condition generated after the user signs the contract, after the data is configured, modified, deleted, activated, and deactivated; for example, the user activates Or deactivate the default callback service trigger condition; for example, the user modifies the timer period of the callback service in the unanswered callback service; for example, the user sets the roaming or non-roaming state in the roaming callback service.
  • the callback service is activated; for example, the user sets a callback service in a specific presentation state, such as a "meeting" state, and activates the callback service in a specific presentation state, such as other than "lunch”. Status, activate callback service;
  • At least one of the following processing modes may be specifically used in the called network:
  • Method 1 Determine whether the callback start condition is satisfied according to the failure response code
  • Method 2 According to the local logic state, determine whether the callback start condition is satisfied, such as the status of the checker; if the callback service is started after the timer is exceeded;
  • Method 3 determining, according to the state of the called user, whether the callback activation condition is satisfied; the state of the called user includes: at least one of a registration state, a session state, a roaming state, and a presence state;
  • Method 4 Determine whether the callback activation condition is met according to the calling user attribute, and the calling user attribute may include a calling party number, a media type, and the like.
  • At least one of the following processing modes may be specifically used in the called network:
  • Method 1 Determine whether the callback activation condition is satisfied according to the local state of the buffer; if the callback service is activated after the timer is exceeded;
  • Method 2 Determine whether the callback activation condition is satisfied according to the state of the called user; the status packet of the called user Included: at least one of a registration status, a session state, a roaming state, and a rendering state;
  • whether the callback service is initiated according to the obtained intention of the calling user may be determined, so that the calling user can participate in the callback. Call the business during the startup control process.
  • the callback service is started to notify the called party that the called network is started, and the called network may send a notification message to the calling network.
  • a mechanism for deleting the initiated callback service may be set in the called network, and the corresponding mechanism is The implementation manner may be: determining whether the activated callback service is activated within a predetermined time zone, and if not activated, deleting (or stopping) the initiated callback service; or receiving the deletion sent by the called user After the initiated callback service indication, the initiated callback service is deleted (or stopped).
  • the setting may be set in the called network, and set to After a predetermined number of callback services are activated, the new callback service is no longer activated.
  • the method further includes: after determining, according to the callback service triggering policy, that the callback activation condition is met, according to the obtained calling user.
  • the status determines whether the callback service is activated, so that whether the callback service is activated according to the situation of the calling user, and the success rate of the activated callback service is improved, for example, after the status of the calling user is known, the calling user cannot In the case of being connected, the callback service is no longer activated, thereby avoiding unnecessary occupation of network resources, and also improving the success rate of the callback service after activation.
  • the embodiment of the present invention further provides a device for implementing a callback service, where the device may be specifically configured in a network device of a called network where the called user is located, or may be independently set in the called network. As shown in FIG. 1 and FIG.
  • the device for implementing the callback service mainly includes a callback service control unit, and the unit is configured to provide a callback service logic control function, which is a host execution environment of the callback service, and may be specifically used in
  • the callback service is started after determining that the callback activation condition is met according to the callback service triggering policy; After the service triggering policy determines that the callback activation condition is met, the callback service is activated to establish communication between the calling user and the called user.
  • the callback service includes but is not limited to: a busy callback service Any one or more of the service, the unanswered callback service, the unrecognizable callback service, the unregistered callback service, the roaming callback service, and the presence status callback service.
  • the callback service control unit may further include a callback service initiation assistance determining unit, configured to perform at least one of a failure response code, a local logic state, and a state of the called user according to the obtained callback service.
  • the item determines whether to initiate the callback service.
  • the callback initiation assistance determining unit may further determine whether to initiate the callback service according to the obtained intention of the calling user, so that the calling user may also participate in the startup process of the callback service. .
  • the callback service initiation assistance determining unit may further be configured to communicate with the called terminal status management unit, to obtain status information of the called user from the called terminal status management unit.
  • the callback service control unit may further include a callback service management unit, configured to determine whether the initiated callback service is activated within a predetermined time zone, and if not activated, delete the callback service.
  • the initiated callback service or receiving an indication sent by the called user to delete the initiated callback service, and deleting the initiated callback service; and the unit can control to delete (or stop) the initiated callback service. , thus facilitating the management of callback services.
  • the callback service management unit may further include a callback service control unit, configured to control, after starting a predetermined number of callback services, no longer initiate a new callback service. To avoid starting too many callback services in the network, affecting the communication performance of the network.
  • a callback service control unit configured to control, after starting a predetermined number of callback services, no longer initiate a new callback service. To avoid starting too many callback services in the network, affecting the communication performance of the network.
  • the callback service control unit in the apparatus provided by the embodiment of the present invention may further include a callback service activation assistance determining unit, configured to determine whether to activate according to at least one of the states of the called user according to the obtained local logic state. Call back business.
  • the callback service activation assistance judging unit may determine whether to activate the callback service according to the obtained status of the calling user, so that it is possible to determine whether to activate the callback service according to the situation of the calling user, and improve the activated callback service. Success rate.
  • the callback service activation assistance determining unit may further be in communication with the calling terminal status management unit, configured to obtain status information of the calling user managed and maintained by the calling user status management unit.
  • the callback service activation assistance determining unit may further be in communication with the called terminal status management unit, configured to obtain, from the called user status management unit, the status of the called user that is managed and maintained by the called user status management unit.
  • the callback service control unit may further include a callback policy management unit, configured to manage a callback service triggering policy, and used to send the callback service management unit to the callback
  • the service initiation assistance judging unit or the callback service activation assistance judging unit provides a callback service triggering policy; the callback policy management unit can access the user database (such as the HSS home domain user server, the USPF user service profile, etc.) to obtain the user. At least one of the subscription status and the default callback service triggering condition.
  • the callback policy management unit may specifically, but not limited to, implement any of the following processing operations.
  • the callback service control unit needs to communicate with the session control unit in the called network, and the session control unit is specifically configured to provide functions such as packet network session routing, for example,
  • the function of the session control unit may be specifically implemented by Call Session Control in the IMS network.
  • CSCF Call Session Control Function
  • P-CSCF Proxy Call Session Control Function
  • S-CSCF Server Call Session Control Function
  • I-CSCF Noation Call Session Control Function
  • the protocol used by the E1 interface between the session control unit and the callback service control unit may be SIP.
  • the session control unit forwards the session request of the user terminal in the autonomous calling network to the callback service control unit; and forwards the session request from the callback service control unit to the user.
  • the user terminal that initiates the call includes a legacy terminal and a packet terminal; if the user terminal is a SIP terminal, it can directly access the session control unit, that is, the protocol used by the E2 interface of the SIP terminal is SIP. Therefore, it can directly communicate with the session control unit that provides the SIP interface; if the user terminal is a legacy circuit terminal or a packet non-SIP terminal, the user terminal of the user needs to access through the SIP user agent node, for example, when the user terminal is a traditional Circuit terminal ISDN (Integrated Services Digital Network) terminal ⁇ , which can access the session control unit through AGCF (access gateway control function) or VGW (video gateway), E1 interface between SIP user agent node and session control unit Protocol is SIP, user terminal and SIP
  • the protocol used by the interface between user agent nodes is the DSS1 (Digital Subscriber Signal System 1) protocol.
  • the callback policy data configuration related to the callback service may be specifically performed on the callback service control unit, for example, the callback initiation condition and the callback activation condition included in the callback service triggering policy are configured. Wait.
  • the corresponding configuration operation process may be implemented by using a WEB service, or may be implemented by a user terminal; wherein, when the callback policy data configuration operation is performed by the user terminal, the session control unit may specifically route to the callback service control.
  • the unit for example, activates the CCBS operation by dialing the service code, and can also directly route to the callback service control unit, for example, through the Ut interface (the interface between the user terminal and the callback service control unit) on the callback service control unit.
  • Step 1 After receiving the incoming call, the callback service control unit in the called network determines whether the callback initiation condition in the callback service triggering policy is met according to the pre-configured callback service triggering policy and the current call information. If it is determined that the callback activation condition is met, the corresponding callback service is started;
  • the callback initiation condition includes: the incoming call is not accepted, and the reason that the incoming call is not accepted is consistent with the callback service triggering policy; optionally, the callback initiation condition may further include The interaction is performed to determine whether to initiate the callback service, for example, the callback service is initiated after the calling user agrees, and the foregoing interaction may be implemented by using an IVR (interactive voice response) mode or a signaling method;
  • IVR interactive voice response
  • the callback service triggering policy may include: a user subscription status and a callback service trigger condition
  • the callback service triggering condition includes a default callback service triggering condition and a configured callback service triggering condition
  • the default callback service triggering condition refers to a callback service triggering condition directly generated by the user after signing the contract, and includes a callback initiation condition for determining whether to initiate the callback service and determining whether to perform the callback.
  • the callback activation condition of the callback activation condition may be specifically, but not limited to, including at least one of the following:
  • the callback service triggering condition of the configuration refers to a callback service triggering condition generated after the user signs the contract by data configuration setting, modification, deletion, activation or deactivation operation; for example, busy callback, no response back Calling, shutdown, callback, terminal callback or roaming, callback, etc., after the user signs the corresponding callback service, it is not immediately valid, but needs to be activated by the user to take effect; the presence callback, the user can configure Callback in a particular presentation state, such as the "rest" state; for the configured callback service trigger condition, the corresponding callback activation condition requires, in addition to the conditions described in (1) - (6) above, Meet the conditions for user activation;
  • the process of determining whether the callback activation condition is met may be: determining whether the content is satisfied according to the failure response code; or determining whether the content is satisfied according to local logic (such as a buffer); or, according to the user Status (such as registration status, session status, roaming status, presentation status, etc.) to determine whether it is satisfied;
  • Step 2 After the callback service is started, the callback service control unit saves the information related to the call, for example, the address of the calling user and the like;
  • the callback service control unit may further send the notification information to the calling network.
  • the callback service control unit may also start the callback service control device, and if the callback is not initiated after the callback service control device is exceeded, stopping the callback service;
  • the callback service control unit may further maintain a queue, and save the initiated callback service information.
  • the callback service queue reaches a maximum value, the control no longer starts a new callback service
  • the called user can perform an interaction operation with the callback service control unit.
  • Step 3 After the callback activation condition is met, that is, the callback activation condition in the callback service trigger policy is satisfied ⁇
  • [88] judge whether the callback activation condition is met according to the callback service triggering policy and the current status of the called user.
  • the implementation manner of determining whether the callback service triggering policy is satisfied may be: according to local logic (such as a fixed buffer) to determine whether it is satisfied; or, according to the state of the called user (such as registration state, session state, roaming state, Presenting state, etc.) to determine whether it is satisfied;
  • the corresponding callback activation condition can be any one or more of the following:
  • the callback service control unit can also subscribe to the status event package of the called user, such as subscribing the called user's Reg-event Package and Dialog-event Package (The session status event package, etc.; the receiving subscription may be the called user terminal, a third party device, such as a presence server, and the like.
  • the callback activation condition may further include a status of the calling user, so as to determine whether to initiate a callback according to the status of the calling user; wherein, in order to obtain the status of the calling UE
  • the callback service control unit can also subscribe to the caller's dialog event packet: the receiving subscription can be the calling AS (access server), the calling S-CSCF, or the calling user.
  • the callback activation condition may further include an interaction operation between the callback service control unit and the calling user, so as to determine whether to initiate a callback according to the interaction with the calling user.
  • the method for the callback service control unit to initiate the callback may be a method controlled by a third party, or may be a method for sending a REFER to the calling user or the called user; wherein, the third party control method
  • the callback service control unit sends a call request to the calling user and the called user to establish a session between the calling user and the called user.
  • Another method is to send the REF ER request message to the callback service control unit.
  • the calling user and carrying the identifier of the called user in the REFER request, requesting the calling user to send a call request to the called user; or the callback service control unit sends a REFER request message to the called user, and carries the main in the REFER request
  • the identity of the calling user requesting the called user to send a call request to the calling user.
  • the calling user A in the calling network initiates a call to the called user B in the called network, and the called user B signs the callback service, and sets and activates the callback service trigger. Policy, triggers the callback service when the called user is busy.
  • the process of implementing the callback service may include:
  • Step 1 The calling user A sends a call, that is, the calling network sends an initial session message INVITE message to the session control unit where the called user B is located;
  • Step 2 the session control unit forwards the INVITE message to the callback service control unit;
  • Step 3 the callback service control unit forwards the INVITE message to the session control unit;
  • Step 4 the session control unit forwards the INVITE message to the called user;
  • Step 5 the session control unit receives the 486 returned by the called user B.
  • Busy (busy) response that is, the user busy message, indicating that the called user B is currently unable to accept the session request;
  • Step 6 the session control unit forwards the 486 Busy message to the callback service control unit;
  • Step 7 the callback service control unit receives the above 486
  • Busy responds to determine whether the callback start condition is met. When the callback start condition is satisfied, the callback service is started.
  • the callback service control unit can determine whether the callback activation condition is satisfied by the received response code; for example, in this embodiment, it can be received according to 486.
  • the Busy response message initiates the busy callback service.
  • the callback service control unit receives the 503 response (the called party is unable to respond)
  • the unreachable forward service can be initiated;
  • the callback service control unit receives the incoming call Restricting the 603 response of the service AS (rejecting the response) ⁇ , the callback service after the incoming call restriction can be activated;
  • the callback service control unit can also use other conditions to determine whether the callback activation condition is satisfied, for example Start the callback service by obtaining the status of the called user. For example, the called user status is busy, and the busy callback service is started.
  • the unanswered callback timer is started, and the fixed caller is activated. After , starting the unanswered callback service; if judging the registration status of the called user, starting the unregistered callback service if the called user is not registered;
  • the callback service control unit may further initiate a busy callback service by using an interaction with the calling network, and if the calling user agrees, specifically, the IVR mode may be adopted.
  • the callback service control unit completes the call connection with the calling user A, and then prompts the calling user to be busy by the IVR voice, and is willing to accept the callback service of the called user B.
  • the calling user A can specifically pass The button selection accepts or does not accept, so that the callback service control unit knows the desire of the calling user A; the callback service control unit can also complete the interaction with the calling network through signaling, for example, returning to the calling network.
  • the request header field of the P-CCBS-Request (CCBS service request) is carried in the 183 Linyi response, and the calling network is requested to accept the callback service of the called user B, and the calling network can respond to the 183 response in the above 183.
  • the message carries the P-CCBS-Response response parameter, indicating that the callback service of the called user B is accepted or rejected; the above request and ringing Parameters can also be carried by the SIP message body carries.
  • the callback service control unit may save the current call related information, for example, save the address of the calling user A for subsequent callback; correspondingly, the callback service control The unit can maintain a queue for storing the called callback service information. When the callback service queue reaches the maximum value, the callback service is no longer activated.
  • the callback service control unit may further send a notification message to the calling network, indicating that the corresponding callback service of the calling user has been started, for example, the callback service control unit sends a 486 busy response.
  • the message is sent to the calling network, and the P-CCBS-Notification (CCBS Service Notification) header field is carried in the 486 response message, indicating that the busy callback service has been started; the callback service control unit can also pass the message body. Subscribing to an event package, etc., to send a notification to the calling network that the callback service has been started;
  • the callback service control unit can also start the fixed buffer, and if the busy callback service is still not activated after the fixed buffer is exceeded, the callback service is stopped; Alternatively, after the callback service is started, the called user can stop the callback service by using an interaction operation with the callback service control unit, for example, the called user passes the SIP mode (such as through a header field, a message body, or an event package).
  • Step 8, 9 the callback service control unit subscribes to the status of the calling user
  • the callback service control unit may specifically determine whether to activate the callback by using the status of the calling user.
  • the callback service control unit may subscribe to the session event packet of the calling user to obtain The status of the calling user, specifically the status of the calling party from the calling AS, the calling S-CSCF or the calling user;
  • Step 10 the session state of the calling user A changes to idle
  • Step 11 the calling network informs the callback service control unit of the information of the change of the status of the calling user A through the NOTIFY message.
  • Step 12 After receiving the information of the state change of the calling user A, the callback service control unit returns an acknowledgement message to the calling network;
  • Step 13 after the callback service control unit receives the NOTIFY notification, it determines whether the callback activation condition is satisfied.
  • the corresponding manner of determining whether the callback activation condition is satisfied may be a combination of any one or more of the following:
  • the callback service control unit can determine whether the callback activation condition is satisfied by the status of the caller in the received NOTIFY notification; for example, in this embodiment, specifically, according to the received NOTIF Y Notifying the idle state in the message to initiate a busy callback;
  • the callback service control unit may also subscribe to the status of the called user to obtain the status of the called user, or the callback service control unit may also obtain the manner by other means, such as periodic query.
  • the status of the called user as a basis for judging whether the callback activation condition is met; taking the status of the subscribed called user as an example, for the busy callback service, the callback service control unit needs to subscribe to the called user.
  • the callback service control unit needs to subscribe to the roaming state of the called user, for the conference ⁇ Callback service, callback service control unit needs to subscribe to the presentation status of the called user.
  • the callback service control unit may specifically subscribe the called user to the called user's state, or, in an actual application, the callback service control unit may also provide a third-party device, such as a presence server. To subscribe to the status of the called user;
  • the callback service control unit can determine whether the callback activation condition is satisfied according to the decision to initiate a callback, for example, when the callback service control unit receives If the called user is idle, a busy callback or no answer callback may be initiated; if the called user registration notification is received, an unregistered callback may be initiated, when the callback service control unit receives the called user from entering The notification of the home domain may initiate a roaming callback.
  • the callback service control unit receives the notification of the presence status of the called user, the conference call may be initiated.
  • the callback service control unit may further determine whether to activate the callback according to the interaction with the called user and according to the instruction of the called user; for example, the called user state may be performed by the IVR method.
  • the callback service control unit initiates a call to the called user B.
  • the called user B is prompted by the IVR voice to select whether to activate the callback service, so as to facilitate The selection of the called user B determines whether the callback service is activated.
  • the callback service control unit can also complete the interaction with the called user B by means of signaling, for example, by sending a callback activation request to the called party through the header field, the message body or the event packet. Calling user B, the called user B selects whether to activate the callback;
  • Steps 14, 15, and 16 the callback service control unit determines that the callback service needs to be activated, and then initiates a call request to the calling user A and the called user B, respectively, and implements the calling by means of a third party control. a session between user A and called user B;
  • the session between the calling user A and the called user B may also be implemented in other manners, thereby implementing activation of the callback, for example:
  • the callback service control unit sends a REFER (consultation) message to the calling user A, carries the address of the called user B in the Refer-To header field, and initiates a call by the calling user A. Request to call User B, to implement callback;
  • the callback service control unit may also send a REFER message to the called user B, carry the address of the calling user A in the Refer-To header field, and initiate a call request to the calling user A by the called user B. To achieve callback.
  • the implementation of the callback service provided by the embodiment of the present invention can control the implementation of the callback service in the called network, thereby facilitating the implementation of the callback service; for example, when the called user is in the The called user can realize the callback when the called user is busy, does not answer, shuts down, the network is inaccessible, or the situation is actively restricted due to roaming. Therefore, for the user, the implementation of the embodiment of the present invention can greatly improve the user experience and improve user satisfaction, and for the operator, the session connection rate can be improved to bring more operating income.
  • the calling user can also control the implementation process of the callback service, so that the implementation of the callback service is more reliable.
  • various processing procedures for starting the callback service and activating the callback service are further provided, so that the reliability of the callback service can be further improved.

Abstract

La présente invention concerne un procédé et un dispositif de réalisation d'un service de rappel, comprenant principalement les étapes suivantes : en premier lieu, après que le réseau appelé dans lequel la partie appelée se trouve a reçu l'appel provenant de la partie appelante, il lance le service de rappel s'il remplit la condition d'initiation de rappel selon la stratégie de déclenchement du service de rappel, si la communication entre le réseau appelé et la partie appelée échoue. Ensuite, lorsque le réseau appelé remplit la condition d'activation de rappel selon la stratégie de déclenchement du service de rappel, le service de rappel est activé afin d'établir la communication entre les parties appelante et appelée. Les équipements du réseau appelé dans lequel la partie appelée se trouve peuvent surveiller la procédure de mise en œuvre du service de rappel en utilisant les modes de réalisation de la présente invention. Les informations de la partie appelée peuvent ainsi être obtenues de manière facile et intégrale, et donc à l'étape suivante, le champ d'application du service de rappel est nettement accru.
PCT/CN2008/071800 2007-08-07 2008-07-29 Procédé et dispositif de réalisation d'un service de rappel WO2009018752A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710120033.X 2007-08-07
CNA200710120033XA CN101365016A (zh) 2007-08-07 2007-08-07 实现回叫业务的方法及装置

Publications (1)

Publication Number Publication Date
WO2009018752A1 true WO2009018752A1 (fr) 2009-02-12

Family

ID=40340956

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/071800 WO2009018752A1 (fr) 2007-08-07 2008-07-29 Procédé et dispositif de réalisation d'un service de rappel

Country Status (2)

Country Link
CN (1) CN101365016A (fr)
WO (1) WO2009018752A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105101128A (zh) * 2014-05-05 2015-11-25 中国移动通信集团北京有限公司 一种发送挂机快信的方法及装置

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101827339A (zh) * 2010-03-02 2010-09-08 中兴通讯股份有限公司 一种通信终端主叫和被叫角色互换的方法及系统
CN102148903B (zh) * 2010-10-22 2013-10-09 华为软件技术有限公司 遇忙回叫的方法和装置
CN102833693B (zh) * 2011-06-14 2018-03-13 中兴通讯股份有限公司 一种呼叫处理方法、装置及系统
CN103856639B (zh) * 2012-11-29 2017-01-25 中国移动通信集团天津有限公司 一种回呼预约取消方法、相关设备及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6169795B1 (en) * 1998-03-30 2001-01-02 International Business Machines Corporation Internet telephony callback system and method of operation
CN1295752A (zh) * 1997-12-31 2001-05-16 阿尔卡塔尔美国公司 有回叫能力的电话系统和用于将消息的接收方与主叫用户连接起来的方法
CN1929519A (zh) * 2006-08-16 2007-03-14 华为技术有限公司 一种遇忙提醒业务的实现方法及系统
CN1984187A (zh) * 2006-04-24 2007-06-20 华为技术有限公司 一种限定回叫业务触发的方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1295752A (zh) * 1997-12-31 2001-05-16 阿尔卡塔尔美国公司 有回叫能力的电话系统和用于将消息的接收方与主叫用户连接起来的方法
US6169795B1 (en) * 1998-03-30 2001-01-02 International Business Machines Corporation Internet telephony callback system and method of operation
CN1984187A (zh) * 2006-04-24 2007-06-20 华为技术有限公司 一种限定回叫业务触发的方法和系统
CN1929519A (zh) * 2006-08-16 2007-03-14 华为技术有限公司 一种遇忙提醒业务的实现方法及系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105101128A (zh) * 2014-05-05 2015-11-25 中国移动通信集团北京有限公司 一种发送挂机快信的方法及装置

Also Published As

Publication number Publication date
CN101365016A (zh) 2009-02-11

Similar Documents

Publication Publication Date Title
US8744054B2 (en) Method and system for automatic call redialing
US10044553B2 (en) Media resource reservation request failure handling for voice over mobile wireless network
EP2461558B1 (fr) Procédé, système et appareil pour la mise en oeuvre d'un service multimédia de tonalité de retour d'appel
EP2112799A1 (fr) Gestion de l'intégrité de service dans un système basé sur IMS
WO2007098713A1 (fr) Procédé et système d'appel d'urgence
EP2104305A1 (fr) Gestion de service d'appel dans un système basé sur IMS
US20060153353A1 (en) Intelligent secondary call treatment for advanced calling scenarios
EP1874016A1 (fr) Procede pour realiser un signal de rappel dans un systeme de communication
JP2004350260A (ja) 途絶えた呼の継続
WO2008028416A1 (fr) Procédé de commande de transfert intercellulaire d'appel et système de communication mettant en oeuvre ce procédé et dispositif utilisateur
WO2008154842A1 (fr) Procédé et dispositif pour fournir un service de transfert d'appel pour les utilisateurs
WO2007137485A1 (fr) Procédés et systèmes pour mise en oeuvre de transfert d'appel et réseau domestique de terminal d'utilisateur
WO2010045812A1 (fr) Procédé, appareil et système pour commutation d’appel
US20080273671A1 (en) Method, system and application server for preventing crosstalk of color ring back tone
WO2008086690A1 (fr) Procédé de services de déviation de requête et dispositif correspondant
US20150222753A1 (en) Method for Handling a Call from a Calling Subscriber Towards a Called Subscriber
WO2010022648A1 (fr) Procédé et dispositif de lecture de tonalité de retour d'appel personnalisée multimédia et système correspondant
US20030123474A1 (en) System and method for call completion on busy subscribers
WO2009018752A1 (fr) Procédé et dispositif de réalisation d'un service de rappel
WO2008000134A1 (fr) Méthode et dispositif de transmission d'un message de demande dans un système multimédia
JP2011526441A (ja) Ｉｍｓネットワーク内でカスタマイズされたビデオサービスを実現するための方法およびネットワークユニット
US20070004388A1 (en) System, method, and network elements for providing a service in a communication network
EP2173085B1 (fr) Procédé permettant de faire suivre un état occupé décidé par l'utilisateur
WO2007124662A1 (fr) Procédé, système, dispositif d'abonnement, dispositif d'information de commande centrale d'abonnement
WO2008110110A1 (fr) Procédé et système de fourniture de service de sous-système multimédia 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: 08783793

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08783793

Country of ref document: EP

Kind code of ref document: A1