Message storage and delivery system

BACK GROUND OF THE INVENTION

Field of the Invention

This invention relates to a system and method for storing and delivering messages and, more particularly, to a system and method for storing messages and for delivery the messages through a network, such as the Internet, or a telephone line to an intended recipient.

Description of the Prior Art

One type of system, such as the one disclosed in <patcit id="pcit0001" dnum="US5257112A"><text>U.S. Pat. No. 5,257,112 to Okada</text></patcit>, can route an incoming call to a particular facsimile machine based upon codes entered with telephone push-buttons by the sender of the message. Another type of system, such as the one disclosed in <patcit id="pcit0002" dnum="US5115326A"><text>U.S. Pat. No. 5,115,326 to Burgess et al</text></patcit>. or in <patcit id="pcit0003" dnum="US5247591A"><text>U.S. Pat. No. 5,247,591 to Baran</text></patcit>, requires the sender to use a specially formatted cover page which is read by the system. This type of system, however, burdens the sender, who may very well be a client or customer, by requiring the sender to take special steps or additional steps to transmit a facsimile message. These systems are therefore not very effective or desirable.

Another type of routing system links a facsimile machine to a Local Area Network (LAN) in an office. For instance, in the systems disclosed in the patents to Baran and Burgess et al., after the system reads the cover sheet to determine the intended recipient of the facsimile message, the systems send an E-mail message to the recipient through the local network connecting the facsimile machine to the recipient's computer. Other office systems, such as those in <patcit id="pcit0004" dnum="US5091790A"><text>U.S. Pat. No. 5,091,790 to Silverberg</text></patcit> and <patcit id="pcit0005" dnum="US5291546A"><text>U.S. Pat. No. 5,291,546 to Giler et al.</text></patcit>, are linked to the office's voice mail system and may leave a message with the intended recipient that a facsimile message has been received. Some systems which are even more advanced, such as those in <patcit id="pcit0006" dnum="US5317628A"><text>U.S. Pat. No. 5,317,628 to Misholi et al</text></patcit>. and <patcit id="pcit0007" dnum="US5333266A"><text>U.S. Pat. No. 5,333,266 to Boaz et al.</text></patcit>, are connected to an office's local network and provide integrated control of voice messages, E-mail messages, and facsimile messages.

The various systems for routing facsimile messages, and possibly messages of other types received in the office, are very sophisticated and expensive systems. While these office systems are desirable in that they can effectively route the messages at the office to their intended recipients, the systems are extremely expensive and only those companies with a great number of employees can offset the costs of the system with the benefits that the system will provide to their company. Thus, for most businesses, it still remains a problem to effectively and quickly route messages to the intended recipients. It also remains a problem for most businesses to route the messages in a manner which can preserve the confidential nature of the messages.

Even for the businesses that have a message routing system and especially for those that do not have any type of system, it is usually difficult for a person to retrieve facsimile messages while away from the office. Typically, a person away on business must call into the office and be informed by someone in the office as to the facsimile messages that have been received. Consequently, the person must call into the office during normal business hours while someone is in the office and is therefore limited in the time that the information in a facsimile message can be relayed.

If the person away on business wants to look at the facsimile message, someone at the office must resend the message to a facsimile machine accessible to that person. Since this accessible machine is often a facsimile machine at another business or at a hotel where the person is lodging, it is difficult for the person to receive the facsimile message without risking disclosure of its contents. Further, since someone at the person's office must remember to send the message and since someone at the accessible facsimile machine must route the message to the person away from the office, the person may not receive all of the facsimile messages or may have to wait to receive the messages.

The retrieval of facsimile messages, as well as voice mail messages, while away from the office is not without certain costs. For one, the person often must incur long distance telephone charges when the person calls the office to check on the messages and to have someone in the office send the messages to another facsimile. The person will then incur the expenses of transmitting the message to a fax bureau or hotel desk as well as the receiving location's own charges for use of their equipment. While these charges are certainly not substantial, the charges are nonetheless expenses incurred while the person is away from the office.

Overall, while the facsimile machine is an indispensable piece of equipment for many businesses, the facsimile machine presents a number of problems or costs. Many businesses or households are disadvantaged since they are unable to reap the benefits of the facsimile machine. For the businesses that do have facsimile machines, the businesses must incur the normal costs of operating the facsimile machine in addition to the costs that may be incurred when the facsimile machine or machines are unable to receive a message. Further, the facsimile messages may not be efficiently or reliably routed to the intended recipient and may have its contents revealed during the routing process. The costs and problems in routing a facsimile message are compounded when the intended recipient is away from the office.

Many of the problems associated with facsimile messages are not unique to just facsimile messages but are also associated with voice mail messages and data messages. With regard to voice messages, many businesses do not have voice mail systems and must write the message down. Thus, the person away from the office must call in during normal office hours to discover who has called. The information in these messages are usually limited to just the person who called, their number, and perhaps some indication as to the nature of the call. For those businesses that have voice mail, the person away from the office must call in and frequently incur long distance charges. Thus, there is a need for a system for storing and delivery voice messages which can be easily and inexpensively accessed at any time.

With regard to data messages, the transmission of the message often requires some coordination between the sender and the recipient. For instance, the recipient's computer must be turned on to receive the message, which usually occurs only when someone is present during normal office hours. Consequently, the recipient's computer is usually only able to receive a data message during normal office hours. Many households and also businesses may not have a dedicated data line and must switch the line between the phone, computer, and facsimile. In such a situation, the sender must call and inform the recipient to switch the line over to the computer and might have to wait until the sender can receive the message. The retransmission of the data message to another location, such as when someone is away from the office, only further complicates the delivery. It is therefore frequently difficult to transmit and receive data messages and is also difficult to later relay the messages to another location.

STATEMENT OF INVENTION

The present invention and various embodiments thereto are set forth in the appended claims.

SUMMARY OF THE INVENTION

It is an object of the invention to reliably and efficiently route messages to an intended recipient.

It is another object of the invention to route messages to the intended recipient while maintaining the contents of the message confidential.

It is another object of the invention to enable the intended recipient to access the messages easily and with minimal costs.

It is a further object of the invention to permit the simultaneous receipt of more than one message on behalf of the intended recipient.

It is a further object of the invention to enable the intended recipient of a message to access the message at any time and at virtually any location world-wide.

It is yet a further object of the invention to enable the intended recipient of a message to browse through the received messages.

It is yet a further object of the invention to quickly notify an intended recipient that a message has been received.

It is still another object of the invention to receive messages of various types.

It is still another object of the invention to deliver messages according to the preferences of the intended recipient.

It is still a further object of the invention to record and track correspondence, such as facsimile messages, voice mail messages, and data transfers.

To achieve the foregoing and other objects, in accordance with the present invention, as embodied and broadly described herein, a message storage and delivery system receives an incoming call and detects an address signal associated with the incoming call, the address signal being associated with a user of the message storage and delivery system. A message accompanied with the address signal is then received and converted from a first file format to a second file format. The message is stored in the second file format within a storage area and is retrieved after a request has been received from the user. At least a portion of the message is then transmitted to the user over a network with the second file format being a mixed media page layout language.

In another aspect, a network message storage and delivery system comprises a central processor for receiving an incoming call, for detecting an address signal on the incoming call, for detecting a message on the incoming call, and for placing the message in a storage area. The address signal on the incoming call is associated with a user of the network message storage and delivery system. A network server receives the message from the storage area, converts the message into a mixed media page layout language, and places the message in the storage area. When the network server receives a request from the user over the network, the network server transmits at least a portion of the message over the network to the user.

Preferably, the network storage and delivery system can receive facsimile messages, data messages, or voice messages and the network is the Internet. The messages are converted into hyper-text mark-up language and the user is notified that a message has arrived through E-mail or through a paging system. A listing of the facsimile messages may be sent to the user in one of several formats. These formats include a textual only listing or a listing along with a full or reduced size image of the first page of each message. A full or reduced size image of each page of a message in the listing may alternatively be presented to the user.

