WO1996041463A1 - A method for utilizing point-to-point communication devices including fax machines as bi-directional internet terminals - Google Patents

Abstract

Devices, such as FAX machines (201, 207), which are intended to communicate with each other over point-to-point dial-up (i.e. telephone) communication networks and, thus, do not affix electronic addresses to their message content, can be made to successfully communicate with addressable electronic mailboxes, such as those common on The Internet, by interfacing with an internet/FAX server (203, 205) which determines an appropriate network address and repackages the communication for a packet-switching communication network. The electronic address can be derived directly from information specified from the transmitting FAX station including: machine-readable graphics (e.g., barcodes or OCR text) embedded within the FAX content, DTMF keypad tones, a digital FAX ID field or new digital information field; or indirectly by table-look-up based on data including: the DID, caller ID, FAX ID field. In particular, when an EMail message is delivered from the internet to a FAX, via such an internet/FAX server, a return coversheet can be provided which will automatically route any return FAX to the original EMail box.

Description

A METHOD FOR UTILIZING POINT-TO-POINT COMMUNICATION DEVICES

INCLUDING FAX MACHINES AS BI-DIRECTIONAL INTERNET TERMINALS

TECHNICAL FIELD The instant invention relates to a class of methods, techniques and systems for permitting the utilization of point-to-point communication devices, such as FAX machines, as bi-directional internet teπninals. This will permit the large installed base of standard (and advanced, computerized, or server) FAX machines to be integrated into "The Internet" (or similar communications networks) as terminals for both information reception and transmission. Inventor refers to such service as "INTERFAX™".

BACKGROUND AND PRIOR ART There has come to be (in North America specifically and, more generally, worldwide) two distinct electronic communications networks. These may, in fact, share the same physical lines in many cases, but are more clearly distinct based on the type of "terminals" and connection methods utilized. The first is the familiar "telephone" network — local, long distance, and international. Here the type of

"terminals" are primarily simple voice telephones, FAX machines and, occasionally, video- or picture-phones. The characterization of these terminals, and the connection method used, is that the teπninals are relatively unintelligent transducers (for voice or image) and are connected point-to-point for what is usually a dedicated and short term "conversation" on a "dial-up" basis. The crucial aspect here is that the information gets to where it is going by virtue of the specific and dedicated nature of the connection. That is, a particular phone/FAX at one location or phone number, is connected to another by creating a point-to-point connection to another particular location or phone number. The information gets to where it is going because that is the only place for the information to go — over the single established connection. It should be noted that pairs of computers may also "converse" over such point-to- point connections via modems; although, unlike the other "terminals" described above, because of their additional capabilities, computers may also communicate over the network type described directly below.

The second type of electronic communication network is a message or packet switching network; the most conspicuous of these being "The Internet".¹ [Throughout this document references made to "The Internet" or "internet" may be considered to apply to any similar data network. Similarly, throughout this document references made to internet or EMail accounts may be considered to apply to any similar account, location or "mail-box" even if not strictly on The Internet, for example: accounts located at on-line services such as America On Line or

CompuServe; accounts on bulletin board services; or accounts on large computer systems at universities, laboratories, military or government agencies, or businesses.] The difference is that messages, or message parts, comprise, in addition to message content, a header or other section that constitutes a destination address or routing information. Thus, a large number of computers may communicate with each other over a large (or distributed) shared connection network without requiring individual "wires", or separate connections, between each pair of terminals. That is, since the message packets have routing or addressing information incorporated into them, many such packets may travel down the same section of "wire" with no confusion. Routing capabilities are incorporated into the network that direct the packets over the network to the appropriate destination, based on the packet address. While computers may be programmed to separate their communications into packets, and wrap them in the appropriate "protocol" including addressing information, telephones and FAXs may not, in general, do so.

Thus, the purpose of this invention is to permit the use of teπninals, such as FAX machines, intended for point-to-point dial-up communication, to be utilized as reception and or transmission terminals on a packet switching- type network such as The Intemet.

It should be noted that it is possible that some large point-to-point communication networks, at internal levels, may actually be implemented as packet switching networks. For example, once voice data arrives from a "point" to the local exchange it may be digitized and "packetized" to be transmitted over a network in a packet switching manner. At the destination exchange the packets would then be reassembled, converted back to analog and delivered to the reception "point". As far as this invention is concerned, this changes nothing. As far as the users at each end of the network are concerned, the connection is point-to-point with no addressing available other than to dial a particular user's telephone number.

Specifically, with regard to FAXs, it has been noted (in The Whole Internet User's Guide ά Catalog — Second Edition by Ed Krol, Published by O'Reilly & Associates, Inc., November 1994, at Page 338) regarding the integration of FAX and Internet technologies, that: "the technologies are indeed merging, but not as quickly as you would anticipate ... computer people have viewed FAX as a lesser service, because the documents are not machine- readable, merely machine-transferable and -displayable ... What's there is not text, but a picture of the page". Thus, FAX and computer networks "have merged [only] to a limited extent". Routable in the outgoing direction only, it is possible to "take a file ... and send it via a modem to a FAX". To do mat via the Internet "you have to create a really strange email address that contains the destination FAX machine's phone number. For example, say you wanted to send a FAX to Ed Krol, whose FAX phone number is 1-217-555-1234. You would send an email to the following address:

remote.printer.Ed_Krol/1120_DCL@12175551234.iddd.tpc.int

The Mailbox (the part to the left of the @) always starts with remote . rinter. After remote .printer you can put some text that will be printed on the FAX'S cover sheet ... No matter what the address looks like, the body of the mail message is just a normal email message. The test of the message is printed on the recipient's FAX machine." As used herein, the term "machine-readable" graphic is used in the sense as used above by Mr. Krol; i.e., machine-intelligible, that is with content in a form capable of being understood by the machine, not "merely machine-transferable and -displayable".

