CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of co-pending U.S. patent application entitled, â€œSystem to Record and Analyze Voice Message Usage Informationâ€ , Ser. No. 11/250,763, filed on Oct. 13, 2005.

BACKGROUND OF THE INVENTION

1. Field

This invention relates generally to telecommunications, and more specifically, to a system to record and analyze voice message usage information.

2. Related Art

Voice mail systems, also known as voice message systems, gained popularity in the corporate world since its introduction in late 1970s. A user can leave a voice message at a voice mail system for another user without the assistance of an attendant or a secretary. Likewise, a user can listen to his or her voice messages from a voice mail system without the assistance of an attendant or a secretary.

Voice mail systems have since become an essential communications tool for businesses, government agencies, education institutions and communities. While providing convenience for the users to conduct business and for personal use, the usage of voice messages for communications creates a set of privacy problems.

In one example, John works for Central Realtors as a real estate broker. John uses the company's voice message system for both business and personal purposes. The company publishes a voice message usage policy, which respects the privacy of its employees. However, there is no tractable information to allow the company to distinguish between a business voice message and a personal voice message in order to apply usage measures as stated.

In another example, the management of Corner Technologies suspects that an employee has been leaking proprietary information to a competitor, and would like to collect evidence, including the employee's voice messages between Aug. 10 and Aug. 22, 2003. However, the employee has already deleted these voice messages, and there is no consistent backup procedure to ensure the availability of deleted voice messages.

Accordingly, there exists a need for a method and system for recording and analyzing voice message usage information. The present invention addresses such a need.

BRIEF SUMMARY OF THE INVENTION

A voice message system records voice message usage information by creating voice message records when a voice message is sent and when it is received. The voice message record includes: the voice message, a voice message sender identity, a voice message recipient identity, and voice message action records. A voice message action records includes a voice message action that specifies an action on the voice message, and a voice message action time that includes the time at which the action occurs. Voice message actions include sent, received, and listened. The system further includes a voice message analyzer for analyzing voice message records, and a voice message reporter for generating reports from an analysis by the analyzer. The voice message system provides tractable information for voice messages, allowing companies to enforce a voice message usage policy.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE FIGURES

FIG. 1 illustrates a Voice Message, a Voice Message Sender, and a Voice Message Recipient.

FIG. 2 illustrates a Voice Message Record.

FIG. 3 illustrates a Voice Message System.

FIG. 4 illustrates a process to record sending information about a Voice Message.

FIG. 5 illustrates a process to record receiving information about a Voice Message.

FIG. 6 illustrates a process to record listening information about Voice Message.

FIG. 7 illustrates a process of analyzing a plurality of Voice Message Records.

FIG. 8 illustrates a process of reporting on a plurality of Voice Message Records.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates a Voice Message 150, a Voice Message Sender 111 and a Voice Message Recipient 119. Voice Message 150 includes a recorded spoken message from Voice Message Sender 111 to Voice Message Recipient 119.

FIG. 2 illustrates a Voice Message Record. A Voice Message Record includes usage information about a Voice Message.

A Voice Message Record 200 includes a Voice Message 210, a Voice Message Sender Identity 220, a Voice Message Recipient Identity 230, and a plurality of Voice Message Action Records 250.

Voice Message Sender Identity 220 identifies the Voice Message Sender 111 who sends a Voice Message 210. Voice Message Recipient Identity 230 identifies the Voice Message Recipient 119 who receives the Voice Message 210.

A Voice Message Action Record 250 records one or more actions on Voice Message 210.

A Voice Message Action Record 250 includes a Voice Message Action 251 that specifies the action, and a Voice Message Action Time 255 that includes the time at which the action indicated in Voice Message Action 251 occurs. In one embodiment, Voice Message Action Time 255 includes the time of day at which the action occurs. In another embodiment, Voice Message Action Time 255 includes the time period during which the action occurs.

FIG. 3 illustrates a Voice Message System.

Voice Message System 310 connects to a Datastore 350. Datastore 350 stores a plurality of Voice Message Records. A Voice Message Sender 311 connects to Voice Message System 310 to send a Voice Message. A Voice Message Recipient 319 connects to a Voice Message System 310 to listen to a Voice Message.

Voice Message System 310 includes a plurality of processes. One embodiment includes processes to record sending information, receiving information, or listening information about a Voice Message. One embodiment includes processes of analyzing or reporting on the plurality of Voice Message Records. The processes are discussed in subsequent illustrations.