Another aspect of the invention relates to a method of storing and delivering a message for a user. The method comprises the steps of receiving an incoming call and detecting an address signal associated with the incoming call, with the address signal associated with a user. A message accompanied with the address signal is received in a first file format, converted into a second file format, and stored in a storage area. A request for the message is received from the user and the message is retrieved from the storage area and at least a portion of the message is transmitted to the user. The transmission of the portion of the message occurs over a network and the step of converting the message converts the message into a mixed media page layout language.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in, and form a part of, the specification, illustrate an embodiment of the present invention and, together with the description, serve to explain the principles of the invention. In the drawings: <ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">FIG. 1</figref> is a block diagram illustrating the connections of a message storage and delivery system MSDS;</li><li><figref idref="f0002">FIG. 2</figref> is an overall flow chart of operations for transmitting a message to the MSDS of <figref idref="f0001">FIG. 1</figref>;</li><li><figref idref="f0003">FIG. 3</figref> is an overall flow chart of operations for receiving a message stored at the MSDS of <figref idref="f0001">FIG. 1</figref>;</li><li><figref idref="f0004">FIGS. 4(A)</figref> and <figref idref="f0005">(B)</figref> are flowcharts of operations for generating HTML files according to user preferences;</li><li><figref idref="f0006">FIG. 5</figref> is a flowchart of operations for generating requested information;</li><li><figref idref="f0007">FIG. 6</figref> is a flowchart of operations for converting a facsimile message into HTML files;</li><li><figref idref="f0008">FIG. 7</figref> is an exemplary display of a first page of a facsimile message according to a fourth display option;</li><li><figref idref="f0009">FIG. 8</figref> is a flowchart of operations for converting a voice message into an HTML file;</li><li><figref idref="f0010">FIG. 9</figref> is a flowchart of operations for converting a data message into an HTML file;</li><li><figref idref="f0011">FIG. 10</figref> is a flowchart of operations for detecting a type of call received at the MSDS 10;</li><li><figref idref="f0012">FIG. 11</figref> is a flowchart of operations for receiving voice messages;</li><li><figref idref="f0013">FIG. 12</figref> is a flowchart of operations for interacting with an owner's call;</li><li><figref idref="f0014">FIG. 13</figref> is a more detailed block diagram of the MSDS 10;</li><li>FIG. 14 is a block diagram of the central processor in <figref idref="f0014">FIG. 13</figref>;</li><li><figref idref="f0015 f0016">FIG. 15</figref> is a block diagram of the Internet Server of <figref idref="f0014">FIG. 13</figref>;</li><li><figref idref="f0017">FIGS. 16(A)</figref> and <figref idref="f0018">16(B)</figref> depict possible software layers for the Internet Server of <figref idref="f0014">FIG. 13</figref>.</li></ul>

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

Reference will now be made in detail to the preferred embodiments of the invention, examples of which are illustrated in the accompanying drawings.

With reference to <figref idref="f0001">FIG. 1</figref>, a message storage and delivery system (MSDS) 10 is connected to a central office 20 of the telephone company through at least one direct inward dialing (DID) trunk 15. With each call on the DID trunk 15, an address signal indicating the telephone number being called is provided to the MSDS 10. The DID trunk 15 can carry a large number of telephone numbers or addresses. Preferably, the DID trunk 15 comprises a number of DID trunks 15 connected in parallel between the central office 20 and the MSDS 10 so that the MSDS 10 can simultaneously receive more than one call and, moreover, can simultaneously receive more than one call for a single telephone number or address.

The central office 20 is connected to a number of third parties. For instance, the central office 20 may be connected to a facsimile machine 24, a telephone set 26, and to a computer 28 with each connection being made through a separate telephone line. While a single computer 28 is shown in the figure, the single computer 28 may actually represent a local area network which is connected through the central office 20 to the MSDS 10. Although the facsimile machine 24, telephone set 26, and computer 28 have been shown on separate lines, it should be understood that one or more of these devices could share a single line.

The MSDS 10 is also connected to a network, preferably the Internet World Wide Web 30. Although the Internet 30 has been shown as a single entity, it should be understood that the Internet 30 is actually a conglomeration of computer networks and is a constantly evolving and changing structure. The MSDS 10 therefore is not limited to the current structure or form of the Internet 30 but encompasses any future changes or additions to the Internet 30. Further, the MSDS 10 is shown as being directly connected to the Internet 30, such as through its own node or portal. The MSDS 10, however, may be practiced with any suitable connection to the Internet 30, such as through an intermediate Internet access provider.

With reference to <figref idref="f0002">FIG. 2</figref> depicting an overall operation of the invention, a telephone call directed to a number serviced by the MSDS 10 is initiated at step 40 by a third party, for instance, through the facsimile machine 24, telephone set 26, or computer 28. The incoming telephone call may therefore carry a facsimile message, a voice message, or a data message. At step 42, the address signal associated with the initiated call is routed through the central office 20, over the DID trunk 15, and to the MSDS 10.

When the call reaches the MSDS 10, the call is routed within the MSDS 10 in a manner that will be described in more detail below with reference to <figref idref="f0014">FIG. 13</figref>. At step 46, the MSDS 10 answers the telephone call and receives the address signal from the DID trunk 15. Next, at step 48, the call is established between the MSDS 10 and the third party and, at step 50, the MSDS 10 receives the message transmitted over the telephone line. The message is stored at step 52, a database within the MSDS 10 is updated at step 54, and the intended recipient of the message is notified at step 56. The intended recipient of the message uses the services provided by the MSDS 10 and will hereinafter be referred to as a user. At step 58, the message is converted into hyper-text mark-up language (HTML).

After the MSDS 10 receives a message for one of its users, the user can then communicate with the MSDS 10 at any time and at any location by connecting to the Internet World Wide Web 30 and retrieving the message stored within the MSDS 10. With reference to <figref idref="f0003">FIG. 3</figref>, at step 60 the user first connects to the Internet 30, such as through a personal computer 32 which may be connected to the Internet 30 in any suitable manner, such as through its own portal or node or through some intermediate access provider. The personal computer 32 is not limited to a single computer but may instead comprise a network of computers, such as a local area network within an office.

Once connected with the Internet 30, at step 62, the user accesses with a hyper-text browser the Universal Resource Locator (URL) associated with his or her MSDS 10 mailbox. The computer 32 may use any suitable hypertext browser, such as Netscape, to access the mailbox. A Hypertext Transfer Protocol Deamon (HTTPD) within the MSDS 10 receives the URL request at step 64 and, at step 66, requests user authentication. The user then supplies his or her ID and password at step 68 and, if found valid at step 70, the MSDS 10 provides the computer 32 with access to the mailbox at step 72. If the ID and password are invalid, as determined at step 70, then the HTTPD sends the computer 32 an authentication failure message at step 74.

After the user gains access to the mailbox at step 72, the user can request information stored within the MSDS 10. The MSDS 10 receives the request at step 76 and, at step 78, determines whether the information exists. As is common practice, the MSDS 10 also determines the validity of the request at step 78. The request from the user will include the mailbox number for the user, the message identifier, display preferences, and, if the message is a facsimile message, a page identifier. If for any reason the request is invalid, such as when a hacker is attempting to gain access to privileged information, the request for the information will be terminated.

If the requested information is available, then at step 80 the information is transmitted through the Internet 30 to the user's computer 32. If, on the other hand, the information does not exist, then at step 82 the MSDS 10 will generate the requested information and then send the information to the user's computer through the Internet 30 at step 80.

Prior to gaining access to the mailbox at step 72, the user is preferably sent a greeting page or other such type of information which permits the user to learn about the services provided by the MSDS 10, open an account with the MSDS 10, or gain access to an account. Once access is provided at step 72, the user is provided with information indicating the total number of messages stored in his or her mailbox within the MSDS 10. Preferably, the information sent by the MSDS 10 indicates the total number of messages for each type of message and also the total number of saved messages versus the total number of new messages.

The user is also preferably given the option at this step to change account information. The account information might include the E-mail address for the user, the manner in which messages are to be reviewed, the user's pager information, as well as other user preferences. The display options and other user preferences will be discussed in further detail below.

The general information HTML file which indicates the total number of different messages is provided with a number of anchors, which are also termed links or references. In general, an anchor permits a user on the computer 32 to retrieve information located on another file. For instance, an anchor to a listing of facsimile messages is preferably provided on the display of the total number of messages. When the user selects the anchor for the facsimile list, the MSDS 10 pulls up and displays the file containing the list of facsimiles, such as a file "faxlist.html. " The other types of messages, such as voice messages and data messages, would have similar anchors on the general information page directed to their respective HTML listing files.