Specifically, with regard to FAX on The Internet, the problem is that while there is (spotty, unreliable, volunteer-mediated, as of this date) outgoing service, to deliver EMail messages to a FAX machine located at a dial- up telephone number, there is no way at all for the receiver of that FAX to respond in kind. This deficiency is addressed below; and, its elimination permits a number of novel and useful services to be provided.

THE INVENTION IN BRIEF

As described above, it is possible for an EMail account holder on The Internet (or similar participant on a packet switching network) to send a file (text or image) to a FAX machine attached to a particular line (phone number) on a point-to-point communications network. This is done by specifying an address that incorporates (or, alternately incorporation in the message content would be possible) the point-to-point address (phone number) which, in turn, is translated or mapped to the address of a FAX server computer on the packet switching network. Thus, the message is routed to a server on the packet switching network which also has the ability to dial-up a FAX on the point-to-point network; e.g., through the use of an installed FAX/Modem (or PC/FAX) card. The message text content is converted to a FAX image (or image content incorporated directiy) and delivered over the phone in the usual FAX manner.

The problem, then, is that the recipient of the FAX cannot respond in kind. There is cuπently no way for the intemet FAX server to determine the required remm routing information (e.g., an EMail address) from information provided by the recipient, or recipient's FAX machine. Various embodiments of the instant invention will overcome this limitation: wiώ some ambiguity, or definitively; for "return" FAXs only, or for "initiated" FAXs as well.

SPECIFIC EMBODIMENTS

First, a flawed embodiment may be implemented with no modification of delivered messages by the FAX server. In this case, (return) routing information is deduced from the phone number called by, and/or from, the returning FAX machine.

In one case the recipient is directed (in the received cover sheet instructions) to call a particular phone number that is associated with only one (or a limited number of) account(s). This may work well when a server is dedicated to one, or a relatively few, accounts). However, in general, the server will be delivering messages for a large number of intemet users compared to the number of lines or phone numbers it has associated with it. Nevertheless, identification of the number called by the FAX returning (or initiating) a call may be used by sensing it with DID (direct-inward-dial) technology. A more practical embodiment would have recipients respond by calling one (or a small number of) phone number(s) incoming to the FAX server, and to then be directed to also enter (dial) an "extension" number that identifies the account (or even Λe specific communication) being responded to, or account being chosen for an initial communication (i.e., not a "reply"). The problem with this embodiment is that, since the extension needs to be entered, automatic FAXing may not be possible — a human operator may need to enter the extension when prompted.

In a third, related, embodiment the account identification, specific communication number identification, or routing information would be imbedded in the FAX ID field that is normally reserved to identify the sender. There are two problems with this embodiment, however. First, programming this field is usually a cumbersome process; done once, when the FAX machine is installed. Having to re-program the FAX before each transmission would, likely, be an unreasonable overhead. However, providing a convenient mechanism for doing this would be part of the instant invention and may take the form of: easier entry via fuller keyboard on a standard FAX machine; storing a "directory" of entries to be loaded into the ID field with a few keystrokes on a standard FAX machine; providing software to control the ID field used by a PC-FAX board (installed in a single machine or on a FAX server) from the keyboard or a stored directory. Second, as per FCC regulations, the ID field is supposed to identify the sender, not the recipient.

Whether entirely practical or not, these three embodiments have in common that the sending (returning) FAX machine provides to the intemet server some indication of the intemet account requested. Alternately, the identification is of a specific communication delivered earlier and, thus, the server may consult its records to determine the intemet account that initiated the communication being responded to. A second class of embodiments, instead, identifies the current sender (and, thus, presumably, the prior recipient) and, again, the server may consult its records to determine the internet account that initiated the communication being responded to. In one variation the sending FAX machine will be identified from the ID field supplied by the FAX machine; in another, the sending machine will be identified by "caller ID" information supplied by the phone company which identifies (in some cases) the number of the party (i.e., the FAX machine) making the call.

The problem with both these embodiments is the ambiguity involved with identifying the FAX machine rather than the actual recipient or sender. Particularly in large organizations, several recipients may share the same FAX machine; similarly, several individuals with accounts on The Intemet may send FAXs to the same individual using the same FAX machine. Thus, when a return FAX comes in, even if it can be identified as coming from a particular FAX machine (i.e., from a particular phone number or with a particular ID field) it may not be certain to whom the transmission should be returned to.

This problem may be partially overcome by identifying and combining both DID and caller ID. In this case, to a limited extent at least, multiple recipients at the same FAX may be separately identified. In particular, if the FAX server has N phone numbers under which it may receive FAXs (call them A, B, C, D ... N) then for each FAX number (FAX machine) that the FAX server delivers FAXs to, it may distinguish up to N separate accounts (or transmissions) to be responded to. For example, at each separate FAX machine: recipients being delivered FAXs from a first account are told (via instruction on the delivered cover sheet) to respond to phone number A; recipients being delivered FAXs from a second account are told (via instruction on the delivered cover sheet) to respond to phone number B; etc. This procedure may be carried out for as many (say M, numbered 1, 2, ... M) FAX numbers as the server delivers to. In this way as many as N x M pairs of DID and caller ID pairs may be identified for delivery to particular EMail accounts. In particular, if one EMail account user causes to have delivered FAXs to several different persons at a single FAX machine, each recipient would have to have a unique phone number to return FAX to if they were to be separately identified; otherwise they could all respond to the same remm FAX number, and all meir FAXs would be correctly returned to the same intemet account holder, but individual respondents would not be automatically separately identifiable.

However, when someone is responding to a FAX received from an Intemet account, the response may be made from a FAX machine other than from the one that received the original transmission, which is incompatible with the technique described directly above. Further, for initiated transmissions (rather than replies) there is no way to reasonably determine to whose Intemet account to send the FAX to with these embodiments.

PREFERRED EMBODIMENTS