FIG. 4 illustrates a process to record sending information about a Voice Message. A Voice Message Sender 411 connects to a Voice Message System 410 and sends a Voice Message 480. The recipient of Voice Message 480 is Voice Message Recipient 419. Voice Message System 410 receives Voice Message 480. Voice Message System 410 creates a Voice Message Record.

Voice Message System 410 includes Voice Message 480 in the Voice Message Record for the sent Voice Message.

Voice Message System 410 includes a Voice Message Sender Identity of Voice Message Sender 411 in the Voice Message Record.

In one embodiment, Voice Message Sender 411 connects to Voice Message System 410 in a telephone call via a telephone system. In one embodiment, the telephone system provides to Voice Message System 410 a telephone extension number of the telephone used in the connection. Voice Message System 410 includes the telephone extension number in the Voice Message Sender Identity. In one embodiment, Voice Message System 410 obtains a user name based on the telephone extension number. Voice Message System 410 includes the user name in the Voice Message Sender Identity. In another embodiment, the telephone system provides Voice Message System 410 the calling party telephone number of the telephone call. Voice Message System 410 includes the calling party telephone number in the Voice Message Sender Identity. In one embodiment, the telephone system provides Voice Message System 410 the caller identity of the telephone call. Voice Message System 410 includes the caller identity in the Voice Message Sender Identity. In one other embodiment, Voice Message System 410 prompts Voice Message Sender 411 for information about Voice Message Sender 411. Voice Message Sender 411 provides Voice Message System 410 the information. Voice Message System 410 includes the information in the Voice Message Sender Identity. In one embodiment, the information includes a user identity for the Voice Message Sender 411.

In another embodiment, Voice Message Sender 411 connects to Voice Message System 410 via an electronic message system. Voice Message Sender 411 sends Voice Message 480 in an electronic message. In one embodiment, the electronic message system provides Voice Message System 410 a sender identity of the electronic message.

Voice Message System 410 includes the sender identity in the Voice Message Sender Identity.

Voice Message System 410 includes a Voice Message Recipient Identity of Voice Message Recipient 419 in the Voice Message Record.

In one embodiment, Voice Message Sender 411 connects to Voice Message System 410 in a telephone call via a telephone system. In one embodiment, the telephone system provides Voice Message System 410 the digits Voice Message Sender 411 dials when setting up the telephone call. Voice Message System 410 includes the dialed digits in the Voice Message Recipient Identity. In another embodiment, Voice Message System 410 prompts Voice Message Sender 411 for information about Voice Message Recipient 419. Voice Message Sender 411 provides Voice Message System 410 the information. Voice Message System 410 includes the information in the Voice Message Recipient Identity. In one embodiment, the information includes a user identity for the Voice Message Recipient 419.

In another embodiment, Voice Message Sender 411 connects to Voice Message System 410 via an electronic message system. Voice Message Sender 411 sends Voice Message 480 in an electronic message. In one embodiment, the electronic message system provides Voice Message System 410 a recipient identity of the electronic message.

Voice Message System 410 includes the recipient identity in the Voice Message Recipient Identity.

Voice Message System 410 further includes in the Voice Message Record a Voice Message Action Record with Voice Message Action set to Action Send. In one embodiment, Voice Message System 410 includes the current time of day in the Voice Message Action Time of the Voice Message Action Record. In another embodiment, the electronic message system provides Voice Message System 410 a sending time. The sending time is the time of day when Voice Message Sender 411 sends the electronic message that includes Voice Message 480. Voice Message System 410 includes the sending time in the Voice Message Action Time of the Voice Message Action Record.

In one embodiment, the Voice Message Sender Identity in a Voice Message Record indicates the location of the Voice Message Sender 411 identified by the Voice Message Sender Identity at the time when the Voice Message Sender 411 sends the Voice Message 480 that is included in the Voice Message Record. In one embodiment, the Voice Message Sender Identity includes a telephone extension number. In one embodiment, the telephone extension number indicates the location based on a telephone wiring plan of a Private Branch Exchange (PBX) that connects to the telephone extension. In one embodiment, the location is a cubicle. In another embodiment, the location is a conference room. In one other embodiment, the location is the front lobby of a building. In another embodiment, the Voice Message Sender Identity includes a calling party telephone number. In one embodiment, the calling party indicates the location based on information about the telephone service associated with the telephone number. In one embodiment, the telephone service is a residential telephone service; the location is a street address of the service subscription. In another embodiment, the telephone service is a mobile telephone service; the location is a street address of a wireless base station that serves the telephone call the Voice Message Sender 411 uses to send the Voice Message 480.