When a new message is received at step 54 in <figref idref="f0002">FIG. 2</figref>, the user's mailbox is updated to display the total number and types of messages. The MSDS 10 might also update other files in addition to the total listing of messages. Additionally, at this time, the MSDS 10 sends an E-mail message to the user's computer 32 to inform the user of the newly arrived message. The MSDS 10 could also send notice to the user through a paging system so that the user receives almost instantaneous notice that a message is received.

The MSDS 10 also generates additional information according to the user's preferences. These preferences on how the MSDS 10 is configured for the user include options on how the messages are reviewed. With facsimile messages, for instance, the user can vary the amount or the type of information that will be supplied with the listing of the facsimile messages by selecting an appropriate option. Other options are also available so that the user can custom fit the MSDS 10 to the user's own computer 32 or own personal preferences.

For instance, when a facsimile message is received, the MSDS 10, at step 54, will update the total listing of all messages to indicate the newly received message and may additionally generate the HTML files for the newly received facsimile message according to the user's preferences. When the user later requests information on the message at step 76, the HTML information has already been generated and the MSDS 10 may directly send the requested information to the user at step 80. If, on the other hand, the user desires to view the message according to one of the other options, the MSDS 10 will generate the HTML files at step 82 according to that other option at the time of the request.

A first option available to the user for viewing a facsimile message is a textual only listing of the messages. The information on the textual listing preferably includes the date and time that the message was received at the MSDS 10, the telephone number from where the message was transmitted, the number of pages, the page size, and the size of the message in bytes. The messages, of course, could be listed with other types of information. When the user selects one of the facsimile messages on the list, a request is sent to the HTTPD within the MSDS 10 causing the message to be downloaded via the Internet 30 to the user's computer 32. Once the message is received by the computer 32, the message can be displayed, printed, or saved for further review.

The second through fifth options allow the user to preview an image of the facsimile message before having the message downloaded from the MSDS 10 through the Internet 30 and to the computer 32. The second option permits the user to view the list of messages with a reduced size image of the cover page next to each entry on the list. When the user selects one of the messages on the list, the selected facsimile message is transmitted through the Internet 30 to the computer 32. The user may also scroll through the listings if all of the message cannot be displayed at one time on the computer 32.

The third option provides the user with a full size view of the cover page of each facsimile message. The user can quickly scroll through the cover pages of each message without downloading the entire message to the computer 32. The full size view of the cover pages permit the user to clearly discern any comments that may be placed on the cover page, which may not be possible from just a reduced image of the cover page available through the second option.

The fourth option provides the user with a reduced size image of each page and permits the user to scroll through the entire message. The user can therefore read the entire facsimile message on screen before the message is downloaded onto the computer 32. With this option, the user can go through the pages of the facsimile message and can also skip to the next message or previous message. Additionally, the user has the option of enlarging a page to a full size view of the page. When one of the messages is selected, as with the other options, the HTTPD within the MSDS 10 causes the facsimile message to be transmitted through the Internet 30 to the user's computer 32.

With a fifth option, a full size image of each page is transmitted to the user's computer 32. The user can scroll through the pages of the facsimile message and easily read the contents of each page. If the user wants the message downloaded to the computer 32, the user selects the message and the HTTPD within the MSDS 10 transmits the message to the user's computer 32 through the Internet 30.

As discussed above, after the database is updated at step 54, the MSDS 10 will generate additional information based upon the option selected for displaying the facsimile messages. More specifically, as shown in <figref idref="f0004">FIG. 4(A)</figref>, if the first option has been selected, as determined at step 100, then at step 102 the MSDS 10 will generate the textual listing of the facsimile messages with anchors or references to the respective facsimile files. The HTML files are then moved to an Internet Server at step 104.

If the first option is not selected, the MSDS 10 next determines whether the second option has been selected at step 106. With the second option, the facsimile messages are listed along with a reduced size image of the cover page. To generate this information, the cover page is extracted from the facsimile file at step 108 and a reduced size HTML image of the cover page is created at step 110. At step 112, a listing of the facsimile messages is generated with a thumbnail view of each cover page linked to its respective facsimile file. The generated HTML files are then sent to the Internet Server at step 104.

When the third option is selected, as determined at step 114, a full size image of the cover page is sent to the computer 32. The full size image of the cover page is generated by first extracting the cover page from the facsimile file at step 116. Next, the cover page is converted into a full size HTML image at step 118 and, at step 120, the listing is generated with the embedded cover page linked to the facsimile file.

If, at step 122, the fourth option is determined to be selected, then a reduced size image of each page is provided to the user with the option of enlarging the page to view the contents of the page more clearly. With reference to <figref idref="f0005">FIG. 4(B)</figref>, the information necessary for the third option is produced by first extracting the first page of the facsimile message at step 124. A reduced size HTML image is created at step 126 and then a full size HTML image is created at step 128. At step 130, the listing is generated with embedded thumbnail images of the pages with links to the full size images. If the page is not the last page, as determined at step 140, then the next page is extracted at step 142 and steps 126 to 130 are repeated to generate the HTML files for the other pages of the facsimile message. After the last page has been converted into an HTML file according to the third option, the files are moved onto the Internet Server at step 104.

At step 144, the MSDS 10 determines whether the fifth option has been selected. The fifth option provides the user with a full size image of each page of the facsimile message. While only five options have been discussed, the invention may be practiced with additional options. Consequently, with additional options and with the fourth option not being selected, the MSDS 10 would next determine whether one of the additional options have been selected. With the preferred embodiment of the invention having only five options, however, the MSDS 10 will assume that the fifth option has been selected if none of the first four options were found to be selected.

The information necessary to display the pages of the facsimile message according to the fifth option is generated by first extracting the first page of the facsimile message at step 146. At step 148, a full size HTML image of the page is created and, at step 150, a listing is generated with an embedded image and links to previous and next pages. When the page is not the last page, as determined at step 152, the MSDS 10 extracts the next page and generates the HTML file for that page. After all pages have been converted into HTML files according to the fourth option, the files are sent to the Internet Server at step 104.

While <figref idref="f0004">FIGS. 4(A)</figref> and <figref idref="f0005">(B)</figref> describe the operations of the MSDS 10 at the time a message is received, <figref idref="f0006">FIG. 5</figref> depicts an overall flowchart of operations for the MSDS 10 when the user requests a page of information in a display format other than the user's preferred option of displaying the message. <figref idref="f0006">FIG. 5</figref> is therefore a more detailed explanation of how the MSDS 10 generates the necessary information at step 82 of <figref idref="f0003">FIG. 3</figref>.

In general, as shown in <figref idref="f0006">FIG. 5</figref>, the MSDS 10 first determines the type of image that is needed at step 82a. For example, at this step, the MSDS 10 will determine whether images are unnecessary, whether an image of just the cover page is necessary, whether an image is needed for every page, and whether the image needs to be a full size, a reduced size, or both full and reduced sized images. At step 82b, the MSDS 10 determines whether the image has already been created. If the image has not been created, then at step 82c the MSDS 10 will extract the page from the base facsimile file and, at step 82d, generate the required HTML image. As discussed above, the required image may be for just the cover page, for all the pages, and may be a full size and/or a reduced size image of the page. At step 82e, the image is embedded with links or anchors to other HTML files. These links or anchors might be references to the next and previous pages and also to the next and previous facsimile messages. Finally, the HTML file having the embedded image and links is sent to the user at step 80 in <figref idref="f0003">FIG. 3</figref>.

The process for converting a facsimile message into HTML files according to the fifth option will be described with reference to <figref idref="f0007">FIG. 6</figref>. This process will occur at step 54 when the message is received and when the fifth option is the user's preferred option of displaying the messages. It should be understood that a similar type of process will also occur when the user requests a page of information according to the fifth option when the user is retrieving a facsimile message and the fifth option is not the user's preferred option. The conversion processes according to the other options will become apparent to those skilled in the art and will therefore not be discussed in further detail.

With reference to <figref idref="f0007">FIG. 6</figref>, when the facsimile message is received, the message is in a Tagged Image File Format/Facsimile (TIFF/F) and each page of the facsimile message is split into a separate file. Each page of the facsimile message is then converted from the TIFF/F format into a Portable Pixel Map (PPM) format. The PPM files are next converted into separate Graphic Interchange Format (GIF) files and then into separate HTML files. Thus, each page of the facsimile message is converted into a separate HTML file. The TIFF/F files may be converted into PPM with an available software package entitled "LIBTIFF" and the PPM files may be converted into GIF files with an available software package found in "Portable Pixel Map Tools."