A preferred embodiment suitable for responding from a standard FAX machine, to a document received "from an intemet EMail user's account, works as follows. The intemet/FAX server would insert into the transmission to be delivered (anywhere, but nominally as a pre-cover sheet which is delivered first, even before any cover sheet provided by the intemet user) a specially composed set of printed information that comprises, at least, an indication of the sending party (or their account) and, perhaps, a unique identification of the message itself. The message identifier would be composed of two parts (nominally): a prefix identifying the intemet/FAX server, and a suffix consisting of a sequence number for the transmission. Thus, each server may keep an independent overlapping sequence list and, yet, each document on the network will have a unique identifier.

Additional information might be included indicating: sender's name, address, telephone and FAX numbers, EMail account (if not already indicated); recipient's name, address, telephone and FAX numbers; date; subject; priority; security level; etc.; perhaps, even the message content itself. All of this information would be provided as a graphic image in "machine-readable format". An example of such a format is a bar code which is readable by the machine but, generally, not a human. A human-readable version may then also be provided. Alternately, some form of OCR text might be used which is readable by both machine and human. Whatever the case, the requirement is that the information on the cover sheet may be decoded by the intemet FAX server whenever it should encounter a FAXed back image of that cover sheet in the future. In that case, the originator's intemet or EMail account address would be decoded (or, the message sequence number, from which the sender's account may be looked up in a table) so that the FAX transmission would be deliverable to the originator's EMail account on some intemet connected computer.

Thus, even from a point-to-point connected FAX machine, a FAX message may be submitted to the intemet within which the required addressing information is incoφorated in machine readable format; even though FAXs are considered by intemet experts to be "documents [that] are not machine-readable, merely machine-transferable and -displayable" (see, earlier quotation).

For further details concerning "return coversheets" and other details of the use of machine-readable graphics with FAXs the reader is directed to Inventor's prior patent applications, cited above. In particular, directions to the recipient, on how to use the return cover sheet can be included on the remm cover sheet; and, these directions can include what number(s) to call to contact the intemet/FAX server, and directions on using the received coversheet as a pre-cover sheet to any reply.

An alternate prefeπed embodiment would be to provide the intemet/FAX server with user account, or message sequence, information as follows. First, the directions to accomplish this may be provided on the delivered cover sheet, or may be provided via an automated dialog initiated by the intemet/FAX server. Such, interactive sessions between a computer with a synthetic or pre-recorded voice, and a human at a keypad (or voicing responses) is common and, in and of itself, is not the substance of the instant invention.

In either case, the remm user would enter the message sequence number (presumably all numeric to facilitate easy entry) from the telephone's numeric keypad (or, by voice recognition or voice response to specific automatically generated audio directions — e.g., "press or say 1 now" — as is now common), perhaps terminated by the (#) "pound" key. From the message sequence number, the intemet/FAX server would look up the EMail account of the initiating message sender, and use that to deliver the remm message. Similarly, the intemet/FAX server, in the original delivery, may supply a substitute, all numeric (for ease of telephone keypad entry) representation of the originator's EMail account. Such substitution may be accomplished (and reversed) by a standard that is either network-wide or just known to the local intemet FAX server. Alternately, an alphanumeric EMail account number may be entered as follows. For example, the "2" touchtone key also contains "A", "B" and "C". In this case A is entered as 21, B as 22, and C as 23; or A as 2, B as 22, and C as 222. Systems that use such entry algorithms often use 11, 12 and 13 as "Q", "Z" and "space". Such data entry from a telephone keypad is common and, in and of itself, is not generally the substance of the instant invention. For intemet addresses, assigning 01, 02, 03, 04 and 05 (or some other key combination) to "@", ".", ":", "/" and "_" would also be useful.

The only problem with this second prefeπed embodiment is that the interactive session may be cumbersome and requires human intervention and, thus, would interfere with automated, unattended FAXing of the return document.

In all cases when someone is responding to a received FAX which comprises "fill in the form" type content, the following techniques may be used for greater efficiency. First the "fill-in" sections may be excised by the FAX server (which will have been supplied with a template by the original sender) and only those returned, to be optionally re-integrated into the form at the originator's computer. Alternately, the fill-ins may be OCR converted to text and returned. In either case, eliminating remm of the form will reduce transmission and storage requirements and, for returns of many like responses to broadcast-FAX messages, can be very efficient. One way to affect a similar benefit, without the remm intemet FAX server having to be provided with a cut-out template, is for the server to keep a copy of the original transmission and to then "subtract" that from the response. The original image can be translated, rotated or scaled (and Inventor's "framing information", disclosed in his prior patent applications) in order to register it with the returned FAX prior to subtraction. The result after subtraction will be just the information added by the recipient, prior to returning the form. Similarly, for mark-sense forms returned via an intemet/FAX server, the mark-sense analysis may be done at the server, and only the results returned as ASCII EMail.

ALTERNATIVE PREFERRED EMBODIMENTS The preceding section concerned how a recipient at a standard FAX machine, of an internet-initiated communication, might respond to the initiating user.

Alternately, someone at a standard FAX machine may want to initiate such a communication to an intemet EMail account or similarly addressed network location. In that case the previous embodiments may be adapted. In reverse order, the interactive keypad entry mechanism may be used almost exactly as described. All that is required is that the user know a phone number to call a connection into the intemet FAX server, and an EMail account designation or other address to enter. The "machine-readable graphic" embodiment is a bit more complicated.

A first approach requires a PC with a dot-matrix, laser or other graphic capable printer. In that case, the user with the FAX machine would be provided with software which would print the entered EMail account address (and any other coversheet information, such as sender's name and FAX number, subject, etc., which may then be displayed as a summary at recipient's computer by EMail management software) in a bar code, OCR-type text, or other machine-readable graphic form. This would then (nominally) be used as the first sheet when FAXing to the intemet/FAX server.