In one embodiment, Voice Message System 410 stores the Voice Message Record in Datastore 450. In one embodiment, Datastore 450 is a flash memory. In another embodiment, Datastore 450 is a hard disk. In yet another embodiment, Datastore 450 is a memory. In one other embodiment, Datastore 450 is a database. In one embodiment, Voice Message System 410 includes the Datastore 450.

FIG. 5 illustrates a process to record receiving information about a Voice Message.

When Voice Message System 510 receives a Voice Message 580 from a Voice Message Sender 511 for a Voice Message Recipient 519, Voice Message System 510 creates a Voice Message Record.

Voice Message System 510 includes Voice Message 580 in the Voice Message Record.

Voice Message System 510 includes a Voice Message Sender Identity of Voice Message Sender 511 in the Voice Message Record.

In one embodiment, Voice Message Sender 511 connects to Voice Message System 510 in a telephone call via a telephone system. In one embodiment, the telephone system provides Voice Message System 510 a telephone extension number of the telephone used in the connection. Voice Message System 510 includes the telephone extension number in the Voice Message Sender Identity. In one embodiment, Voice Message System 510 obtains a user name based on the telephone extension number. Voice Message System 510 includes the user name in the Voice Message Sender Identity. In another embodiment, the telephone system provides Voice Message System 510 the calling party telephone number of the telephone call. Voice Message System 510 includes the calling party telephone number in the Voice Message Sender Identity. In one embodiment, the telephone system provides Voice Message System 510 the caller identity of the telephone call. Voice Message System 510 includes the caller identity in the Voice Message Sender Identity. In one other embodiment, Voice Message System 510 prompts Voice Message Sender 11 for information about Voice Message Sender 511. Voice Message Sender 511 provides Voice Message System 510 the information. Voice Message System 510 includes the information in the Voice Message Sender Identity. In one embodiment, the information includes a user identity for the Voice Message Sender 511.

In another embodiment, Voice Message Sender 511 connects to Voice Message System 510 via an electronic message system. Voice Message Sender 511 sends Voice Message 580 in an electronic message. In one embodiment, the electronic message system provides Voice Message System 510 a sender identity of the electronic message.

Voice Message System 510 includes the sender identity in the Voice Message Sender Identity.

Voice Message System 510 includes a Voice Message Recipient Identity of Voice Message Recipient 519 in the Voice Message Record.

In one embodiment, Voice Message Sender 511 connects to Voice Message System 510 in a telephone call via a telephone system. In one embodiment, the telephone system provides Voice Message System 510 the digits the phone system receives for setting up the telephone call. Voice Message System 510 includes the received digits in the Voice Message Recipient Identity. In one embodiment, Voice Message System 510 maps the received digits to a telephone extension number. Voice Message System 510 includes the telephone extension number in the Voice Message Recipient Identity. In one embodiment, Voice Message System 510 obtains a user name based on the telephone extension number. Voice Message System 510 includes the user name in the Voice Message Recipient Identity. In another embodiment, Voice Message System 510 obtains a user name based on the received digits. Voice Message System 510 includes the user name in the Voice Message Recipient Identity. In one other embodiment, Voice Message System 510 prompts Voice Message Sender 511 for information about Voice Message Recipient 519. Voice Message Sender 511 provides Voice Message System 510 the information. Voice Message System 510 includes the information in the Voice Message Recipient Identity. In one embodiment, the information includes a user identity for the Voice Message Recipient 519.

In another embodiment, Voice Message Sender 511 connects to Voice Message System 510 via an electronic message system. Voice Message Sender 511 sends Voice Message 580 in an electronic message. In one embodiment, the electronic message system provides Voice Message System 510 a recipient identity of the electronic message. Voice Message System 510 includes the recipient identity in the Voice Message Recipient Identity.

Voice Message System 510 further includes a Voice Message Action Record in the Voice Message Record with Voice Message Action set to Action Receive. In one embodiment, Voice Message System 510 includes the current time of day in the Voice Message Action Time of the Voice Message Action Record. In one embodiment, Voice Message 580 is sent to more than one Voice Message Recipient. A Voice Message Action Record would then be created for the Voice Message received by each Voice Message Recipient.

In one embodiment, Voice Message System 510 stores the Voice Message Record in Datastore 550. In one embodiment, Datastore 550 is a flash memory. In another embodiment, Datastore 550 is a hard disk. In yet another embodiment, Datastore 550 is a memory. In one other embodiment, Datastore 550 is a database. In one embodiment, Voice Message System 510 includes the Datastore 550.