The invention is not limited to this exact conversion process or to the particular software packages used in the conversion process. For instance, the TIFF/F files may be converted into another portable file format, through any other type of intermediate format, or may be converted directly into the GIF format. Further, instead of GIF, the facsimile messages may be converted into JPEG, BMP, PCX, PIF, PNG, or any other suitable type of file format.

The files may be identified with any suitable filename. In the preferred embodiment, the files for each user are stored in a separate directory assigned to just that one user because an entire directory for a given user generally can be protected easier than the individual files. The memory, however, may be organized in other ways with the files for a single user being stored in different directories. The first part of the filename is a number preferably sequentially determined according to the order in which messages arrive for that user. The preferred naming convention for ending the filenames is depicted in <figref idref="f0007">FIG. 6</figref>. Each page of the facsimile message is saved as a separate file with an extension defined by the format of the file. Thus, the files will end with an extension of ".TIFF," ".PPM," ".GIF," or ".HTML" according to the format of the particular file. In the example shown, the separate pages have filenames which end with the respective page number, for instance, the first page ends with a "1." The files, however, are preferably terminated with a letter or multiples letters to indicate the order of the pages. For instance, page 1 might have an ending of "aa," page 2 might have an ending of "ab," etc. The invention, however, is not limited to the disclosed naming convention but encompasses other conventions that will be apparent to those skilled in the art.

As shown in <figref idref="f0007">FIG. 6</figref>, in addition to the GIF files representing the pages of the facsimile message, the HTML files include a number of anchors or references. In the example shown, the first HTML file has an anchor a for the "Next Page." Anchor a is defined as a=&lt;A HREF="2.htm1"&gt;Next Page&lt;/a&gt; and will therefore reference the second HTML file when a user selects the "Next Page." The second HTML file has an anchor b for the "Previous Page" and an anchor c for the "Next Page" and the third HTML file has an anchor d for the "Previous Page." With these particular HTML files, the user can scroll through each page of the facsimile message and view a full size image of the page.

Each HTML file preferably contains anchors in addition to those relating to "Next Page" and "Previous Page." For instance, each HTML file may contain an anchor to the next facsimile message, an anchor to the previous facsimile message, and an anchor to return to the facsimile list. The HTML files preferably contain anchors relating to "Save" and "Delete." When the "Save" anchor is selected, the user would be able to save the message under a more descriptive name for the message. The "Delete" anchor is preferably followed by a inquiry as to whether the user is certain that he or she wants to delete the message. Other anchors, such as an anchor to the general listing, will be apparent to those skilled in the art and may also be provided.

<figref idref="f0008">FIG. 7</figref> provides an example of a display according to the fifth option for the first page of the facsimile message shown in <figref idref="f0007">FIG. 6</figref>. The headings of the display provide information on the telephone number from where the message was sent, the date and time the message was received at the MSDS 10, and an indication of the page of the message being displayed. The main portion of the display is the full size image of the page. At the bottom of the display, an anchor or link is provided to the "Next Page" and another anchor is provided to the "Return to Fax Listing." Additional information may also be provided on the display, such as a link to a company operating the MSDS 10.

An example of the "1.html" file for generating the display shown in <figref idref="f0008">FIG. 7</figref> is shown below in Table 1. <tables id="tabl0001" num="0001"><table frame="none"><title>TABLE 1</title><tgroup cols="1"><colspec colnum="1" colname="col1" colwidth="131mm" /><tbody><row rowsep="0"><entry>&lt;HTML&gt;</entry></row><row rowsep="0"><entry>&lt;HEAD&gt;</entry></row><row rowsep="0"><entry>&lt;TITLE&gt;Fax Received on May 31, 1995 at 1:58 PM from (404)249 6801; Page 1 of 3&lt;/TITLE&gt;</entry></row><row rowsep="0"><entry>&lt;/HEAD&gt;</entry></row><row rowsep="0"><entry>&lt;BODY&gt;</entry></row><row rowsep="0"><entry>&lt;H1&gt;Fax from (404)249-6801&lt;/H1&gt;</entry></row><row rowsep="0"><entry>&lt;H2&gt;Received on May 31, 1995 at 1:58 PM&lt;/H2&gt;</entry></row><row rowsep="0"><entry>&lt;H2&gt;Page 1 of3&lt;/H2&gt;</entry></row><row rowsep="0"><entry>&lt;IMG SRC=" 1.gif"&gt;</entry></row><row rowsep="0"><entry>&lt;P&gt;</entry></row><row rowsep="0"><entry>&lt;A HREF="2.htm1"&gt;Next Page&lt;/a&gt;</entry></row><row rowsep="0"><entry>&lt;HR&gt;</entry></row><row rowsep="0"><entry>&lt;A HREF="faxlist.html"&gt;Return to Fax Listing&lt;/A&gt;</entry></row><row rowsep="0"><entry>&lt;P&gt;</entry></row><row rowsep="0">&lt;entry /&gt;</row><row rowsep="0"><entry>This page was automatically generated by FaxWeb(tm) on May 31, 1995 at 2:05 PM.</entry></row><row rowsep="0"><entry>&lt;P&gt;</entry></row><row rowsep="0"><entry>© 1995 NetOffice, Inc.</entry></row><row rowsep="0"><entry>&lt;HR&gt;</entry></row><row rowsep="0"><entry>&lt;Address&gt;</entry></row><row rowsep="0"><entry>&lt;A HREF="http://www.netoffice.com/"&gt;NetOffice, Inc.&lt;/A&gt;</entry></row><row rowsep="0"><entry>PO Box 7115</entry></row><row rowsep="0"><entry>Atlanta, Ga. 30357</entry></row><row rowsep="0"><entry>&lt;A HREF="mailto:info@netoffice.com"&gt;info@netoffice.com&lt;/A&gt;</entry></row><row rowsep="0"><entry>&lt;/Address&gt;</entry></row><row rowsep="0"><entry>&lt;/BODY&gt;</entry></row><row rowsep="0"><entry>&lt;/HTML&gt;</entry></row></tbody></tgroup></table></tables> As is apparent from the listing in Table 1, the image file "1.gif" for the first page is embedded into the HTML file "1.html." Also apparent from the listing is that the anchor for "Next Page" directs the MSDS 10 to the second page of the facsimile message having the filename "2.html" and the anchor for "Return to Fax Listing" directs the MSDS 10 to the filename "faxlist.html" containing the list of facsimile messages.

A process for converting a voice message into an HTML file is illustrated in <figref idref="f0009">FIG. 8</figref>. The voice message is originally stored in a VOX format or an AD/PCM format and is retrieved at step 170. The voice message is then converted either into an AU format or WAV format in accordance with the user's preference, which is stored in memory. Preferably, the message is preferably in the AD/PCM format originally and is converted in WAV, but the voice files may alternatively be stored and converted in file formats other than the ones disclosed, such as RealAudio (RA).

At step 174, the listing of all of the voice messages is then updated to include a listing of the newly received voice message and an anchor to the voice message. For instance, the original voice message may be stored with filename "1.vox" and is converted into WAV and stored with a filename "1.wav." The HTML file "voicelist.html" which contains a list of all voice messages would then have an anchor to the filename "1.wav" along with identifying information for the voice message, such as when the message was received.

The listing of the voice messages may have additional anchors or references. For instance, each voice message may have an anchor directing the MSDS 10 to a file which contains a short sampling of the message. Thus, when the user selects this anchor, the user could receive the first 5 seconds of the message or some other predefined number of seconds. As with the listing of facsimile messages, the listing of the voice messages also preferably has anchors to "Save" and "Delete."

<figref idref="f0010">FIG. 9</figref> illustrates a process for converting a data message into HTML. At step 180, the data file is retrieved from a database and at step 182 the HTML file containing the list of data messages is updated to include a listing of the newly received message along with identifying information. For instance, the HTML file for the listing "datalist.html" would be updated to include an anchor to a data file "file 1.1" and would have information such as the time and date that the data was transmitted, the size of the data file, as well as additional identifying information.

Because the MSDS 10 can receive messages of various types, such as a facsimile message, voice message or data message, the MSDS 10 must be able to determine the type of message that is being sent over the DID trunk 15. With reference to <figref idref="f0011">FIG. 10</figref>, when an incoming call is received, the MSDS 10 goes off hook at step 200 and starts to generate a ringing sound. If, at step 202, a facsimile calling tone is detected, then the ringing sound is stopped at step 204 and the message is received as a facsimile message at step 206. Similarly, when a data modem calling tone is detected at step 208, the ringing sound is stopped at step 210 and the message is identified as a data message at step 212.

