WO2008106853A1 - Procédé destiné à notifier une file d'attente basé sur le message et serveur d'application correspondant - Google Patents

Procédé destiné à notifier une file d'attente basé sur le message et serveur d'application correspondant Download PDF

Info

Publication number
WO2008106853A1
WO2008106853A1 PCT/CN2007/071069 CN2007071069W WO2008106853A1 WO 2008106853 A1 WO2008106853 A1 WO 2008106853A1 CN 2007071069 W CN2007071069 W CN 2007071069W WO 2008106853 A1 WO2008106853 A1 WO 2008106853A1
Authority
WO
WIPO (PCT)
Prior art keywords
queue
waiting
terminal
calling
message
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2007/071069
Other languages
English (en)
French (fr)
Inventor
Jianming Zhou
Congxing Ouyang
Jinglei Liu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
Original Assignee
China Mobile Communications Corp
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 China Mobile Communications Corp filed Critical China Mobile Communications Corp
Priority to US12/530,140 priority Critical patent/US8848896B2/en
Publication of WO2008106853A1 publication Critical patent/WO2008106853A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management

Definitions

  • the invention relates to a notification method and an application server, in particular to a notification method and an application server for providing real-time waiting information of a called terminal, belonging to the field of voice calls. Background technique
  • the called party usually sets up the call center. According to different information service areas, the call center assigns different service access numbers.
  • the calling party (the calling party, the calling party or the calling party) sends a corresponding call request according to its own needs, thereby establishing a call with the corresponding called party on the call center.
  • the existing voice call service mainly adopts the M/M/1/1 single service window loss system queuing model, and M is a probability distribution, that is, a negative exponential distribution.
  • M is a probability distribution, that is, a negative exponential distribution.
  • the first M in the M/M/1/1 single service window loss queuing model refers to the probability distribution of the time interval T in which different calling users initiate calls in succession to satisfy the negative exponential distribution with the parameter " ⁇ ";
  • the probability distribution of the talk time ⁇ consumed by a single user satisfies the negative exponential distribution with the parameter " ⁇ ";
  • the first 1 refers to the number of service windows, that is, a called The user only talks to one calling user at the same time; the second one refers to the maximum queue capacity, including the users who are serving and queuing, that is, only one calling user is allowed to be served at the same time.
  • this call queuing method automatically determines the called user's private team when determining that the called user is in the "busy" state. The queue is queued; when the called user is idle, the caller connects to the called party. Compared with the calling mode of the first M/M/ 1/ 1 single service window loss queuing model, this call queuing method can automatically be placed in the private state of the called user when the called user is in the "busy" state.
  • the idle or busy status information of the called terminal is provided, and the called party may be broadcasted to the calling terminal by the voice when the call is not established with the called terminal.
  • the calling user 1, the calling user 2, and the calling user 5 both want to establish a call connection with the called user A, if At this time, the called user A is communicating with the calling user 1, and the remaining calling users 2-5 need to wait.
  • the calling user 2-5 knows that the called user A is communicating, the called party is in a busy state. However, it is impossible to judge whether it is necessary to continue waiting.
  • the waiting time will be wasted; if a certain number of callers need to wait, there are not many people, such as the calling user 2, but because they do not know The number of people waiting in front will be wrongly canceled, which may affect the needs of the calling user.
  • the purpose of the present invention is to provide a message-based waiting queue notification method and a method for not waiting for a queue of a called terminal in the prior art, and failing to determine whether it is necessary to continue waiting when the called terminal is in a busy state.
  • the application server can timely know the current waiting status when calling the called terminal through the calling terminal of the present invention.
  • the present invention provides a message-based waiting queue notification method, including:
  • the calling terminal sends a call request to the called terminal
  • the application server forwards the call request sent by the calling terminal to the called terminal, and according to the called terminal
  • the response message returned by the terminal determines whether the called terminal is in an idle state
  • the application server adds the calling terminal to the waiting queue of the called terminal, and sends a waiting notification message including the waiting queue value corresponding to the calling terminal to the calling terminal;
  • the method further includes: when the calling terminal cancels the call request, deleting the calling terminal from the waiting queue of the called terminal, and performing a waiting queue for the called terminal Rearrangement; a wait notification message containing the wait queue value after rearrangement is respectively sent to all the calling terminals in the waiting queue queue that are originally arranged after the calling terminal.
  • the method further includes: analyzing the calling terminal, comparing with data stored in a blacklist of the called terminal, and if the calling terminal is recorded in the "blacklist", The step of forwarding the call request sent by the calling terminal to the called terminal is not performed.
  • the present invention further provides an application server, including: a call processing module, configured to complete a basic call processing transfer process between a calling terminal and a called terminal;
  • the response message discriminating module is connected to the call processing module, and configured to receive a response message returned by the called terminal, determine whether the called terminal is in an idle state, and establish a calling terminal by using a call processing module when the called terminal is in an idle state.
  • the connection of the called terminal; the queue processing module is connected to the response message discriminating module, and is configured to join the calling terminal to the waiting queue of the called terminal when the called terminal is in a busy state, and complete the called terminal Waiting for the calculation of the waiting queue value corresponding to all calling terminals in the queuing queue;
  • a storage module connected to the queue processing module, configured to store a waiting queue value corresponding to each calling terminal
  • the waiting message notification module is connected to the storage module and the response message discriminating module, and is configured to send, when the called terminal is in a busy state, a waiting notification message including a waiting queue value corresponding to the calling terminal to the calling terminal.
  • the invention provides a notification method for the calling terminal waiting queue value in the real-time voice call field and an application server. When the called terminal is busy, the waiting queue notification method and the application server proposed by the invention can accurately reach the calling terminal. Notifying the number of people waiting for the queue to be queued by the called terminal, how many users the calling terminal needs to wait before establishing a call connection with the called terminal, letting the calling terminal decide whether to continue waiting, avoiding wasting time, and the present invention also calls the calling party.
  • the terminal and the called terminal are analyzed in various situations during actual use, and different processing methods are adopted for various operations, such as different operations such as "blacklisting", canceling waiting, or halfway exiting, and the present invention also Examples of various notification methods for waiting for a notification message, such as by voice notification, short message notification, MMS notification, email notification, notification to another terminal bound to the calling terminal, or any combination thereof, to the primary
  • the terminal is called to perform the prompt of the current waiting queue value, which enriches the notification form.
  • Figure 1 shows the existing voice call M/M/ 1 / 1 single service window loss system queuing model
  • FIG. 2 is a flowchart of Embodiment 1 of a message-based waiting queue notification method according to the present invention
  • FIG. 3 is a flowchart of a second embodiment of a message-based waiting queue notification method according to the present invention
  • FIG. 5 is a schematic diagram of an embodiment 1 of a waiting queue queue of a called terminal in a message-based waiting queue notification method according to the present invention
  • FIG. 6 is a schematic diagram of Embodiment 2 of a waiting queue of a called terminal in a message-based waiting queue notification method according to the present invention
  • FIG. 7 is a schematic diagram of Embodiment 3 of a waiting queue of a called terminal in a message-based waiting queue notification method according to the present invention.
  • FIG. 8 is a schematic diagram of Embodiment 4 of a message-based waiting queue notification method according to the present invention, in which a calling terminal waits for a queuing queue when canceling a waiting;
  • FIG. 8(b) is a schematic diagram of Embodiment 4 of a message-based waiting queue notification method in which a calling terminal cancels waiting and waits for a queued queue to be rearranged;
  • FIG. 9 is a schematic diagram of a fourth embodiment of a message-based waiting queue notification method according to the present invention.
  • FIG. 10 is a state flow diagram of an embodiment of an M/M/1 queuing model adopted by a message-based waiting queue notification method according to the present invention.
  • Embodiment 1 is a schematic diagram of Embodiment 1 of an application server according to the present invention.
  • Embodiment 2 is a schematic diagram of Embodiment 2 of an application server according to the present invention.
  • FIG. 13 is a schematic diagram of Embodiment 3 of an application server according to the present invention.
  • Embodiment 1 of a message-based waiting queue notification method according to the present invention. As shown in FIG. 2, this embodiment includes:
  • Step 1 The calling terminal sends a call request to the called terminal.
  • Step 2 The application server forwards the call request sent by the calling terminal to the called terminal, and receives the call.
  • Step 3 Determine whether the called terminal is in an idle state, if yes, go to step 5, otherwise go to step 4;
  • Step 4 Add the calling terminal to the waiting queue of the called terminal, and send a waiting notification message including the waiting queue value corresponding to the calling terminal to the calling terminal;
  • Step 5 The calling terminal and the called terminal directly establish a call connection.
  • the application server after receiving the call request, performs different judgments according to the response message returned by the called terminal. If the called terminal is in a busy state, the waiting queue value corresponding to the calling terminal is reversely notified. The message informs the calling terminal, so that the calling terminal can obtain the status of the called terminal and the number of users that need to wait in time according to the received reverse notification message.
  • the waiting notification message including the waiting queue value of the calling terminal may be another terminal bound to the calling terminal by voice notification, short message notification, MMS notification, mail notification, notification, or the above
  • the calling terminal performs a prompt for the current waiting queue value, for example: writing the waiting queue value corresponding to the calling terminal to the rendering state of the called terminal, and transmitting the value to the calling terminal.
  • the calling terminal can obtain the number of waiting to wait according to the waiting notification message, and judge whether it is necessary to continue waiting to avoid wasting time.
  • FIG. 3 it is a flowchart of Embodiment 2 of a message-based waiting queue notification method according to the present invention.
  • This embodiment is similar to FIG. 2, and the process is the same. The difference is that after sending the wait notification message in step 4, the method further includes:
  • Step 41 Determine whether the calling terminal continues the call request, that is, whether to continue waiting, if yes, go to step 4 3, otherwise go to step 42;
  • Step 42 After receiving the cancellation wait message sent by the calling terminal, the application server deletes the calling terminal from the waiting queue of the called terminal, and rearranges the waiting queue of the called terminal. Sending a wait notification message including the corresponding wait queue value after rearrangement to all the calling terminals that are originally arranged after the calling terminal;
  • Step 4 3 The calling terminal continues to wait.
  • the application server determines whether the calling terminal is ranked at the forefront of the waiting queue of the called terminal. If yes, proceed to step 44. Otherwise, continue to wait and continue to perform step 4 3;
  • Step 44 After the current call of the called terminal ends, establish a connection with the called terminal; Step 45. Determine whether the call ends, if yes, send a release connection message, otherwise continue to step 45.
  • the calling terminal After the calling terminal obtains the current waiting queue value, if the number of users before the calling terminal is too large, the calling terminal can immediately take measures, cancel the call, and avoid the wasted time.
  • the application server receives the cancel waiting message, it needs to reorder the waiting queue of the called terminal, delete the canceled calling terminal from the waiting queue, and notify other waiting users to rearrange after canceling the waiting caller. Waiting for the notification message afterwards.
  • FIG. 4 is a flowchart of Embodiment 3 of a message-based waiting queue notification method according to the present invention. Compared with FIG. 2 and FIG. 3, this embodiment adds some processing steps, specifically including the following steps:
  • Step 1 The calling terminal sends a call request to the called terminal.
  • Step. Determine whether the calling terminal belongs to the calling terminal that is prohibited from calling by the called terminal, for example, the data in the "blacklist" of the called terminal, and then returns a failure response message rejecting the call request to the calling terminal, ending the call. Otherwise, step 2 is performed;
  • blacklist is the common knowledge of the person skilled in the art, indicating the user data that the called terminal does not want to establish a call with, and the called terminal can add some user data that is prohibited from talking to the blacklist. In the middle, avoid waiting in the waiting queue of the called terminal;
  • Step 2 The application server forwards the call request sent by the calling terminal to the called terminal, and receives the response message returned by the called terminal.
  • Step 3 Determine whether the called terminal is in an idle state, if yes, go to step 5, otherwise go to step 4;
  • Step 4 Add the calling terminal to the waiting queue of the called terminal, and send a waiting notification message including the waiting queue value corresponding to the calling terminal to the calling terminal;
  • Step 41 Whether the calling terminal continues the call request, that is, whether to continue waiting, if yes, go to step 43, otherwise, go to step 42;
  • Step 42 After receiving the cancellation wait message sent by the calling terminal, the application server deletes the calling terminal from the waiting queue of the called terminal, and rearranges the waiting queue of the called terminal. Sending a wait notification message including the wait queue value after rearrangement to all the calling terminals that are originally arranged after the calling terminal, and ending;
  • Step 43 The calling terminal continues to wait, and the application server determines whether the calling terminal is in the front of the called terminal waiting for the queuing queue. If yes, go to step 44. Otherwise, proceed to step 43.
  • Step 44 Current call at the called terminal After the end, the connection with the called terminal is established;
  • Step 45 Determine whether the call is over, if yes, send a release connection message, go to step 53, otherwise continue to step 45;
  • Step 5 The calling terminal and the called terminal directly establish a call connection
  • Step 51 Determine whether the call is over, if yes, go to step 52, otherwise continue to step 51;
  • Step 52 Send a release connection message.
  • Step 53 When the application server receives the release connection message, the waiting queue queue of the called terminal is updated, and a waiting notification message is sent to all the calling terminals that are waiting for the calling terminal that is originally scheduled to end the call, the waiting The notification message includes the wait queue value corresponding to the calling terminal after updating the queue waiting for queue.
  • the calling terminal is allowed to establish a connection with the called terminal, which may be specifically: when the calling terminal is the called terminal waiting for the foremost calling terminal in the queuing queue, after the current call of the called terminal ends,
  • the called terminal establishes a connection.
  • the called terminal currently has 5 users in the waiting queue, indicating that there are 5 calling terminals A, B, C, D, and E all wishing to establish connection communication with the called terminal, when the calling terminals A, B, C, After D is removed from the waiting queue (with the called terminal ending or canceling the waiting), the calling terminal E is ranked at the foremost position of the waiting queue, and the calling terminal E allows the calling terminal D to end the call or cancel the waiting.
  • Establish a connection with the called terminal may be specifically: when the calling terminal is the called terminal waiting for the foremost calling terminal in the queuing queue, after the current call of the called terminal ends,
  • the called terminal establishes a connection.
  • the called terminal currently has 5 users in the waiting queue, indicating that there are 5 calling terminals
  • a user who determines whether the caller is called to be called such as a user in the blacklist, directly returns a rejection message, does not forward the call request, and also avoids the user in the blacklist.
  • Join the waiting queue to increase the number of queues, which will affect the subsequent work efficiency and calculation.
  • the calling terminal that prohibits the call is directly excluded from the waiting queue of the called terminal, and the subscribers joining the waiting queue are the users that the called terminal may connect, bringing a double experience to the calling and called terminals.
  • the present invention can be embodied in a variety of different forms.
  • the technical solutions of the present invention are exemplified above with reference to FIG. 2 to FIG. 4, which does not mean that the specific examples applied to the present invention can be limited to In a particular embodiment, those of ordinary skill in the art will appreciate that the specific embodiments provided above are just a few examples of various preferred uses, any when multiple calling calls are called the same, to the unsuccessful master
  • the method of returning a reverse waiting notification message containing the number of users that the calling party needs to wait for, and the manner of prompting the waiting queue value for the unconnected calling party should be within the scope of the technical solution claimed in the present invention.
  • the waiting queue of the called terminal (called the called party) is initially empty.
  • the pointer at the head position of the queue is represented as "head”
  • the pointer at the position of the tail of the queue is represented as "rear”
  • Each calling terminal (called the calling party) in the waiting queue has a position (hereinafter referred to as pos) attribute and a waiting (hereinafter called wait) attribute, and W[i] indicates the i-th calling in the queue.
  • pos to indicate the position of the i-th caller in the entire queue, using W[i].
  • the user W0 is selected from the head of the queue to establish a connection with the called party, and the call is made.
  • the calling W0 moves out of the queue, the head points to the next position, the head value adds 1 to 0, and the rear position does not. Change, the value is still 5.
  • the pointer head value of the queue header is 0, and the queue tail pointer has a rear value of 5.
  • each time a caller enters the rear value is 1, and each caller's head value is incremented by 1.
  • the application server receives the message to release the connection, the head value is incremented by 1, and the waiting number of the calling i at the foremost position of the queue is W[i].
  • a calling party Whenever a calling party enters the queue, it will receive a notification message containing the waiting queue value corresponding to the calling party.
  • the waiting queue value is 0, the calling party can talk with the called party; Waiting for a caller in the queuing queue to cancel the wait, the canceled caller is removed from the waiting queue, regardless of which position in the waiting queue is waiting for the canceled waiting call, the application server needs to The remaining callers after canceling the waiting caller respectively send a wait notification message containing the wait queue value after the update;
  • the feedback to the calling party includes a waiting notification message corresponding to the waiting queue value of the calling party, and the calling party receives only when the called party is in a busy state. Wait for the notification message.
  • the first calling user calls the called user, it is a normal connection process, the second calling user initiates the call and the called party has not finished talking with the first calling party.
  • the called party will feed back to the application server the information that the called party is busy.
  • the second calling user enters the queuing queue processing flow, and then sends a waiting notification message;
  • the called party When the called party ends a call with a certain caller, it will send a release connection message. At this time, it needs to update the called queue queue, and send it to all the calling terminals that are originally arranged after the caller whose call ends. A wait notification message for the updated wait queue value.
  • FIG. 9 is a schematic diagram of the fourth embodiment of the message-based waiting queue notification method according to the present invention.
  • FIG. 9 and FIG. 2 to FIG. Specifically include:
  • the calling terminal 1 sends a call request to the called terminal;
  • the application server learns that the calling terminal 1 is not in the blacklist of the called terminal, and forwards the call request of the calling terminal 1 to the called terminal;
  • the called terminal is idle, and a response message is returned, indicating that the called terminal can be connected;
  • the application server receives the return response message of the called terminal, starts the queuing queue processing (as shown in the embodiment of FIG. 5 - FIG. 8), and connects the calling terminal 1 and the called terminal, as shown in FIG.
  • the terminal 1 and the called terminal make a call;
  • the calling terminal i initiates a call request; as shown in FIG. 9;
  • the application server is queried to know that the calling terminal i is not in the blacklist of the called terminal, and then forwards the call request of the calling terminal i to the called terminal;
  • the called terminal is in a busy state, is talking to the calling terminal 1, and the called terminal returns a response message, indicating that the called terminal is busy;
  • the application server receives the return response message of the called terminal, starts the queuing queue processing, and sends a waiting notification message including the waiting queue value corresponding to the calling terminal i to the calling terminal i;
  • the called terminal is talking to the calling terminal 1 and returns a response message indicating that the called terminal is busy;
  • the application server receives the return response message of the called terminal, starts the queuing queue processing, and sends a waiting notification message including the waiting queue value corresponding to the calling terminal i + 1 to the calling terminal i + 1;
  • the calling terminal 1 ends the call with the called terminal, and the calling terminal 1 and the called terminal send a release connection message.
  • the application server After receiving the release connection message of the calling terminal 1 and the called terminal, the application server starts the queue queue processing, such as As shown in the embodiment of FIG. 6 and FIG. 7, the waiting queue queue is updated, and the waiting notification message including the waiting queue value corresponding to the calling terminal 2 after the update is sent to the calling terminal 2; the waiting queue value after the calling terminal 2 is updated. 0, can establish a connection with the called terminal, and make a call;
  • the application server sends a wait notification message containing a new waiting queue value to all the calling terminals behind the calling terminal 2, as shown in FIG. 9, resending the waiting notification message to the calling terminal i+1, the message including waiting Waiting queue value corresponding to the calling terminal i + 1 after the queue queue is updated;
  • K When waiting for a caller in the queue to cancel the waiting midway, the calling terminal i waits for a long time waiting in Figure 9 to cancel the waiting. , the user hangs up, sends a cancellation wait message;
  • the application server After receiving the message that the calling terminal i cancels the waiting, the application server starts the queuing queue processing, as shown in the embodiment of FIG. 8 ( a ) FIG. 8 ( b ), rearranging the waiting queue, after the calling terminal i
  • the calling terminal i + 1 that continues to wait sends a waiting notification message, which includes the waiting queue value corresponding to the calling terminal i+1 after waiting for the queuing queue to be rearranged.
  • the waiting notification message includes the waiting queue value corresponding to each calling terminal after the update, indicating that the number of currently waiting users has changed, and the calling terminal in the waiting state obtains the current number of users that need to wait in time.
  • the waiting queue notification method described in the present invention can be applied to a voice real-time service. After the calling terminal initiates a call request, the calling terminal can notify the state of the called terminal and the situation that the calling terminal needs to wait by voice, short message, etc., for example, : By voice announcement "There are 5 more users waiting in front of you to talk to XXX".
  • FIG. 10 is a state flow diagram of an embodiment of an M/M/1 queuing model adopted by the message-based waiting queue notification method of the present invention.
  • FIG. 10 is a queuing model adopted by the present invention.
  • FIG. 1 is a single service window loss queuing model in the existing voice call service, M/M/1 /1.
  • the existing M/M/1/1/ model refers to the called party only talking to one calling party at the same time, and the number of calling users being served plus the number of waiting calling users is 1. , that is, the maximum queue capacity is 1, and only one caller is allowed to be served at the same time.
  • the message queue calling model of the present invention adopts the M/M/1 single service window waiting system queuing model.
  • the waiting system queuing model there is no limit of the maximum queuing capacity, and the default is infinity, that is, an unlimited number of users are allowed to be queued.
  • "0" in the figure indicates that there are 0 users at this time; "1" indicates that there is one user, ...
  • the waiting queue notification method of the present invention is substantially different from the existing queuing call mechanism.
  • the number of queues is not limited to one, and the waiting queue value associated with the calling party can be notified to the calling user through the waiting message.
  • the waiting notification message used may be a voice notification, a short message notification, a multimedia message notification, an instant message notification, or even an email notification.
  • the caller is a fixed-line call, it can be notified by voice; the caller is a mobile phone, and can be notified by voice, SMS, MMS, etc.
  • voice SMS, MMS, etc.
  • SMS short message notification
  • MMS mobile phone
  • the call processing module in the embodiment is a module that is provided by the general application server, and is used to complete a basic call processing transfer process between the calling terminal and the called terminal.
  • This embodiment is related to the existing server. More than, it also includes:
  • the response message discriminating module is connected to the call processing module, and configured to receive a response message returned by the called terminal, determine whether the called terminal is in an idle state, and establish a master by the call processing module when the response message indicates that the called terminal is in an idle state. Calling the connection between the terminal and the called terminal; receiving a cancel waiting message sent when the calling terminal quits the waiting queue of the called terminal and/or a release connection message of the calling/called terminal when ending the call;
  • the queue processing module is connected to the response message discriminating module, and is configured to join the calling terminal to the waiting queue of the called terminal when the called terminal is in a busy state, and receive the release connection message forwarded by the response message discriminating module or Cancel the waiting message, update the waiting queue of the called terminal after a calling terminal ends the call or quits midway; completes the calculation of the waiting queue value corresponding to all calling terminals in the waiting queue of the called terminal;
  • a storage module connected to the queue processing module, configured to store a waiting queue value corresponding to each calling terminal
  • the waiting message notification module is connected to the storage module and the response message discriminating module, and configured to send, when the response message returned by the called terminal indicates that the called terminal is in a busy state, send a waiting notification message including the waiting queue value corresponding to the calling terminal to
  • the calling terminal is further configured to receive the active query information of the calling terminal, and query the storage module to send a waiting notification message including the waiting queue value corresponding to the calling terminal to the calling calling terminal.
  • the waiting notification information including the waiting queue value may be sent to the calling terminal. If the current waiting number of the called terminal is too large, the calling terminal may immediately take measures and do not wait, thereby preventing the calling terminal from wasting waiting. Time, and timely know the waiting queue status of the called terminal.
  • FIG. 12 is a schematic diagram of Embodiment 2 of an application server according to the present invention.
  • FIG. 12 is similar to FIG. 11 , and the same module is not described again, and has the corresponding functions and effects of FIG. 11 .
  • the message response module is further refined, and the message response module includes a message forwarding sub-module, and is connected to the queue processing module. For canceling the waiting message sent when the calling terminal quits the waiting queue of the called terminal, or releasing the connection message sent by the calling/called terminal when ending the call, and forwarding to the queue processing Module. Receiving, by the queue processing module, the cancellation waiting message, deleting the calling terminal from the waiting queue of the called terminal, and rearranging the waiting queue of the called terminal; receiving the called terminal The release connection message updates the waiting queue of the called terminal.
  • the waiting situation and the response of the calling party are divided, the calling party cancels the waiting, and needs to re-queue the waiting queue, as shown in FIG. 8(a) and FIG. 8(b); the called end ends with a calling party. Call, update the waiting queue, as shown in Figure 7.
  • FIG. 13 is a schematic diagram of Embodiment 3 of an application server according to the present invention.
  • the module in the queue processing module is further refined as shown in FIG. 13 .
  • the queue processing module in this embodiment includes:
  • the waiting queue attribute sub-module is connected to the message forwarding sub-module, and is used for arranging the location of each calling terminal waiting for the queuing queue to join the called terminal according to the sequence in which the calling terminal sends the call request to the called terminal. 6 , storing the queue head waiting for the queue queue and the location of the tail of the queue;
  • the waiting queue calculation sub-module is connected to the waiting queue attribute sub-module, and is configured to calculate a waiting queue of each calling terminal in the called waiting queue according to the position of each calling terminal in the waiting queue and the position of the queue head. value.
  • the internal structure and function modules of the application server can be understood in comparison with the specific embodiment of the waiting queue notification method in the present invention, and the corresponding functions in the above methods are mainly implemented by the execution logic inside the application server.
  • the called terminal waiting queue attribute sub-module in the foregoing embodiment may be further divided into: a queue re-arranging sub-unit, connected to the message forwarding sub-module, configured to receive a cancellation waiting message sent by the calling terminal, and send a cancellation waiting message. All the calling terminals that continue to wait after the calling terminal advance one bit in the original waiting queue queue, the queue head position of the waiting queue queue is unchanged, and the tail position of the queue moves forward by one bit;
  • the queue update subunit is connected to the message forwarding submodule, and is configured to receive a release connection message sent by the called terminal or the calling terminal, and remove the calling terminal located at the foremost position of the waiting queue queue from the queue, and The called terminal establishes a call connection, and recalculates the waiting row Waiting queue value corresponding to all calling terminals in the queue, and waiting for the waiting queue value of the calling terminal in the queuing queue to decrease by 1.
  • the present invention provides a message-based waiting queue notification method and an application server.
  • the waiting queue notification method and the application server proposed by the present invention can accurately notify the calling terminal of the inclusion of the waiting queue value. Waiting for the queue notification message, prompting the number of people the caller needs to wait, that is, how many users the caller terminal needs to wait before establishing a call connection with the called terminal, letting the calling terminal decide whether to continue waiting, avoiding wasting time, and
  • the present invention also analyzes various situations in which the calling terminal and the called terminal are actually used, and adopts different processing methods for various operations, such as different operations such as "blacklisting", canceling waiting, or halfway exiting.
  • the present invention also exemplifies a plurality of notifications waiting for a notification message, such as by voice notification, short message notification, multimedia message notification, mail notification, notification to another terminal bound to the calling terminal, or any combination thereof
  • the method prompts the calling terminal to perform a current waiting queue value, The rich and other forms of notification.
  • the invention can realize the information process by means of communication mode in which the calling terminal and the called terminal are integrated in an interactive, real-time, data and multimedia manner.
  • the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Description

