Systems and methods for managing messages
Abstract
A network message storage and delivery system comprising: a) means (17) for receiving an incoming call (15) and for detecting an address signal associated with the incoming call, the address signal being associated with a user ( 32) of the system; b) means (41) for receiving a message, in a first file format, which accompanies the address signal; c) software controlled processor means (3) (7) for converting the first file format message to a generalized standard markup language format; d) means (11) for storing the generalized standard marking format message in a storage area; e) software-controlled server means (5) (9) for receiving a system user request for the generalized standard dialing language format message and for retrieving the message from the storage area; and f) server means that are intended to transmit at least a part of the generalized standard markup language message to the system user over a network (30); characterized in that: g) the system user request comprises a search query that specifies at least one parameter for a desired search; h) the server software (9) transfers the search query to the server (5); i) the server is intended to perform the desired search by identifying all the message signals that satisfy the search parameter; and j) the server sends the search results to the user (32) of the system.

Term
Term ended
Projected expiry passed 2 October 2018, 8 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
6 claims: 3 independent, 3 dependent
- 1ES 2 274 583 T5 REIVINDICACIONES 1. - Un método de almacenamiento y entrega de un mensaje a un usuario en una red, que comprende los pasos o etapas de:a) recibir una llamada entrante (15) y detectar una señal de dirección asociada con la llamada entrante, estando asociada la señal de dirección con un usuario (32) del sistema;b) recibir un mensaje de usuario, en un primer formato de fichero, que acompaña a la señal de dirección;c) convertir el mensaje de usuario del primer formato de fichero a un formato de lenguaje de marcado estándar generalizado;d) almacenar el mensaje de usuario de formato de lenguaje de marcado estándar generalizado en un directorio individual establecido para cada usuario en un área de almacenamiento (11);e) recibir (321) una solicitud de usuario de sistema para el mensaje de formato de lenguaje de marcado estándar generalizado e identificar el mensaje de usuario en el área de almacenamiento, la solicitud de usuario de sistema recibida comprende un formulario de consulta de búsqueda desde el usuario (32) del sistema que especifica al menos un parámetro para la solicitud de búsqueda;f) trasmitir al menos una parte del mensaje de usuario de formato de lenguaje de marcado estándar generalizado al usuario de sistema sobre una red (30);g) almacenar una entrada de datos (300) que comprende una pluralidad de campos (301-309) para identificar el mensaje de usuario para cada mensaje de usuario recibido;h) recibir (324) la solicitud de búsqueda de usuario de sistema (321), que especifica los parámetros de información de mensaje del campo de datos para una búsqueda deseada;i) realizar (324) la búsqueda solicitada a través del área de almacenamiento (11), en respuesta a la solicitud de búsqueda de usuario identificando todos los mensajes de usuario que satisfacen los parámetros de búsqueda;j) enviar (325) los resultados de la búsqueda al usuario de sistema (32);caracterizado por: k) almacenar (326) los resultados de búsqueda como un usuario mencionado: i) Búsqueda abierta, en donde la búsqueda se reactiva en respuesta a una solicitud de usuario;ii) Búsqueda cerrada, en donde los mensajes en una búsqueda mencionada están limitados a aquellos que existen en el momento de la búsqueda.
- 2- Un método como el reivindicado en la reivindicación 1 para recibir y almacenar un mensaje como una señal dirigida a un receptor pretendido y para transmitir la señal de mensaje a un ordenador de usuario además operativo para:a) recibir la llamada entrante (15) desde una red de telefonía conmutada pública (20);y b) recibir la solicitud de búsqueda en un “demonio” (37) de protocolo de transferencia de hipertextos.
- 3- Un método con el reivindicado en la reivindicación 2, y además operativo para almacenar una entrada de datos en el almacenamiento (11) para cada señal de mensaje recibida.
- 4- Un método como el reivindicado en cualquiera de las reivindicaciones 1 a 3 y además operativa para enviar (325) los resultados de búsqueda al usuario del sistema (32) devolviendo una lista de todos los mensajes contenidos dentro de la búsqueda deseada.
- 5- El método de la reivindicación 3 y además operativo para almacenar (326) la entrada de datos (300) en una base de datos relacional.
- 6- Un sistema para almacenar y entregar mensajes en red, que comprende:a) medios (17) para recibir una llamada entrante (15) y para detectar una señal de dirección asociada con la llamada entrante, estando asociada la señal de dirección con un usuario (32) del sistema;b) medios (41) para recibir un mensaje de usuario, en un primer formato de fichero, que acompaña a la señal de dirección;c) medios de procesador (3) controlados por software (7) para convertir el mensaje del primer formato de fichero a un formato de lenguaje de marcado estándar generalizado;d) medios (11) para almacenar el mensaje de formato de marcado estándar generalizado en un área de almacenamiento;y e) medios de servidor (5) controlados por software (9) para llevar a cabo el método de cualquiera de las reivindicaciones 1
Independent claims6
215 paragraphs in 16 sections, as filed
ES 2 274 583 T5
DESCRIPTION
Systems and methods for managing messages
FIELD DFI INVFNTO
This invention relates to systems and methods for storing and delivering messages and, more particularly, to systems and methods for storing messages and for delivering the message over a network, such as the Internet, or a telephone line to an intended recipient.
In another aspect, the invention relates to systems and methods for storing, delivering, and managing messages or other files, such as for archival purposes or for document tracking.
ANTFCFDFNTFS DFI INVFNTO
Even though the fax machine is highly trusted by businesses of all sizes and is fast becoming a standard piece of office equipment, many businesses or households cannot receive the benefits of the fax machine. Unfortunately, for a small business, or for a private home, a fax machine is quite an expensive piece of equipment. In addition to the cost of purchasing the fax machine, the fax machine also requires toner, paper, maintenance, as well as possible repairs. These expenses can be large enough to prevent many small businesses and certainly many households from benefiting from the service that the fax machine can provide. For other people who are constantly on the go and don't have an office, owning a fax machine may be impractical. In fact, the Atlanta Business Chronicle estimates that 30% of small businesses do not have a fax machine. As a result, many businesses and households are at a disadvantage because they cannot access a fax machine.
Because a fax machine can be an asset to a company and is highly reliable for quickly transmitting and receiving documents, there is a problem that the machines are not always available to receive a fax message. Sometimes a fax may be busy receiving another message or the machine may be transmitting a message from its owner. During these times, a person should periodically attempt to send the message until communication is established with the desired fax machine. The inability to connect to a fax machine can be frustrating, can be time consuming, and prevent the person from performing more productive tasks. While some more advanced faxes will retry to establish communication several times, one person will still have to check the fax machine to make sure the message was transmitted or restart the transmission of the message.
In addition to labor costs and a reduction in office efficiency, a fax machine can represent costs to businesses that are not easily computable. These costs include loss of business or loss of goodwill that occurs when the fax machine is not accessible by other fax machines. These costs can occur for a variety of reasons, such as when the fax machine runs out of paper, needs repair, or when the fax machine is busy with another message. These costs occur more frequently with some of the smaller businesses, who are also less capable of incurring these expenses, since many of them have only one phone line for a desk phone and the fax machine and therefore can miss so many calls. such as fax messages when the single line is busy. In fact, the Atlanta Business Chronicle estimated that less than 5% of small businesses have 2 or more fax machines. Many of the larger companies can reduce these losses by having more than one fax machine and having switched calls to another machine when one of the machines is busy. These losses, however, cannot be completely eliminated, as machines may still experience a demand that exceeds their capacities.
A main benefit of the fax machine, in particular the fast transfer of documents does not necessarily mean that the documents will be sent quickly to the intended recipient. Fax machines can be unattended and a received fax message may not be observed until a relatively long period of time has elapsed. Furthermore, even for those machines that are under constant supervision, the routine procedures established in an office can delay the delivery of documents. It is therefore a problem in many offices to quickly send the fax message to the intended recipient.
The nature of the fax message also makes it difficult for the intended recipient to receive a sensitive message without having exposed the message to others in the office who may intercept and read the message. If the intended recipient is not aware that the message is being sent, another person can view the message while it is being delivered or while the message remains close to the machine. When the intended recipient realizes that a sensitive message is being transmitted, the intended recipient must wait near the fax until the message has been received. As a result, it was difficult to keep the content of a fax message confidential.
In an office with a large number of employees it can be difficult to determine simply where the item should be shipped.
ES 2 274 583 T5 fax message. In light of this difficulty, some systems have been developed to automatically route fax messages to their intended recipient. One type of this system, such as that described in US Patent No. 5,257,112 to Okada, can route an incoming call to a particular fax based on codes entered with push buttons on the telephone by the sender of the message. Another type of system, such as that described in US Patent No. 5,115,326 to Burgess et al. or in US Patent No. 5,247,591 to Baran, it requires the sender to use a specially formatted cover page that is read by the system. This type of system, however, involves the sender, who may very well be a customer, requiring the sender to perform special operations or additional operations to transmit a fax message. These systems are therefore not very effective or desirable.
Another type of routing or forwarding system links a fax to a Local Area Network (LAN) in an office. For example, in the system described in the Baran and Burgess et al. Patents, after the system reads the cover page to determine the intended recipient of the fax message, the system sends an electronic mail message (email) to the receiver via the local network that connects the fax with the receiver's computer. Other office systems, such as Silverberg US Patent No. 5,091,790 and Giler et al. US Patent No. 5,291,546, are linked to the office voice message system and you can leave a message. with the intended recipient that a fax message has been received. Some systems that are even more advanced, such as those in US Patent No. 5,317,628 to Misholi et al and US Patent No. 5,333,266 to Boaz et al., Are connected to a local office network and provide full control of voice messages, email messages, and fax messages.
The various systems for routing fax messages, and possibly messages of other types received in the office, are very sophisticated and expensive systems. Although these office systems are desirable because they can effectively route messages in the office to their intended recipients, the systems are extremely expensive and only companies with large numbers of employees can offset the system costs with the benefits that the system will provide to your company. Thus, for most businesses, it is still a problem to effectively and quickly route messages to the intended recipients. It also remains a problem for most businesses to route messages in a way that can preserve the confidential nature of the messages.
Even for businesses that have a message routing system and especially those without any system, it is normally difficult for a person to retrieve fax messages while away from the office. Typically, a person away from the business should call the office and be informed by someone in the office of the fax messages that have been received. Consequently, the person must call the office during normal business hours while someone is in the office and is therefore limited in the time that information from a fax message can be transmitted.
If the person away from the office wants to view the fax message, someone in the office must resend the message to a fax machine accessible to that person. As this accessible machine is often a fax machine in another business or a hotel where the person is staying, it is difficult for the person to receive the fax message without risking discovering its content. Also, because someone in that person's office must remember to send the message and because someone at the accessible fax machine must route the message to the person who is far from the office, the person may not receive all of the fax messages or may have to wait to receive the messages.
Retrieval of fax messages, as well as voice messages, while you are away from the office is not done without a certain cost. For one, the person must often incur long distance phone charges when the person calls the office to check messages and have someone in the office to send the messages to another fax. The person will then incur the costs of transmitting the message to a fax office or a hotel reception, as well as the charges of the reception situation for the use of their equipment. Although these charges are certainly not substantial, the charges are nonetheless expenses incurred while the person is away from the office.
Above all, while the fax machine is an indispensable piece of equipment for many businesses, the fax machine presents various problems or costs. Many businesses or households are at a disadvantage as they are unable to reap the benefits of the fax machine. For businesses that have fax machines, businesses must incur the normal costs of running the fax machine in addition to the costs they may incur when the fax machine (s) are unable to receive a message. Furthermore, fax messages may not be efficiently or reliably routed to the intended recipient and may have their content revealed during the sending process. The costs and problems in sending a fax message are compounded when the intended recipient is away from the office.
Many of the problems associated with fax messages are not unique only to fax messages but are also associated with voice messages and data messages. With regard to voice messages, many businesses do not have voice mail systems and must write the message. Thus, the person who is far from the office should call
ES 2 274 583 T5 during normal business hours to find out who has called. The information in these messages is normally limited only to the person who called, their number, and perhaps some indication as to the nature of the call. For those businesses that have voicemail, the person who is far from the office must call and frequently incur long distance charges. Thus, there is a need for a system that stores and delivers voice messages that can be easily and cheaply accessed at any time.
With regard to data messages, the transmission of the message often requires some coordination between the sender and the receiver. For example, the recipient's computer must be turned on to receive the message, which usually occurs only when someone is present during normal business hours. Consequently, the recipient's computer is normally only capable of receiving a data message during business hours. Many homes and businesses may not have a dedicated data line and must switch the line between the phone, the computer, and the fax. In such a situation, the sender must call to inform the receiver to switch the line over the computer and may have to wait until the sender can receive the message. Retransmission of the data message to another location, such as when someone is away from the office, only further complicates delivery. It is therefore often difficult to transmit and receive data messages and it is also difficult to transmit the messages later to another location.
A standard business practice of many companies is to keep records of all correspondence between the company and other entities. Traditionally, correspondence that has been tracked and recorded includes letters or other types of printed materials that are mailed to or from one company to another entity. Although tracking correspondence from printed materials is relatively easy, non-traditional correspondence, such as fax messages, email messages, voice messages, or data messages, are more difficult to track and record.
For example, fax messages can be difficult to track and record as messages can be received on thermal paper, which has the disadvantage that the print fades over time. Also, accurate tracking of fax messages is difficult as the fax messages may only be partially printed on the fax machine or the messages may be lost or only partially delivered to their intended recipients. Fax messages also present difficulties as they are often delivered within an organization through different channels than ordinary mail and thus easily fall outside the normal record keeping procedures of the company.
Voice messages are also difficult to follow and record. Although voice messages can be saved, many voicemail servers automatically delete messages after a certain period of time. To keep a permanent record of a voice message, the voice message can be transcribed and a hard copy of the message can be kept in the records. This transcribed copy of the voice message, however, is less credible and therefore less desirable than the original voice message as the transcribed copy may have altered material or may omit certain parts of the message.
In addition to fax and voice messages, data messages are also difficult to track and record. A download or upload of a file can only be evident by the existence of the same file. A file transfer procedure does not normally by itself lead to any permanent recording of what file was transferred, the telephone number dialed, the telephone number of the computer receiving the file, the time, or the date of the transfer. It is therefore difficult to keep accurate records of all transfers between each other and another entity.
PREVIOUS TECHNIQUE
Document WO-A-96/34341 [BOBO CHARLES II] describes “A Message Storage and Delivery System (MSDS) (10) is connected to a plurality of DID telephone lines and receives fax messages, voice messages, and data messages. The messages are stored in memory and are also converted to appropriate hypertext markup language (HTML) files (30). Users can then connect to the MSDS (10) via the Internet (30). Users of the MSDS (10) therefore have the advantage of being able to receive their messages at any time and anywhere at a reasonable cost. The user can also phone the MSDS (10) to listen to messages or alter the service provided by the MSDS (10. "
COMPENDIO DEI INVENTO
It is a feature of the invention to reliably and efficiently route messages to an intended recipient.
It is another feature of the invention to route messages to the intended recipient while keeping the content of the message confidential.
It is another feature of the invention to allow the intended recipient to access the messages easily and at minimal cost.
ES 2 274 583 T5
It is another feature of the invention to allow the simultaneous reception of more than one message from the intended recipient.
It is another feature of the invention to allow the intended recipient of a message to access the message at any time and in any position virtually around the world.
It is yet another feature of the invention to allow the intended recipient of a message to search through received messages.
It is yet another feature of the invention to promptly notify an intended recipient that a message has been received.
It is still another feature of the invention to receive messages of different types.
It is yet another feature of the invention to deliver messages according to the preferences of the intended recipient.
It is still another feature of the invention to record and track correspondence, such as fax messages, voice messages, and data transfers.
PEI INVENT EXHIBITION
The present invention provides a method, as set forth in claims 1 to 5, of storing and delivering a message to a user on a network; and a network message storage and delivery system, as set forth in claim 6.
WO-A-96/34341 does not teach a network server to receive the message from the storage area, to convert the message into a mixed media page layout or layout, and to place the message in the storage area. .
Additional advantages and new features of the invention will be set forth in the description that follows, and will become apparent to those skilled in the art after reading this description or practicing the invention. The objects and advantages of the invention can be realized and achieved by the appended claims.
RRFVF PFSCRIPCIÓN PF IOS PIRUJOS
The accompanying drawings, which are incorporated in and form part of the specification, illustrate one embodiment of the present invention and, together with the description, serve to explain the principles of the invention. In the drawings:
Figure 1 is a block diagram illustrating the connections of an MSPS message storage and delivery system;
Figure 2 is a total flow chart of operations for transmitting a message to the MSPS of Figure 1;
Figure 3 is a total flow diagram of operations to receive a message stored in the MSPS of Figure 1;
Figures 4 (A) and 4 (R) are operation flow diagrams for generating HTML files according to user preferences;
Figure 5 is a flow chart of operations to generate the requested information;
Figure 6 is a flow chart of operations for converting a fax message to HTML files;
Figure 7 is an exemplary presentation of a first page of a fax message in accordance with a fourth presentation option;
Figure 8 is a flow chart of operations for converting a voice message to an HTML file;
Figure 9 is a flow chart of operations for converting a data message to an HTML file;
Figure 10 is a flow chart of operations for detecting a type of call received at MSPS 10;
Figure 11 is a flow chart of operations for receiving voice messages;
Figure 12 is a flow chart of operations for interacting with an owner call;
Figure 13 is a more detailed block diagram of MSPS 10;
Figure 14 is a block diagram of the central processor in Figure 13;
Figure 15 is a block diagram of the Internet Server of Figure 13;
Figures 16 (A) and 16 (R) represent possible software layers for the Internet server of Figure 13;
Figure 17 is a diagram of a data input for a message signal;
Figure 18 is a flow chart of a process for submitting a search query, for conducting a search, and for returning search results to a computer via the Internet;
Figure 19 is an example of a search query format for defining a desired search;
Figure 20 is an example of a complete search query;
Figure 21 is an example of a set of search results returned to the computer in response to the search query of Figure 20; and
Figure 22 is an example of a stored search list.
ES 2 274 583 T5
DFSCRIPTION DFTAIIADA DF IAS RFAII7ACIONFS PRFFFRIDAS
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 Figure 1, a message storage and delivery system (MSDS) 10 is connected to a central office 20 of the telephone company via at least one direct inward dialing (DID) line 15. With each call on DID line 15, an address signal indicating the telephone number being called is provided to MSDS 10. DID line 15 can support a large number of telephone numbers or addresses. Preferably, the DID line 15 comprises a number of DID lines 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, furthermore, it can simultaneously receive more than one call to a single phone number or address.
The central office 20 is connected to a number of third parties. For example, central office 20 may be connected to a fax machine 24, a telephone set 26, and a computer 28 with each connection being made through a separate telephone line. Although a single computer 28 is shown in the figure, the single computer 28 may actually represent a local area network that is connected through the central office 20 to the MSDS 10. Although the fax machine 24, the telephone set 26, and the 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 30 (World Wide Web). 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 structure that is constantly evolving and changing. The MSDS 10 is not therefore limited to the current structure or form of the Internet 30 but encompasses any future changes or additions to the Internet 30. Furthermore, 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, can be implemented with any suitable Internet connection 30, such as through an intermediate Internet access provider.
With reference to Figure 2 which depicts a total operation of the invention, a telephone call directed to a number served by the MSDS 10 is initiated in operation 40 by a third party, for example, through the fax machine 24, from the telephone apparatus 26, or computer 28. The incoming telephone call can therefore carry a fax message, a voice message, or a data message. In step 42, the address signal associated with the initiated call is routed through central office 20, over DID line 15, and to MSDS 10.
When the call reaches MSDS 10, the call is routed into MSDS 10 in a manner that will be described in more detail below with reference to Figure 3. In step 46, MSDS 10 answers the phone call and receives the address signal from the DID line 15. Next, in step 48, the call is established between the MSDS 10 and the third party and, in step 50, the MSDS 10 receives the message transmitted over the telephone line. The message is stored in step 52, a database within the MSDS 10 is updated in step 54, and the intended recipient of the message is notified in step 56. The intended recipient of the message uses the services provided by the MSDS 10 and will be referred to hereinafter as a user. In operation 58, the message is converted to Hypertext Markup 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 anywhere by connecting to the Internet World Wide Web 30 and retrieve the message stored within the MSDS 10. With reference to Figure 3, in step 60 the user first connects to the Internet 30, such as through a personal computer 32 that can be connected to the Internet 30 in any suitable way, such as through his 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 computer network, such as a local area network within the office.
Once connected to the Internet 30, in operation 62, the user accesses with a browser or hypertext search engine the Universal Resource Positioner (URL) associated with his MSDS mailbox 10. The computer 32 can use any suitable hypertext browser, such as Netscape, to access the mailbox. A Hypertext Transfer Protocol Daemon (HTTPD) within the MSDS 10 receives the URL request at step 64 and, at step 66, requests user authentication. The user then provides his ID and password in step 68 and, if valid in step 70, the MSDS 10 provides computer 32 with access to the mailbox in step 72. If the ID and password are invalid, as determined in step 70, then the HTTPD sends an authentication failure message to computer 32 at step 74.
After the user gains access to the mail in step 72, the user can request information stored within the MSDS 10. The MSDS 10 receives the request in step 76 and, in step 78, determines whether
ES 2 274 583 T5 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, the presentation preferences, and, if the message is a fax message, a page identifier. If for any reason the request is invalid, such as when a hacker is attempting to gain access to inside information, the request for the information will be terminated.
If the requested information is available, then in step 80 the information is transmitted via the Internet 30 to the user's computer 32. If, on the other hand, the information does not exist, then in step 82 the MSDS 10 will generate the requested information and then send the information to the user's computer via the Internet 30 in step 80.
Before accessing the mailbox in operation 72, the user is preferably sent a welcome page or other information that allows the user to learn about the services provided by the MSDS 10, open an account with the MSDS 10 , or access an account. Once access is provided in step 72, information is provided to the user indicating the total number of messages stored in his mailbox within MSDS 10. Preferably, the information sent by MSDS 10 indicates the total number of messages. messages for each message type and also the total number of saved messages against the total number of new messages.
The user is also preferably given the option in this operation to change the account information. Account information could include the email address for the user, how messages are to be reviewed, the user's pager information, as well as other user preferences. Presentation options and other user preferences will be described in more detail below.
The general information HTML file indicating the total number of different messages is provided with several anchors, which are also called links or references. In general, an anchor allows a user on computer 32 to retrieve information located in another file. For example, an anchor to a list of fax messages is preferably provided in the presentation of the total number of messages. When the user selects the anchor for the fax list, the MSDS 10 extracts and displays the file containing the fax list, such as a "faxlist.html" file. The other types of messages, such as voice messages and data messages, would have similar anchors on the overview page directed to their respective HTML list files.
When a new message is received in step 54 in Figure 2, the user's mailbox is updated to display the total number and types of messages. The MSDS 10 could also update other files in addition to the total message list. Additionally, at this time, the MSDS 10 sends an email message to the user's computer 32 to inform the user of the message just received. The MSDS 10 could also notify the user through a paging system so that the user receives almost instantaneous notification that a message has been received.
The MSDS 10 also generates additional information according to user preferences. These preferences for how the MSDS 10 is configured for the user include options for how messages are reviewed. With fax messages, for example, the user can vary the amount or type of information that will be supplied with the list of fax messages by selecting an appropriate option. Other options are also available so that the user can tailor the MSDS 10 to the user's own computer 32 or personal preferences.
For example, when a fax message is received, the MSDS 10, in step 54, will update the total list of all messages to indicate the newly received message and may additionally generate the HTML files for the newly received fax message accordingly. with user preferences. When the user later requests information from the message in step 76, the HTML information has already been generated and the MSDS 10 can directly send the requested information to the user in step 80. If, on the other hand, the user wants to view the message from According to one of the other options, the MSDS 10 will generate the HTML files in step 82 according to that other option at the time of the request.
A first option available to the user for viewing a fax message is a single textual message list. The information in the textual list preferably includes the date and time the message was received on the MSDS 10, the telephone number from which 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 fax messages from 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 computer 32, the message can be displayed, printed, or saved for further review.
The second through five options allows the user to preview an image of the fax message before
ES 2 274 583 T5 have the message downloaded from the MSDS 10 through the Internet 30 and to the computer 32. The second option allows the user to view the list of messages with a reduced size image of the cover page after each entry in the list. When the user selects one of the messages from the list, the selected fax message is transmitted over the Internet to the computer 32. The user can also scroll through the lists if all messages cannot be viewed at once on the computer 32.
The third option provides the user with a full-size view of the cover page of each fax 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 main pages allows the user to clearly discern any comments that may be located 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 allows the user to scroll through the entire message. The user can therefore read the entire fax message on the screen before the message is downloaded onto the computer 32. With this option, the user can go through the pages of the fax message and can also go to the next message or to the previous one. Additionally, the user has the option to enlarge 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 fax message to be transmitted over 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 fax message and easily read the content of each page. If the user wants the message downloaded to computer 32, the user selects message and the HTTPD within the MSDS 10 transmits the message to the user's computer 32 via the Internet 30.
As described above, after the database is updated at step 54, the MSDS 10 will generate additional information based on the option selected for presenting the fax messages. More specifically, as shown in Figure 4 (A), if the first option has been selected, as determined in step 100, then in step 102 the MSDS 10 will generate the textual list of the fax messages with anchors or references to the respective fax files. The HTML files are then moved to an Internet Server in step 104.
If the first option is not selected, the MSDS 10 then determines whether the second option has been selected in step 106. With the second option, the fax messages are listed along with a reduced size image of the cover page. To generate this information, the cover page is extracted from the fax file in step 108 and a reduced size HTML image of the cover page is created in step 110. At step 112, a list of the fax messages is generated with a thumbnail view of each main page linked to its respective fax file. The generated HTML files are then sent to the Internet Server in step 104.
When the third option is selected, as determined in step 114, a full-size image of the cover page is sent to computer 32. The full-size image of the cover page is generated by first extracting the cover page. of the fax file in operation 116. Next, the cover page is converted to a full-size HTML image in step 118 and, in step 120, the list is generated with the embedded cover page linked to the fax file.
If, in step 122, it is determined that the fourth option is selected, then a reduced size image of each page is provided to the user with the option to enlarge the page to see the content of the page more clearly. Referring to Figure 4 (B), the information necessary for the third option is produced by first extracting the first page of the fax message in step 124. A reduced size HTML image is created in step 126 and then a full size HTML image is created in step 128. In step 130, the list is generated with embedded thumbnail images of the pages with links to the images of the full size. If the page is not the last page, as determined in step 140, then the next page is extracted in step 142 and steps 126 to 130 are repeated to generate the HTML files for the other pages of the fax message. After the last page has been converted to an HTML file according to the third option, the files are moved to the Internet Server in step 104.
At step 144, the MSDS 10 determines if the fifth option has been selected. The fifth option provides the user with a full-size image of each page of the fax message. Although only five options have been described, the invention can be practiced with additional options. Consequently, with additional notions and the fourth option not having been selected, the MSDS 10 would then determine if one of the additional options has been selected. With the preferred embodiment of the invention having only five options, however, the
ES 2 274 583 T5
MSDS 10 will assume that the fifth option has been selected if none of the first four options were found to have been selected.
The information necessary to display the pages of the fax message according to the fifth option is generated by first extracting the first page of the fax message in operation 146. In operation 148, a full-size HTML image of the page is created and , in step 150, a list is generated with an embedded image and links to previous and next pages. When the page is not the last page, as determined in step 152, the MSDS 10 extracts the next page and generates the HTML file for that page. After all the pages have been converted to HTML files according to the fourth option, the files are sent to the Internet Server in step 104.
While Figures 4 (A) and 4 (B) describe the operations of the MSDS 10 at the time of a received message, Figure 5 represents a total flow diagram of operations for the MSDS 10 when the user requests an information page in a presentation format other than the user's preferred option to present the message. Figure 5 is therefore a more detailed explanation of how the MSDS 10 generates the necessary information in operation 82 of Figure 3.
In general, as shown in Figure 5, the MSDS 10 first determines the type of image that is necessary in step 82a. For example, in this operation, the MSDS 10 will determine if images are not needed, if an image only of the cover page is needed, if an image is needed for each page, and if the image needs to be full size, size reduced, or both full and reduced size images. In step 82b, the MSDS 10 determines if the image has already been created. If the image has not been created, then at step 82c the MSDS will extract the page from the base fax file and, at step 82d, generate the required HTML image. As described above, the required image may be for the cover page only, for all pages, and it may be a full-size and / or reduced-size image of the page. In step 82e, the image is embedded with links or anchors to other HTML files. These links or anchors could be references to the next and previous pages and also to the next and previous fax messages. Finally, the HTML file that has the embedded image and links is sent to the user in operation 80 in Figure 3.
The processes for converting a fax message into HTML files according to the fifth option will be described with reference to Figure 6. This process will occur in operation 54 when the received message and when the fifth option is the user's preferred option to present the messages. It should be understood that a similar type of process will also occur when the user requests an information page according to the fifth option when the user is retrieving a fax message and the fifth option is not the user's preferred option. Conversion processes according to the other options will be apparent to those skilled in the art and will not therefore be described in further detail.
Referring to Figure 6, when the fax message is received, the message is in a Tagged / Fax Image File Format (TIFF / F) and each page of the fax message is divided into a separate file. Each page of the fax message is then converted from the TIFF / F format to a Portable Picture Element Map (PPM) format. The PPM files are then converted to separate Graphic Interchange Format (GIF) files and then to separate HTML files. Thus, each page of the fax message is converted to a separate HTML file. TIFF / F files can be converted to PPM with an available software package titled "LIBTIFF" and PPM files can be converted to GIF files with an available software package found in Portable Image Element Map Tools.
The invention is not limited to this exact conversion process or the particular software packages used in the conversion process. For example, TIFF / F files can be converted to another portable file format, through any other type of intermediate format, or they can be directly converted to GIF format. Also, instead of GIF, fax messages can be converted to JPEG, BMP, PCX, PIF, PNG, or any other suitable type of file format.
Files can be identified with any suitable filename. In the preferred embodiment, the files for each user are stored in a separate directory assigned only to one user because an entire directory for a given user can generally be protected more easily than individual files.
The memory, however, should be organized in other ways, the files being stored for a single user in different directories. The first part of the file name is a number preferably determined sequentially according to the order in which messages arrive for that user. The preferred naming arrangement for terminating filenames is depicted in Figure 6. Each page of the fax message is saved as a separate file with an extension defined by the file format. Thus, the files will end with an extension of ".TIFF," ".PPM," ".GIF," or ".HTML" according to the particular file format. In the example
ES 2 274 583 T5 shown, the separate pages have file names that end with the respective page number, for example, the first page ends with a "1." The files, however, are preferably terminated with a letter or multiple letters to indicate the order of the pages. For example, page 1 could end with "aa," Page 2 could end with "ab," and so on. The invention, however, is not limited to the naming agreement described but encompasses other agreements that will be apparent to those skilled in the art.
As shown in Figure 6, in addition to the GIF files representing the pages of the fax 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". The anchor a is defined as a = <A HREF = “2.html"> Next Page </a> and therefore will refer to 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 fax message and see a full-size image of the page.
Each HTML file preferably contains anchors in addition to those for Next Page and Previous Page. For example, each HTML file can contain an anchor to the next fax message, and an anchor to the previous face message, and an anchor to return to the fax list. HTML files preferably contain anchors relative 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 question as to whether the user is sure they want to delete the message. Other anchors, such as an anchor to the general list, will be apparent to those skilled in the art and may also be envisioned.
Figure 7 provides an example of a presentation according to the fifth option for the first page of the fax message shown in Figure 6. The presentation headings provide information on the telephone number from which the message was sent, on the day and the time the message was received on the MSDS 10, and an indication of the page of the message that is displayed. The main part of the presentation is the full size image of the page. At the end of the presentation, an anchor or link to the "Next Page" has been provided and another anchor has been provided for the "Return to Fax List". Information may also be provided in the presentation, such as a link to a company using the MSDS 10.
An example of the "1.html" file to generate the presentation shown in Figure 7 is shown below in Table 1.
TABLE 1 <HTML>
<HEAD>
<TITLE> Fax Received May 31, 1995, at 1:58 PM from (404) 249 6801;
Page 1 of 3 </TITLE>
</HEAD>
<BODY>
<H1> Fax from (404) 249-6801 </H1>
<H2> Received May 31, 1995 at 1:58 PM </H2>
<H2> Page 1 of 3 </H2>
<IMG SRC = ”1.gif '>
<P>
<A HREF="2.html"> Next Page </a>
<HR>
<A HREF="faxlist.html"> Return to Fax List </A>
<P>
This page was automatically generated by FaxWeb (tm) on May 31, 1995, at 2:05 PM.
<P>
& copy; 1995 NetOffice, Inc.
<HR>
<Address>
<A HRFF=http7/www netoffice com/> NetOffice, lnc </A> <BR>
PO Box7115 <BR>
Atlanta, GA 30357 <BR>
<A REF="mailto:infoetoffice.com"> infonetoffice.com </A>
</Adress>
</BODY>
</HTML>
ES 2 274 583 T5
As is evident from the list in Table 1, the image file "1.gif" for the first page is embedded in the HTML file "1.html.". It is also evident from the list that the anchor for "Next Page" directs the MSDS 10 to the second page of the fax message that has the file name "2.html" and the anchor for "Return to list of Fax ”directs the MSDS 10 to the file name“ faxlist.html ”that contains the list of fax messages.
Illustrated in Figure 8 is a process for converting a voice message into an HTML file. The voice message is originally stored in a VOX format or an AD / PCM format and is retrieved in step 170. The voice message is then converted to either an AU format or a WAV format according to the user's preference. , which is stored in memory. Preferably, the message is preferably in the AD / PCM format originally and is converted to WAV, but the voice files can alternatively be stored and converted in file formats other than those described, such as RealAudio (RA).
At step 174, the list of all voice messages is then updated to include a list of the newly received voice message and an anchor to the voice message. For example, the original voice message can be stored with the filename "1.vox" and it is converted to WAV and stored with a filename "1.wav.". The HTML file "voicelist.html" containing a list of all voice messages would then have an anchor to the file name "1.wav" along with identifying information for the voice message, such as when the message was received.
The list of voice messages can have additional anchors or references. For example, each voice message may have an anchor that directs the MSDS 10 to a file that contains a short sample 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 list of fax messages, the list of voice messages also preferably has anchors for "Save" and "Delete".
Figure 9 illustrates a process for converting a data message to 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 list of the newly received message with identifying information. For example, the HTML file for the listing "datalist.html" would be updated to include an anchor for a data file "file1.1" and would have information such as the time and date the data was transmitted, the size of the data file, as well as additional identification information.
Because the MSDS 10 can receive messages of different types, such as a fax message, a voice message, or a data message, the MSDS 10 must be able to determine the type of message that is being sent over the DID line. 15. Referring to Figure 10, when an incoming call is received, the MSDS 10 disengages at step 200 and begins to generate a ringing sound. If, at step 202, a fax ringtone is detected, then the ringtone is stopped at step 204 and the message is received as a fax message at step 206. Similarly, when a data modem ringtone at step 208, the ringtone 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 in step 218, the message is identified as a fax message. The MSDS 10 thereafter will receive and store the fax message in the manner described above with reference to Figure 2. If the digit is identified as a "0" in step 220, the call is identified as an owner call and will be processed in the manner to be described later with reference to Figure 12. As will be apparent, other digits may do. MSDS 10 to take additional operations. If any other DTMF digit is pressed, in step 224 the MSDS 10 activates a voice call system, which will be described in greater detail below with reference to Figure 11.
With operation 226, the MSDS 10 will enter a continuous check loop for a fax ringtone, a data modem ringtone, or for a DTMF digit. If after n rings none of these tones or digits are detected, the ringing sound is stopped in step 228 and the voice calling system is activated in step 224.
Referring to Figure 11, when a fax ringtone or modem ringtone is not detected, the voice calling system begins at step 230 by playing a voice greeting. If the greeting has not been interrupted by a DTMF digit as determined in step 232, then the caller is triggered for the voice message in step 234 and, in step 236, the voice message is recorded and stored in memory. At step 238, the caller is provoked with various options, such as listening to the message, saving the message, or re-recording the message. As 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 in operation 240, the caller is again
ES 2 274 583 T5 triggered for a message in step 234. If the caller does not want to re-record the message, the call is terminated in step 242.
If the voice greeting is interrupted by a DTMF digit, as determined in step 232, then the MSDS 10 finds out which digits have been pressed. At step 244, if the digit is a "0", the MSDS 10 detects that the call is an owner call. When the digit is a "1", the MSDS 10 is informed in step 206 that the call carries a fax message. As described above with reference to Figure 10, other DTMF digits may cause the MSDS 10 to take additional operations. 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 Figure 11. As described above, the invention can respond to DTMF digits other than just a "0" and a "1". Other variations and alterations will be apparent to those skilled in the art.
Referring to Figure 12, when the call is considered an owner call, the caller is first triggered for the password at step 250. The password is received at step 252 and, if found correct at step 254, a set of advertisements are played for the owner. These announcements would preferably inform the owner of the number of new messages that have been received, the number of saved 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 example, the DTMF digit "1" may be associated with playing a message, the DTMF digit "2" may be associated with a menu of options, and the DTMF digit "*" may be associated with returning to a previous menu. or end the call if there is no previous menu.
A DTMF digit is detected in operation 260 and the appropriate action is taken based on the received digit. Thus, if the digit is determined as a "1" in step 264, the owner can play a message in step 266. In step 266, the owner is preferably greeted with a menu that provides the owner with the options to play or play. download new messages, saved messages, fax 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 as a "2" in operation 268, then the owner receives a menu of options in operation 270. With the menu of options, the owner can enter or change certain parameters of the MSDS 10 . For example, the owner can change his password, the owner can change the way fax messages are presented on the computer 32, the owner can change the image file format from GIF to another format, the owner can select file formats for voice messages, as well as other options.
If the DTMF digit "*" is received, as determined in step 272, then the owner is returned to a previous menu. The digit "*" is also used to end the call when the owner has returned to the initial menu. The digit "*" is therefore universally recognized by the MSDS 10 in all the different menus as a command to return to a previous menu.
If the owner enters a DTMF digit that is not being used by MSDS 10, the owner receives an indication at step 276 that the password is invalid and the owner is then provided with the user menu again at step 258 When the owner does not enter a DTMF digit while the owner menu is being played, as determined in operation 260, the menu will be played again n times. Once the menu has been replayed n times, as determined in step 262, then the call will be terminated at step 278.
If the password is incorrect, as determined in step 254, then the MSDS 10 checks if the user has made more than "n" attempts at step 280. If no "n" attempts have been made, then it will be displayed. an incorrect password message to the user at step 282 and the user will be triggered again for the password at step 250. When the user has made "n" attempts to enter the correct password, the MSDS 10 will play an error message for the user at step 284 and then terminate the call at step 286. The specific number "n" can be three of so the call is terminated after three unsuccessful attempts.
The owner's menu can be sensitive to an additional number of DTMF digits and can be structured differently. For example, separate DTMF digits can direct the owner to the respective types of messages, such as a fax message, a data message, or a voice message. Also, separate DTMF digits can direct the
ES 2 274 583 T5 owner to a recording of new messages or a recording of saved messages. Other variations will be apparent to those of skill in the art.
A more detailed diagram of the MSDS 10 is shown in Figure 13. As shown in the figure, a plurality of DID lines 15 are received by an input / output device 17 and are then sent to a central processor 3. The number of li DID lines 15 can be changed to any appropriate number that would be necessary to accommodate the anticipated number of phone calls that can be made to the MSDS 10. The input / output device 17 routes a call on one of the DID lines 15 to an open port of the central processor 3 and is preferably a DID Junction Box manufactured by Exacom.
The central processor 3 receives the calls on the DID lines 15 and stores the messages in the storage 11 according to the software 7. Preferably, a separate directory has been established in the storage 11 for each user who has an account on the MSDS 10 so that all messages for a single user will be stored in the same directory. It should be understood that the number of processors within the core processor 3 depends on the number of DID lines 15. With a greater number of DID lines 15 capable of handling a greater number of telephone calls, the central processor 3 can actually comprise several computers. The input / output device 17 would then function to route the incoming calls to an available computer within the central processor 3.
A more detailed diagram of central processor 3 is shown in Figure 14. Central processor 3 comprises a telephone line link 21 for each DID line 15. Telephone link 21 provides the call sounds and other communication that links to the lines telephone. The signals from the telephone link 21 are routed to a pulse / tone decoder 23 and a digital signal processor (DSP) 25. The pulse / tone decoder 23 detects the turned off address signal of an incoming call and sends the address signal over a transmission line or bus 29 to a microprocessor 27. The DSP performs the necessary signal processing on incoming calls and routes the signals processed to the microprocessor 27.
The microprocessor 27 will then read the address signal from the pulse / tone decoder 23 and stores the message from the DSP 25 in an appropriate directory in storage 11. As described above, the central processor 3 may comprise several computers or more precisely, several microprocessors 27 with each microprocessor 27 handling calls from a certain number, such as four, DID lines 15. Microprocessor 27 may comprise any suitable microprocessor, but at least one PC 486 is preferable.
In addition to handling incoming calls and storing messages in storage 11, central processor 3 also coordinates the interactive voice response system of MSDS 10. The software 7 would incorporate the flow diagrams of operations to receive a message, shown in Figure 3, to detect the type of message in an incoming call shown in Figure 10, to receive voice messages shown in Figure 11, and to receive a call from the owner shown in Figure 12. Based on the above referenced flow charts and respective descriptions, the production of the software 7 is within the ability of one skilled in the art and will not be described in 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 various functions according to the software 9. For example, the Internet server 5 retrieves the data files stored in the memory 11 by the central computer 3 and converts the files into the appropriate HTML files. The converted HTML files are then stored in memory 11 and can be downloaded to computer 32 via the Internet 30. Internet Server 5 also handles requests from computer 32, which may require retrieval of files from storage. 11 and enable the generation of additional HTML files.
The software 9 for the Internet Server 5 would therefore incorporate the flow diagram of operations to generate HTML files according to the user preferences shown in Figure 4, to generate information required by a user shown in Figure 5, to convert HTML fax messages shown in Figure 6, to convert voice messages to HTML shown in Figure 8, and to convert data messages to HTML shown in Figure 9. Based on the aforementioned flowcharts and their respective descriptions, the production of the software 9 is within the ability of one skilled in the art and need not be described in further detail.
However, a more detailed block diagram of the Internet Server 5 is shown in Figure 15. The Internet Server 5 runs on a suitable operating system (OS) 39, which is preferably Windows NT. The Internet Server 5 has various application programs 31, such as those represented in the flow diagrams described above, to communicate with the central processor 3 and to access data from storage 11 and also from memory 33.
The memory 33, among other things, would contain the data indicating the preferences of each user. For example,
ES 2 274 583 T5 when a fax message in the TIFF / F format is retrieved by the Internet Server 5, the Internet Server 5 would find out from the data in memory 33 the preferred presentation option of the fax message and would generate the appropriate HTML files.
All links to the Internet 30 are handled by HTTPD 37, which, in the preferred embodiment, is an "Enterprise Server" from NetScape Communications. Corp. Any request from users, such as a request for a file, would be handled by HTTPD 37, transferred through CGI 35, and then received by application programs 31. The application programs 31 would then take appropriate actions in accordance with the request, such as transferring the requested file through CGI 35 to HTTPD 37 and then through the Internet 30 to user computer 32.
The Internet Server 5 can 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 can also activate the paging system 13 of so that a pager 15 would be activated. In this way, the user could almost instantly receive the notification that he has received a message.
The paging system 13 is preferably one that transmits alphanumeric characters so that a message can be relayed to the user pager 15. The Internet Server 5 therefore comprises a signal processor 41 for generating signals recognized by the paging system 13 and a telephone link 43. The signal processor 41 preferably receives the information from the application programs 31 and generates a paging message in a paging file format, such as XIO / TAP. The telephone link 43 would include a modem, an automatic dialer, and other components suitable for communicating with the paging system 13.
The information from the application programs 31 may simply notify the user of a message or it may provide more detailed information. For example, with a fax message, the information from the application programs 31 may comprise CSI information that identifies the telephone number of the sender. The user would thereby receive a message on pager 15 informing the user that a fax message has been received from a specified telephone number. The amount and type of information that can be sent to the user on the pager 15 can vary according to the capabilities of the paging system 13 and can provide a greater or lesser amount of information than the examples provided.
The Internet Server 5 is not limited to the structure shown in Figure 15 but may comprise additional components. For example, the HTTPD 37 would be linked to the Internet 30 through some type of link, such as a modem or a router. The Internet Server 5 can be connected to the Internet 30 via typical telephone 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 can be connected to other types of networks. For example, Internet Server 5, or more generally Network Server 5, could be connected to a large private network, such as that established for a large corporation. The Network Server 5 would function in the same way by converting messages into HTML files, receiving requests for information from users on the network, and transmitting the information to users.
Also, at least one interchange 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 link can be provided within both of the Internet Server 5 as of the central processor 3 or within just one, or of the Internet Server 5, or of the central processor 3.
Examples of the software layers of the Internet Server 5 have been shown in Figures 16 (A) and 16 (B), with Figure 16 (A) representing the Internet Server 5 in an asynchronous mode of communication and Figure 16 representing (B) the Internet 5 in a synchronous mode of communication. As shown in the figures, the software 9 for the Internet Server 5 may additionally comprise an Internet Daemon to launch the HTTPD 37. The software 9 for the Internet Server 5 would also include a TCP / IP or other transport layers. Furthermore, although authentication is provided through HTTPD 37, authentication of the user password and ID can be supplemented or replaced with another mode of authentication.
The term synchronous has been used to refer to a mode of operation for the MSDS 10 in which all possible HTML files for a message are generated at the moment the message is received. The HTML files can be generated by the central processor 3 or by the application programs 31. When an information request 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 the storage 11 and transmit the information to the user computer 32. With a synchronous mode of operation, CGI 35 would be unnecessary.
ES 2 274 583 T5
The MSDS 10 preferably operates in accordance with a synchronous mode of operation. In an asynchronous mode of operation, the information required by the user may not be available and may have to be generated after the request. The asynchronous mode of operation is preferred as few files are generated, thereby reducing the required amount of storage 11. Because the information required 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 example, an anchor can be defined as <AHREF = ”/ faxweb / users / 2496801 / viewpage.cgi? FAX_NUM = 1 & PAGE = 1 & VIEW_MODE = FULL”> to make the CGI run a page viewer program so that the page 1 or 1 fax message will be presented in a full size image. CGI 35 will generate the required information when the information has not been generated, otherwise CGI 35 will retrieve the information and relay the information to HTTPD 37 for transmission to the user.
With the invention, the MSDS 10 can reliably receive voice, fax, and data messages for a plurality of users and can receive more than one message for one user at the same 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 World Wide Web of the Internet 30 is a constantly expanding network that allows the user to retrieve messages from virtually anywhere in the world. Since the user only needs to incur a local charge to connect to the Internet 30, the user can retrieve or review messages at a relatively low cost.
Even for users in the office or at home, MSDS 10 provides a number of benefits. The user would not need a fax machine, voice mail system, or a dedicated machine to receive data messages. The user also does not need to worry about the missing part of messages or violating the confidential nature of the messages. The user, of course, may still have a fax machine and a dedicated computer for data messages. The MSDS 10, however, will allow the user to use the telephone company's "call forwarding" feature so that messages can be transferred to the MSDS 10 at the user's convenience, such as when the user is away from the office.
The software 7 and software 9 are not limited to exact forms of the flow diagrams shown but can be varied to suit the particular hardware employed by the invention. The software can comprise additional processes not shown or it can combine one or more processes shown into a single process. Furthermore, software 7 and 9 can be run by a single computer, such as a Silicon Graphics Workstation, or it can be run by a larger number of computers.
Fax messages preferably undergo signal processing such that images in fax messages are converted from a two-tone black or white image to a variable gray scale image. As is known in the art, a grayscale image of a fax message provides a better image than simply a black or white image of the message. The signal processing may comprise any appropriate standard contrast curve processing method, such as anti-confusion or a smoothing filter. The signal processing can take place concurrently with the conversion from TIFF / F to GIF and is preferably performed for both full-size and reduced-size images of fax messages.
Furthermore, the user may be provided with a greater or lesser number of options in presentation or retrieval messages. The options are not limited to the exact forms provided but may allow the user to review or retrieve messages in other formats. The options can also allow a user to join two messages into a single message, delete parts of a message, or otherwise the content of the messages. Also, the various menus provided to the user on the phone can have a greater number of options and the MSDS 10 can accept responses that involve more than a single DTMF digit.
The specific DTMF digits described in the various menus are only examples and, as will be apparent to those skilled in the art, other digits may be used instead. For example, a "9" may be used in place of a "*" in order to exit the menu or return to the previous menu. Also, the DTMF digits can be changed according to the user's personal convention. If the user had a previous voice email system, the user could customize the commands that correspond to the commands used in the previous system in order to provide a smooth transition to MSDS 10.
MSDS 10 can restrict a user to only certain types of messages. For example, a user may want the MSDS 10 to store only fax messages in order to reduce costs of using the MSDS 10. In such a situation, the MSDS 10 would perform an additional operation of checking that the type of message received for a user is a type of message that the MSDS 10 has authorized to receive on behalf of the user. When the message is an unauthorized type of message, the MSDS 10 can ignore the message completely or the MSDS 10 can inform the user that someone has tried to send a message to the MSDS 10.
ES 2 274 583 T5
Furthermore, the MSDS 10 has been described as having the central processor 3 to handle incoming calls and the Internet Server 10 to link to the Internet 30. The invention can be practiced in other ways than with two separate processors. For example, the central processor 3 and the Internet Server 5 may comprise a single computer or workstation to handle incoming calls and to link to the Internet 30. The MSDS 10 can convert the messages to HTML files before storing the messages. Also, the central processor 3 can communicate with the paging system 13 instead of with the Internet Server 5. Additionally, as described above, the central processor 3 can comprise several microprocessors 27 to handle a greater number of DID lines.
The invention has been described as the act of converting the messages into HTML files 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 actually it is just one type of a Standard Generalized Markup Language. The invention is not therefore limited to the HTML format but can be practiced with any type of mixed media page implementation language that can be used to exchange information on the Internet 30.
SGML is not limited to any specific standard but covers many dialects and variations in languages. An example of an SGML dialect is the Virtual Reality Markup Language (VRML) which is used to deliver three-dimensional images over the Internet. As another example, the computer 32 for accessing the MSDS 10 via the Internet 30 may comprise a handheld device. A handheld device is generally characterized by a small display size, limited input capabilities, limited bandwidth, and limited resources, such as limited amount of memory, processing power, or permanent storage. In view of these limited capabilities, a handheld device markup language (HDML) has been proposed to provide easy access to the Internet 30 for handheld devices. The SGML information transmitted by the MSDS 10 to the computer 32 may therefore comprise HDML information appropriate for a handheld device or it may comprise VRML.
As another example, Extensible Markup Language (XML) is a shortened version of SGML, which makes it easier to define document types and makes it easier for programmers to write programs to handle them. XML omits some of the more complex and less used parts of the standard SGML in exchange for the advantages of being easier for writing applications, being easier to understand, and more suitable for delivery and interoperability over the Web. Because XML is nevertheless a dialect of SGML, MSDS 10 therefore encompasses the translation of fax, voice, and data messages into XML, including all dialects and variations, and the delivery of these messages to the computers 32 over the Internet 30.
As another example, MSDS 10 encompasses the use of "dynamic HTML." "Dynamic HTML" is a term that has been used to describe the combination of HTML, style sheets, and scripts that allow documents to be animated. The Document Object Model (DOM) is a platform-neutral link and a language-neutral link that allows dynamic access and updating of document content, structure, and style. The MSDS 10 may therefore include the use of the DOM and dynamic HTML to deliver dynamic content to computer 32 over the Internet 30.
The MSDS 10 is also not limited to any particular or standard version of HTTP and thus not to any particular hypertext transfer protocol daemon 37. In general, HTTP is a data access protocol that works over TCP and is the base of the World Wide Web. HTTP began as a generic question-answer protocol, designed to accommodate a variety of applications ranging from document exchange and management to search and form processing. Through the developments of HTTP, the request for extensions and new features of HTTP has been exploited; such extensions range from caching, distributed authorization and content negotiation to different remote procedure call mechanisms. By not having a modularized architecture, the price of the new features has been a complex overlap and an incomprehensible protocol. For example, a Protocol Extension Protocol (PEP) is an extension mechanism for HTTP designed to access the tension between private agreement and public specification and to accommodate the extension of http clients and servers by software components. The Multiplexing Protocol (MUX) is another extension that introduces asynchronous messaging support at a lower layer of HTTP. As a result of these drawbacks of HTTP, a new version of HTTP, in particular HTTP-NG, has been proposed and its purpose is to provide a new architecture for the HTTP protocol based on a simple, extensible, distributed object-oriented model. HTTP-NG, for example, provides support for business transactions that includes improved security and support for online payments. Another version of HTTP, in particular S-HTTP, provides secure messaging. MSDS 10 and HTTPD 37 may incorporate these versions or other versions of HTTP.
In addition to the different versions of HTTP, the HTTPD 37 of the MSDS 10 can work with other implementations of HTTP. For example, the W3C has an HTTP mode called “Jigsaw”. Jigsaw is an HTTP server written entirely in Java and provides benefits in terms of portability, extensibility, and efficiency. The MSDS 10 can employ Jigsaw or other HTTP implementations.
ES 2 274 583 T5
For the purpose of transmitting messages to the user's computer 32, the MSDS 10 allows the user to display the voice message or preview the fax message without requiring the MSDS 10 to transmit the entire message to the computer 32. This sampling capability this is a significant advantage since transmission of the entire message would frequently tie up the computer 32 for a fairly 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 decides that the entire message needs to be transmitted, as stated above, the user computer 32 could be receiving the message for a relatively long period of time. After the complete message has been received, the user then has the options to view, listen to, retrieve, or save the message. As an alternative, the user computer may in turn indicate the contents of the message to the user as the message is being received.
For example, with a voice message, the user computer 32 could send the message to a loudspeaker when the message is being received. In this way, the message would be played in real time and the user would not need to wait until the full message has been received before listening to the message. In order to reproduce 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 computer 32, the browser will activate a program for use with RA files. The operations and performance 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 into a browser program. The RA program will request the RA data file that contains the message from the MSDS 10 and when the RA file is being received in the computer 32, this program will reproduce the message in real time.
The MSDS 10 and the user computer 32 could also be arranged so that every page or even line of a fax message could be displayed when the computer 32 receives the fax message. Furthermore, although the transmission of a data message is relatively fast compared to a fax or voice message, the computer 32 could also be programmed to allow access to the data messages when 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 type of audio message most often stored in the MSDS 10. The invention, however, can be used with any type of audio message and is in no way limited to messages only. voice.
In accordance with another aspect of the invention, the MSDS 10 can be used as a file store that serves as a file for a particular user or group of users. As described above, the MSDS 10 can maintain a list of all messages for a particular user that is presented to the user when the user accesses their mailbox. The MSDS 10 can store all messages, whether voice, fax, or data, for a user in the database indefinitely. The MSDS 10 can therefore be entrusted to a user to establish the authenticity of a message and the existence or absence of a particular message. Through the MSDS 10, a user can thereby keep an accurate record of all received email messages, fax messages, and data transfers.
In addition to serving as a repository for files, the MSDS 10 can also function as a document management tool. As described above with reference to Figure 2, when MSDS 10 receives a message, MSDS 10 updates a database with information about the message. This information includes the type of message, whether it is a fax message, a voice message, or a data message, the time and day the message was received, the size of the file, such as in bytes, the number phone number of the sender who leaves the message, as well as other information, such as the number of pages in a fax message. Because the dialed telephone number is unique to each user, the information also includes the intended recipient of the message.
An example of a data entry 300 in storage 11 for a message is shown in Figure 17. The data entry 300 represents only the single entry for a single message with each message having a separate data entry 300. Preferably, the data entries 300 are stored in a relational database and can be searched through a language. structured question (SQL).
As shown in Figure 17, the data field 300 for a message may comprise numerous data fields to describe the message. One of these data fields may comprise a field 301 to indicate the name of the person receiving the message. As will be appreciated by those skilled in the art, the person can be identified in different ways, such as by a portion of the person's name or by a unique number. Other field
ES 2 274 583 T5
302 in data entry 300 indicates the type of the document, such as whether the document is a fax message, voice message, or data transfer, and fields 303 and 304 indicate respectively the day and time that the message was received by MSPS 10. The sender's phone number is indicated in field 305 while the size of the message, which can be measured in bytes, is indicated in field 306 and the number of pages of the message is indicated in field 307. A document number to uniquely identify the message is indicated in field 308. As described above, files or messages received for a particular user can be sequentially numbered in the order they are received by the MSPS 10. Files and messages, however, can be numbered or identified in other ways, such as by a combination of numbers with an identifier for the date the message was received. Also, the number of documents or identifier may be unique for each file or message addressed to one user or, alternatively, it may be unique for each file or message addressed to a plurality of users, which is advantageous when the MSPS 10 tracks documents for a entire company or another group of users.
In addition to fields 301 through 308, data entry 300 for a message or file may have other fields 309 to describe or document the message or file. The other fields 309, for example, can be used to identify the type of storage that a message should receive. Messages or files can have different lengths of time for the message to be stored before being automatically deleted. The type of storage, such as whether the full text of the message has been stored, may also be indicated by field 309. Another example of a feature that can be contained within the other field 309 is security. But from time to time, a user may wish to and may grant access to another person's mailbox, such as when the MSPS 10 tracks documents for an entire company. By assigning a message or file as safe in field 309, a user can restrict or deny access to that message or file to other users. The other fields 309 can also be used by a user to customize the MSPS 10 according to their own wishes. For example, if the user is a company, the company may want to classify messages according to the division to which the message is addressed, such as a code for marketing, another for sales, another for engineering, and another for legal.
As another example of a use of one of the other fields 309, a user can enter notes in the other field 309. When a user initially receives a data entry 300, the entry 300, for example, can include data in all fields 301 to 308 except for field 309, which has been left blank. The user can then enter his notes in the other field. An initial data entry 300 may include field 305 for the sender's phone number that contains the digits for the calling number. The user, however, may not easily recognize the caller by reading the telephone number listed in field 305. To more clearly indicate the caller, the user can enter notes in field 309 to identify the name of the caller. Alternatively, the notes in field 309 may reflect part or all of the content of the message. The user can receive a large document or message and can enter a short description of the document or message in field 309. As another example, the recipient of the message can read the message or document and discover that the caller is requesting some service or things. of the recipient, such as a request for certain documents or delivery of a certain number of things. The receiver can read the document or message and place some notes in field 309 to indicate the type of service or follow-up action that needs to be taken. An assistant to the receiver can then view the notes in field 309 and perform the appropriate operations to ensure that the requested service or items are delivered. If the data entry is securely protected, one of the other 309 fields, as described above, can grant the wizard limited access only to field 309 or can grant more expansive access so that the wizard can see the fields. 301 to 309 as well as the actual document or message. Fields 309 can serve a number of other purposes, as will be apparent to those of skill in the art.
Figure 18 illustrates a process 320 for using the MSPS 10 for document management purposes. Referring to Figure 18, a user submits a search request to the MSPS 10 for a particular document or set of documents in step 321. The user can issue this request with the computer 32 by clicking on a link, such as a link for "Find Documents", which can be presented to the user by the MSPS 10 after the user has been granted access to their mailbox. email in operation 72 shown in Figure 3. The MSPS 10 may present the user with the option of searching the document files at other times, such as when the user first tries to access the mailbox in step 62, or when the URL received by HTTPP 37 from the computer 32 points to the document files.
In response to this request, the HTTPP 37 sends the user a search query form in step 322 to allow the user to define the desired search. An example of a search query form is shown in Figure 19. The search query form may include one entry for each of data fields 301 through 309 in data entry 300. For example, the user can enter one or more names for a recipient and has the MSPS 10 search for all messages or files addressed only to these recipients. The user can also indicate the type of document, be it a fax, a voice message or a data file. The search query form also has entries for the date or time, preferably accepting ranges of times and dates, and an entry for the caller's phone number for MSPS 10. The search query form
ES 2 274 583 T5 may also include an entry for the size of the file or for the number of pages, which is relevant if the message is a fax message. The search query form can also include an entry for the document number, which can accept a range of document numbers, and also an entry for another field.
In step 323, the user enters the search parameters in the search query form with the computer 32 and returns the information to the MSDS 10 through the Internet 30. The user can define the search on any data field or You can define your search on a combination of two or more data fields. For example, as reflected in the completed search query form shown in Figure 20, a user can define a search by designating the document type as a fax and the calling number as (404) 249-6801. Once the user has finished defining the search, the user then selects the "SEARCH" link shown at the bottom of the screen so that the user computer 32 would send the completed search query form through Internet 30 to HTTPD 37 of MSDS 10.
In step 324, HTTPD 37 receives the completed search query form and, through CGI 35, invokes one or more of the application programs 31 to perform the desired search for any files or messages that fall within the parameters. of the search. The search results are passed from the application programs 31 through the CGI 35 to the HTTPD 37 and, in step 325, they are returned to the user through the Internet 37. Preferably, the MSDS 10 returns the search results in the form of a list of all files or messages contained within the search parameters, although the MSDS 10 may return the results in other ways.
An example of the search result of the query shown in Figure 20 is shown in Figure 21. As described above, the search parameters were all fax messages from telephone number (404) 249-6081. Referring to Figure 21, this query resulted in three messages being discovered. The first document has a document number 11 and is described as a fax from the telephone number designated to Jane Doe on May 31, 1995, and consists of three pages. This first listed document is an example of the fax shown in Figure 7. The other two documents correspond respectively to document numbers 243 and 1002 and are also from the designated telephone number.
At step 326, the user selects the desired file or message from the list of messages and files. For example, by clicking on the first listed document, in particular document number 11, the computer 32 sends a request to the MSDS 10 for a view of that document and, in response, the MSDS 10 provides a view of the document in accordance with user-defined preferences. As described above, the user may receive a reduced size image of the first page, a full size image of the first page, reduced size images of all pages, or full size images of all pages of the message. fax. Thus, if the user has selected the fourth display option as the user-defined preference, the MSDS 10 would return an image of the first page of the fax, such as that depicted in Figure 7.
At step 326, the user can also have the MSDS 10 save the search results. For example, as shown in Figure 21, the user can enter the name "CHARLES R. BOBO FAXES" as the name for the search. By clicking on the "SAVE SEARCH AS" link, the name of the search is provided from computer 32 to MSDS 10. In the MDSD 10, the HTTPD 37 transfers the information from the computer 32 to the CGI 35 and the CGI 35 invokes an application program 31 to store the search result in the storage 11 under the designated name. The invoked application program 31 preferably does not store the content of all messages but instead stores a list of search results in storage 11.
The result of a search can be stored in the storage 11 either as a closed search or as an open search. If the MSDS 10 saves the result of a search as an open search, then the files or messages in that named search can be updated with recent files or messages that fall within the particular search parameters for the search. On the other hand, a closed search is one in which the files or messages in the named search are limited to those existing at the time of the search. For example, if the MSDS 10 has saved the search results shown in Figure 21 as a closed search, then any retrieval of the "CHARLES R. BOBO FAXES" would result in only the three listed documents. If, on the other hand, the search called as “FAXES DE CHARLES R. BOBO ”has been saved by MSDS 10 as an open search, then MSDS 10 would reactivate the search query shown in Figure 20 in response to a request by computer 32 for that search in order to get all the fax messages from of the home phone number, including those received after initial saving of search results.
With reference to Figure 19, instead of defining a new search, the user can click on the link "STORED SEARCHES" in order to receive the results of a search previously carried out. For instance,
By clicking on this link, the MSDS 190 can return a list of searches stored for that particular user, such as the searches shown in Figure 22. As shown in this figure, the "FAXES DE CHARLES R . BOBO ”are included in the list of stored searches. If the user has then selected the search for “FAXES DE CHARLES R. BOBO ”, the user may then be presented with the list of faxes shown in Figure 21, possibly including recent additions to the hunt group.
Referring to Figure 19, the MSDS 10 may also provide a user with a link to "RECENT FILES" in step 322. By selecting this link, the MSDS 10 may return a list of all fax, voice, and email messages. data received during a particular period of time, such as the last month. By placing the link "RECENT FILES" on the search query and instead of the list of "STORED SEARCHES", the user can quickly return to the most recent files and messages. The search query form may contain other links such as easy-to-access links, such as a link to the last search performed by the MSDS 10 at the request of the user.
The messages or files received by the MSDS 10 do not need to come from a third party. In other words, the MSDS 10 can be used as a file store or file manager for self-generated documents. The user can call the designated telephone number to receive messages and transmit voice messages, data messages, or fax messages and have the MSDS document 10 the reception and content of these messages. A user can easily use a fax machine as a scanner to enter documents into the storage 11 of the MSDS 10.
The MSDS 10 may have applications in addition to those described above with respect to serving as a message delivery device, file repository, and file manager. For example, the MSDS 10 may perform some additional processing on incoming calls before advancing them to the user. For voice messages, this treatment may involve the transcription of the message and then the return of the transcribed messages to the user. The MSDS 10 can therefore be seen as an offered secretarial aid that can be of great value to small companies or individuals who cannot afford a secretary or even to larger businesses that may need some help in cases of overwork. The transcription can be provided by individuals located anywhere in the world and can be performed automatically by speech recognition software, such as an IBM VoiceType.
Another type of treatment that the MSDS 10 can provide is translation services. The incoming call, whether it is a voice, fax or data message, can be converted to SGML and then forwarded to a first translator. Given the reach of the Internet, the translator being located virtually anywhere in the world and can return the translated document through the Internet to MSDS 10. The MSDS 10 can notify the user that the transmission has been completed via email, voicemail, pager, fax, or other means. The user would then connect to the Internet and retrieve the document produced. MSDS translation services 10 may also provide a transcription of the message, such as with speech recognition software.
The foregoing description of the preferred embodiments of the invention has been presented for the purpose of illustration and description only. It is not intended to be exhaustive or to limit the invention to the precise form described. Many modifications and variations are possible in light of the above teaching.
The embodiments were chosen and described in order to explain the principles of the invention and its practical application so as to enable others skilled in the art to use the invention and various embodiments and with various modifications as appropriate for the particular use under consideration. The scope of the invention is intended to be limited only by the claims appended thereto.
Contents16
18 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18
77 members in 14 offices
Priority claims3
| Document | Office | Kind | Date |
|---|---|---|---|
| 944741 | United States of America | – | |
| 94474197 | United States of America | A | |
| 9820732 | United States of America | W |
Members77
| Document | Office | Kind | |
|---|---|---|---|
| TW262620B | Taiwan Province of China | B | |
| JPH07306695A | Japan | A | |
| EP0683482A2 | European Patent Office (EPO) | A2 | |
| CN1113335A | China | A | |
| KR950034057A | Republic of Korea | A | |
| CA2232397A1 | Canada | A1 | |
| WO9634341A1 | World Intellectual Property Organization (WIPO) | A1 | |
| US5668927A | United States of America | A | |
| US5675507A | United States of America | A | |
| EP0683482A3 | European Patent Office (EPO) | A3 | |
| US5771486A | United States of America | A | |
| EP0870238A1 | European Patent Office (EPO) | A1 | |
| US5870549A | United States of America | A | |
| CA2305459A1 | Canada | A1 | |
| WO9918716A1 | World Intellectual Property Organization (WIPO) | A1 | |
| AU9679398A | Australia | A | |
| US5974373A | United States of America | A | |
| EP1034651A1 | European Patent Office (EPO) | A1 | |
| EP1065656A2 | European Patent Office (EPO) | A2 | |
| EP1065657A1 | European Patent Office (EPO) | A1 | |
| EP1065656A3 | European Patent Office (EPO) | A3 | |
| US2001014910A1 | United States of America | A1 | |
| EP0683482B1 | European Patent Office (EPO) | B1 | |
| DE69522605D1 | Germany | D1 | |
| JP2001519624A | Japan | A | |
| EP0870238A4 | European Patent Office (EPO) | A4 | |
| US6350066B1 | United States of America | B1 | |
| DE69522605T2 | Germany | T2 | |
| KR100335162B1 | Republic of Korea | B1 | |
| EP1065657B1 | European Patent Office (EPO) | B1 | |
| AU755321B2 | Australia | B2 | |
| DE69529002D1 | Germany | D1 | |
| US6564321B2 | United States of America | B2 | |
| DE69529002T2 | Germany | T2 | |
| EP1065656B1 | European Patent Office (EPO) | B1 | |
| DE69531710D1 | Germany | D1 | |
| US2003208688A1 | United States of America | A1 | |
| JP3484757B2 | Japan | B2 | |
| DE69531710T2 | Germany | T2 | |
| CA2232397C | Canada | C | |
| US6857074B2 | United States of America | B2 | |
| US2005050349A1 | United States of America | A1 | |
| EP1034651A4 | European Patent Office (EPO) | A4 | |
| MY121946A | Malaysia | A | |
| EP1034651B1 | European Patent Office (EPO) | B1 | |
| AT348478T | Austria | T | |
| ATE348478T1 | Austria | T1 | |
| DE69836644D1 | Germany | D1 | |
| US2007081457A1 | United States of America | A1 | |
| US2007083614A1 | United States of America | A1 | |
| US2007083656A1 | United States of America | A1 | |
| US2007088808A1 | United States of America | A1 | |
| ES2274583T3 | Spain | T3 | |
| US2007130269A1 | United States of America | A1 | |
| US2007130270A1 | United States of America | A1 | |
| DE69836644T2 | Germany | T2 | |
| JP4230661B2 | Japan | B2 | |
| EP0870238B1 | European Patent Office (EPO) | B1 | |
| AT437405T | Austria | T | |
| ATE437405T1 | Austria | T1 | |
| DK0870238T3 | Denmark | T3 | |
| DE69637973D1 | Germany | D1 | |
| EP2107776A1 | European Patent Office (EPO) | A1 | |
| ES2326565T3 | Spain | T3 | |
| US7836141B2 | United States of America | B2 | |
| EP2270668A1 | European Patent Office (EPO) | A1 | |
| EP2270669A1 | European Patent Office (EPO) | A1 | |
| US7895306B2 | United States of America | B2 | |
| US7895313B2 | United States of America | B2 | |
| US7934148B2 | United States of America | B2 | |
| EP0870238B2 | European Patent Office (EPO) | B2 | |
| ES2326565T5 | Spain | T5 | |
| DK0870238T4 | Denmark | T4 | |
| EP1034651B2 | European Patent Office (EPO) | B2 | |
| ES2274583T5This record | Spain | T5 | |
| DE69836644T3 | Germany | T3 | |
| CA2305459C | Canada | C |
Numbers
- Publication
- 2274583
- Application
- 98950859
Titles2
- Spanish
- Sistemas y métodos para gestionar mensajes
- English
- Systems and methods for managing messages
Classification
- CPC, 40
- H04L51/066
- H04M3/4938
- H04M3/5307
- H04M3/53316
- H04M3/53333
- H04M3/53358
- H04M3/537
- H04M7/12
- H04M2201/52
- H04M2201/60
- H04M2203/2066
- H04M2203/253
- H04M2203/4509
- H04M2203/4536
- H04N1/00209
- H04N1/00458
- H04N1/324
- H04N1/32438
- H04N2201/0068
- H04N2201/0086
- H04N2201/0093
- H04Q2213/13034
- H04Q2213/1305
- H04Q2213/13095
- H04Q2213/13103
- H04Q2213/13106
- H04Q2213/13175
- H04Q2213/13204
- H04Q2213/13216
- H04Q2213/13286
- H04Q2213/13292
- H04Q2213/13336
- H04Q2213/13374
- H04Q2213/13389
- H04Q2213/13405
- H04L67/02
- H04L51/224
- H04L51/48
- H04L51/56
- H04L9/40
- IPC, 11
- H04L29 08
- G06F13 00
- H04L12 58
- H04L29 06
- H04M3 493
- H04M3 53
- H04M3 533
- H04M3 537
- H04M7 12
- H04N1 00
- H04N1 32