A second approach does not require special software but, instead, special forms to indicate the EMail address. Several types of such forms may be used. One is "mark-sense" in which one of a column of small boxes is marked for each position, as often used when answering standardized tests. Another is a form with specific boxes outlined where a letter or digit is to be carefully hand printed or typed into each box. Another would be where a specific place on a sheet were indicated where a EMail address would be carefully hand printed or typed for OCR analysis. In a third approach, neither software nor forms would be required. Instead, a "standard" would be established that would assist the intemet/FAX server to identify a carefully hand-written or typed EMail address. As an example only, of one such standard, the EMail address (perhaps double spaced) (103) would be by itself in the top several inches of the first sheet framed by " = " (101) and "*" (102) and, optionally, would be followed (or preceded) by an example of the alphabet in a specific "standardized" order (104), also perhaps double spaced, which would be used to help any OCR software identify the characters in the EMail address (103). See Figure 1. A non- proportionally-spaced typeface would be prefeπed to ease OCR requirements, as would a larger font size. If the EMail address could not be decoded, an error message would be returned to the initiating FAX machine as identified by the FAX ID field or caller ID information. However, in this situation (and any others where an address could not be automatically determined), prior to giving up on delivery, a human system administrator might be notified to apply "human character recognition" to the situation by locating, reading and typing into the computer, the EMail address.

In a fourth approach, a more free-form cover sheet would be analyzed by the internet/ FAX server utilizing more "intelligent" software as described in Inventor's earlier patent applications, referenced above. Here, however, the software would be fine-tuned to extract an EMail account; which may be facilitated by: first locating any "@" characters; then looking for proper form; and, then checking for a valid account — for example by using the UNIX commend FINGER. Again, human intervention and automatic eπor notification could be applied in the event of failure to automatically recognize a valid EMail account.

A fifth approach incoφorates the first approach described above into an otherwise standard, stand-alone or server-variety, FAX machine of somewhat revised manufacture. In that case, the EMail address or other non- content information would be entered by a user from a keyboard; or an index into a previously stored table of entries would be entered, such as the mechanism used to store 7 or 11 digit (or longer for international and extension-added numbers) phone numbers in an "autodialer" and retrieve them by the entry of only 1 or 2 digits. This information would then be directly converted (rather than printed and then scanned by the FAX) to a compressed FAX transmission format image which is equivalent to the machine-readable graphic (e.g., barcode, OCR text, etc.) cover sheet, and which would then precede (or, possibly, follow) the otherwise standard FAX transmission.

Similarly, the FAX machine could be modified so that the entered information would be conveniently and automatically put into the FAX ID Field. Alternately, the entered information- could be made to reside in a new digital information field that would precede (or, more likely, follow) the otherwise standard FAX transmission, only to be recognized by FAX machines or servers programmed in accordance with this new digital field in mind.

The reason that the new field would, most effectively, follow the standard transmission is that standard FAX machines would, in that way, receive a standard FAX transmission and then shut down. Receiving FAX machines programmed with this new field in mind would, at the termination of the standard FAX transmission, continue to listen for the new information field. If the new field were present, after the completion of the standard transmission, a FAX machine programmed to look for it would receive the information. If the new field were not present, a FAX machine programmed to look for it would eventually "time out" and shut down the connection.

APPLICATIONS

Once the basic mechanisms, described above, permit a FAX machine to be used in both directions as a (limited) intemet terminal, many applications are possible and include, without limitation, the following. Generally, these may be available in other systems and, in general, in and of themselves, are not the substance of the instant invention; although, intemet or related implementations of these services are novel and would be part of the instant invention. They will, thus, not be described in detail.

Broadcast FAX — in which a single transmission (initiated from an EMail account or FAX machine) may be delivered by the network to many recipients (at both FAXs and EMail accounts).

Delayed FAX (store and forward service) — a FAX may be scheduled to be delivered at a later time for: convenience, cost reduction, busy signal, etc.