基于消息的等待队列通知方法及应用服务器 技术领域
本发明涉及一种通知方法及应用服务器， 尤其是一种提供被叫终端实时 等待信息的通知方法以及应用服务器， 属于语音呼叫领域。 背景技术
现有的实时信息服务方式有很多种， 通常是被叫方 （被叫用户， 筒称被 叫终端或被叫）设置呼叫中心。 按不同的信息服务领域， 呼叫中心分配不同 的服务接入号码。 主叫方 （主叫用户， 筒称主叫终端或主叫）根据自己的需 求发送相应的呼叫请求， 从而与呼叫中心上相应的被叫方建立通话。
现有的语音呼叫业务主要采用 M/M/1/1单服务窗损失制排队模型， M是 一种概率分布， 即负指数分布（一般的呼叫模型中， 用户的随机呼叫都满 足负指数分布） 。 M/M/1/1单服务窗损失制排队模型中第一个 M是指不同 主叫用户相继发起呼叫的时间间隔 T的概率分布满足参数为 " λ " 的负指 数分布； 第二个 Μ指单个用户所耗费的通话时间 τ的概率分布满足参数为 " μ " 的负指数分布； 在 M/M/1/1模型中第一个 1是指服务窗的个数， 即 指一个被叫用户同一时刻只与一个主叫用户通话； 第二个 1指最大排队容 量， 包含正在服务和排队的用户，即同一时刻只允许 1个主叫用户被服务， 具体的状态流图如图 1所示， 图 1中的 "0" 表示服务窗空闲， "1" 表示 服务窗忙碌。 现有的 M/M/1/1单服务窗损失制排队模型在主叫用户发现被 叫用户忙碌时会自动放弃服务， 因此， 根据现有的 M/M/1/1单服务窗损失 制排队模型在多个主叫用户呼叫同一个被叫用户时， 主叫用户并不知道当 前被叫用户的排队情况。
现有技术中还有一种呼叫排队方法， 申请号为 200410038332.5, 这种呼 叫排队方法在判断被叫用户处于 "忙" 状态时， 会自动在被叫用户的私有队 列中排队等待； 当被叫用户空闲时， 主叫接续至被叫方。 与第一种 M/M/ 1/ 1 单服务窗损失制排队模型的呼叫方式相比， 这种呼叫排队方法虽然可以在被 叫用户处于 "忙" 状态时， 自动排在被叫用户的私有队列中排队等待， 增加 了排队的用户数目， 但这种呼叫排队方法并没有相关的消息通知， 只是可以 暂时存在被叫用户的私有队列中， 一直到被叫用户可以接续， 主叫用户却还 是无法获得当前自己在被叫用户中的排队情况， 只是盲目等待。
现有技术中虽然可以实现用户之间的通信，提供被叫终端的空闲或忙碌 状态信息， 也可以在与被叫终端未建立通话时通过语音向主叫终端播报被叫 的空闲或忙碌状态， 但是当有多个主叫用户均希望与同一被叫用户建立通信 时， 例如主叫用户 1、 主叫用户 2 ··· .主叫用户 5 , 均希望与被叫用户 A建立 呼叫连接， 如果此时被叫用户 A正在与主叫用户 1进行通信， 其余的主叫用 户 2 - 5均需要等待， 主叫用户 2-5虽然知道被叫用户 A正在通信， 获得被叫 处于忙碌的状态， 但无法判断是否需要继续等待， 如主叫用户 5需要等待的 人数较多， 则会浪费等待时间； 如果某一主叫用户需要等待的人数并不多， 如主叫用户 2 , 但是由于不知道前面等待的人数， 会错误的取消等待， 可能 会影响主叫用户的需求。
发明内容
本发明的目的是，针对现有技术中并没有提供被叫终端的等待队列状态， 在被叫终端处于忙碌状态时无法判断是否需要继续等待的缺陷， 提供一种基 于消息的等待队列通知方法及应用服务器， 通过本发明主叫终端呼叫被叫终 端时能够及时获知当前的等待状况。
为了实现上述目的， 本发明提供了一种基于消息的等待队列通知方 法， 包括：
^
主叫终端向被叫终端发送呼叫请求；
应用服务器向被叫终端转发主叫终端发送的呼叫请求， 并根据被叫终 端返回的响应消息判断被叫终端是否处于空闲状态；
若被叫终端处于忙碌状态， 应用服务器将所述主叫终端加入所述被叫 终端的等待排队队列， 并将包含主叫终端对应的等待队列值的等待通知消 息发送给主叫终端；
若被叫终端处于空闲状态， 主叫终端和被叫终端直接建立通话连接。 上述技术方案中， 还包括： 当主叫终端取消所述呼叫请求时， 将所述 主叫终端从所述被叫终端的等待排队队列中删除， 并对所述被叫终端的等 待排队队列进行重新排列； 向等待排队队列中原先排在所述主叫终端之后 的所有主叫终端分别发送包含重新排列后等待队列值的等待通知消息。
本方法中还包括： 对所述主叫终端进行分析， 与保存在被叫终端 "黑 名单" 中的数据进行对比， 如果所述主叫终端被记录在所述 "黑名单" 中， 是则不执行向被叫终端转发主叫终端发送的呼叫请求的步骤。
为了实现上述目的， 本发明还提供了一种应用服务器， 包括： 呼叫处理模块， 用于完成主叫终端和被叫终端之间基本的呼叫处理转 接流程；
响应消息判别模块， 与呼叫处理模块相连， 用于接收被叫终端返回的 响应消息， 判断被叫终端是否处于空闲状态， 并在被叫终端处于空闲状态 时， 通过呼叫处理模块建立主叫终端和被叫终端的连接； 队列处理模块， 与响应消息判别模块连接， 用于在被叫终端处于忙碌状态时， 将所述主叫 终端加入所述被叫终端的等待排队队列， 完成被叫终端的等待排队队列中 所有主叫终端对应的等待队列值的计算；
存储模块， 与队列处理模块连接， 用于存储各个主叫终端对应的等待 队列值；
等待消息通知模块， 与存储模块及响应消息判别模块连接， 用于在被 叫终端处于忙碌状态时， 将包含主叫终端对应等待队列值的等待通知消息 发送给主叫终端。 本发明提出了一种语音实时呼叫领域中对主叫终端等待队列值的通 知方法及应用服务器， 当被叫终端忙时， 本发明提出的等待队列通知方法 及应用服务器可以准确的向主叫终端告知被叫终端当前等待排队队列的 人数， 主叫终端需要等待多少个用户之后才能与被叫终端建立呼叫连接， 让主叫终端决定是否继续进行等待， 避免浪费时间， 并且本发明还对主叫 终端和被叫终端在实际使用时的多种情况进行分析， 对各种操作采取了不 同的处理方式， 如对 "黑名单" 、 取消等待或中途退出等操作进行了不同 的处理， 本发明还对等待通知消息的多种通知方式进行了举例， 如通过语 音通知、 短信通知、 彩信通知、 邮件通知、 通知与主叫终端绑定的另一终 端， 或其上述任意组合的方式对所述主叫终端进行当前等待队列值的提 示， 丰富了通知形式。
下面通过附图和实施例， 对本发明的技术方案做进一步的详细描述。 附图说明
图 1为现有的语音呼叫 M/M/ 1 / 1单服务窗损失制排队模型；
图 2为本发明基于消息的等待队列通知方法实施例一流程图； 图 3为本发明基于消息的等待队列通知方法实施例二流程图； 图 4为本发明基于消息的等待队列通知方法实施例三流程图； 图 5为本发明基于消息的等待队列通知方法中被叫终端的等待排队队列 实施例一解析示意图；
图 6为本发明基于消息的等待队列通知方法中被叫终端的等待排队队列 实施例二解析示意图；
图 7为本发明基于消息的等待队列通知方法中被叫终端的等待排队队列 实施例三解析示意图；
图 8 )为本发明基于消息的等待队列通知方法中一主叫终端取消等待 时等待排队队列的实施例四解析示意图； 图 8 ( b )为本发明基于消息的等待队列通知方法中一主叫终端取消等待， 等待排队队列重排后的实施例四解析示意图；
图 9为本发明基于消息的等待队列通知方法实施例四解析示意图； 图 10为本发明基于消息的等待队列通知方法采用的 M/M/ 1排队模型的实 施例状态流图；
图 11为本发明应用服务器实施例一示意图；
图 12为本发明应用服务器实施例二示意图；
图 1 3为本发明应用服务器实施例三示意图。
具体实施方式
参见图 2 , 为本发明基于消息的等待队列通知方法实施例一流程图。 如 图 2所示， 本实施例包括：
步骤 1.主叫终端向被叫终端发送呼叫请求；
步骤 2.应用服务器向被叫终端转发主叫终端发送的呼叫请求，接收被
^
叫终端返回的响应消息；
步骤 3.判断被叫终端是否处于空闲状态， 是则执行步骤 5 , 否则执行 步骤 4 ;
步骤 4.将主叫终端加入所述被叫终端的等待排队队列，并将包含该主 叫终端对应的等待队列值的等待通知消息发送给主叫终端；
步骤 5.主叫终端和被叫终端直接建立通话连接。
本实施例中， 应用服务器接到呼叫请求后， 根据被叫终端返回的响应 消息， 进行不同的判断， 如果被叫终端处于忙碌状态， 则将包含主叫终端 对应的等待队列值通过反向通知消息告知主叫终端， 从而主叫终端可以根 据收到的反向通知消息及时获得被叫终端的状态及需要等待的用户数目。 包含主叫终端的等待队列值的等待通知消息可以通过语音通知、 短信通 知、 彩信通知、 邮件通知、 通知与主叫终端绑定的另一终端， 或其上述任 意组合等方式对所述主叫终端进行当前等待队列值的提示， 例如： 将主叫 终端对应的等待队列值写入被叫终端的呈现状态中， 并发送给主叫终端。 主叫终端根据等待通知消息即可获得需要等待的数量， 判断是否需要继续 等待， 避免浪费时间。
参见图 3 , 为本发明基于消息的等待队列通知方法实施例二流程图。 本 实施例与图 2类似， 大致流程相同， 不同之处在于， 在步骤 4发送等待通知 消息后， 还包括：
步骤 41.判断主叫终端是否继续呼叫请求， 即是否继续等待， 是则执行 步骤 4 3 , 否则执行步骤 42 ;
步骤 42. 应用服务器接收到主叫终端发送的取消等待消息后， 将所述 主叫终端从所述被叫终端的等待排队队列中删除， 并对所述被叫终端的等 待排队队列进行重新排列； 向原先排在所述主叫终端之后的所有主叫终端 分别发送包含重新排列后对应等待队列值的等待通知消息；
步骤 4 3.主叫终端继续等待， 应用服务器判断主叫终端是否排在被叫 终端的等待排队队列的最前面， 是则执行步骤 44 , 否则继续等待， 继续执 行步骤 4 3 ;
步骤 44. 在被叫终端的当前呼叫结束后， 与所述被叫终端建立连接； 步骤 45.判断通话是否结束， 是则发送释放连接消息， 否则继续步骤 45。 本实施例主叫终端获得当前等待队列值后， 如果主叫终端之前的用户 人数过多， 主叫终端可以立即采取措施， 不进行等待， 取消呼叫， 避免浪 费时间。 应用服务器收到取消等待消息时， 需要对被叫终端的等待排队队 列进行重排， 从等待队列中删除所述取消等待的主叫终端， 并通知取消等 待的主叫之后的其他等待用户重排后的等待通知消息。
图 4为本发明基于消息的等待队列通知方法实施例三流程图。 本实施例 与图 2和图 3相比， 又增加了一些处理的步骤，具体包括以下步骤：
步骤 1 .主叫终端向被叫终端发送呼叫请求； 步骤 . 判断主叫终端是否属于被叫终端禁止通话的主叫终端， 如， 被 叫终端 "黑名单" 中的数据， 是则向所述主叫终端返回拒绝呼叫请求的失败 响应消息， 结束呼叫， 否则执行步骤 2 ; "黑名单" 为本领域技术人员的公 知常识， 表示被叫终端不希望与之建立呼叫的用户数据 ， 被叫终端可以将一 些禁止与之通话的用户数据加入 "黑名单" 中， 避免在被叫终端的等待排队 队列中进行排队等待；
步骤 2.应用服务器向被叫终端转发主叫终端发送的呼叫请求，接收被 叫终端返回的响应消息；
步骤 3.判断被叫终端是否处于空闲状态， 是则执行步骤 5 , 否则执行 步骤 4 ;
步骤 4.将主叫终端加入所述被叫终端的等待排队队列，并将包含主叫 终端对应的等待队列值的等待通知消息发送给主叫终端；
步骤 41.主叫终端是否继续呼叫请求， 即是否继续等待， 是则执行步骤 43 , 否则执行步骤 42;
步骤 42. 应用服务器接收到主叫终端发送的取消等待消息后， 将所述 主叫终端从所述被叫终端的等待排队队列中删除， 并对所述被叫终端的等 待排队队列进行重新排列； 向原先排在所述主叫终端之后的所有主叫终端 分别发送包含重新排列后等待队列值的等待通知消息， 结束；
步骤 43.主叫终端继续等待， 应用服务器判断主叫终端是否排在被叫 终端等待排队队列的最前面， 是则执行步骤 44 , 否则继续执行步骤 43; 步骤 44. 在被叫终端的当前呼叫结束后， 与所述被叫终端建立连接； 步骤 45.判断通话是否结束， 是则发送释放连接消息， 执行步骤 53 , 否 则继续步骤 45 ;
步骤 5.主叫终端和被叫终端直接建立通话连接；
步骤 51.判断通话是否结束， 是则执行步骤 52 , 否则继续步骤 51 ;
步骤 52.发送释放连接消息； 步骤 53. 应用服务器收到释放连接消息时， 更新被叫终端的等待排队 队列， 并向等待排队队列中原先排在呼叫结束的主叫终端之后的所有主叫 终端发送等待通知消息， 所述等待通知消息包含更新等待排队队列后主叫 终端对应的等待队列值。
图 4实施例中主叫终端允许与被叫终端建立连接可以具体为： 当主叫 终端为被叫终端等待排队队列中最前面的主叫终端时， 在被叫终端的当前呼 叫结束后， 与所述被叫终端建立连接。 例如， 被叫终端当前等待队列中有 5 个用户， 说明有 5个主叫终端 A、 B、 C、 D、 E均希望与被叫终端建立连接通 信， 当主叫终端 A、 B、 C、 D均从等待队列中移出 （与被叫终端呼叫结束或取 消等待）后， 主叫终端 E排在等待排队队列的最前面位置， 主叫终端 E在主 叫终端 D结束呼叫或取消等待后允许与被叫终端建立连接。 本实施例中还加 入了判断呼叫的主叫是否为被叫禁止通话的用户， 如黑名单中的用户， 是则 直接返回拒绝消息， 不用转发呼叫请求， 并且也避免了将黑名单中的用户加 入等待排队队列， 增加排队的数量， 给后续工作效率和计算带来影响。 将禁 止通话的主叫终端直接排除在被叫终端的等待排队队列之外， 加入等待队列 的均是被叫终端可能接续的用户， 给主叫和被叫终端带来了双方面的体验。
本发明能有多种不同形式的具体实施方式， 上面以图 2-图 4为例结合附 图对本发明的技术方案作举例说明， 这并不意味着本发明所应用的具体实例 只能局限在特定的实施例中， 本领域的普通技术人员应当了解， 上文所提供 的具体实施方案只是多种优选用法中的一些示例， 任何在多个主叫呼叫同一 被叫时， 向未接续的主叫返回包含该主叫当前需要等待的用户数量的反向等 待通知消息， 对未接续的主叫进行等待队列值提示的实施方式均应在本发明 技术方案所要求保护的范围之内。
下面通过图 5-图 8对本发明中等待排队队列的排队队列处理过程做举例 说明。
1、 如图 5 所示， 被叫终端 （筒称被叫） 的等待排队队列初始为空， 为说明方便， 将队列头位置处的指针表示为 "head" , 队列尾位置处的指 针表示为 "rear" , 初始值 head=rear=_l。 等待排队队列中的每个主叫终 端 （筒称主叫）有一个位置 （以下筒称 pos ) 属性和一个等待 （以下筒称 wait )属性， 用 W[i]表示队列中第 i个主叫的对象数组， 用 W[i]. pos表 示第 i个主叫在整个队列中的位置， 用 W[i]. wait表示第 i个主叫是被叫 的第几个等待者， 该值即为本发明中所述的各个主叫终端对应的等待队列 值， W[i] . wait=W[i] . pos-head, W [i] · pos的初: ½值为其力口入队歹 l]后的 rear 值。 图 5 中有一个用户 （User ) 在接受服务， 即第一个主叫， 图 5 中上半部分表示被叫的等待排队队列， 右下角表示正在服务的用户服务窗 口， 从图 5 -图 8可以看出被叫的等待排队队列中的人数可以多于一个， 但 正在服务窗口只有一个， 即同一时刻只有一个用户接收通话， 等待排队队 列中的其余用户需要进行等待；
2、 当主叫 user尚未结束通话时， 另一主叫发起呼叫， 此时将其加 入等待队列， rear指向的位置向后移 1位， rear值加 1, 变为 0; head 仍指向队列头的位置， 值为 -1; 当继续有其它主叫呼叫该被叫并加入该被 叫的等待排队队列时， rear的值持续加 1。 如图 6所示， 有 6个主叫用户 W0-W5陆续发起呼叫请求， 最后队列尾指针 rear指向队列中 W5的位置， rear值为 5。 W[5].wait= W [5] . pos-head =5-(-1)=6, 即 W5是第六个等 待者；
3、 当主叫 User结束通话， 则从队列头位置处选择用户 W0与被叫 建立连接， 进行通话， 主叫 W0移出队列， head指向下一位置， head值加 1变为 0, rear位置不变， 值仍为 5。 如图 7所示， 队列头的指针 head值 为 0, 队列尾指针 rear值为 5。 此时， W [5] . wai t=5-0=5 , 即 W5是第五个 等待者；
4、 依次类推，每进入一个主叫， rear值力口 1,每移出一个主叫 head 值加 1, 当 W[i] . wait=W[i] . pos_head=l时， 表明主叫 i是目前排在队列 最前面位置处的主叫。 当被叫结束当前通话， 发送释放连接消息后， 应用 月良务器收到释放连接的消息， head值加 1, 排在队列最前面位置处的主叫 i 的等待人数为 W[i]. wait=l-l = 0, 它将与被叫建立通话， 并移出等待队 歹 ij : 即在被叫结束通话后， 排在在队列最前面位置处的主叫可以与被叫建 立连接；
5、 当等待排队队列中的某一主叫中途取消等待时， 队列中需要进 行重新排列， 该取消等待的主叫之后的所有继续等待的主叫在原先的等待 排队队列中的位置向前进一位， 等待排队队列的队列头位置不变， 队列尾 位置向前移动一位， 每个主叫的 pos值和 wait值也将变化。 如图 8 ( a ) 所示， 在 W0 通话过程中， 等待排队队列中 W3取消等待， 从队列中移出， 则主叫 W3后面的 W4、 W5都将前移动一位， 形成图 8 (b)所示的重新排列 后的等待排队队列。 如图 8 (b)所示， 主叫 W4和 W5的位置分别向前移动 一位， 重新排列后 W4和 W5的当前位置值分别为 3、 4; 等待队列值（wait ) 分别为 3、 4, 队列尾指针 rear指向 W5在等待排队队列中的位置， rear 值变为 4。
另外， 有几点需要说明：
1.每当一个主叫进入队列时，都会收到一个包含该主叫对应的等待队 列值的通知消息， 在等待队列值为 0时， 主叫即可与被叫进行通话； 当被 叫的等待排队队列中有某一主叫需要取消等待， 则将该取消等待的主叫从 等待队列中移出， 无论该取消等待的主叫处在等待排队队列中的哪一位 置， 应用服务器均需要向取消等待的主叫之后的其余主叫分别发送包含更 新后等待队列值的等待通知消息；
2.被叫处于忙碌状态时， 通过计算和查询被叫的等待队列， 反馈给主 叫包含该主叫对应等待队列值的等待通知消息， 只有被叫处于忙碌状态 时， 主叫才会收到等待通知消息。 第一个主叫用户呼叫被叫用户时， 是正 常的接续流程， 第二个主叫用户发起呼叫且被叫与第一个主叫还未通话完 毕时， 被叫会给应用服务器反馈被叫忙的信息， 此时第二个主叫用户才进 入排队队列处理流程， 才会发送等待通知消息；
3.被叫与某一主叫结束通话时会发送释放连接消息， 此时， 需要更新 被叫的等待排队队列， 并向原先排在该呼叫结束的主叫之后的所有主叫终 端分别发送包含更新后的等待队列值的等待通知消息。
图 9为本发明基于消息的等待队列通知方法实施例四解析示意图； 现对 照图 9及图 2 -图 8的实施例对本发明具体的应用流程进行举例说明，如图 9 所示， 本实施例具体包括：
A. 主叫终端 1向被叫终端发送呼叫请求；
B. 应用服务器经查询获知主叫终端 1 不在被叫终端的黑名单中， 则 转发主叫终端 1的呼叫请求给被叫终端；
C. 被叫终端空闲， 返回响应消息， 表示被叫终端可以接通；
D. 应用服务器收到被叫终端的返回响应消息， 启动排队队列处理（如 图 5 -图 8实施例所示）， 并接通主叫终端 1和被叫终端， 如图 9中， 主叫 终端 1和被叫终端进行通话；
E. 在主叫终端 1和被叫终端的通话过程中， 主叫终端 i发起呼叫 请求； 如图 9所示；
F. 应用服务器经查询获知主叫终端 i 不在被叫终端的黑名单中， 则转发主叫终端 i的呼叫请求给被叫终端；
G. 被叫终端处于忙碌状态， 正在与主叫终端 1 通话， 被叫终端返 回响应消息， 表示被叫终端忙碌；
H. 应用服务器收到被叫终端的返回响应消息， 启动排队队列处理， 向 主叫终端 i发送包含主叫终端 i对应的等待队列值的等待通知消息；
E，.在主叫终端 1和被叫终端的通话过程中， 有 i + 1个主叫终端陆续发 起呼叫请求； 如图 9所示， 最后一个发起呼叫的主叫终端 i + 1向被叫终端 发送呼叫请求； F，. 应用服务器经查询获知主叫终端 i + 1 不在被叫终端的黑名单中， 则转发主叫终端 i + 1的呼叫请求给被叫终端；
G，. 被叫终端正在与主叫终端 1 通话， 返回响应消息， 表示被叫终端 忙碌；
Η' . 应用服务器收到被叫终端的返回响应消息， 启动排队队列处理， 向主叫终端 i + 1 发送包含主叫终端 i + 1 对应的等待队列值的等待通知消 息；
I . 主叫终端 1 与被叫终端结束通话， 主叫终端 1 和被叫终端发送 释放连接消息，应用服务器收到主叫终端 1和被叫终端的释放连接消息后， 启动排队队列处理，如图 6和图 7实施例所示，进行等待排队队列的更新， 向主叫终端 2发送更新后包含主叫终端 2对应的等待队列值的等待通知消 息； 主叫终端 2更新后的等待队列值为 0 , 可以与被叫终端建立连接， 进 行通话；
J. 应用服务器向主叫终端 2 后面的所有主叫终端均发送包含新的 等待队列值的等待通知消息， 如图 9中， 向主叫终端 i + 1重新发送等待通 知消息，该消息包含等待排队队列更新后主叫终端 i + 1对应的等待队列值； K. 当等待排队队列中的某一主叫中途取消等待时， 如图 9 中主叫 终端 i经过长时间等待之后， 决定取消等待， 用户挂机， 发送取消等待消 息；
L. 应用服务器收到主叫终端 i 取消等待的消息后， 启动排队队列处 理， 如图 8 ( a ) 图 8 (b)实施例所示， 对等待队列进行重新排列， 向主叫 终端 i之后的继续等待的主叫终端 i + 1发送等待通知消息， 该消息包含等 待排队队列重新排列后主叫终端 i+1对应的等待队列值。
等待通知消息包含更新后各主叫终端对应的等待队列值， 表示当前等 待的用户数目发生了变化， 让处于等待状态的主叫终端及时获得当前需要 等待的用户数目。 本发明中所述的等待队列通知方法可应用于语音实时业务， 在主叫终 端发起呼叫请求后， 可以通过语音、 短信等方式通知被叫终端的状态及该 主叫终端需要等待的状况， 例如： 通过语音播报 "您前方还有 5个用户等 待与 X X X通话" 。
图 10为本发明基于消息的等待队列通知方法采用的 M/M/ 1排队模型的 实施例状态流图。 图 10为本发明采用的排队模型， 图 1为现有语音呼叫 业务中的 M/M/ 1 / 1是单服务窗损失制排队模型。
对比图 10和图 1可看出， 现有的 M/M/ 1 / 1模型指同一时刻被叫只与 一个主叫通话， 且正在服务的主叫用户数加等待的主叫用户数为 1 , 即最 大排队容量为 1 , 同一时刻只允许 1个主叫被服务。 本发明的消息队列呼 叫模型采用的是 M/M/ 1单服务窗等待制排队模型， 对于等待制排队模型， 没有最大排队容量的限制，默认为无穷大，即允许无限多个用户进行排队。 如图 10所示， 图中的 "0"表示此时有 0个用户； "1 "表示有 1个用户， … k表示此时有 k个用户， 1个用户正在通话， k-1个用户在排队等待， 依次类 推。 本发明的等待队列通知方法与现有的排队呼叫机制有实质上的不同， 排 队的人数不限制为 1个， 且可以将与主叫相关的等待队列值通过等待消息通 知主叫用户。
根据主叫终端的呈现能力判别， 采用的等待通知消息可以是语音通知， 短信通知， 彩信通知， 即时消息通知， 甚至邮件通知等。 如主叫是一部固话， 可以通过语音方式通知； 主叫是手机， 可以语音、 短信、 彩信等通知。 当然 还可以有多种实时通知方式， 如， 主叫是固话， 也可以短信通知与该主叫绑 定的手机、 邮件上等等。
参见图 11 , 为本发明应用服务器实施例一示意图。 如图 11所示， 本实施 例中呼叫处理模块为一般应用服务器具有的模块，用于完成主叫终端和被叫 终端之间基本的呼叫处理转接流程， 本实施例与现有的服务器相比， 还包 括： 响应消息判别模块， 与呼叫处理模块相连， 用于接收被叫终端返回的 响应消息， 判断被叫终端是否处于空闲状态， 并在响应消息表示被叫终端 处于空闲状态时， 通过呼叫处理模块建立主叫终端和被叫终端的连接； 接 收主叫终端中途退出被叫终端的等待排队队列时发送的取消等待消息和 / 或结束通话时主叫 /被叫终端的释放连接消息；
队列处理模块， 与响应消息判别模块连接， 用于在被叫终端处于忙碌 状态时， 将所述主叫终端加入所述被叫终端的等待排队队列， 接收响应消 息判别模块转发的释放连接消息或取消等待消息， 在某一主叫终端结束呼 叫或中途退出后对被叫终端的等待排队队列进行更新； 完成被叫终端的等 待排队队列中所有主叫终端对应的等待队列值的计算；
存储模块， 与队列处理模块连接， 用于存储各个主叫终端对应的等待 队列值；
等待消息通知模块， 与存储模块及响应消息判别模块连接， 用于在被 叫终端返回的响应消息表示被叫终端处于忙碌状态时， 将包含主叫终端对 应的等待队列值的等待通知消息发送给主叫终端； 还用于接收主叫终端的 主动查询信息， 并向存储模块查询， 将包含主叫终端对应的等待队列值的 等待通知消息发送给查询的主叫终端。
图 11实施例可以将含有等待队列值的等待通知信息发送给主叫终端， 如果被叫终端的当前等待人数过多， 主叫终端可以立即采取措施， 不进行 等待， 从而避免主叫终端浪费等待时间， 并及时获知被叫终端的等待队列 状况。
图 12为本发明应用服务器实施例二示意图。 图 12与图 11类似， 相同模 块不再赘述， 具有所有图 11相应的功能和效果， 本实施例中对消息响应模块 进一步细化， 消息响应模块包括消息转发子模块， 与队列处理模块连接， 用 于收到主叫终端中途退出被叫终端的等待排队队列时发送的取消等待消 息或结束通话时主叫 /被叫终端发送的释放连接消息， 并转发到队列处理 模块。 队列处理模块收到所述取消等待消息， 将所述主叫终端从所述被叫 终端的等待排队队列中删除， 并对所述被叫终端的等待排队队列进行重新 排列； 收到被叫终端的释放连接消息， 更新被叫终端的等待排队队列。
本实施例对等待的情况及主叫的反应进行了划分， 主叫取消等待， 需要 重新排队等待队列， 如图 8 ( a )和图 8 ( b )所示； 被叫结束与一主叫的通话， 对等待队列进行更新， 如图 7所示。
图 1 3为本发明应用服务器实施例三示意图。 本实施例与图 12相比， 对 队列处理模块内部的模块进一步细化， 如图 1 3所示， 本实施例中队列处理模 块包括：
等待队列属性子模块， 与消息转发子模块相连， 用于按主叫终端向被叫 终端发送呼叫请求的先后对加入被叫终端等待排队队列的每个主叫终端进行 位置排列， 具体可参见图 6 , 存储等待排队队列的队列头及队列尾所在的位 置；
等待队列计算子模块， 与等待队列属性子模块相连， 用于根据每个主叫 终端在等待排队队列中的位置及队列头的位置， 计算被叫的等待排队队列中 各主叫终端的等待队列值。
上述应用服务器内部的结构和功能模块可对照本发明中等待队列通知方 法的具体实施例理解， 主要通过应用服务器内部的执行逻辑实现上述方法中 的相应功能。上述实施例中被叫终端等待队列属性子模块还可进一步划分为： 队列重排子单元， 与消息转发子模块相连， 用于接收到主叫终端发送的 取消等待消息， 将发送取消等待消息的主叫终端之后的所有继续等待的主 叫终端在原先的等待排队队列中的位置向前进一位， 所述等待排队队列的 队列头位置不变， 队列尾位置向前移动 1位；
队列更新子单元， 与消息转发子模块相连， 用于接收到被叫终端或主 叫终端发送的释放连接消息， 将位于等待排队队列最前面位置处的主叫终 端从队列中移出， 并与所述被叫终端建立通话连接， 重新计算位于等待排 队队列中的所有主叫终端对应的等待队列值， 更新后等待排队队列中的主 叫终端的等待队列值减 1。
综上所述， 本发明提供了基于消息的等待队列通知方法及应用服务 器， 当被叫终端忙时， 本发明提出的等待队列通知方法及应用服务器可以 准确的向主叫终端告知包含等待队列值的等待队列通知消息， 提示主叫当 前需要等待的人数， 即该主叫终端需要等待多少个用户之后才能与被叫终 端建立呼叫连接， 让主叫终端决定是否继续进行等待， 避免浪费时间， 并 且本发明还对主叫终端和被叫终端在实际使用时的多种情况进行分析， 对 各种操作采取了不同的处理方式， 如对 "黑名单" 、 取消等待或中途退出 等操作进行了不同的处理， 本发明还对等待通知消息的多种通知进行了举 例， 如通过语音通知、 短信通知、 彩信通知、 邮件通知、 通知与主叫终端 绑定的另一终端， 或其上述任意组合的方式对所述主叫终端进行当前等待 队列值的提示， 丰富了等通知的形式。 本发明可以使主叫终端和被叫终端 之间以交互式、 实时、 数据和多媒体相融合的通信方式实现信息过程。
本领域普通技术人员可以理解： 实现上述方法实施例的全部或部分步骤 可以通过程序指令相关的硬件来完成， 前述的程序可以存储于一计算机可读 取存储介质中， 该程序在执行时， 执行包括上述方法实施例的步骤； 而前述 的存储介质包括： R0M、 RAM, 磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是： 以上实施例仅用以说明本发明的技术方案， 而非对其 限制； 尽管参照前述实施例对本发明进行了详细的说明， 本领域的普通技术 人员应当理解： 其依然可以对前述各实施例所记载的技术方案进行修改， 或 者对其中部分技术特征进行等同替换； 而这些修改或者替换， 并不使相应技 术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims

权利 要求 书
1. 一种基于消息的等待队列通知方法， 其特征在于， 包括：
主叫终端向被叫终端发送呼叫请求；
应用服务器向被叫终端转发主叫终端发送的呼叫请求， 并根据被叫终 端返回的响应消息判断被叫终端是否处于空闲状态；
若被叫终端处于忙碌状态， 应用服务器将所述主叫终端加入所述被叫 终端的等待排队队列， 并将包含所述主叫终端对应的等待队列值的等待通 知消息发送给主叫终端；
若被叫终端处于空闲状态， 主叫终端和被叫终端直接建立通话连接。
2. 根据权利要求 1所述的基于消息的等待队列通知方法， 其特征在于， 所述应用服务器向被叫终端转发主叫终端发送的呼叫请求之前还包括： 对所述主叫终端进行分析， 与保存在被叫终端 "黑名单" 中的数据进行 对比， 如果所述主叫终端被记录在所述 "黑名单" 中， 则不执行向被叫终端 转发主叫终端发送的呼叫请求的步骤。
3. 根据权利要求 1所述的基于消息的等待队列通知方法， 其特征在于， 所述将等待通知消息通过语音通知、 短信通知、 彩信通知、 邮件通知， 或 其上述任意组合的方式发送给主叫终端。
4. 根据权利要求 1 至 3 中任意一项所述的基于消息的等待队列通知方 法， 其特征在于， 还包括：
当主叫终端取消所述呼叫请求时， 将所述主叫终端从所述被叫终端的 等待排队队列中删除， 并对所述被叫终端的等待排队队列进行重新排列； 向等待排队队列中原先排在所述主叫终端之后的各个主叫终端分别发 送包含重新排列后等待队列值的等待通知消息。
5. 根据权利要求 4所述的基于消息的等待队列通知方法， 其特征在于， 所述对被叫终端的等待排队队列进行重新排列具体为： 所述取消呼叫请求的主叫终端之后的所有继续等待的主叫终端在原先 的等待排队队列中的位置向前进一位， 所述等待排队队列的队列尾位置向 前进 1；
所述取消呼叫请求的主叫终端之后的所有继续等待的主叫终端对应的 等待队列值均减少 1 ;
所述等待队列值为主叫终端在等待排队队列中的位置与队列头位置之 差。
6. 根据权利要求 4所述的基于消息的等待队列通知方法， 其特征在于， 还包括：
被叫终端的当前呼叫结束时， 呼叫结束的主叫终端或被叫终端发送释放 连接消息；
应用服务器收到所述释放连接消息时， 更新被叫终端的等待排队队列， 并向等待排队队列中的所有主叫终端分别发送包含更新后等待队列值的 等待通知消息。
7. 根据权利要求 6所述的基于消息的等待队列通知方法， 其特征在于， 所述更新被叫终端的等待排队队列具体为：
将位于等待排队队列最前面位置处的主叫终端从所述等待排队队列中 移出， 并与所述被叫终端建立通话连接；
重新计算位于等待排队队列中的所有主叫终端的等待队列值， 等待排 队队列中的所有主叫终端对应的等待队列值均减 1；
所述等待队列值为主叫终端在等待排队队列中的位置与队列头位置之 差。
8. 一种应用服务器， 包括呼叫处理模块， 用于完成主叫终端和被叫终 端之间基本的呼叫处理转接流程， 其特征在于， 还包括：
响应消息判别模块， 与呼叫处理模块相连， 用于接收被叫终端返回的 响应消息， 判断被叫终端是否处于空闲状态， 并在被叫终端处于空闲状态 时， 通过呼叫处理模块建立主叫终端和被叫终端的连接；
队列处理模块， 与响应消息判别模块连接， 用于在被叫终端处于忙碌 状态时， 将所述主叫终端加入所述被叫终端的等待排队队列， 完成被叫终 端的等待排队队列中所有主叫终端对应的等待队列值的计算；
存储模块， 与队列处理模块连接， 用于存储各个主叫终端对应的等待 队列值；
等待消息通知模块， 与存储模块及响应消息判别模块连接， 用于在被 叫终端处于忙碌状态时， 将包含主叫终端对应的等待队列值的等待通知消 息发送给主叫终端。
9. 根据权利要求 8所述的应用服务器，其特征在于，所述响应消息判别 模块包括：
消息转发子模块， 与队列处理模块连接， 用于接收主叫终端中途退出被 叫终端的等待排队队列时发送的取消等待消息和 /或结束通话时主叫 /被 叫终端的释放连接消息， 并转发到队列处理模块；
所述队列处理模块还用于接收消息转发子模块转发的释放连接消息或 取消等待消息， 在主叫终端结束呼叫或中途退出后对被叫终端的等待排队 队列进行更新。
10. 根据权利要求 8所述的应用服务器，其特征在于，所述等待消息通知 模块还用于接收主叫终端的主动查询信息， 向存储模块查询， 将包含主叫 终端对应的等待队列值的等待通知消息发送给查询的主叫终端。
11. 根据权利要求 8-1 Q任意一项所述的应用服务器， 其特征在于， 所述 队列处理模块包括：
等待队列属性子模块， 与消息转发子模块相连， 用于根据主叫终端向被 叫终端发送呼叫请求的先后， 对每个加入被叫终端等待排队队列的主叫终端 进行位置排列， 存储等待排队队列的队列头及队列尾所在的位置；
等待队列计算子模块， 与等待队列属性子模块相连， 用于根据每个主叫 终端在等待排队队列中的位置及队列头的位置， 计算每个主叫终端对应的等 待队列值。
12. 根据权利要求 11 所述的应用服务器， 其特征在于， 所述被叫终端等 待队列属性子模块包括：
队列重排子单元， 与消息转发子模块相连， 用于接收到主叫终端发送的 取消等待消息， 将发送取消等待消息的主叫终端之后的所有继续等待的主 叫终端在原先的等待排队队列中的位置向前进一位， 所述等待排队队列的 队列头位置不变， 队列尾位置向前移进 1位；
队列更新子单元， 与消息转发子模块相连， 用于接收被叫终端或主叫终 端发送的释放连接消息， 将位于等待排队队列最前面位置处的主叫终端从 队列中移出， 并与所述被叫终端建立通话连接， 重新计算位于等待排队队 列中的所有主叫终端对应的等待队列值。
PCT/CN2007/071069 2007-03-05 2007-11-15 Procédé destiné à notifier une file d'attente basé sur le message et serveur d'application correspondant Ceased WO2008106853A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/530,140 US8848896B2 (en) 2007-03-05 2007-11-15 Message-based notifying method for notifying waiting queue and application server

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN 200710064178 CN101262623B (zh) 2007-03-05 2007-03-05 基于消息的等待队列通知方法及应用服务器
CN200710064178.2 2007-03-05