FIG. 6 illustrates a process to record listening information about Voice Message.

In one embodiment, a User 619 connects to Voice Message System 610. User 619 submits to Voice Message System 610 an identity. In one embodiment, Voice Message System 610 selects from Datastore 650 a Voice Message Record with Voice Message Recipient Identity matching the submitted identity, and that includes a Voice Message Action Record with Voice Message Action of Action Receive.

Voice Message System 610 updates the selected Voice Message Record with a Voice Message Action Record. The Voice Message Action Record has Voice Message Action set to Action Listen. In one embodiment, Voice Message System 610 updates the selected Voice Message Record after the Voice Message Record is selected. In one embodiment, Voice Message System 610 updates the selected Voice Message Record after User 619 listens to the Voice Message included in the selected Voice Message Record. In one embodiment, Voice Message System 610 includes in the Voice Message Action Time of the Voice Message Action Record the time of day when User 619 listens to the Voice Message. In one embodiment, Voice Message System 610 includes in the Voice Message Action Time of the Voice Message Action Record the time period during when User 619 listens to the Voice Message. In one embodiment, User 619 deletes the Voice Message after listening to the Voice Message. Voice Message System 610 includes a Voice Message Action Record in the Voice Message Record with Voice Message Action set to Action Delete. In one embodiment, User 619 forwards the Voice Message to another Voice Message Recipient. Voice Message System 610 includes a Voice Message Action Record in the Voice Message Record with Voice Message Action set to Action Forward. In one embodiment, Voice Message System 610 additionally creates a new Voice Message Record for the forwarded Voice Message with Voice Message Action Record set to Action Sent.

In one embodiment, when a User 619 wants to listen to a voice message, Voice Message System 610 selects a voice message that has not been listened to. In this embodiment, Voice Message System 610 selects from Datastore 650 a Voice Message Record that includes a Voice Message Recipient Identity matching the identity submitted by the User 619, and that includes a Voice Message Action Record with Voice Message Action of Action Receive, and that does not include a Voice Message Action Record with Voice Message Action of Action Listen.

In another embodiment, when a User 619 wants to listen to a voice message, Voice Message System 650 selects a voice message even if the voice message has been listened to. Voice Message System 610 selects from Datastore 650 a Voice Message Record that includes a Voice Message Recipient Identity matching the identity submitted by the User 619, and that includes a Voice Message Action Record with Voice Message Action of Action Receive. Each time the User 619 listens to the Voice Message included in the selected Voice Message Record, Voice Message System 610 adds a Voice Message Action Record to the selected Voice Message Record.

In one embodiment, Voice Message Action Record includes a User Action Attribute. In one embodiment, User Action Attribute includes information about the connection over which a User 619 listens to a voice message. In one embodiment, the information about the connection indicates the location where the User 619 listens to the voice message. In one embodiment, a User 619 connects to Voice Message System 610 in a telephone call via a telephone system to listen to a voice message. In one embodiment, the telephone system provides Voice Message System 610 a telephone extension number of the telephone used in the connection. Voice Message System 610 includes the telephone extension number in the User Action Attribute. In another embodiment, the telephone system provides Voice Message System 610 a calling party telephone number of the telephone call. Voice Message System 610 includes the calling party telephone number in the User Action Attribute. In yet another embodiment, the telephone system provides Voice Message System 610 a caller identity of the telephone call. Voice Message System 610 includes the caller identity in the User Action Attribute.

In one embodiment, User Action Attribute includes the identity of a first User who listens to a voice message for a second User. In one embodiment, a first User connects to Voice Message System 610 to listen to a voice message. The first User submits to Voice Message System 610 an identity of the first User and an identity of a second User. Voice Message System 610 selects a Voice Message Record with Voice Message Recipient Identity matching the identity of the second User. Voice Message System 610 updates the selected Voice Message Record with a Voice Message Action Record. Voice Message System 610 includes the identity of the first User in the User Action Attribute. In this embodiment, a manager can delegate to her secretary to listen to her voice messages with proper recording of usage information.

In one embodiment, Voice Message System 610 stores the updated Voice Message Record in Datastore 650. In one embodiment, Datastore 650 is a flash memory. In another embodiment, Datastore 650 is a hard disk. In yet another embodiment, Datastore 650 is a memory. In one other embodiment, Datastore 650 is a database. In one embodiment, Voice Message System 610 includes the Datastore 650.