If the MSDS 10 detects a DTMF digit at step 214, the ringing sound is stopped at step 216 and the MSDS 10 then determines which digit was pressed. When the digit is a "1," as determined at step 218, the message is identified as a facsimile message. The MSDS 10 will thereafter receive and store the facsimile message in the manner described above with reference to <figref idref="f0002">FIG. 2</figref>. If the digit is identified as a "0" at step 220, the call is identified as an owner's call and will be processed in a manner that will be described below with reference to <figref idref="f0013">FIG. 12</figref>. As will be apparent, other digits may cause the MSDS 10 to take additional steps. If any other DTMF digit is pressed, at step 224 the MSDS 10 activates a voice call system, which will be described in more detail below with reference to <figref idref="f0012">FIG. 11</figref>.

With step 226, the MSDS 10 will enter a loop continuously checking for a facsimile calling tone, a data modem calling tone, or for a DTMF digit. If after n rings none of these tones or digits has been detected, the ringing sound is stopped at step 228 and the voice call system is activated at step 224.

With reference to <figref idref="f0012">FIG. 11</figref>, when a fax calling tone or modem calling tone is not detected, the voice call system begins at step 230 by playing a voice greeting. If the greeting was not interrupted by a DTMF digit as determined at step 232, then the caller is prompted for the voice message at step 234 and, at step 236, the voice message is recorded and stored in memory. At step 238, the caller is prompted with a number of options, such as listening to the message, saving the message, or re-recording the message. Since the selection of these options with DTMF digits will be apparent to those skilled in the art, the details of this subroutine or subroutines will not be described in further detail. When the caller wishes to re-record the message, as determined at step 240, the caller is again prompted for a message at step 234. If the caller does not wish to re-record the message, the call is terminated at step 242.

If the voice greeting is interrupted by a DTMF digit, as determined at step 232, then the MSDS 10 ascertains which digit has been pressed. At step 244, if the digit is a "0," the MSDS 10 detects that the call is an owner's call. When the digit is a "1," the MSDS 10 is informed at step 206 that the call carries a facsimile message. As discussed above with reference to <figref idref="f0011">FIG. 10</figref>, other DTMF digits may cause the MSDS 10 to take additional steps. If an invalid digit is pressed, by default at step 248 the routine returns to step 234 of prompting the caller for a message.

It should be understood that the invention is not limited to the specific interactive voice response system described with reference to <figref idref="f0012">FIG. 11</figref>. As discussed above, the invention may be responsive to DTMF digits other than just a "0" and a "1." Further variations or alterations will be apparent to those skilled in the art.

With reference to <figref idref="f0013">FIG. 12</figref>, when the call is considered an owner's call, the caller is first prompted for the password at step 250. The password is received at step 252 and, if found correct at step 254, a set of announcements are played to the owner. These announcements would preferably inform the owner of the number of new messages that have been received, the number of saved messages, the number of facsimile message, the number of data messages, and the number of voice messages. Other announcements, of course, could also be made at this time.

At step 258, the owner then receives a recording of the owner's menu with the appropriate DTMF digit for each option. For instance, the DTMF digit "1" may be associated with playing a message, the DTMF digit "2" may be associated with an options menu, and the DTMF digit "*" may be associated with returning to a previous menu or terminating the call if no previous menu exists.

A DTMF digit is detected at step 260 and the appropriate action is taken based upon the digit received. Thus, if the digit is determined to be a "1" at step 264, the owner can play a message at step 266. At step 266, the owner is preferably greeted with a menu giving the owner the options of playing or downloading new messages, saved messages, facsimile messages, data messages, or voice messages. As should be apparent to those skilled in the art, the owner may receive one or more menus at step 266 and the owner may enter one or more DTMF digits in order to play or download a particular message.

If, instead, the digit is determined to be a "2" at step 268, then the owner receives an options menu at step 270. With the options menu, the owner can enter or change certain parameters of the MSDS 10. For instance, the owner can change his or her password, the owner can change the manner in which facsimile messages are displayed on the computer 32, the owner can change the image file format from GIF to another format, the owner can select the file formats for the voice messages, as well as other options. If the "*" DTMF digit is received, as determined at step 272, then the owner is returned to a previous menu. The "*" digit is also used to terminate the call when the owner has returned to the initial menu. The "*" digit is therefore universally recognized by the MSDS 10 throughout the various menus as a command for returning to a previous menu.

If the owner enters a DTMF digit that is not being used by the MSDS 10, the owner receives an indication at step 276 that the key is invalid and the owner is then again provided with the owner's menu at step 258. When the owner does not enter a DTMF digit while the owner's menu is being played, as determined at step 260, the menu will be replayed n times. Once the menu has been replayed n times, as determined at step 262, then the call will be terminated at step 278.

If the password is incorrect, as determined at step 254, then the MSDS 10 checks whether the user has made more than "n" attempts at step 280. If "n" attempts have not been made, then a password incorrect message will be displayed to the user at step 282 and the user will once again be prompted for the password at step 250. When the user has made "n" attempts to enter the correct password, the MSDS 10 will play a failure message to the user at step 284 and then terminate the call at step 286. The specific number "n" may be three so that the call is terminated after three failed attempts.

The owner's menu may be responsive to an additional number of DTMF digits and may be structured in other ways. For instance, separate DTMF digits may direct the owner to the respective types of messages, such as a facsimile message, data message, or voice message. Also, separate DTMF digits may direct the owner to a recording of new messages or to a recording of saved messages. Other variations will be apparent to those skilled in the art.

A more detailed diagram of the MSDS 10 is shown in <figref idref="f0014">FIG. 13</figref>. As shown in the figure, a plurality of DID trunks 15 are received by an input/output device 17 and are then sent to a central processor 3. The number of DID trunks 15 may be changed to any suitable number that would be necessary to accommodate the anticipated number of telephone calls that may be made to the MSDS 10. The input/output device 17 routes a call on one of the DID trunks 15 to an open port of the central processor 3 and is preferably a DID Interface Box manufactured by Exacom.

The central processor 3 receives the calls on the DID trunks 15 and stores the messages in storage 11 in accordance with software 7. Preferably, a separate directory in storage 11 is established for each user having an account on the MSDS 10 so that all of the messages for a single user will be stored in the same directory. It should be understood that the number of processors within the central processor 3 is dependent upon the number of DID trunks 15. With a greater number of DID trunks 15 capable of handling a larger number of telephone calls, the central processor 3 may actually comprise a number of computers. The input/output device 17 would then function to route incoming calls to an available computer within the central processor 3.

A more detailed diagram of the central processor 3 is shown in FIG. 14. The central processor 3 comprises a telephone line interface 21 for each DID trunk 15. The telephone interface 21 provides the ringing sounds and other communication interfacing with the telephone lines. The signals from the telephone interface 21 are routed to a pulse/tone decoder 23 and to a digital signal processor (DSP) 25. The pulse/tone decoder 23 detects the address signal off of an incoming call and sends the address signal onto a bus 29 to a microprocessor 27. The DSP performs the necessary signal processing on the incoming calls and routes the processed signals to the microprocessor 27.

The microprocessor 27 will then read the address signal from the pulse/tone decoder 23 and store the message from the DSP 25 in an appropriate directory in storage 11. As discussed above, the central processor 3 may comprise a number of computers or, more precisely, a number of microprocessors 27 with each microprocessor 27 handling the calls from a certain number, such as four, DID trunks 15. The microprocessor 27 may comprise any suitable microprocessor, but is preferably at least a 486 PC.

In addition to handling incoming calls and storing the messages in storage 11, the central processor 3 also coordinates the interactive voice response system of the MSDS 10. The software 7 would incorporate the flowcharts of operations for receiving a message shown in <figref idref="f0003">FIG. 3</figref>, for detecting the type of message on an incoming call shown in <figref idref="f0011">FIG. 10</figref>, for receiving voice messages shown in <figref idref="f0012">FIG. 11</figref>, and for receiving an owner's call shown in <figref idref="f0013">FIG. 12</figref>. Based upon the above-referenced flowcharts and the respective descriptions, the production of the software 7 is within the capability of one of ordinary skill in the art and will not be described in any further detail.