Publications (1)

Publication Number Publication Date
WO2008106853A1 true WO2008106853A1 (fr) 2008-09-12

Family

ID=39737777

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/071069 Ceased WO2008106853A1 (fr) 2007-03-05 2007-11-15 Procédé destiné à notifier une file d'attente basé sur le message et serveur d'application correspondant

Country Status (3)

Country Link
US (1) US8848896B2 (zh)
CN (1) CN101262623B (zh)
WO (1) WO2008106853A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101895848A (zh) * 2009-05-20 2010-11-24 中兴通讯股份有限公司 一种虚拟坐席的监控系统和方法

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8379816B1 (en) * 2008-05-15 2013-02-19 Trend Micro Incorporated Methods and arrangement for handling phishing calls for telecommunication-enabled devices
US8825962B1 (en) 2010-04-20 2014-09-02 Facebook, Inc. Push-based cache invalidation notification
WO2013097663A1 (zh) * 2011-12-28 2013-07-04 北京奇虎科技有限公司 消息处理方法及装置
CN103905267B (zh) * 2012-12-28 2017-12-15 腾讯科技（北京）有限公司 一种数据监控方法和装置
US20150206092A1 (en) * 2014-01-21 2015-07-23 Avaya, Inc. Identification of multi-channel connections to predict estimated wait time
CN105207973A (zh) * 2014-06-18 2015-12-30 北京信威通信技术股份有限公司 一种ims通信系统中用户同时呼叫对方时的互通方法
CN106060110A (zh) * 2016-05-09 2016-10-26 乐视控股（北京）有限公司 在线通信提示方法及装置
CN105959392A (zh) * 2016-06-14 2016-09-21 乐视控股（北京）有限公司 访问量控制方法及装置
CN110769017A (zh) * 2018-07-27 2020-02-07 北京国双科技有限公司 数据请求的处理方法、装置、存储介质和处理器
CN110727507B (zh) * 2019-10-21 2022-09-09 广州欢聊网络科技有限公司 一种消息的处理方法、装置、计算机设备和存储介质
WO2022039077A1 (ja) * 2020-08-19 2022-02-24 ソニーグループ株式会社 ネットワーク機器、ネットワーク機器の制御方法およびネットワークシステム

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998048607A1 (en) * 1997-04-14 1998-11-05 Nokia Telecommunications Oy Call waiting in call setup
CN1585559A (zh) * 2004-05-28 2005-02-23 中兴通讯股份有限公司 一种被叫转入可接受呼叫状态时主动通知主叫的方法
CN1700716A (zh) * 2004-05-19 2005-11-23 华为技术有限公司 呼叫排队方法

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5509055A (en) * 1993-06-30 1996-04-16 At&T Corp. Inbound telecommunications services resources management system
US7231031B2 (en) * 1997-02-26 2007-06-12 Qwest Communications International Inc. AIN call queuing
US6141328A (en) * 1997-09-29 2000-10-31 Qwest Communications International Inc. Method and system for two-way negotiated call hold
FI107983B (fi) * 1998-12-23 2001-10-31 Nokia Networks Oy Vilpillisen käytön havaitseminen ja estäminen tietoliikenneverkossa
US6694009B1 (en) * 1999-06-15 2004-02-17 Avaya Technology Corp. Estimation of a work item's wait-time from the present stages of processing of preceding work items
US6754333B1 (en) * 2000-04-27 2004-06-22 Avaya Technology Corp. Wait time prediction arrangement for non-real-time customer contacts
US7095842B2 (en) * 2001-12-03 2006-08-22 International Business Machines Corporation Enabling caller controlled hold queue position adjustment
US8411843B1 (en) * 2005-10-04 2013-04-02 Avaya Inc. Next agent available notification
US7606360B2 (en) * 2006-05-31 2009-10-20 Cisco Technology, Inc. Automated system and method for handling human and caller queues

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998048607A1 (en) * 1997-04-14 1998-11-05 Nokia Telecommunications Oy Call waiting in call setup
CN1700716A (zh) * 2004-05-19 2005-11-23 华为技术有限公司 呼叫排队方法
CN1585559A (zh) * 2004-05-28 2005-02-23 中兴通讯股份有限公司 一种被叫转入可接受呼叫状态时主动通知主叫的方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101895848A (zh) * 2009-05-20 2010-11-24 中兴通讯股份有限公司 一种虚拟坐席的监控系统和方法