Confirmation — a remm message (either FAX or Email, as appropriate) may be delivered to sender when recipient (or at least recipient's machine) has received the message. If delivered as EMail, confirmation of reading (i.e., accessing the delivered file) may also be given.

FAX On Demand — in which FAX transmissions are sent in response to an automated voice and keypad telephone session, may now be delivered via the intemet and may include any intemet mediated information, such as World Wide Web pages or archived text; or even a request to be added to a mailing list. Further, the "demand" may now be initiated by FAX (via barcode, OCR, mark sense, or just sending a request or even a "null message" to an EMail account) or EMail, rather than just by interactive voice/keyboard sessions.

In particular, since FAX machines are, by these techniques, limited intemet terminals, FAX transmissions may now travel: from a first FAX machine, to a first intemet FAX server, over the internetwork, to a second intemet/FAX server, to a second FAX machine. See Figure 2. Thus, many services, such as some of those listed above, not available by dialing direct, FAX machine to FAX machine, would now be routinely available, via software programmed on the intemet/FAX server and via the intemet. Also, cost reduction may be achieved for long distance FAX transmissions by using The Intemet for the "long haul" portion of the transmission.

Additionally, Inventor has disclosed, in his prior patent applications, techniques he calls "secure FAX". These techniques may be incoφorated into the intemet/FAX server so that FAXs incoming to the server (or generated by the server from EMail text) may be "scrambled" so as provide secure transmission and storage of such communications. They may then be automatically unscrambled prior to delivery as a FAX, or delivered as secure FAXs. Similarly, communications coming in from a FAX intended to be delivered to an EMail account may be scrambled by the intemet/FAX server for secure delivery over the relatively public and insecure intemet, and then only unscrambled by the recipient at his computer by entering a password or de-encryption key. In particular, some forms of secure "electronic commerce" may be affected by a variation on this method, transmitting scrambled signatures or other information.

ANOTHERAPPLICATION-THEPHANTOMORVIRTUALEMAILACCOUNT

One particularly useful application of the techniques described herein is the establishment of a "phantom" or "virtual" EMail account for people who do not have access to (or do not want to use) such an account via computer terminal or PC. Such people would be able to receive and send EMail via FAX. For example, many people who now routinely conduct business communication via FAX do not want to go the added expense of acquiring and/or the effort of learning to use on-line communication services. Nevertheless, many other people expect to be able to communicate by EMail and, so, such a virtual EMail account would be of benefit. Such a party could notify people about their EMail account (e.g., in advertizements, on business cards or letterhead, or any other way) as if it were a standard EMail account; it could have a standard-seeming EMail name rather than a phone number. Any EMail sent to them would arrive at the local intemet/FAX server and then be converted from text to image and forwarded to their FAX.

Such forwarding might occur as each EMail message arrived. Alternately, forwarding might occur on a demand basis, by placing a call to the intemet/FAX server and entering an ID and request code; and delivery to some FAX machine other than the default, office, FAX machine might also be specified for FAX forwarding, while "on the road" or at home, for example. A third alternative would be for messages to be delivered en masse at a convenient time; for example, at night, when network and/or FAX traffic are usually reduced and sometimes less expensive. [A related service permits the holder of a standard EMail account to call into an intemet FAX server and

"pick up" their EMail by requesting the server to convert the EMail messages to images of text and have them delivered to a default, or keyed in, FAX machine. Off-the-shelf text-to-voice software may "read" the sender and reference line of each message so that the user may select (by keying) which messages to forward and which to hold as text, as well as which to delete after sending and which to retain. In addition, any other available intemet resources may similarly be requested to be delivered by FAX, rather than to an computer-based intemet account. These include, without limitation, archived text files, computerized database search results, World Wide Web pages, etc.]

Using the remm coversheet delivered with each message, responses could be returned to any parties sending EMail. One particularly useful option here would be the conversion of the FAXed back EMail from FAX image to ASCII text, prior to returning it as EMail to some party who sent EMail from a standard EMail account. In this way the "virtual, FAX-mediated" nature of the InterFAX account would be hidden.

Such conversion can be accomplished by any number of cuπently available OCR software packages which might be installed on the intemet FAX server. In order to facilitate easy and accurate OCR conversion, die following techniques can be applied by the users of such a service. First, if using a wordprocessor, printing documents to be FAXed in a large (e.g., 14 point or more) typeface will improve results; printing using a mono-spaced (rather than proportionally spaced) typeface will improve results; using the same typeface each time (for which the OCR software may be fine-tuned, and such specification or fine-tuning stored and recalled for each user's account) will improve results. Sending an example of the typeface alphabet, in a standardized order (as shown in Figure 1, used with an EMail address) can help.

— β— Alternately, a software application could be supplied to each user with such an InterFAX account which would convert EMail text to a series of dots or other characters which may then be re-converted back to text at die intemet FAX server. Inventor calls such technology the "Paper Modem" and this is discussed in greater detail in his prior patent applications, cited above. Alternately, if an image were to be delivered, rather than ASCII text, a common image format might be chosen, such as TIFF, which most recipients would likely be able to display. Or, a display utility might be delivered by the intemet/FAX server, appended to the EMail transmission (or, at least, a note as to how to request delivery of such a utility via the intemet). Binary (non-ASCII-text) files, such as an image file or display utility, must usually be converted to a peculiar text format, such as by a UNIX utility called UUENCODE, prior to sending as EMail, and converted back by the complementary utility UUDECODE. The display utility (or note) may only be sent the first (few) times such InterFAX EMail were sent to a particular party (account) on the net — to be suppressed once a particular user is assumed to be familiar with the procedure. Alternately, part of the "note" may be instructions on how to send EMail to a particular account accessible to the intemet/FAX server involved to register one's EMail address as an "experienced" user and, u_us, not in further need of the utility or note. For InterFAX EMail that such a party wants to initiate rather than respond to, various methods have been described elsewhere herein to facilitate the specification of an EMail delivery address. The FAX to text conversion techniques described elsewhere herein can also be applied here as well.

THE INTERNET PHANTOM OR VIRTUAL FAX ACCOUNT Similarly, a complementary service can provide to a user an EMail account that will function as a

"phantom" or "virtual" FAX machine. This would be useful for people who have an EMail account but who do not want to go to the trouble/expense of obtaining a FAX machine or second telephone line, or who do not want to go to the inconvenience or lack of reliability and security associated with using a shared or "public" FAX at a copy shop or in an office. There are many people who focus communication on their computers, and this will permit them to conveniently communicate with others who rely on FAX for business communication.

In this case, the intent will be to provide a mechanism that appears to die public, and particularly those who carry out business by FAX, as a FAX number but which, for the account owner, functions as an EMail account. Outgoing EMail-to-FAX communication would operate as already described; as would machine-readable graphic remm coversheet technology. However, the idea here is to be able to publish a seemingly standard FAX number — in an advertizement, on a business card, etc. — and have an intemet/FAX server receive incoming FAXs for forwarding to the user's EMail account (perhaps after OCR conversion to text).

One approach is for each user to have a separate telephone line coming into the internet/ FAX server; however, this will be expensive. A less expensive alternative is to have a single (or a few) physical line(s) which respond(s) to a range of dialed numbers. Separate numbers within the range are then distinguished by DID technology and converted to a user's EMail address by consulting a table.

A third alternative is to use one phone number for multiple user accounts and to publish an extension to be dialed in after the main number which, again, would coπespond to an EMail account or address.

A fourth approach (which will not hide as well, the virtual nature of this FAX machine) is to have the FAX originator call a common number, there to be instructed to enter their FAX machine number and a published code for the recipient. These would be stored by the intemet/FAX server and, using caller ID technology, when a FAX came in from the FAX machine specified during the dialog, it would be identified as intended for the user's account.

BILLING In general, billing for such services is not considered part of the invention. However, it is noted mat: either the sender or recipient may be billed; either the EMail or FAX user may be billed; billing may be mediated by me intemet or a phone company, and may be available only on an account basis only, or offered to the general public; and, 800 number, 900 number, calling card, credit card or any other billing options may be used.

DESCRIPTIONS OF DRAWINGS Figure 1 has already been described in the section entitled ALTERNATE PREFERRED EMBODIMENTS. Figure 3 shows how a message (311) originated on an intemet connected machine (310) (e.g., from an EMail account (312)) is passed to an intemet/FAX server (304) over the intemet (309), and is tiien passed from die intemet/FAX server (304) to a standard FAX machine (or computer-based FAX server) (301), at a standard telephone dial-up number (302), over a standard dial-up telephone line (303). Included in the intemet/FAX server (304) is a FAX/Modem (also called a PC/FAX card, and which may be also comprise operating routines, supplied in PROMs or as separate software) (305) or equivalent, and software that: converts the EMail text to FAX image (306); generates die bar code or other machine-readable graphic for the return coversheet (307); and, keeps a record of the transmission (308) including, for example, a sequence number and die originating EMail account number.

Figure 4 shows a FAX message content (405), which message also includes addressing information in a barcoded or OCR coversheet (403) or as account ID information (404), originated on a standard FAX machine (or FAX server) (401), which machine is connected to a standard dial-up phone number (402). The FAX information is passed over a standard dial-up phone line (406) to an intemet FAX server (407), and is Λen delivered to an EMail or other intemet account (413) residing on the recipient's computer (412) via the intemet (411). Included in die intemet FAX server (407) is a FAX-Modem (408) and software to: read and decode the barcode or OCR information identifying the intemet account for delivery (409); and, look up an intemet account number from a document sequence number (if needed) and initiate an EMail message to that EMail account (410).

Figure 2 shows how two standard FAXs (201) and (207) which operate as in Figure 3 and Figure 4 can communicate with each other by connecting to two intemet/FAX servers (203) and (205) via standard dial-up lined

(202) and (206); die two intemet FAX servers (203) and (205) communicate with each otiier over die intemet (204).

Figure 5 shows a more detailed diagram of element (304) of Figure 3, die intemet FAX server, in EMail to FAX mode of operation. An EMail message (501), comprising botii content and address, is received by die intemet/FAX server, via die intemet, and a software routine (502) extracts the recipient's phone number embedded in the EMail address. Alternately, for some embodiments, die EMail address will specify an apparently standard account (nominally, but not necessarily, on the server machine) which will be known to die server to be an alias for a FAX number and, in tiiat case, die recipient's phone number will be looked up in a table accessible by d e server.

An additional software routine (503) will generate a special remm cover sheet with human readable information, as is usual, and a machine-readable (e.g., barcoded or OCR printed) document sequence number and/or Email account designation as described above. A ird software routine (504) will convert die ASCII text of the EMail content to a FAX image of tiiat text. The EMail may also contain information already in image form which will not require such conversion.

FAX image element outputs from (503) and (504) are combined into the total FAX content (505) and is delivered along witii the phone number (506) generated by (502) to a PC/FAX card or equivalent (507) equipment in die intemet/FAX server.

Element (507) under control of die computer which comprises die bulk of die intemet/FAX server tiien calls up a standard FAX machine or equivalent (509) over a standard dial-up telephone line (508) to deliver composite FAX document (505).

Figure 6 shows a more detailed diagram of elements, (401) a FAX machine and (407) die intemet/FAX server, of Figure 4, in FAX to EMail mode of operation. A standard FAX machine or equivalent (600) produces scanned FAX information of a document's content (601) which is transmitted as content (605) with a separate or integrated EMail address or document sequence number (606). Element (606) comprises some combination of three alternatives: a machine readable graphic (e.g., barcode, OCR text, etc.) on die coversheet (602); user entry from a telephone keypad (603); or, information placed in die FAX ID Field of die FAX transmission (604). Elements

(605) and (606) are sent together as a complete FAX transmission (607) over a standard dial-up telephone line (608) to internet/ FAX server (609).

Intemet/FAX server (609) is an internet-connected computer system tiiat comprises, in addition to standard computer components, a PC/FAX card or equivalent (610) capable of: receiving FAX transmissions (611); decoding DTMF telephone keypad tones (612); and, carrying on an interactive voice script witii the user (613); in addition to several software routines. The routines comprise: software (614) to convert FAX content (605) to a computer image format, such as TIFF (615); optional software (616) to process tiiat computer image (615) by OCR algoridims (616), converting die image information to ASCII text format (617); and some combination of three elements, directly corresponding to which combination of elements (602), (603) and (604) were utilized in transmission, to derive die document sequence number or EMail address. Of die three alternatives: software routine (618) derives tiiat information by decoding die machine-readable (e.g., barcode or OCR text) coversheet (602); software routine (619) converts DTMF tones (603) from the interactive script; and, software routine (620) reads the FAX ID Field (604) from the PC FAX card.

In addition, the intemet/FAX server computer contains software that will (if needed) look up the recipient's EMail address from a table referenced by die sequence numbers of any previously delivered documents (621); intemet EMail generation software (622) that sends content (605), (615) and/or (617) to die address derived from some combination of (618), (619), (620) and (621); and a physical connection (623) controlled by communication software (624) to die intemet (625).

For all the system diagrams depicted herein, the structures shown are exemplary, some elements may be organized differently, combined into a single element, split into two or more elements, omitted entirely, or provided by a different mechanism. However, die depicted systems will work. In particular, some of tiiese functions may be carried out by hardware components, such as a PC/FAX card; or by software routines residing on, or supplied witii, such a component, or available on the server system or via the intemet.

The information flow already shown in Figure 3 and Figure 5 is again described, tins time as a Software Flow Diagram in Figure 7. An EMail message arrives at die intemet/FAX server in the usual manner (700). At tiiat point the address of the recipient is verified as a valid delivery to tiiis site (701) and, if not, the mail and an eπor message are "bounced back" to die originator of the EMailing.

If the address is valid it is checked (702) to determine if die "EMailbox" specified is a standard (i.e., non- FAX) address and, if it is standard address, die EMail is delivered as standard EMail. Otherwise, delivery to a FAX machine is determined (703) by extracting a phone number from the EMail address itself, or by accessing a table of valid accounts accessible by this site and determining tiiat die EMail address is actually a "phantom" or "virtual" address which is meant to appear as a standard EMail address but which, in actuality, is an "alias" for FAX delivery of EMail.

A unique sequence number for the document is generated (704); uniqueness may be guaranteed by prefixing the Server's site address to a local sequence number which is constantly incremented.

A machine-readable graphic (e.g., barcode or local OCR standard) return coversheet is generated (705) which included coded versions of the sender's EMail address and/or the document's sequence number, and which may include other information such as recipient data, etc. In addition, human-readable printed instructions to the recipient, such as how to use a remm cover sheet when responding, can also be included in this cover sheet. The text (presumably ASCII) of sender's message is converted (706) to an image of that text, perhaps in a format such as TIFF, or perhaps directly into compressed FAX transmission format. This is integrated with any elements of die EMail content which are already in graphic or image format, and with the image of the coversheet generated at (705) above. The composite message image is tiien converted (707), if necessary, to compressed FAX transmission format.

The content, via (707), is scheduled (perhaps delayed for convenience, or to lower phone tolls) for delivery (708) to die phone number derived at (703) and an entry of relevant transaction information is made. The transaction record is updated when delivery is actually affected, or given up on.

Delivery is affected (709) via a PC/FAX card or equivalent mechanism over a dial-up telephone line and retried until successful, or until a maximum number of attempts has been made. If delivery is unsuccessful the originator is notified by remm EMail. Similarly, successful delivery may also cause notification to originator.

The information flow already shown in Figure 4 and Figure 6 is again described, this time as a Software Flow Diagram in Figure 8. A FAX message, with optional voice/keypad interaction from the user, arrives at the intemet FAX server (800). At that point the EMail address of die intended recipient must be determined and can be an any of (or any combination of) eight ways. [In particular, it may be determined tiiat the message is to be delivered to another FAX location in which case it may be forwarded tiiere, via the intemet and anodier intemet FAX server, as shown in Figure 2. Otherwise, if delivery is to be a(n apparently) standard EMail account die depicted software/process flow is followed.] The eight methods of identification of the intended EMail account (either directly or, indirectly, by referencing a document sequence number which is associated with an originator's EMail account) include the following.

The DID of the specific intemet/FAX server phone number called by die FAX machine may be used to reference (801) a table linking such numbers with EMail account addresses.

The Caller ID of d e telephone number that die FAX machine calls from and may be used to reference (802) a table linking such numbers with EMail account addresses. The FAX ID Field of the incoming FAX message may be consulted to specify (803) an EMail account, document sequence number or other reference into a table linking such references with EMail account addresses. A non-standard digital header, footer, or other inserted information, contained in the incoming FAX message can be consulted to specify (804) an EMail account, document sequence number or other reference into a table linking such references with EMail account addresses. Information contained in a machine-readable graphic (e.g., a barcode or OCR text) residing on the coversheet (perhaps, a remm coversheet supplied by the intemet/FAX server with a FAX previously delivered to die cuπent sender) or in the body of die incoming FAX can be detected, decoded and consulted to specify (805) an EMail account, document sequence number or other reference into a table linking such references with EMail account addresses. Similarly, an agreed upon "standard" format for information residing on die coversheet (such as depicted in Figure 1) or in the body of die incoming FAX can be detected, decoded and consulted to specify (806) an EMail account, document sequence number or other reference into a table linking such references with EMail account addresses.

In die absence of an agreed upon "standard" format, information residing on the coversheet or in the body of die incoming FAX, may be analyzed by an intelligent computer program, as described in Inventor's prior patent applications, referenced above, to detect, decode and specify (807) an EMail account, document sequence number or other reference into a table linking such references with EMail account addresses.

Information can be input by sender via the touchtone keypad, directly as an "extension" or during an interactive session further comprising synthesized or pre-recorded voice segments from e computer, and the DTMF tones detected, decoded and consulted to specify (808) an EMail account, document sequence number or other reference into a table linking such references with EMail account addresses.

At tiiat point an EMail address has been determined; in addition, by the same mechanisms, other information may be specified by the sender, for example, sender's name or EMail address, a reference line, and options such as whether to convert the FAX content from image to text before sending, delivery priority, etc.

The incoming FAX is (usually) translated (809) from compressed FAX translation format to a more usual computer image format, such as ΗFF. Optionally, if specified by die user, or if die default procedure for this user's account established at the intemet/FAX server, the FAX content is further converted (810) via OCR to text, presumably ASCII, in standard EMail format; or further converted via Inventor's "paper modem" technology to 'text' or 'binary' digital format. In this way, the recipient, if a holder of a standard EMail account, may access the message as standard EMail text, without having to access a graphic software utility to display the FAX message as an image. The recipient may, thus, be totally unaware that the message originated at a FAX machine radier ti an a standard EMail account.

In either case, the text or image format message is formatted as the content part of an EMail message (for example, using UUENCODE to permit a binary image or compressed image file to be transmitted as a non-binary-mode text message) which is then submitted to The Intemet (811) for delivery to the EMail account derived by any combination of steps (801-808) above.

The flows τlepicted in the software flow diagrams herein are exemplary, some items may be ordered differently, combined in a single step, skipped entirely, or accomplished in a different manner. However, die depicted flows will work. In particular, some of these functions may be carried out by hardware components, such as a PC/FAX card; or by software routines residing on, or supplied witii, such a component, or available on the server system or via die intemet.

AVAILABILITY OF ELEMENTS OF TECHNOLOGY It should be noted tiiat the vast majority of individual elements of die foregoing invention are available "off- the-shelf" as hardware and software components, and are easily integrateable by one of ordinary skill in computer systems programming, integration and administration.

Specifically, computer add-in hardware boards are available to provide FAX/Modem capabilities, and "voice mail" capabilities (i.e., voice recording and playback, sensing of DTMF keypad entry, and reading of embedded DID and Caller ID signals). These components are available from many vendors and many developer- level software routines and whole application programs are available to operate such boards. These software routines can be coordinated and made to communicate and exchange information under operating systems such as UNIX, DOS, Windows, or System 7.

Similarly, the communication, EMailing and other software functions that make up "The Intemet" are widely know and available and their use and adaption are well within the ken of one of ordinary skill in computer network administration.

Thus, the various technological elements that comprise the invention disclosed herein are (except as described otherwise) standard, well-known, widely available elements. Their construction, operation, use and integration are not, in general, the subject of the instant invention. For the details of the construction, operation, use and integration of these components die practitioner is directed to die available published literature, as well as software and equipment manuals, in the areas of hardware, software and information formats relating to, without limitation: FAX machines, FAX/Modems, FAX servers, voice mail devices, barcode printing, barcode scanning, optical character recognition, computer communication and networking (including, specifically, EMail, The Intemet, and related communication and information exchange protocols such as HTTP, UDP, TCP/IP, etc.) and computers and operating systems.

Many of the elements of the present invention are available "off-the-shelf" and, in and of themselves, not inventive. However, the design, construction and operation of the composite systems and techniques disclosed herein, as well as the use to which tiiey are put, are the subject of the instant invention and are presented as novel and useful. These novel, composite, high-level system designs are described herein and depicted in die accompanying system and flow diagrams.

Finally, it is noted tiiat the capabilities and system components described herein may be provided by equivalently functioning substitutes. For example: signals and hardware may be of analog or digital construction; certain functions may be exist .as special puφose hardware, or as programming residing on general puφose hardware; software may be provided on PROMs, or be stored in memory or on magnetic or optical disk; various capabilities may, in different situations, reside in a FAX machine, FAX/Modem in a computer, in a local computer, or in a remote computer; many options exist for FAX-to-FAX, FAX-to-computer or computer-to-computer interconnection; etc. The use of any appropriate system component, now in use or later developed, to affect the methods and systems described herein, is considered to be within the scope of the instant invention. It will thus be seen that the objects set forth above, among those made apparent from the preceding description, are efficiently attained and certain changes may be made in carrying out the above method and in die construction set forth. Accordingly, it is intended tiiat all matter contained in the above description or shown in die accompanying figures shall be inteφreted as illustrative and not in a limiting sense.

While there has been shown and described what are considered to be prefeπed embodiments of die invention, it will, of course, be understood tiiat various modifications and changes in form or detail could readily be made without departing from the spirit of the invention. It is, therefore, intended that the invention be not limited to die exact form and detail herein shown and described, nor to anything less than the whole of die invention herein disclosed as hereinafter claimed.

I claim:

Claims

1. A method for specifying information from which a packet-switching network address may be derived by incorporating into a transmission intended for FAX reception a machine-readable graphic comprising said addressing information.

2. A method for facilitating the routing via a packet-switching network of a communication such as a FAX initiated from a dial-up source by incoφorating into the dial-up transmission information auxiliary to the message content from which can be automatically derived a network address.

3. A method for routing via a packet-switching network a communication such as a FAX transmission derived from a dial-up source by incorporating information auxihary to the message content into that transmission and passing it on to a packet-switching network which additional information comprises a network address.

4. A metiiod as in claim 2 wherein said auxiliary information comprises a machine-readable graphic.

5. A mediod as in claim 4 wherein said machine-readable graphic comprises a barcode.

6. A mediod as in claim 4 wherein said machine-readable graphic comprises OCR text.

7. A metiiod as in claim 4 wherein said machine-readable graphic comprises a filled in mark-sense form.

8. A mediod as in claim 4 wherein said machine-readable graphic comprises a specially formatted printing of network addressing information.

9. A method as in claim 2 wherein said auxiliary information comprises DTMF tones.

10. A method as in claim 2 wherein said auxiliary information comprises DID information.

11. A method as in claim 2 wherein said auxiliary information comprises caller ID information.

12. A method as in claim 2 wherein said auxiliary information comprises FAX ID field information.

13. A method as in claim 2 wherein said auxiliary information comprises a digital information field additional to those normally included in a Group 3 FAX transmission.

14. A mediod as in claim 3 wherein said auxiliary information is derived from intelligent analysis of the FAX content by the steps of:

a. decoding an encoded document FAX transmission into a document image in raster format;

b. format analysis of the output of said decoding step, to analyze the document raster image and identify and type at least one image section, and producing a sectioned document image; c. at least one graphic decoding/conversion process, each keyed to a particular type of document image section, to process the output of said format analysis step, to decode at least one document image section and convert its content to a machine-usable coded document section; and,

d. context dependent extraction, to process the output of die graphic decoding/conversion step, tiiat will analyze one or more machine-usable coded document sections to identify and extract document/recipient information.

15. A method for facilitating a virtual EMail account affected at least in part by the method of claim 3.

16. A method for facilitating a virtual FAX machine account affected at least in part by die mediod of claim 3.

17. A method as in claim 15 comprising the additional step of converting a FAX image of text to ASCII by OCR techniques.

18. A method as in claim 16 comprising die additional step of converting a FAX image of text to ASCII by OCR techniques.

19. A method for forwarding already delivered EMail residing in an EMailbox to die intended recipient via

FAX comprising:

a. converting EMail to compressed FAX transmission image format; and,

b. delivering via FAX/Modem said EMail converted to FAX compressed transmission image format to a standard FAX machine.

20. A method for picking up EMail comprising:

a. telephoning a network/FAX server; and,

b. entering a request to said network/FAX server for delivery affected by die mediod of claim 19.