FIG. 7 illustrates a process of analyzing a plurality of Voice Message Records.

Voice Message System includes a Voice Message Analyzer 710. Voice Message Analyzer 710 connects to Datastore 750. Voice Message Analyzer 710 analyses a plurality of Voice Message Records regarding usage information. In one embodiment, the analysis answers a query. In one embodiment, the result of the analysis is for generating a report.

In one embodiment, Voice Message Analyzer 710 answers the query â€œWho has received a voice message from John Smith?â€ Voice Message Analyzer 710 selects from Datastore 750 all Voice Message Record with Voice Message Sender Identity that matches the name â€œJohn Smithâ€ , and that includes a Voice Message Action Record with Voice Message Action of Action Receive. Voice Message Analyzer 710 extracts from the selected zero or more Voice Message Record the Voice Message Recipient Identity as the result of the analysis. In one embodiment, John Smith uses a plurality of telephones to send voice messages, Voice Message Analyzer 710 matches the Voice Message Sender Identity against a plurality of telephone numbers John Smith uses.

In one embodiment, Voice Message Analyzer 710 answers the query â€œWho has sent a voice message to telephone extension number 3325?â€ Voice Message Analyzer 710 selects from Datastore 750 all Voice Message Record with Voice Message Recipient Identity that matches telephone extension number â€œ3325â€ , and that includes a Voice Message Action Record with Voice Message Action of Action Send. Voice Message Analyzer 710 extracts from the selected zero or more Voice Message Record the Voice Message Sender Identity as the result of the analysis.

In another embodiment, Voice Message Analyzer 710 retrieves a â€œlist of voice messages being sent during the half hour before 3 p.m., Jun. 29, 2005, the closing time for the New York Stock Exchange.â€ Voice Message Analyzer 710 selects from Datastore 750 all Voice Message Record that includes a Voice Message Action Record with Voice Message Action Time between 2:30 p.m., and 3 p.m., on Jun. 29, 2005, and with Voice Message Action of Action Send. Voice Message Analyzer 710 retrieves from the selected zero or more Voice Message Record the Voice Message as the result of the analysis.

In one embodiment, Voice Message Analyzer 710 answers the query â€œDid Maria Anderson listen to a voice message from telephone number â€œ408-234-5678â€ on Jul. 10, 2001?â€ Voice Message Analyzer 710 selects from Datastore 750 all Voice Message Record that includes Voice Message Recipient Identity matching the name â€œMaria Andersonâ€ and Voice Message Sender Identity matching the telephone number â€œ408-234-5678â€ , and that includes a Voice Message Action Record with Voice Message Action of Action Listen, and with Voice Message Action Time matching Jul. 10, 2001. If one or more Voice Message Record is selected, Voice Message Analyzer 710 indicates a â€œyesâ€ as the result of the analysis. If no Voice Message Record is selected, Voice Message Analyzer 710 indicates a â€œnoâ€ as the result of the analysis.

In yet another embodiment, Voice Message Analyzer 710 retrieves a â€œlist of senders who had mentioned the word â€œEnronâ€ and â€œshort sellâ€ in a voice message he or she sent on Aug. 17, 2003?â€ Voice Message Analyzer 710 selects from Datastore 750 all Voice Message Record that includes Voice Message containing the audio patterns of â€œEnronâ€ and â€œshort sellâ€ , and that includes a Voice Message Action Record with Voice Message Action of Action Send, and with Voice Message Action Time matching â€œAug. 17, 2003â€ . Voice System retrieves from the selected zero or more Voice Message Record the Voice Message Sender Identity as the result of the analysis.

In one other embodiment, Voice Message Analyzer 710 answers the query â€œAmong those who has listened to a voice message from John Smith on May 20, 2005, who has sent a voice message to the telephone number 408-222-3333 on May 20, 2005 or May 21, 2005?â€ Voice Message Analyzer 1010 selected from Datastore 750 a first group of Voice Message Record that includes Voice Message Sender Identity matching the name â€œJohn Smithâ€ and that includes a Voice Message Action Record with Voice Message Action of Action Listen and with Voice Message Action Time matching â€œMay 20, 2005â€ . Voice Message Analyzer 710 extracts the Voice Message Recipient Identity from the first group of Voice Message Record. Voice Message Analyzer 710 selects from Datastore 750 a second group of Voice Message Record that includes Voice Message Recipient Identity matching the telephone number â€œ408-222-3333â€ , and that includes Voice Message Sender Identity matching one of the extracted Voice Message Recipient Identity, and that includes a Voice Message Action Record with Voice Message Action of Action Send and with Voice Message Action Time matching â€œMay 20, 2005â€ or â€œMay 21, 2005â€ . Voice Message Analyzer 710 retrieves from the second group of Voice Message Record the Voice Message Sender Identity as the result of the analysis.