Also Published As

Publication number Publication date
US20100142696A1 (en) 2010-06-10
US8848896B2 (en) 2014-09-30
CN101262623A (zh) 2008-09-10
CN101262623B (zh) 2010-07-21

Similar Documents

Publication Publication Date Title
WO2008106853A1 (fr) Procédé destiné à notifier une file d'attente basé sur le message et serveur d'application correspondant
WO2006097032A1 (fr) Procede et systeme pour mise en place de routage intelligent
CN101529833A (zh) 供接收者稍后进行获取的数据消息的存储
US20100172483A1 (en) Conversation of a phone call into a smart pushed voice message
JP2009225319A (ja) グループ通信システム、グループ識別番号発行装置、および、呼制御装置
CN102326376B (zh) 座席终端接入呼叫的方法、呼叫中心及系统
WO2012062052A1 (zh) 基于呼叫中心的排队处理方法及系统
CN101155389A (zh) 处理呼叫冲突的方法及装置
US7831032B2 (en) System and method for the establishment of a connection between a contact requester and a communications center
CN101330759B (zh) 呼叫实现方法、消息路由实现方法和短消息中心
KR20120106881A (ko) 외부 메시지 센터들로의 메시지 대기 통지
CN101631273B (zh) 呼叫转移业务更改方法及装置
CN102883081B (zh) 互联系统和互联方法
CN1323569C (zh) 一种呼叫智能路由的方法及其系统
JP6870443B2 (ja) Ｉｐ電話ネットワークシステム、親ゲートウェイ、および子ゲートウェイ
CN101467406B (zh) 多媒体消息定时任务处理系统及其方法
CN107666543B (zh) 一种数据处理方法及装置
CN101193163B (zh) 实现自动业务和人工业务互控的方法及系统
US20060210029A1 (en) System and methods for handling voice mail messages to increase voice traffic in a telephone system
CN103428379B (zh) 坐席服务对象的交换方法及装置
CN102833426B (zh) 一种代答方法
KR100793351B1 (ko) 통화 중 예약 호 처리 시스템 및 그 제어방법
CN1984187B (zh) 一种限定回叫业务触发的方法和系统
JP2001203756A (ja) ネットワーク通信方法及びネットワーク通信システム
JPH07221845A (ja) 交換機

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 12530140

Country of ref document: US

122 Ep: pct application non-entry in european phase

Ref document number: 07817259

Country of ref document: EP

Kind code of ref document: A1