A system for processing voicemail is provided that includes a voicemail database processor establishing one or more of an accounts table, a messages table, a distribution list table, a distribution lists members tables, and a delete request table. In operation a message navigation menu is provided to a user to allow the user to move back and forth a specified number of voicemails, change between urgent and normal priority voicemails, retrieve messages only from a specific mailbox or from outside the system, or initiate an improved deletion operation.
|
1. A system for processing voicemail, said system including:
a plurality of voicemail mailboxes; and
a voicemail database processor, wherein said voicemail database processor includes a database having:
an accounts table having, for a plurality of said plurality of voicemail mailboxes, an entry identifying each of said plurality of voicemail mailboxes by an extension number and an internal identifier,
a messages table having, for each of a plurality of voicemail messages, an entry identifying each of said voicemail messages and associating said voicemail message with an internal message identifier, an identification of the sender, an identification of the receiver, an identification of a name of a sound file representing a recording of said voicemail and the delivery time,
wherein said messages table also includes an entry identifying whether a voicemail has been forwarded from another mailbox.
5. A method for processing voicemail, said method including:
receiving a voicemail at a voicemail database processor and logically associating said voicemail with a messages table, wherein said messages table includes, for each of a plurality of voicemail messages, an entry identifying each of said voicemail messages and associating said voicemail message an identification of a mailbox of a recipient and a deleted flag;
providing an audio-driven navigation menu allowing a user to audibly command the deletion of one or more of said plurality of voicemail messages, wherein said user is associated with a user mailbox;
reviewing said messages table and determining a plurality of voicemails having said user mailbox as an associated mailbox of a recipient and determining at least one of said plurality of voicemails having said deleted flag set to indicate that said voicemail is not deleted; and
adjusting said deleted flag to indicate that said voicemail is deleted.
4. A method for processing voicemail, said method including:
receiving a voicemail at a voicemail database processor and logically associating said voicemail with a messages table, wherein said messages table includes, for each of a plurality of voicemail messages, an entry identifying each of said voicemail messages and associating said voicemail message with an internal message identification and an identification of a mailbox of a recipient;
providing an audio-driven navigation menu allowing a user to audibly indicate a desired number of messages to skip forward or backward, wherein said user is associated with a user mailbox;
wherein said navigation menu allows a user to indicate a desired number of messages of two or more,
reviewing said messages table and determining a plurality of voicemails having said user mailbox as an associated mailbox of a recipient and ordering said plurality of voicemails in chronological order;
skipping forward or backward through said plurality of chronologically ordered voicemails by the number of messages specified by said user.
2. The system of
3. The system of
6. The method of
7. The method of
8. The method of
9. The method of
10. The method of
11. The method of
|
|||||||||||||||||||||||||
The present invention generally relates to a voicemail system. More particularly, the present invention relates to an improved system and method for navigating messages stored on a voicemail system
Voicemail systems are currently in wide use in both businesses and residences. In a standard voicemail system, an incoming phone message is recorded and stored in a voicemail system for later retrieval and playback by the operator of the voicemail system. Additionally, since the concept of voicemail was invented, it has been used in a variety of settings. For example, businesses and residences use voicemail to receive messages from individuals when the called party cannot be reached directly. Also, voicemail may be used internally within an organization to send messages to staff members, for example, if they cannot be spoken to directly at the moment. Furthermore, distribution lists may be defined and used so that a user of the voicemail system may record a single message and then have the message automatically copied and sent to the multiple recipients set forth in the distribution list. For example, a department head may have a distribution list including each of the department head's subordinates, and the department head may record a single voicemail message and use the distribution list to have the single voicemail message automatically copied and distributed to the voicemail of each person on the distribution list.
As is readily appreciated from the examples above, over the years voicemail has evolved to a point that distribution lists have begun to influence the way in which voicemail is used. However, the standard playback controls provided by current voicemail user interfaces are clunky an inelegant. For example, if a particular voicemail box receives a large number of messages, a user must typically spend a considerable amount of time listening to each message sequentially and is unable to sort the voicemails in a way that may provide greater convenience and speed. Further, because of the way a typically voicemail system performs commands initiated by a user, the user may perceive the voicemail system as slow or non-responsive.
One or more embodiments of the present invention provide a system for processing voicemail that includes a voicemail database processor establishing one ore more of an accounts table, a messages table, a distribution list table, a distribution lists members tables, and a delete request table. In operation a message navigation menu is provided to a user to allow the user to move back and forth a specified number of voicemails, change between urgent and normal priority voicemails, retrieve messages only from a specific mailbox or from outside the system, or initiate an improved deletion operation.
One embodiment of the present invention provides an improved voicemail system that allows users to automatically send messages to multiple recipients in such a way that facilitates group discussions. For example, as further described below, a user of a voicemail box may act as a moderator and, upon receiving a message intended for a discussion group, the moderator may forward the message out to the group. The moderator may also originate new messages and send them out to the entire group of boxes in a distribution list.
Attempting to implement such a system with present voicemail systems presents several problems. For example, in such a system, the number of messages one mailbox receives may be quite large, and navigating and managing these messages using the current controls available in a voicemail user interface may be quite difficult. Further, the large number of voicemails may be a strain on the database holding the pointers to the voicemails or the voicemails themselves. For example, searching, parsing, or retrieving the voicemails in a large database may incur an undesirable delay.
Further, traditional voicemail systems allow you to retrieve messages only in the order they are sent, or in reverse order, and may possibly allow messages to be designated as “urgent” to be placed at the beginning of the message list, ahead of those not marked “urgent.” However, if one were to get messages from one or more discussion groups, and the number of messages in the voicemail box grows considerably to hundreds or thousands of messages, the following problems render the traditional voicemail system unsatisfactory:
First, to find a particular message in the mailbox in the prior art voicemail system, one has to advance through every message before it, one by one, using a touch-tone command. With potentially thousands of messages through which to advance, this may take a considerable amount of time.
Second, in the prior art voicemail system, if a user decides they want to go through messages all from a particular individual or discussion group, one has to advance through potentially many messages from many other senders to get to the messages of interest.
Third, in the prior art voicemail system, if one wishes to delete all the messages in the mailbox, one may only be able to delete them one-by-one which may take considerable time to issue the touch-tone command for each message. A voicemail system may offer an option to delete all messages, but this results in a highly-intensive database query being performed which may take considerable time while the voicemail user waits on the telephone line. Further, this database query may be so intensive that it may result in other queries of the message list from other phone lines to be delayed or rejected by the database server. Also, with a large number of messages from various mailboxes available, one may wish to delete only a portion of those messages, choosing between urgent or normal messages, new or saved messages, or messages only from a specific box or from outside callers.
One or more of the embodiments of the present invention represent systems and methods that provide an improved interface control for a voicemail system and an improved database management system for a voicemail system, as further described below.
In operation, a voicemail 110 is sent to a distribution mailbox 120. The voicemail 110 may be sent by one of the receiver mailboxes 150-170, may originate with the user of the distribution mailbox 120, or may come from outside the voicemail system from a user without a mailbox. The voicemail 110 is received by the distribution mailbox 120, and then passed to the voicemail database processor 130. The voicemail database processor stored the voicemail 110 in the storage memory 140 and then awaits commands from the distribution mailbox 120. For example, the distribution mailbox 120 may instruct the voicemail database processor 130 to send copies of the voicemail to each of the receiver mailboxes 150-170 that is identified on a specific distribution list at the voicemail database processor 130.
The voicemail database processor 130 uses an improved voicemail database management system, as further described below, to process the commands from the distribution mailbox (or any other mailbox) quickly and efficiently.
Additionally, although only three receiver mailboxes are shown in
Also, the voicemail database processor is preferably a database running in a relational database environment such as a Microsoft SQL Server. The database processor preferably includes the tables shown in
The accounts table 200 identifies each active mailbox on the system. That is, each mailbox in the system includes an entry in the accounts table 200. Although the accounts table 200 of
The extension number associated with each mailbox is an indication of the telephone extension that a user dials in order to record messages in that mailbox. The internal ID is an internal references number creased by the voicemail database processor that is used as an internal reference for a specific extension number.
Each voicemail stored in the system is represented in the messages table 200. Thus, for each voicemail the system creates a data table with an assigned internal messaged ID 315. Further, the entry includes the internal ID of the mailbox of the sender 320. Alternatively, if the voicemail has been received from an outside call, the sender ID may be a different predetermined code such as zero, for example. Also included is the ID of a recipient's mailbox 325 of the recipient of the voicemail, as well as the name of the sound file containing the audio recording of the voicemail message. The name of the sound file is typically automatically signed internally by the voicemail system as field 330.
The message table 200 also includes an entry so that if a voicemail is forwarded from a first recipient to a second recipient and the first recipient records an additional introduction voicemail to be sent to the second recipient with the original voicemail, then when the voicemail entry in the messages table 300 is for the additional introduction e-mail, the voicemail entry also includes an ID of the forwarded message to which the additional introduction voicemail has been attached as field 335.
Also, the voicemail A entry 310 includes an indication of the date and time that the voicemail was originally delivered to a mailbox as field 340. Finally, a deleted flag 345 is included. As further described below with regard to the deletion process, the deletion flag is set to false until the voicemail A 310 is deleted at which point the deleted flag is set to true.
Although the messages table 300 shows seven data fields associated with each voicemail, a lesser or greater number of data fields may be employed. Additionally, although only two voicemails are illustrated in
The distribution list ID numbers are preferably automatically assigned by the voicemail system. Further, although the distribution lists table 400 shows two mailboxes, a much larger number of mailboxes is typically employed. Further, although the example mailboxes shown in
As mentioned above, the distribution list ID numbers and the member internal ID numbers are preferable automatically assigned by the voicemail system. Further, although the distribution list members table shows two distribution lists, in practice a much greater number of distribution lists is likely to be implemented. Similarly, although distribution list ID 1 510 is associated with three members of the distribution list, a greater of lesser number of members may be associated with a distribution list ID. Further, in practice the number of members of a distribution list may be quite large.
More specifically, and as further described below, if a user of the mailbox system desires to delete all voicemails that have been received from a particular sender mailbox, then the internal ID of the sender mailbox is stored in the second data field 620. Alternatively, if the user of the voicemail system wishes to delete all messages from all mailboxes, the second data field 620 may include a predetermined identifier, such as zero, for example. Also, if the user of the voicemail system wishes to delete all messages received from outside (these messages are not associated with a mailbox), then the second data field 620 may include a different predetermined identifier, such as one, for example.
The third data filed 630 preferably includes an entry designating the folder of the messages to be deleted. For example, the folders may include the logical groupings of new messages, saved messages, or all messages, for example. Further, each folder may be identified by a different predetermined identifier such as zero for the new folder, one for the saved folder, and negative one for the all messages folder. Additional folders and identifiers may be employed.
The fourth data field 640 indicates the priority status of the messages to be deleted. For example, the priority status may be logical grouping representing one of normal status, urgent status, or both normal and urgent status. Further, each priority status may be identified by a different predetermined identifier such as zero for the normal status, one for the urgent status, and negative one for all/both statuses. Additional statuses and identifiers may be employed.
The done flag 650 is set to a first value before the delete operation specified in the delete request table has been completed and is then updated to a second status once the delete request has been completed. For example, the done flag may be set to “False” before the delete operation has been completed and then set to “true” once the delete operation has been completed.
When a message is retrieved from a typical voicemail system, the user is offered several options after the message is played, such as moving the message to the “saved” folder, deleting the message, replying to the message, or skipping to the next message. However, as described above, such options are very rudimentary and are not sufficient for a high-use voicemail system.
Consequently, as illustrated in
For the message skipping functions, the system has selected a set of voicemail messages from the database. There is a subquery which has selected messages belonging to the user's mailbox. The set of messages may be further narrowed down according to whether the message is new or saved, and may be narrowed down further to include only messages from a specific mailbox. At this time, the message just played exists as the Current Record (the record or message currently selected). When the menu options are used to move forward or backward through a number of messages, the system will execute a number of “Move Next” or “Move Previous” statements to move forward or backward through the selected set of messages, changing the Current Record, to arrive at the message to which the user wants to skip.
The second function 720 allows a user to skip forward through the messaged. When a user first selects this function, the user is prompted for a number of messages to skip forward. The voicemail system then moves forward through the database records assigned to the user's mailbox until the specific number of messages have been skipped. In a first embodiment, the current message is not counted as the first of the messages to be skipped, but in an alternative embodiment the current message is counted
The third function 730 allows a user to cycle between “urgent” messages and “normal” messages. That is, messages received by the voicemail system may be associated with a priority status such as normal or urgent, as discussed above. If the last message retrieved was marked “urgent”, the system moves to the first “normal” message in the mailbox. If the last message retrieved was marked “normal”, the system resumes message retrieval with the first “urgent” message in the mailbox.
The fourth function 740 allows a user to retrieve voicemails from a mailbox specified by the user. That is, when a user selects the fourth function 740, the user is prompted for a mailbox number. If the mailbox is valid, a new database query is run on the message table to retrieve messages only from that mailbox. If the mailbox number entered is not valid, the user is prompted to re-enter the box number.
The fifth function 750 allows a user to retrieve voicemails from outside callers only. Similar to the fourth function, when a user selects the fifth function 750, a new database query is run on the message table to retrieve messages only from callers outside the system (not from a mailbox on the system).
The sixth function 760 allows a user to delete voicemails that have been received from a specific mailbox, or from outside callers. That is, when the sixth function 760 is selected, the voicemail system initiates a request to delete all messages from a particular mailbox or from outside callers. As further described below, this request is stored in a database as in the “Delete Requests” table described above. The sender, “urgent/normal” status, and “new/saved” status of the messages to be deleted are determined by the parameters of the last message retrieved in a first embodiment. Thus, in a first embodiment, the parameters in the deletion request are set to be the same as those in the last message retrieved. Consequently, when this option is selected, the user is told the box number, priority status, and folder of the messages to be deleted and asked to confirm that this is the desired action. If confirmation is made, the request is written to the “Delete Requests” table and the user is returned to the “message navigation menu.”
In an alternative embodiment, the user may be prompted to enter one or more of the box number, priority status, and folder fields. The voicemail system may be optionally reconfirm the user's selections before performing the delete request.
At step 830, the background task executed by the voicemail database processor executes a query on the message table to determine the delivery date and time of the newest message in the group to be deleted. The messages are searched according to the priority, folder, and box number identified in the request.
Next, at step 840, the background task executed by the voicemail database processor executes a query to determine the set of messages which were sent in the 24 hours preceding the message located in step 830, including the most recent message determined in step 830.
Then, at step 850, for each of the selected voicemails, the background task executed by the voicemail database processor updates the deleted flag in for the voicemail in the messages table by setting the deleted flag to True.
At step 860, the background task executed by the voicemail database processor determines if any more messages remain in the mailbox according to the selected delete criteria. If so, then the flowchart proceeds back to step 830. Conversely, if not additional voicemail messages remain in the mailbox for deletion, then the flowchart proceeds to step 870.
At step 870, the background task executed by the voicemail database processor moves to next request in “Delete Requests” table and the flowchart proceeds back to step 820.
Once the background task for message deletion searches for messages to be deleted, the system stores the list of messages in a database query. Starting at the first record present in the query, the system sets the “Deleted” flag, then moves to the next record. This continues until all records found are flagged as “Deleted” and the last record is reached.
Consequently, one or more of the embodiments of the present invention provide an improved control interface for a voicemail system and an improved database management system for a voicemail system. By allowing a user to skip messages back and forth, retrieve messages from a specific mailbox or outside the system, and switch between urgent and normal messages, an improved voicemail system provides a user with better access and retrievability of voicemails and greatly increases the ease and quality of the user experience. Additionally, the scheduling of the deletion operation as a background task also minimizes time delay experiences by the user to provide an improved experience.
While particular elements, embodiments, and applications of the present invention have been shown and described, it is understood that the invention is not limited thereto because modifications may be made by those skilled in the art, particularly in light of the foregoing teaching. It is therefore contemplated by the appended claims to cover such modifications and incorporate those features which come within the spirit and scope of the invention.
| Patent | Priority | Assignee | Title |
| Patent | Priority | Assignee | Title |
| 6233318, | Nov 05 1996 | MAVENIR, INC | System for accessing multimedia mailboxes and messages over the internet and via telephone |
| 7023968, | Nov 10 1998 | Intel Corporation | Message handling system |
| 7221742, | Jun 26 2002 | AT&T Intellectual Property I, L P | Voicemail box with caller-specific storage folders |
| 7620161, | Mar 29 2002 | AT&T Intellectual Property I, L P | Saving information from information retrieval systems |
| 20070274468, | |||
| 20080165937, | |||
| 20080167014, |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Date | Maintenance Fee Events |
| Jan 06 2016 | STOM: Pat Hldr Claims Micro Ent Stat. |
| Aug 04 2016 | M3551: Payment of Maintenance Fee, 4th Year, Micro Entity. |
| Jul 08 2020 | M3552: Payment of Maintenance Fee, 8th Year, Micro Entity. |
| Sep 23 2024 | REM: Maintenance Fee Reminder Mailed. |
| Date | Maintenance Schedule |
| Feb 05 2016 | 4 years fee payment window open |
| Aug 05 2016 | 6 months grace period start (w surcharge) |
| Feb 05 2017 | patent expiry (for year 4) |
| Feb 05 2019 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Feb 05 2020 | 8 years fee payment window open |
| Aug 05 2020 | 6 months grace period start (w surcharge) |
| Feb 05 2021 | patent expiry (for year 8) |
| Feb 05 2023 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Feb 05 2024 | 12 years fee payment window open |
| Aug 05 2024 | 6 months grace period start (w surcharge) |
| Feb 05 2025 | patent expiry (for year 12) |
| Feb 05 2027 | 2 years to revive unintentionally abandoned end. (for year 12) |