The Internet Server 5 is connected to the central processor 3, such as through a local area network, and also has access to the storage 11. The Internet Server 5 performs a number of functions according to software 9. For instance, the Internet Server 5 retrieves the data files stored in storage 11 by the central computer 3 and converts the files into the appropriate HTML files. The converted HTML files are then stored in storage 11 and may be downloaded to the computer 32 through the Internet 30. The Internet Server 5 also handles the requests from the computer 32, which might require the retrieval of files from the storage 11 and possibly the generation of additional HTML files.

The software 9 for the Internet Server 5 would therefore incorporate the flowchart of operations for generating HTML files according to user preferences shown in <figref idref="f0004 f0005">FIG. 4</figref>, for generating requested information from a user shown in <figref idref="f0006">FIG. 5</figref>, for converting facsimile messages into HTML shown in <figref idref="f0007">FIG. 6</figref>, for converting voice messages into HTML shown in <figref idref="f0009">FIG. 8</figref>, and for converting data messages into HTML shown in <figref idref="f0010">FIG. 9</figref>. Based upon the above-referenced flowcharts and their respective descriptions, the production of the software 9 is within the capability of one of ordinary skill in the art and need not be described in any further detail.

Nonetheless, a more detailed block diagram of the Internet Server 5 is shown in <figref idref="f0015 f0016">FIG. 15</figref>. The Internet Server 5 runs on a suitable operating system (OS) 39, which is preferably Windows NT. The Internet Server 5 has a number of application programs 31, such as the ones depicted in the flowcharts discussed above, for communicating with the central processor 3 and for accessing data from storage 11 and also from memory 33.

The memory 33, inter alia, would contain the data indicating the preferences of each user. Thus, for example, when a facsimile message in the TIFF/F format is retrieved by the Internet Server 5, the Internet Server 5 would ascertain from the data in memory 33 the preferred option of displaying the facsimile message and would generate the appropriate HTML files.

All interfacing with the Internet 30 is handled by the HTTPD 37, which, in the preferred embodiment, is "Enterprise Server" from NetScape Communications Corp. Any requests from users, such as a request for a file, would be handled by the HTTPD 37, transferred through the CGI 35, and then received by the application programs 31. The application programs 31 would then take appropriate actions according to the request, such as transferring the requested file through the CGI 35 to the HTTPD 37 and then through the Internet 30 to the user's computer 32.

The Internet Server 5 may be connected to a paging system 13. Upon the arrival of a new message, in addition to sending an E-mail message to the user's mailbox, the Internet Server 13 may also activate the paging system 13 so that a pager 15 would be activated. In this manner, the user could receive almost instantaneous notification that a message has arrived.

The paging system 13 is preferably one that transmits alphanumeric characters so that a message may be relayed to the user's pager 15. The Internet Server 5 therefore comprises a signal processor 41 for generating signals recognized by the paging system 13 and a telephone interface 43. The signal processor 41 preferably receives information from the application programs 31 and generates a paging message in a paging file format, such as XIO/TAP. The telephone interface 43 would include a modem, an automatic dialer, and other suitable components for communicating with the paging system 13.

The information from the application programs 31 may simply notify the user of a message or may provide more detailed information. For instance, with a facsimile message, the information from the application programs 31 may comprise CSI information identifying the sender's telephone number. The user would therefore receive a message on the pager 15 informing the user that a facsimile message was received from a specified telephone number. The amount and type of information that may be sent to the user on the pager 15 may vary according to the capabilities of the paging system 13 and may provide a greater or lesser amount of information than the examples provided.

The Internet Server 5 is not limited to the structure shown in <figref idref="f0015 f0016">FIG. 15</figref> but may comprise additional components. For instance, the HTTPD 37 would be linked to the Internet 30 through some type of interface, such as a modem or router. The Internet Server 5 may be connected to the Internet 30 through typical phone lines, ISDN lines, a T1 circuit, a T3 circuit, or in other ways with other technologies as will be apparent to those skilled in the art.

Furthermore, the Internet Server 5 need not be connected to the Internet 30 but may be connected to other types of networks. For instance, the Internet Server 5, or more generally the network Server 5, could be connected to a large private network, such as one established for a large corporation. The network Server 5 would operate in the same manner by converting messages into HTML files, receiving requests for information from users on the network, and by transmitting the information to the users.

Also, at least one interface circuit would be located between the Internet Server 5 and the central processor 3 in order to provide communication capabilities between the Internet Server 5 and the central processor 3. This network interface may be provided within both the Internet Server 5 and the central processor 3 or within only one of the Internet Server 5 or central processor 3.

Examples of the Internet Server 5 software layers are shown in <figref idref="f0017">FIGS. 16(A)</figref> and <figref idref="f0018">16(B)</figref>, with <figref idref="f0017">FIG. 16(A)</figref> representing the Internet Server 5 in an asynchronous mode of communication and <figref idref="f0018">FIG. 16(B)</figref> representing the Internet 5 in a synchronous mode of communication. As shown in the figures, the software 9 for the Internet Server 5 may additional comprise an Internet Deamon for running the HTTPD 37. The software 9 for the Internet Server 5 would also include TCP/IP or other transport layers. Moreover, while the authentication is provided through the HTTPD 37, the authentication of the user's password and ID may be supplemented or replaced with other ways of authentication.

The term synchronous has been used to refer to a mode of operation for the MSDS 10 in which the all possible HTML files for a message are generated at the time the message is received. The HTML files may be generated by the central processor 3 or by the application programs 31. When a request for information is then later received by the HTTPD 37, the information has already been generated and the HTTPD 37 only needs to retrieve the information from storage 11 and transmit the information to the user's computer 32. With a synchronous mode of operation, the CGI 35 would be unnecessary.

The MSDS 10 preferably operates according to an asynchronous mode of operation. In an asynchronous mode of operation, information requested by the user may not be available and may have to be generated after the request. The asynchronous mode of operation is preferred since fewer files are generated, thereby reducing the required amount of storage 11. Because the information requested by a user may not be available, some anchors cannot specify the filename, such as "2.html," but will instead contain a command for the file. For instance, an anchor may be defined as &lt;AHREF="/faxweb/users/2496801/ viewpage.cgi?FAX-NUM=1&amp;PAGE=1&amp;VIEW-- MODE=FULL"&gt; for causing the CGI 35 to run a viewpage program so that page 1 of facsimile message 1 will be displayed in a full size image. The CGI 35 will generate the requested information when the information has not been generated, otherwise the CGI 35 will retrieve the information and relay the information to the HTTPD 37 for transmission to the user.

With the invention, the MSDS 10 can reliably receive voice, facsimile, and data messages for a plurality of users and can receive more than one message for a user at a single time. The messages are stored by the MSDS 10 and can be retrieved at the user's convenience at any time by connecting to the Internet 30. The Internet World Wide Web 30 is a constantly expanding network that permits the user to retrieve the messages at virtually any location in the world. Since the user only needs to incur a local charge for connecting to the Internet 30, the user can retrieve or review messages at a relatively low cost.

Even for the user's at the office or at home, the MSDS 10 provides a great number of benefits. The user would not need a facsimile machine, voice mail system, or a machine dedicated for receiving data messages. The user also need not worry about losing part of the message or violating the confidential nature of the messages. The user, of course, can still have a facsimile machine and dedicated computer for data messages. The MSDS 10, however, will permit the user to use the telephone company's "call forwarding" feature so that messages may be transferred to the MSDS 10 at the user's convenience, such as when the user is away from the office.

The foregoing description of the preferred embodiment of the invention has been presented only for the purpose s of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in the light of the above teaching

For example, the software 7 and software 9 are not limited to the exact forms of the flowcharts shown but may be varied to suit the particular hardware embodied by the invention. The software may comprise additional processes not shown or may combine one or more of the processes shown into a single process. Further, the software 7 and 9 may be executed by a single computer, such as a Silicon Graphics Workstation, or may be executed by a larger number of computers.

The facsimile messages preferably undergo signal processing so that the images of the facsimile messages are converted from a two tone black or white image into an image with a varying gray scale. As is known in the art, a gray scale image of a facsimile message provides a better image than simply a black or white image of the message. The signal processing may comprise any suitable standard contrast curve method of processing, such as anti-aliasing or a smoothing filter. The signal processing may occur concurrently with the conversion from TIFF/F to GIF and is preferably performed for both full and reduced size images of the facsimile messages.