In one embodiment, Voice Message Analyzer 710 retrieves a â€œlist of all voice messages of Dave Leach's family, where Dave's family's phone numbers are 408-123-3456, 650-233-4455, and 650-233-6890â€ . Voice Message Analyzer 710 selects from Datastore 750 a first group of Voice Message Record with Voice Message Recipient Identity that matches â€œDave Leachâ€ , and with Voice Message Sender Identity that matches one of Dave's family's phone numbers, and that includes a Voice Message Action Record with Voice Message Action of Action Receive. Voice Message Analyzer 710 further selects from Datastore 750 a second group of Voice Message Record with Voice Message Sender Identity that matches â€œDave Leachâ€ , and with Voice Message Recipient Identity that matches one of Dave's family's phone numbers, and that includes a Voice Message Action Record with Voice Message Action of Action Send. Voice Message Analyzer 710 retrieves from the first group and the second group of Voice Message Record the Voice Message as the result of the analysis.

In one embodiment, Voice Message Analyzer 710 retrieves â€œlist of all voice messages that match a pattern of being sent to competitors within 24 hours of a board meeting.â€ Voice Message Analyzer 710 selects from Datastore 750 a group of Voice Message Records with Voice Message Recipient Identity that matches a list of competitors, with Voice Message Action Time within 24 hours of a date and time of a board meeting, and that includes a Voice Message Action of Action Sent. The Voice Message Analyzer 710 retrieves from this group of Voice Message Records the Voice Message Sender Identity.

The analysis illustrated in FIG. 7 represents examples regarding usage information. It will be evident to skilled in the art to formulate similar analysis in order to provide other results regarding usage information.

FIG. 8 illustrates a process of reporting on a plurality of Voice Message Records.

Voice Message System includes a Voice Message Reporter 830. In one embodiment, Voice Message Reporter 830 instructs Voice Message Analyzer 810 to conduct an analysis. In one embodiment, Voice Message Reporter 830 instructs the Voice Message Analyzer 850 based on a Report Specification.

In one embodiment, a Report Specification is based on corporate usage policies. In another embodiment, a Report Specification is based on governmental usage regulations. In another embodiment, a Report Specification is based on public service usage policies.

In one embodiment, a Report Specification includes an analysis to be conducted in order to generate a report. In another embodiment, a Report Specification includes a format of a report. In yet another embodiment, a Report Specification includes a method to publish a report. In one other embodiment, a Report Specification includes timing information. In one embodiment, the timing information includes a scheduled time to generate a report, such as 5 pm on Jul. 26, 2005, daily at 6 am, or every hour during business days. In one embodiment, Voice Message Reporter 830 includes a clock. In one embodiment, Voice Message Reporter 830 instructs Voice Message Analyzer 810 to conduct an analysis included in a Report Specification when the time of day indicated by the clock matches the timing information in the Report Specification.

In one embodiment, Voice Message Reporter 830 connects to a Report Specification Datastore 890. Report Specification 890 stores a plurality of Report Specification. In one embodiment, Voice Message Reporter 830 retrieves a Report Specification from Report Specification Datastore 890. In one embodiment, Voice Message Reporter 830 instructs Voice Message Analyzer 810 to conduct the analysis included in the retrieved Report Specification. In one embodiment, Voice Message Reporter 830 receives the result of the analysis to generate a report. In one embodiment, Voice Message Reporter 830 generates the report based on the format and publishing method included in the Report Specification.

In another embodiment, an operator submits a Report Specification to Voice Message Reporter 830. In one embodiment, Voice Message Reporter 830 instructs Voice Message Analyzer 810 to conduct the analysis included in the submitted Report Specification.

Foregoing described embodiments of the invention are provided as illustrations and descriptions. They are not intended to limit the invention to precise form described. In particular, it is contemplated that functional implementation of invention described herein may be implemented equivalently in hardware, software, firmware, and/or other available functional components or building blocks, and that networks may be wired, wireless, or a combination of wired and wireless. Other variations and embodiments are possible in light of above teachings, and it is thus intended that the scope of invention not be limited by this Detailed Description, but rather by Claims following.