Furthermore, the user may be provided with a greater or fewer number of options in displaying or retrieving messages. The options are not limited to the exact forms provided but may permit the user to review or retrieve the messages in other formats. The options may also permit a user to join two or messages into a single message, to delete portions of a message, or to otherwise the contents of the messages. Also, the various menus provided to the user over the telephone may have a greater number of options and the MSDS 10 may accept responses that involve more than just a single DTMF digit.

The specific DTMF digits disclosed in the various menus are only examples and, as will be apparent to those skilled in the art, other digits may be used in their place. For instance, a "9" may be used in the place of a "*" in order to exit the menu or to return to a previous menu. Also, the DTMF digits may be changed in accordance with the user's personal convention. If the user had a previous voice mail system, the user could customize the commands to correspond with the commands used in the previous system in order to provide a smooth transition to the MSDS 10.

The MSDS 10 may restrict a user to only certain types of messages. For instance, a user may want the MSDS 10 to store only facsimile messages in order to reduce costs of using the MSDS 10. In such a situation, the MSDS 10 would perform an additional step of checking that the type of message received for a user is a type of message that the MSDS 10 is authorized to receive on the user's behalf. When the message is an unauthorized type of message, the MSDS 10 may ignore the message entirely or the MSDS 10 may inform the user that someone attempted to send a message to the MSDS 10.

Moreover, the MSDS 10 has been described as having the central processor 3 for handling incoming calls and the Internet Server 10 for interfacing with the Internet 30. The invention may be practiced in various ways other than with two separate processors. For instance, the central processor 3 and the Internet Server 5 may comprise a single computer or workstation for handling the incoming calls and for interfacing with the Internet 30. The MSDS 10 may convert the messages into HTML files prior to storing the messages. Also, the central processor 3 may communicate with the paging system 13 instead of the Internet Server 5. Additionally, as discussed above, the central processor 3 may comprise a number of microprocessors 27 for handling a large number of DID trunks.

The invention has been described as converting the messages into HTML and transmitting the HTML files over the Internet 30 to the computer 32. The HTML format, however, is only the currently preferred format for exchanging information on the Internet 30 and is actually only one type of a Standard Generalized Mark-Up Language. The invention is therefore not limited to the HTML format but may be practiced with any type of mixed media page layout language that can be used to exchange information on the Internet 30.

With regard to the transmission of messages to the user's computer 32, the MSDS 10 permits the user to sample the voice message or to preview the facsimile message without requiring the MSDS 10 to transmit the entire message to the computer 32. This sampling ability is a significant benefit since the transmission of the entire message would frequently tie up the computer 32 for a rather long period of time. Thus, with the preview or sample feature, the user can determine whether the user needs the message transmitted to the computer 32.

If the user does decide that the entire message needs to be transmitted, as stated above, the user's computer 32 might be receiving the message for a relatively long period of time. After the entire message has been received, the user then has the options of viewing, listening, retrieving, or saving the message. As an alternative, the user's computer may instead indicate the contents of the message to the user as the message is being received.

For instance, with a voice message, the user's computer 32 could send the message to an audio speaker as the message is being received. In this manner, the message would be played in real time and the user would not need to wait until the entire message is received before listening to the message. In order to play the messages in real time, the messages are preferably in the RealAudio (RA) format, which the user can select as the preferred file format for voice messages.

In operation, the MSDS 10 would transmit an HTML file containing an RA file. If the user selects the RA file with the browser on the computer 32, the browser will activate a program for use with RA files. The operations and functioning of this program will be apparent to those skilled in the art and will be available as a separate software package or will be incorporated within a browser program. The RA program will request the RA data file containing the message from the MSDS 10 and, as the RA file is being received at the computer 32, this program will play the message in real time.

The MSDS 10 and the user's computer 32 could also be arranged so that each page or even line of a facsimile message could be displayed as the computer 32 receives the facsimile message. Further, although the transmission of a data message is relatively fast in comparison to a voice or facsimile message, the computer 32 could also be programmed to permit access to the data message as the message is being received.

The invention has been described as storing and transmitting voice messages. It should be understood that the voice message would probably be the most often type of audio message stored at the MSDS 10. The invention, however, may be used with any type of audio message and is in no way limited to just voice messages.

The embodiment was chosen and described in order to explain the principles of the invention and their practical application so as to enable others skilled in the art to utilize the invention and various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention only be limited by the claims appended hereto.

Additional features of the present invention are set out below:- <ul id="ul0002" list-style="none" compact="compact"><li>Feature 1. A network message storage and delivery system, comprising: <ul id="ul0003" list-style="none" compact="compact"><li>means for receiving an incoming call and for detecting an address signal associated with said incoming call, said address signal associated with a user of said message storage and delivery system;</li><li>means for receiving a message accompanied with said address signal, said message being in a first file format;</li><li>means for converting said message from said first file format to a second file format;</li><li>means for storing said message in said second file format in a storage area;</li><li>means for receiving a request from said user for said message and for retrieving said message from said storage area; and</li><li>means for transmitting a least a portion of said message in said second file format to said user;</li><li>wherein said portion of said message is transmitted to said user over the network, said second file format is a mixed media page layout language.</li></ul></li><li>Feature 2. The message storage and delivery system as set forth in feature 1, wherein said network comprises the Internet.</li><li>Feature 3. The message storage and delivery system as set forth in feature 1, further comprising means for notifying the user of said message.</li><li>Feature 4. The message storage and delivery system as set forth in feature 3, wherein said notifying means comprises means for sending an E-mail message to said user.</li><li>Feature 5. The message storage and delivery system as set forth in feature 3, wherein said notifying means provides said user with information on a type of said message.</li><li>Feature 6. The message storage and delivery system as set forth in feature 3, wherein said notifying means comprises means for paging said user.</li><li>Feature 7. The message storage and delivery system as set forth in feature 6, wherein said paging means comprises an alphanumeric pager.</li><li>Feature 8. The message storage and delivery system as set forth in feature 1, wherein said message comprises a facsimile message.</li><li>Feature 9. The message storage and delivery system as set forth in feature 1, wherein said message comprises a data message.</li><li>Feature 10. The message storage and delivery system as set forth in feature 1, wherein said message comprises a voice message.</li><li>Feature 11. The message storage and delivery system as set forth in feature 1, wherein said means for receiving said incoming call receives said incoming call over a DID trunk.</li><li>Feature 12. The message storage and delivery system as set forth in feature 11, wherein said means for receiving said incoming call receives said incoming call over a plurality of DID trunks.</li><li>Feature 13. The message storage and delivery system as set forth in feature 1, wherein said means for receiving said message comprises any one of a facsimile message, a data message, or a voice message.</li><li>Feature 14. The message storage and delivery system as set forth in feature 1, wherein said second file format comprises a standard generalized mark-up language.</li><li>Feature 15. The message storage and delivery system as set forth in feature 14, wherein said standard generalized mark-up language comprises hype-text mark-up language.</li><li>Feature 16. The message storage and delivery system as set forth in feature 1, wherein said means for receiving said request from said user comprises a hyper-text protocol daemon for receiving said request over the Internet.</li><li>Feature 17. The message storage and delivery system as set forth in feature 1, wherein said message comprises facsimile message, said first file format comprises TIFF/F, said second file format comprises HTML, and said converting means embeds a reduced size image of at least one page of said facsimile message within said second file format.</li><li>Feature 18. The message storage and delivery system as set forth in feature 17, wherein said reduced size image of said one page is provided as an anchor to a full size view of said one page.</li><li>Feature 19. The message storage and delivery system as set forth in feature 1, wherein said message comprises a facsimile message, said first file format comprises TIFF/F, said second file format comprises HTML, and said converting means embeds a full size image of at least one page of said facsimile message within said second file format.</li><li>Feature 20. The message storage and delivery system as set forth in feature 1, wherein said message comprises a facsimile message, said first file format comprises TIFF/F, said second file format comprises HTML, and said converting means generates a listing of all facsimile messages associated with said user.</li><li>Feature 21. The message storage and delivery system as set forth in feature 1, wherein said message comprises a facsimile message and said system further comprises previewing means for sending a user a listing of all facsimile messages along with a reduced size image of a first page for each facsimile message.</li><li>Feature 22. The message storage and delivery system as set forth in feature 21, wherein each reduced size image of the first page comprises an anchor and said transmitting means transmits the facsimile message associated with said anchor to said user when said user selects said anchor.</li><li>Feature 23. The message storage and delivery system as set forth in feature 1, wherein said message comprises a facsimile message and said system further comprises previewing means for sending said user a listing of all facsimile messages for said user along with a full size image of a first page of each facsimile message.</li><li>Feature 24. The message storage and delivery system as set forth in feature 1, wherein said message comprises facsimile message and said system further comprises previewing means for sending said user a reduced size image of each page of said facsimile message.</li><li>Feature 25. The message storage and delivery system as set forth in feature 24, wherein each reduced size image comprises an anchor to a full size image of the respective page.</li><li>Feature 26. The message storage and delivery system as set forth in feature 1, wherein said message comprises facsimile message and said system further comprises previewing means for sending said user a full size image of each page of said facsimile message.</li><li>Feature 27. The message storage and delivery system as set forth in feature 1, wherein said means for receiving said incoming call comprises a central processor and said means for receiving said request comprises a network server.</li><li>Feature 28. The message storage and delivery system as set forth in feature 1, wherein said message comprises facsimile message and said second file format comprises a grey scale image of said facsimile message.</li><li>Feature 29. The message storage and delivery system as set forth in feature 28, wherein said image of said facsimile message comprises a full size image of said facsimile message.</li><li>Feature 30. The message storage and delivery system as set forth in feature 28, wherein said image of said facsimile message comprises a reduced size image of said facsimile message.</li><li>Feature 31. The message storage and delivery system as set forth in feature 1, wherein said message comprises an audio message and said transmitting means transmits all of said message to said user, said system further comprising means for playing said audio message in real time as said message is received by said user.</li><li>Feature 32. A network message storage and delivery system, comprising: <ul id="ul0004" list-style="none" compact="compact"><li>a central processor for receiving an incoming call, for detecting an address signal on said incoming call, for detecting a message on said incoming call, and for placing said message in a storage area, said address signal being associated with a user of said network message storage and delivery system;</li><li>a network server for receiving said message from said storage area, for converting said message into a mixed media page layout language, and for placing said message in said storage area;</li><li>wherein when said network server receives a request from said user over said network, said network server transmits at least a portion of said message over said network to said user.</li></ul></li><li>Feature 33. The message storage and delivery system as set forth in feature 32, wherein said network comprises the Internet and said network server comprises an Internet server.</li><li>Feature 34. The message storage and delivery system as set forth in feature 32, wherein said central processor comprises pulse/tone decoder for detecting said address signal and a digital signal processor for detecting said message.</li><li>Feature 35. The message storage and delivery system as set forth in feature 32, wherein said network server comprises a hyper-text transfer protocol daemon for receiving said request from said user.</li><li>Feature 36. The message storage and delivery system as set forth in feature 32, wherein said network server sends said user an Email using after said message has been received by said central processor.</li><li>Feature 37. The message storage and delivery system as set forth in feature 32, wherein said network server is connected to a paging system for paging said user after said message has been received by said central processor.</li><li>Feature 38. The message storage and delivery system as set forth in feature 32, wherein said central processor is connected to a DID trunk and said incoming call is received over said DID trunk.</li><li>Feature 39. The message storage and delivery system as set forth in feature 32, wherein said central processor is connected to a plurality of DID trunks and said incoming call is received over one of said DID trunks.</li><li>Feature 40. The message storage and delivery system as set forth in feature 32, wherein said message comprises a facsimile message and said network server converts said facsimile message from TIFF/F into a hyper-text mark-up language file.</li><li>Feature 41. The message storage and delivery system as set forth in feature 32, wherein said message comprises a data message and said network server converts said data message into a hyper-text mark-up language file.</li><li>Feature 42. The message storage and delivery system as set forth in feature 32, wherein said message comprises a voice message and said network server converts said voice message into a hyper-text mark-up language file.</li><li>Feature 43. The message storage and delivery system as set forth in feature 32, wherein said message comprises a facsimile message and said network server generates a grey scale image of said facsimile message.</li><li>Feature 44. The message storage and delivery system as set forth in feature 43, wherein said grey scale image of said facsimile message comprises a full size image of said facsimile message.</li><li>Feature 45. The message storage and delivery system as set forth in feature 43, wherein said grey scale image of said facsimile message comprises a reduced size image of said facsimile message.</li><li>Feature 46. The message storage and delivery system as set forth in feature 32, wherein said message comprises an audio message and said network server transmits all of said message to said user, said system further comprising means for playing said audio message in real time to said user as said message is received by said user.</li><li>Feature 47. A method of storing and delivering a message for a user, comprising the steps of: <ul id="ul0005" list-style="none" compact="compact"><li>receiving an incoming call and detecting an address signal associated with said incoming call, said address signal associated with a user;</li><li>receiving a message associated with said address signal, said message being in a first file format;</li><li>converting said message from said first file format to a second file format;</li><li>storing said message in said second file format in a storage area;</li><li>receiving a request from said user for said message and retrieving said message from said storage area; and</li><li>transmitting at least a portion of said message in said second file format to said user over a transmission link;</li><li>wherein said step of transmitting occurs over a network, said step of converting said message converts said message into a mixed media page layout language.</li></ul></li><li>Feature 48. The method of storing and delivering as set forth in feature 47, wherein said step of transmitting occurs over the Internet.</li><li>Feature 49. The method of storing and delivering as set forth in feature 47, wherein said step of receiving said incoming call comprises the step of receiving said call over a DID trunk.</li><li>Feature 50. The method of storing and delivering as set forth in feature 47, wherein said step of receiving message accompanied with said address signal comprises the step of detecting a type of said message.</li><li>Feature 51. The method of storing and delivering as set forth in feature 50, wherein said step of detecting a type of said message comprises the step of detecting whether said message is a facsimile message, a voice message, or a data message.</li><li>Feature 52. The method of storing and delivering as set forth in feature 47, wherein said message comprises a facsimile message comprises and said step of converting comprises the step of converting said message from TIFF/F to hyper-text mark-up language.</li><li>Feature 53. The method of storing and delivering as set forth in feature 47, wherein said message comprises a voice message and said step of converting comprises the step of converting said message to hyper-text mark-up language.</li><li>Feature 54. The method of storing and delivering as set forth in feature 47, wherein said message comprises a data message and said step of converting comprises the step of converting said message to hyper-text mark-up language.</li><li>Feature 55. The method of storing and delivering as set forth in feature 47, further comprising the step of generating a listing of all messages for said user.</li><li>Feature 56. The method of storing and delivering as set forth in feature 55, wherein said step of generating said listing comprises the step of generating a textual listing of all messages.</li><li>Feature 57. The method of storing and delivering as set forth in feature 55, wherein said messages comprise facsimile messages and the step of generating said listing comprises the step of generating said listing of all messages along with a reduced size image of a first page of each facsimile message.</li><li>Feature 58. The method of storing and delivering as set forth in feature 47, wherein said message comprise facsimile messages and further comprises a step of providing a reduced size image of a page for one of said messages and permitting said user to scroll through pages of said one message.</li><li>Feature 59. The method of storing and delivering as set forth in feature 47, wherein said message comprise facsimile messages and further comprises a step of providing a full size image of a page for one of said messages and permitting said user to scroll through pages of said one message.</li><li>Feature 60. The method of storing and delivering as set forth in feature 47, further comprising the step of notifying said user of said message.</li><li>Feature 61. The method of storing and delivering as set forth in feature 60, wherein said step of notifying comprises the step of sending E-mail to said user.</li><li>Feature 62. The method of storing and delivering as set forth in feature 60, wherein said step of notifying comprises the step of paging said user.</li><li>Feature 63. The method of storing and delivering as set forth in feature 47, wherein said message comprises a facsimile message and step of converting said message further comprises the step of generating a grey scale image of said facsimile message.</li><li>Feature 64. The method of storing and delivering as set forth in feature 63, wherein said step of generating said grey scale image comprises the step of generating a full size image of said facsimile message.</li><li>Feature 65. The method of storing and delivering as set forth in feature 63, wherein said step of generating said grey scale image comprises the step of generating a reduced size image of said facsimile message.</li><li>Feature 66. The method of storing and delivering as set forth in feature 47, wherein said step of receiving comprises the step of receiving an audio message, said step of transmitting comprises the transmitting all of said audio message to said user in real time as said message is being receiver by said user.</li></ul>