The present invention relates generally to the field of communications associated with the communication of facsimile messages and associated with the uniting of traditionally distinct message delivery systems such as facsimile delivery and electronic mail delivery.
The popularity of the quick and easy facsimile delivery of messages and the popularity of low cost delivery of messages via electronic mail (also referred to as “E-mail”) messaging systems have for quite some time enticed attempts to mingle the two technologies, and efforts have become even more fervent in the wake of the recent explosive increase in use of the global computer data network known as the “Internet”. An early attempt to mingle facsimile and Email message delivery technologies is represented by the Facsimile Transmission System of U.S. Pat. No. 4,941,170 (Herbst). Herbst appears to show a system which uses an E-mail system to route a facsimile file between controllers associated with the E-mail network in order to accomplish, in the end result, a facsimile input and a facsimile output. U.S. Pat. No. 4,837,798 (Cohen, et al.) discloses a system whose stated goal is to provide a single, “unified” electronic mailbox for storing either messages or notification of the existence of messages of different types. Cohen, et al. does mention the integration of facsimile mail messages, but does not appear to clearly discuss how the system would handle such fax messages. U.S. Pat. No. 5,339,156 (Ishii) discloses a system where a data communication center and a facsimile mail center are linked in a manner to accomplish the delivery of E-mail messages by way of facsimile, but not visa versa. At the same time, the facsimile industry has seen a growth in the use of interactive communication with remote store and forward facilities (“SAFF”) for storage in a “fax mailbox” in digital image form and managed delivery of facsimile messages, as exemplified by U.S. Pat. No. 5,291,203 (Gordon, et al.); and further, the art includes the use of locally appended devices to the sending fax device to intercept commands and route facsimile messages, in facsimile form, to a remote SAFF for subsequent delivery to a destination facsimile device, as exemplified by U.S. Pat. No. 5,555,100 Bloomfield, et al. Each of the above-mentioned references appears dedicated to the ultimate delivery of the message to a destination fax machine or fax capable device such as an equipped personal computer (“PC”) .
Briefly described, the present invention comprises a fax to E-mail system and related method whereby a facsimile transmission is sent to its recipient via electronic mail (such as through the “Internet”) rather than via another facsimile machine, and is delivered in such a manner that it can be retrieved by the recipient at his/her E-mail device, in the ordinary course of retrieving the E-mail, and viewed on the screen of the E-mail device. The invention provides for and accomplishes the delivery of a document, which begins as a hardcopy, as an electronic file retrieved through an E-mail recipient's terminal and read at the computer screen of the E-mail recipient's terminal.
The system of the present invention includes, in its most preferred apparatus and method embodiments, among other elements, a “local interface” and a remotely located Facsimile/E-mail server system (FEM-GATEWAY) which cooperate to provide a Facsimile/E-mail service whereby hardcopy information, including textual and/or graphical portions, is communicated between a facsimile device and an E-mail device, while still allowing conventional operation of the facsimile device. More specifically, the present invention comprises apparatus and methods for the input of an E-mail address locally to a facsimile machine, for directing the transmission of the image to a remotely located FEM-GATEWAY, for receiving and converting data representative of an image scanned by the facsimile device (referred to herein as facsimile information) into a computer-readable data file formatted in an image data file format, for creating an addressed E-mail message to which the computer-readable data file is attached, and for delivering the E-mail and attachment to a desired recipient over a data network such as a global computer network, such as the “Internet”.
In its preferred embodiments, the interface device of the present invention uniquely receives an alphanumeric E-mail address, displaying the address for verification by the user, is specially configured to command the FEM-GATEWAY to transmit a fax document via E-mail, and conveys an E-mail address and fax message (through the attached fax device) to the FEM-GATEWAY. The interface device allows any pre-existing fax machine to function as the sending machine of the invented system, with no modification to the fax machine itself. The present invention's handling of the fax message by converting the message to a computer-readable image file and attaching it to a system generated E-mail message, and the system's cooperative interaction between the interface device and the FEM-GATEWAY uniquely allow the present invention to accomplish its intended goal of delivering fax messages via the E-mail system. In at least one alternate embodiment, the functions of the interface device are embedded into a conventional fax device.
The present invention bridges two networks, interacting first in the telephone network (PTN) to transmit as telephony signals a facsimile message to the FEM-GATEWAY and then interacting in the E-mail network (through the “Internet” or other data networks) to deliver an E-mail message to its intended E-mail address. A sender wishing to send a facsimile message selectively activates the interface device locally associated with the sending fax machine which results in the fax being sent differently than a normal fax transmission. In accordance with the preferred embodiments, the interface device initiates a connection through the PTN to a server at a remote FEM-GATEWAY, and the interface device interacts with that server to generate and deliver to the intended recipient's E-mail address an E-mail message to which is attached the facsimile document formatted as a computer-readable image file compatible with the recipient's E-mail terminal.
Numerous features, objects and advantages of the present invention in addition to those mentioned or implied above, will become apparent upon reading and understanding this specification, read in conjunction with the appended drawings.
Refer now in greater detail to the drawings in which like numerals represent like components throughout the several views and in which lower letter reference numeral suffixes differentiate similar components referred to collectively without such suffixes.
In a first preferred embodiment of the present invention, the fax interface device 102 is connected by an accessory line 109 (which, in the preferred embodiment is a standard telephone cable) to the standard “telephone out” RJ-11 jack 113 (also, sometimes referred to as the “accessory jack” 113) of a standard fax device 106 (for example, conventional stand alone fax machine or multifunction machine with fax capabilities). Alternatively, the accessory line 109′ by-passes the accessory jack 113 and connects at, for example, a line splitter 117, directly to the common communication line 107. As would be understood by one skilled in the art, this places the fax interface device 102 “on line” with the fax device 106 such that both the fax interface device 102 and fax device 106 are serviced in what might be termed a “parallel relationship” by the same communication line 107 to the public network 108.
The FEM-GATEWAY 104 comprises a Fax-Server 110, a Web Server 111, an E-mail-server 112, and a data network 114. The Fax-Server 110 connects to the E-mail-server 112, and a data network 114. The Fax-Server 110 connects to the data network 114 which includes, in accordance with the preferred embodiment of the present invention, use of a TCP/IP protocol running on Ethernet hardware and includes, but is not limited to routers, hubs, cabling, and other hardware and software necessary for proper connection to the E-mail network and to the E-mail server). It should be understood that the scope of the present invention includes other data networks 114, including local and wide area data networks which utilize other network protocols and network hardware. The E-mail-server 112 connects to an E-mail network 116 (i.e., a network such as the Internet, a satellite network, a cable network, a telephony network, a wireless network, or other data network) which enables the communication of electronic mail (referred to herein as “E-mail”) to an E-mail device 118. An E-mail interface device 120 (including, for example and not limitation, hardware and software systems known as E-mail servers) (hereinafter also referred to as E-mail server 120) connects the E-mail device 118 to the E-mail network 116 and, hence, to the gateway E-mail-server 112 through the E-mail network 116. The Web Server 111 connects to Fax-Server 110, gateway E-Mail-server 112, and data network 114, and hence to the E-mail network 116. It should be understood that the connecting lines shown in
While only one fax device 106 and only one fax interface device 102 are shown in
It should be noted that while only one E-mail device 118 and only one E-mail server 120 are shown in
Other components of the Fax-Server 110 shown in
The Fax-Server 110, as seen in
The Fax-Server 110 monitors its fax/data communication channels for a call from a fax interface device 102. Upon receiving such a call on its fax/data communication channel, the Fax-Server 110 services the call by, among other tasks: verifying (against a stored list of valid identification codes of fax interface devices 102) that the call is to be processed; receiving from the fax interface device 102, an E-mail address associated with a desired recipient of a document; optionally receiving information identifying the sender; receiving fax image data representative of the document to be communicated to the desired recipient; optionally preparing and forwarding a confirmation (i.e., a fax document comprising a single page having text which indicates that the recipient's E-mail address and the fax image data representing the document were received by the Fax-Server 110) to the fax device 106; and, preparing and forwarding an E-mail message 270 (see
In accordance with the preferred embodiment of the present invention, the Fax-Server 110 is programmed to convert fax image data received from all of the plurality of fax devices 106 which deliver to the Fax-Server into the same, pre-selected industry-standard format, as selected by the administrator of the FEM-GATEWAY 104. It is intended, as part of the preferred embodiment of the present invention, that the selected format into which the Fax-Server 110 is preferably programmed to convert fax image data is a format which will be automatically compatible with major E-mail readers and browsers available on the market at a given period of time. Thus, at the time of the writing of this disclosure, the preferred format is the “TIFF format”. In accordance with the preferred embodiments of the present invention, the selected format into which the fax image data is to be converted is periodically changed (and the Fax-Server 110 processes appropriately modified) by the administrator to be compatible with the automatic de-coding and re-assembling software utilized by, for example, a majority (or selected plurality) of browsers and E-mail readers on the “then current” market for E-mail devices 118.
Thus, in accordance with the preferred methods of the present invention, the Fax-Server 104, upon receiving a fax message delivered from a fax device 106, automatically converts the received fax image data to a TIFF formatted file, naming the TIFF file with the appropriate “.TIF” file extension.
The message portion 272, of the E-mail message 270 is generated by the Fax-Server 110 and forwarded to the gateway E-mail Server 112 for delivery to the E-mail network 116. The message portion 272 comprises a plurality of information which corresponds to that same information displayed in the message portion 272′ depicted in
The body portion 280 of the exemplary recipient viewed message portion 272′, as seen in
The attachment portion 284 of the exemplary recipient viewed message portion 272′, as seen in
The information and data used to populate the “fields” 282, 286, 290, of the header portion 276, as well as the text 300 and link data 297 of the body portion 280, as well as the informative data found in the textual portion 299 is all information and data received by the Fax-Server 110 during steps 1034 and 1036 of the process described below (see
The fax interface device 102 comprises telephony circuitry 320 which connects to and interacts with DSP circuitry 322 and Codec circuitry 321 to provide telephony interface support. The Telephony Circuitry connects through a phone line surge protector 326, a phone line coupler 332 and the accessory telephone line 109 to the communication line 107, which also connects to a fax device 106. As mentioned earlier, the fax interface device 102 is preferably connected (in “parallel relationship” with the fax device 106) to the common communication line 107 through connection to the accessory RJ-11 jack 113 of a standard fax machine or fax modem, and, alternatively, through connection of accessory telephone line 109 via splitter 117 to communication line 107.
The Codec circuitry 321 connects to the telephony circuitry 320 and to the DSP circuitry 322, performing analog to digital conversions for tone generation and detection. An example of this Codec is a Texas Instruments TCM29C16 available from Texas Instruments, located in Houston Tex.
The DSP circuitry 322, according to the preferred embodiment of the present invention, comprises a Digital Signal Processor with integrated flash memory for program storage, RAM for temporary data storage, a Codec interface for audio input and output, and an expansion bus to connect other needed peripherals. An example of this DSP is a Texas Instruments TMS320F206 available from Texas Instruments in Houston, Tex.
The DSP circuitry 322 is connected to serial nonvolatile memory, NVRam 323, to the Display 344 comprised, for example, of a Liquid Crystal Display (LCD) with built-in controller, and to the keypad (
The telephony circuitry 320 is connected to Codec 321, speaker 346, and to surge protection circuitry 326. The telephony circuitry 320 performs a variety of functions including ring detection, loop current, and on and off hook control. An example of this circuitry is the TS117 available from CP Clare, located in Wakefield Mass. The Speaker 346 provides line monitoring and program control audio feedback. An example of Speaker 346 as an amplifier is the LM380 available from National Semiconductor located in Santa Clara, Calif. The phone line coupler 332 connects to the Surge protection 326 and provides a telephony jack for interfacing to accessory telephone line 109 which is connected to fax device 106. An example of such a suitable coupler is 555979-1 from AMP Incorporated, located in Harrisburg, Pa. A power supply 341 connects through power adapter 340 to a source of a AC power and supplies necessary power to the components of the interface device 102.
In a configuration and manner of operation that would be understood by those skilled in the art, the telephony circuitry 320, Codec 321 and DSP circuitry 322 cooperate and interact to perform the functions which include, but are not limited to, those mentioned above. By way of example, in accordance with the preferred embodiment of the present invention: the Codec 321 connects to and communicates with the DSP 322 through Codec signal bus 316; signal bus 318 carries analog signals which originate from a telephone company central office (i.e., part of the PTN 108) and which are received by the fax interface device 102 through the accessory telephone line 109; the Codec 321 de-modulates the analog signals and produces digital representations of the analog signals which are communicated, through Codec signal bus 316, for analysis by the DSP 322; the analog signals commonly include, for example and not limitation, dial tone signals, DTMF signals and fax tone signals; after the digital representations of the analog signals are analyzed and identified by the DSP (according to programming stored within ROM memory of the DSP circuitry), the DSP determines whether or not a response is necessary and, if so, determines the appropriate response to the analog signal; the DSP 322, to respond, generates appropriate digital signals which are modulated by the Codec 321 to produce analog signals which are output along signal bus 318 to the telephone circuitry 320 and eventually to the fax line 107; according to the preferred embodiment, the Codec 321 can modulate and de-modulate analog signals in the Bell 202 communication format (which is a standard AT&T frequency shift key communication scheme) and in the V.21 communication format (which is a standard CCITT Group 3 fax negotiation and control procedure).
As an example of the interaction between the Codec 321 and the DSP circuitry 322, consider a sender wishing to communicate a document to a desired recipient via fax/E-mail, in accordance with the preferred embodiment of the present invention. Reference may be had here to the process charts and description related to
According to an alternate embodiment of the present invention shown in
In accordance with other alternate embodiments of the present invention, the Public Telephone Network 108 and E-mail network 116 are replaced by any of a variety of different interconnecting networks, including any combination of public, private, switched, non-switched, wireline, non-wireline, digital, analog, in-band signaling, out-of-band signaling, voice, data, local or wide area networks. In addition, although DTMF signaling and transfer of information through DTMF and data signaling formats are disclosed in the preferred embodiment of the present invention, other alternate embodiments of the present invention include methods and apparatus which accommodate signaling and transferring of information through alternate signaling networks and formats, including modem communications, integrated services digital network (ISDN) and other out-of-band and in-band signaling methods, whereby signals and information are communicated between a FEM-GATEWAY 104 and a fax interface device 102. According to still other alternate embodiments of the present invention, the apparatus of the Fax/E-mail communication system 100 comprises a FEM-GATEWAY 104 which employs only one computer that includes necessary hardware, and executes necessary programs present on the Fax-Server 110 and the E-mail-Server 112 of the preferred embodiment of the present invention. In still other alternate embodiments of the present invention, the apparatus of the Fax/E-mail communication system 100 comprises multiple computers, which include the necessary hardware and software present on the Fax-Server 110 of the preferred embodiment, and multiple computers which include the necessary hardware and software present on the E-mail-Server 112 of the preferred embodiment. It should be understood that it is within the scope of the present invention that indicated subsystems (servers 110, 112, 111) of the FEM-GATEWAY 104 are, acceptably, either geographically separated or geographically co-located.
Represented in
In order to enable Fax-to-E-mail service by performing some of the various steps of the plurality of steps described above with respect to
Referring now to
According to the preferred method of the present invention and as previously noted, an E-mail address associated with a desired recipient is input by the sender (at step 842), using the telephone-style keypad 342 of the sender's fax interface device 102, after being prompted for the recipient's E-mail address on a first row (or line) (e.g, the bottom line 334a) of display 344. Because the standard telephone keypad as represented by keypad 342 are restricted to 12 input keys 342a, multiple alphanumeric characters must be associated with each one of the 12 available keys 342a to provide all characters required to create a valid E-mail address. This is accomplished by associating characters with keys 342a either in alphabetical, numeric, or common trait order such that a sender can “spell” an E-mail address using the reduced-set keypad 342 without limitation to the required character set. In accordance with the preferred embodiment of the present invention, the sender enters the recipient's E-mail address using the fax interface device's keypad 342 (
Upon completion of the entry of the E-mail address, the sender presses the “GO” button 342d on the keypad 342 to begin a process whereby the interface device 106 interacts with the Fax-Server 110 of the FEM-GATEWAY 104 to forward the received E-mail address and to pre-condition the FEM-GATEWAY system for delivery of the fax image data from the fax device 106. With further reference to
The fax interface device 102 continues its processing at step 926 where the fax interface device monitors the communications with the Fax-Server 110 to determine whether or not an acknowledgment “ACK” as been received from the Fax-Server 110. If not, the process 830 branches to step 928 where the fax interface device 102 determines whether or not a time-out condition exists (i.e., the fax interface device 102 has been waiting for an “ACK” for an excessive period of time). If the fax interface device 102 has determined that a time-out condition exists, the fax interface device 102 goes on hook, at step 930, without communicating the recipient's E-mail address nor the fax image data to the Fax-Server 110. If the fax interface device 102 determines, at step 928, that a time-out condition does not exist, the front-end process 830 loops back to step 926. If, at step 926, the fax interface device 102 detects an “ACK”, the process 830 advances to step 932 where the fax interface device 102 sends a Fax-to-E-mail command to the Fax-Server 110. Then, the fax interface device 102 sends, at step 934, its unique identification code (ID) to the Fax-Server 110. Advancing to steps 936 and 938 of the front-end process 830, the fax interface device 102 sends the recipient E-mail address, received previously from the sender, optionally, the sender's ID, and a check sum to the Fax-Server 110. At step 940, the fax interface device 102 determines whether or not an “error-free ACK” has been received from the Fax-Server 110 on fax line 107. If so, the front-end process 830 continues at step 948 described below. If not, the process 830 branches to step 942 where the fax interface device 102 determines whether or not an “error ACK” has been received from the Fax-Server 110 on fax line 107 instead of an “error-free ACK”. If the fax interface device 102 determines that a “error ACK” has been received (i.e., indicating that the Fax-Server 110 is requesting that the fax interface device 102 re-send the fax-to-E-mail command, its own identification code, the recipient's E-mail address, and an associated check sum), the front-end process 830 loops back to step 932. If the fax interface device 102 determines that an “error ACK” has not been received, then the process 830 moves to step 944 where the fax interface device 102 determines whether or not a time-out condition has occurred. If not, the process 830 loops back to step 940 to continue waiting for an “ACK”. If so, the fax interface device 102 goes on-hook and the front-end process 830 returns to its “idle time”.
According to the preferred method of the present invention, and as seen in
As mentioned above, a process referred to herein as the COMCON process 1020 (see
Once communication has been established with a calling fax interface device 102, the COMCON process 1020 advances to step 1032 where, as seen in FIG. I 1A, the Fax-Server 110 receives a fax-to-E-mail command from the fax interface device 102. Then, at step 1034, the Fax-Server 110 receives the identification code of the calling fax interface device 102 followed, at step 1036, by receipt of the E-mail address, and optionally the sender ID as input by the sender on the fax interface device 102. Continuing at step 1038, the Fax-Server 110 receives a check sum from the fax interface device 102. Advancing to step 1040 (
Referring back to step 1040, if the Fax-Server 110 determines that the check sum is okay (i.e., there was no error during communication with the fax interface device 102), the Fax-Server 110 determines, at step 1048, whether or not the identification code received from the fax interface device 102 is okay by comparing the received identification code with a list of fax interface device identification codes which are stored in a database of the Fax-Server 110. If the Fax-Server 110 determines that the received identification code is not valid for any fax interface device 102, the COMCON process 1020 branches to step 1050 where the Fax-Server 110 determines whether or not a time-out condition exists (i.e., determines whether or not a maximum number of re-send requests have been exceeded). If no time-out condition exists, the Fax-Server 110, at step 1052, sends a an “ERROR ACK” command to the fax interface device 102 to request that the fax interface device 102 re-send the information received at steps 1032 through 1038. The COMCON process 1020 then loops back to step 1032. If the Fax-Server 110 determines, at step 1050, that a time-out condition exists, the COMCON process 1020 causes the fax communication interface 130 to go on-hook, thereby hanging-up the telephone call from the fax interface device 02, before looping back to step 1026.
If, at step 1048, the Fax-Server 110 determines that the identification code of the fax interface device 102 is okay, the COMCON process 1020 advances to step 1056 where the Fax-Server 110 sends an “ERROR FREE ACK” to the fax interface device 102 to indicate to the fax interface device 102 that it has received a fax-to-E-mail command, a valid fax interface device identification code, and an E-mail address associated with a desired E-mail recipient. The Fax-Server 110 then, at step 1057, sends a command to the fax interface device 102 to display the message “Press Send on Fax Device Now” on the display 344, which instructs the sender to initiate communications with the Fax-Server by pressing the “SEND” (or “START”, etc.) button on the fax device 106. The Fax-Server 110 then, at step 1058, sends fax tones along the fax line 107 to the fax device 106 and receives fax data from the fax device 106 at step 1060.
Continuing at step 1062 (
By way of example but not limitation, in the preferred embodiment, steps 1076-1084 of the COMCON process 1020 are performed in accordance with what is commonly known as the UNIX METAMAIL process, and the SENDMAIL processes 1120 of
Once sent to the E-mail network 116, the E-mail message 270 is conveyed in accordance with the handling processes of the E-mail network (such as the Internet Global Computer Network) to, for example, the “mailbox” associated with the recipient address 282. The message 270 is retrieved and viewed as discussed above regarding step 812 of
In accordance with an alternate, preferred embodiment of the present invention, as depicted in
Whereas the present invention has been depicted and described in relationship to embodiments in which the fax interface device 102 and the fax device 106 are embodied in separate chassis interconnected by an accessory communication line 109, alternate embodiments of the facsimile-to-electronic mail communication system 100 of the present invention comprise a combined unit fax/fax-to E-mail sending device (hereinafter also identified as the “combined unit 358”) which incorporates within a single chassis the functionality of both the fax interface device 102 and the fax device 106, with necessary component parts. In a first embodiment of such combined unit 102/106′, the fax interface device 102 of the embodiment of
It is understood that new and various communications techniques and systems are available and becoming available which communications techniques and systems are acceptably utilized to provide the “communication links” (e.g., link 132, link 202 , link 203, link 205) of the previously described preferred embodiments. By way of example,
While the embodiments of the present invention which have been disclosed herein are the preferred forms, other embodiments of the present invention will suggest themselves to persons skilled in the art in view of this disclosure. Therefore, it will be understood that variations and modifications can be effected within the spirit and scope of the present invention and that the scope of the present invention should only be limited by the claims below. Furthermore, the equivalents of all means-or-step-plus-function elements in the claims below are intended to include any structure, material, or acts for performing the function as specifically claimed and as would be understood by persons skilled in the art of this disclosure, without suggesting that any of the structure, material, or acts are more obvious by virtue of their association with other elements.
This application is a continuation of U.S. patent application Ser. No. 13/457,408, filed on Apr. 26, 2012, now U.S Pat. No. 8,488,207; which is a continuation of U.S. patent application Ser. No. 12/207,921, filed on Sep. 10, 2008; which is a continuation of U.S. patent application Ser. No. 10/795,655, filed on Mar. 8, 2004, now U.S. Pat. No. 7,446,906; which is a continuation of U.S. patent application Ser. No. 09/717,193, filed on Nov. 21, 2000, now U.S. Pat. No. 6,707,580; which is a continuation of U.S. patent application Ser. No. 09/235,566 filed on Jan. 22, 1999, now U.S. Pat. No. 6,693,729; which is a continuation of International Patent Application PCT/IB1997/001455, filed on Oct. 7, 1997; which claims the benefit of L.J.S. Provisional Patent Applications 60/048,064, filed on May 30, 1997; and 60/028,405, filed on Oct. 15, 1996; all of which are hereby incorporated herein in their entireties by reference. U.S. patent application Ser. No. 09/235,566 is also a continuation-in-part of U.S. patent application Ser. No. 08/839,655, filed on Apr. 15, 1997; which claims the benefit of U.S. Provisional Patent Application 60/028,405, filed Oct. 15, 1996; U.S patent application Ser. No. 09/235,566 is also a continuation-in-part of U.S. patent application Ser. No. 08/915,196, filed on Aug. 20, 1997, now U.S. Pat. No. 6,025,931; which claims the benefit of U.S. Provisional Patent Application Nos. 60/048,064, filed on May 30, 1997; and 60/028,405, filed on Oct. 15, 1996; all of which are hereby incorporated herein in their entireties by reference.
Number | Name | Date | Kind |
---|---|---|---|
3518553 | Ho et al. | Jun 1970 | A |
3594495 | Bond | Jul 1971 | A |
3760171 | Wang et al. | Sep 1973 | A |
3812945 | Koplow et al. | May 1974 | A |
3913721 | Koplow et al. | Oct 1975 | A |
3958088 | Vieri | May 1976 | A |
4137491 | Bartley et al. | Jan 1979 | A |
4145739 | Dunning et al. | Mar 1979 | A |
4198677 | Brunner et al. | Apr 1980 | A |
4207598 | Reich et al. | Jun 1980 | A |
4506111 | Takenouchi et al. | Mar 1985 | A |
4524393 | Ohzeki | Jun 1985 | A |
4573140 | Szeto | Feb 1986 | A |
4582957 | Hayes et al. | Apr 1986 | A |
4586086 | Ohzeki | Apr 1986 | A |
4607289 | Kurokawa | Aug 1986 | A |
4613907 | Yoshimoto et al. | Sep 1986 | A |
4630196 | Bednar, Jr. et al. | Dec 1986 | A |
4638118 | Wang et al. | Jan 1987 | A |
4713780 | Schultz et al. | Dec 1987 | A |
4716544 | Bartley | Dec 1987 | A |
4763191 | Gordon et al. | Aug 1988 | A |
4785473 | Pfeiffer et al. | Nov 1988 | A |
4827085 | Yaniv et al. | May 1989 | A |
4837798 | Cohen et al. | Jun 1989 | A |
4868860 | Andros et al. | Sep 1989 | A |
4902881 | Janku | Feb 1990 | A |
4918722 | Duehren et al. | Apr 1990 | A |
4941170 | Herbst | Jul 1990 | A |
4970603 | Kanai | Nov 1990 | A |
5008835 | Jachmann et al. | Apr 1991 | A |
5014300 | Harvath et al. | May 1991 | A |
5033079 | Catron et al. | Jul 1991 | A |
5062076 | Ho et al. | Oct 1991 | A |
5065254 | Hishida | Nov 1991 | A |
5091790 | Silverberg | Feb 1992 | A |
5115326 | Burgess et al. | May 1992 | A |
5136634 | Rae et al. | Aug 1992 | A |
5175684 | Chong | Dec 1992 | A |
5193110 | Jones et al. | Mar 1993 | A |
5200993 | Wheeler et al. | Apr 1993 | A |
5204757 | Agudelo et al. | Apr 1993 | A |
5247591 | Baran | Sep 1993 | A |
5287199 | Zoccolillo | Feb 1994 | A |
5291302 | Gordon et al. | Mar 1994 | A |
5291546 | Giler et al. | Mar 1994 | A |
5299255 | Iwaki et al. | Mar 1994 | A |
5317628 | Misholi et al. | May 1994 | A |
5333266 | Boaz et al. | Jul 1994 | A |
5339156 | Ishii | Aug 1994 | A |
5377017 | Lam | Dec 1994 | A |
5384835 | Wheeler et al. | Jan 1995 | A |
5386297 | Tanaka et al. | Jan 1995 | A |
5406557 | Baudoin | Apr 1995 | A |
5410416 | Amberg et al. | Apr 1995 | A |
5438611 | Campana, Jr. et al. | Aug 1995 | A |
5452099 | Von Meister | Sep 1995 | A |
5461488 | Witek | Oct 1995 | A |
5488651 | Giler et al. | Jan 1996 | A |
5508817 | Kunigami | Apr 1996 | A |
5548789 | Nakanura | Aug 1996 | A |
5555100 | Bloomfield et al. | Sep 1996 | A |
5559611 | Bloomfield et al. | Sep 1996 | A |
5559721 | Ishii | Sep 1996 | A |
5608786 | Gordon | Mar 1997 | A |
5631946 | Campana, Jr. et al. | May 1997 | A |
5675507 | Bobo, II | Oct 1997 | A |
5712907 | Wegner et al. | Jan 1998 | A |
5739850 | Hori | Apr 1998 | A |
5748484 | Cannon et al. | May 1998 | A |
5767985 | Yamamoto et al. | Jun 1998 | A |
5768347 | Beyda | Jun 1998 | A |
5777754 | Gavan | Jul 1998 | A |
5802314 | Tullis et al. | Sep 1998 | A |
5805298 | Ho et al. | Sep 1998 | A |
5809121 | Elliott et al. | Sep 1998 | A |
5835087 | Herz et al. | Nov 1998 | A |
5838461 | Hsieh | Nov 1998 | A |
5838821 | Matsubara et al. | Nov 1998 | A |
5848397 | Marsh et al. | Dec 1998 | A |
5859967 | Kaufeld et al. | Jan 1999 | A |
5872845 | Feder | Feb 1999 | A |
5881064 | Lin et al. | Mar 1999 | A |
5940187 | Berke | Aug 1999 | A |
5974449 | Chang et al. | Oct 1999 | A |
5999274 | Lee et al. | Dec 1999 | A |
6020980 | Freeman | Feb 2000 | A |
6023345 | Bloomfield | Feb 2000 | A |
6025931 | Bloomfield | Feb 2000 | A |
6028679 | Murphy | Feb 2000 | A |
6061502 | Ho et al. | May 2000 | A |
6073164 | Zey | Jun 2000 | A |
6101397 | Grob et al. | Aug 2000 | A |
6141695 | Sekiguchi et al. | Oct 2000 | A |
6195686 | Moon et al. | Feb 2001 | B1 |
6211972 | Okutomi et al. | Apr 2001 | B1 |
6320677 | Yoon | Nov 2001 | B1 |
6321194 | Berestesky | Nov 2001 | B1 |
6424426 | Henry | Jul 2002 | B1 |
6493022 | Ho et al. | Dec 2002 | B1 |
6590677 | Nakamura et al. | Jul 2003 | B1 |
6625642 | Naylor et al. | Sep 2003 | B1 |
6690480 | Maeda | Feb 2004 | B2 |
6693729 | Bloomfield | Feb 2004 | B1 |
6707580 | Bloomfield | Mar 2004 | B1 |
6857007 | Bloomfield | Feb 2005 | B1 |
6892239 | Kirkeby | May 2005 | B1 |
6920143 | Ortiz et al. | Jul 2005 | B1 |
6963634 | Toyoda et al. | Nov 2005 | B2 |
RE38908 | Ho et al. | Dec 2005 | E |
6999565 | Delaney et al. | Feb 2006 | B1 |
7019853 | Maeda | Mar 2006 | B1 |
7177909 | Stark et al. | Feb 2007 | B2 |
7446906 | Bloomfield | Nov 2008 | B2 |
7895313 | Bobo, II | Feb 2011 | B2 |
7898675 | Murphy | Mar 2011 | B1 |
8224909 | Bloomfield | Jul 2012 | B2 |
8488207 | Bloomfield | Jul 2013 | B2 |
20010000441 | Zinkov et al. | Apr 2001 | A1 |
20020019851 | Pollack | Feb 2002 | A1 |
20020059389 | Toyoda et al. | May 2002 | A1 |
20020062363 | Naylor et al. | May 2002 | A1 |
20020087648 | Petrovykh | Jul 2002 | A1 |
20040073709 | Bloomfield | Apr 2004 | A1 |
20040100648 | Kulakowski | May 2004 | A1 |
20050012965 | Bloomfield | Jan 2005 | A1 |
20060179112 | Weyer et al. | Aug 2006 | A1 |
20070236732 | Henry | Oct 2007 | A1 |
20090021796 | Bloomfield | Jan 2009 | A1 |
20110242606 | Bloomfield | Oct 2011 | A1 |
20120243053 | Bloomfield | Sep 2012 | A1 |
Number | Date | Country |
---|---|---|
1111923 | Nov 1981 | CA |
2507227 | Apr 1998 | CA |
2268333 | Nov 2005 | CA |
0402809 | Dec 1990 | EP |
0465011 | Jan 1992 | EP |
0504884 | Sep 1992 | EP |
0615 377 | Mar 1994 | EP |
0615377 | Sep 1994 | EP |
0850532 | Apr 2002 | EP |
2185361 | Jul 1987 | GB |
1493897 | Nov 1997 | GB |
5447504 | Apr 1979 | JP |
5840949 | Mar 1983 | JP |
58165452 | Sep 1983 | JP |
60134656 | Jul 1985 | JP |
61260741 | Nov 1986 | JP |
62141849 | Jun 1987 | JP |
6412856 | Jan 1989 | JP |
6458160 | Mar 1989 | JP |
6473942 | Mar 1989 | JP |
1112856 | May 1989 | JP |
58160 | Jan 1993 | JP |
6113727 | Apr 1994 | JP |
83942 | Jan 1996 | JP |
1998063759 | Mar 1998 | JP |
WO-9641463 | Dec 1996 | WO |
WO-9710668 | Mar 1997 | WO |
WO-9817041 | Apr 1998 | WO |
WO-0219692 | Mar 2002 | WO |
Entry |
---|
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 09/723,349, mailed May 9, 2003, 26 pages. |
United States Patent and Trademark Office, Final Office Action, U.S. Appl. No. 09/723,349, mailed Jun. 18, 2004, 29 pages. |
United States Patent and Trademark Office, Notice of Allowance, U.S. Appl. No. 09/723,349, mailed Oct. 6, 2004, 7 pages. |
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 10/681,562, mailed Aug. 9, 2007, 15 pages. |
United States Patent and Trademark Office, Final Office Action, U.S. Appl. No. 10/681,562, mailed Jan. 24, 2008, 15 pages. |
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 12/369,785, mailed Aug. 31, 2011, 12 pages. |
United States Patent and Trademark Office, Notice of Allowance, U.S. Appl. No. 12/369,785, mailed Mar. 2, 2012, 16 pages. |
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 13/490,403, mailed Oct. 30, 2012, 11 pages. |
United States Patent and Trademark Office, Notice of Allowance, U.S. Appl. No. 13/490,403, mailed Apr. 9, 2013, 11 pages. |
International Searching Authority, International Search Report, PCT Application PCT/US2001/023402, mailed Nov. 8, 2001, 3 pages. |
International Bureau, Preliminary Examination Report, PCT Application PCT/US2001/023402, completed Oct. 17, 2003, 10 pages. |
Kamae, T., “Development of Public Facsimile Communication System Using Storage and Conversion Techniques”, IEEE 1980, pp. 19.4.1-19.4.5. |
1-Line Worldwide, Inc., “Fax-4-Less Infrastructure Guidelines”, Jun. 4, 1996, 7 pages. |
Cheyenne InfoFax, FaxServe Product Information, pp. 1-15, prior to May 30, 1997. |
Yahoo Finance Business Wire, “Centigram and Lucent deploy VPIM protocol for exchanging voice and fax messages over the Internet”, Apr. 23, 1997, 2 pages. |
“Fax2Net Sends Faxes over the Internet”, Fax Focus Newsletter, vol. 17, Issue 21, Jun. 10, 1997, 2 pages. |
“Fabrik Fax, an E-Mail-To-Fax Service”, Fax Focus Newsletter, vol. 17, Issue 21, Jun. 10, 1997, 2 pages. |
Lumina News, “Lumina Office Products Introduces Internet Fax Software—Internet Fax Utility Offers Simplified Faxing to E-Mail Addresses”, Sep. 3, 1996, 2 pages. |
Biscom Introduces the e-fax Machine, the E-mail/Facsimile Solution “For the rest of us”, Sep. 19, 1996, 2 pages. |
ScanFX—Scanning Hardware for Internet E-Mail, Our Business Machine, Inc.'s Editorial Resource Chest, Irwindale, CA, Aug. 1996, 2 pages. |
F@x Mate, “Fax to E-mail Service: The Basics”, prior to Sep. 18, 1997, 2 pages. |
AT&T Introduces Most Comprehensive Fax-To-Data Service, Feb. 22, 1996, 2 pages. |
TAC Systems, Inc., FaxFree Portal 100, Fax Machine Internet Interface, 1997, 3 pages. |
Biscom, Inc., “The Messaging Machine, the ‘e-fax’ Model”, prior to Nov. 1996, 2 pages. |
JFax Personal Telecom, Extra Press Extra, “What the media says about JFAX Personal Telecom”, retrieved on Oct. 31, 1996, 2 pages. |
JFax Personal Telecom, Plug a Phone Into Your E-Mail, “Get all your Voice-Mail and Faxes in your E-Mail”, copyright 1996, pp. 1-3. |
JFax Personal Telecom, Frequently Asked Questions, Oct. 31, 1996, 3 pages. |
IBM Announcement Letters (US), Document 295, Microsoft Internet Explorer, Nov. 12, 1996, 22 pages. |
Sreenivasan, Sreenath, “German Pop Singer Sets Sights on Virtual Office”, The New York Times Cyber Times, Sep. 23, 1996, pp. 1-3. |
DigitalNote Fax2Net R5S1, Microsoft Internet Explorer, “How to Get Started with Net2Fax”, Oct. 31, 1996, p. 2 of 4. |
DigitalNote Fax2Net R5S1, “A Beginner's Guide to Digital Mail Fax2Net”, copyright 1995, pp. 1-10. |
IBM, “How to Set Up Your DirectTalkMail Box”, Nov. 12, 1996, 1 page. |
IBM Link/InfoLink, “IBM Software Allows Phone Messages to Be Retrieved Via Internet World Wide Web”, Nov. 28, 1995, 2 pages. |
Nigel Ballard @ The Paperless Office, JFAX Personal Telecom main page, Jun. 26, 1996, pp. 1-2. |
FaxWeb, Microsoft Internet Explorer, FaxWeb Viewer copyright 1996, Netoffice Solutions, LLC, Nov. 12, 1996, 1 page. |
Patel, Sanjiv P., et al. “The Multimedia Fax-MIME Gateway.” IEEE Multimedia Winter 1994, pp. 64-70. |
“First Global Fax and Voice to E-Mail Network Launched for Internet Users”. JFAX Press Information, Apr. 30, 1996, pp. 1-2. |
Timura, J., et al., “Studies on Present and Future Public Data Network Services in Japan”, Teleinformatics 79, 1979, pp. 293-299. |
Sheffield, B., “Office Automation in Practice”, Data Processing vol. 27, No. 2, Butterworth & Co. (Publishers) Ltd. Mar. 1985, pp. 18-20. |
Nordin, G., et al., “Introduction of a Store and Forward Facility in the Swedish Telex Network”, ISS '81 CIC, Montreal, Sep. 21-25, 1981, 7 pages. |
Elston, S., Distribution 1, EDI Experiences '88, Lowfield Distribution Ltd., 1988, pp. 186-188. |
Bransby, M., “Voice Mail Makes a Difference”, The Journal of Business Strategy, Jan./Feb. 1990, pp. 7-10. |
Hewer, J.M., “What's new in fax?”, CMA Magazine, vol. 64, Issue 10, Dec. 1990/Jan. 1991, pp. 21-22. |
Miki, T., “KDD's Facsimile Interworking and X.400 Interconnection”, IFIP 1991, pp. 123-134. |
Canadian Intellectual Property Office, Office Action, Application 2,507,227, dated May 29, 2007, 4 pages. |
United States Bankruptcy Court, Northern District of California, In Re Oaz Communications, Inc., Case No. 91-40335T, Notice of Motion for Final Order Authorizing Secured Accounts Receivable Financing Agreement, on Jul. 25, 1991, 1 page. |
Fiore, Dave, Fax Revised License Agreement, May 5, 1991, 8 pages. |
OAZ Communications, Inc., “Introducing NetFax Manager”, PC Week, Jul. 9, 1990, p. 52. |
Kondamorri, Pratap S., Letter re Acct. No. PRA001, May 29, 1991, 1 page. |
Murphy, Jeff, Cover Letter and Statement re Acct. No. PRA001, May 9, 1991, 2 pages. |
Paradox Development Corp., Invoice 14209, Apr. 30, 1990, 1 page. |
Fleming, Bill, “Link Your Workgroup to the World With Electronic Mail”, Mar. 15, 1991, 3 pages. |
Paradox Development Corp., MHS, 1988, 1 page. |
Kramer, Matt, “Lan Fax Gateways”, PC Week, 1989, p. 21. |
Land, Kris, U.S. Bankruptcy Court, Northern District of California, Proof of Claim, May 21, 1991, Case No. 91-40335T, 1 page. |
Paradox Development Corp., Para-Mail User's Manual, Version 2.16, Jul. 6, 1990, 476 pages. |
OAZ Communications, Exhibitors, Network 90 Dallas, 1990, p. 122. |
Fiore, Dave, Letter re two original license agreements, May 29, 1991, 1 page. |
Adams & West, e-mail exchange re: dl-mhs NetWare, Feb. 5-6, 1992, 1 page. |
Product Focus, Lantimes, Dec. 1988, pp. 35-38. |
oaz.l13, Jul. 3, 1991, Communication re NFUser License Agreement, 1 page. |
oaz.l10, May 10, 1991, Communication to U.S. Bankruptcy Court re Oaz case, 1 page. |
oaz.lt9, Mar. 19, 1991, Communication to U.S. Bankruptcy Court re Oaz case, 1 page. |
oaz.lt5, Feb. 21, 1991, Communication re New Letter of Agreement, pp. 1-2. |
oaz.lt8, Feb. 21, 1991, Communication from Kris Land re Oaz Chapter 11, 1 page. |
oaz.lt6, Feb. 1, 1991, Communication re NetFax Server Software Purchase Agreement, 1 page. |
oaz.lt4, Jan. 21, 1991, Communication re NFUser Termination Notice, pp. 1-2. |
oaz.lt2, Oct. 18, 1990, Communication re nonconformance, pp. 1-2. |
oaz.lt1, Oct. 2, 1990, Communication re relationship, 1 page. |
oazsales.rpt, Aug. 9, 1990, Communication re Sales Effort Report, 1 page. |
Thompson, M. Keith, “Para-Mail”, PC Magazine, Nov. 27, 1990, vol. 9, No. 20, p. 297. |
Paradox Development Corp. and Oaz Communications, Inc., Licensing and Professional Services Agreement, May 29, 1991, 11 pages. |
Letter re NFUser License Agreement—Development and Modification, Jun. 20, 1991, 1 page. |
Paradox Development Corp., Statement on Account OAZ001, Jun. 28, 1991, 1 page. |
Letter re NFUser License Agreement—Development & Modification, Jul. 3, 1991, 2 pages. |
Comverse/Ascom, “Ascom Group and Comverse announce formation of strategic marketing relationship and $6 million equity investment”, Business Wire, Aug. 17, 1989, pp. 1-2. |
Van Kampen, H., “Interconnection of the Teletex-, Telex- and Other Services”, International Switching Symposium, Montreal, Sep. 21-25, 1981, 5 pages. |
Shimoda, Minoru et al., “Enhanced Facsimile Data Conversion and Interface Control Equipment in FICS”, Electrical Communications Laboratories Technical Journal, Japan, vol. 34, No. 10, 1985, pp. 1393-1402. |
Intellectual Property Office Philippines, Office Action for Application No. 11999000809, Sep. 1, 2006, 3 pages. |
Postel, J., “Summary of Computer Mail Services Meeting Held at BBN on Jan. 10, 1979”, Mar. 1, 1982, printed from Internet on Jan. 11, 2006, 8 pages. |
Chang, Tawei, “UCL Facsimile System”, Feb. 1982, printed from Internet on Jan. 11, 2006, pp. 1-100. |
The Gale Group, “GammaLink Announces PC-To-Facsimile Communications”, Nov. 18, 1985, PR Newswire, USA, 2 pages. |
The Gale Group News Release, “Direct PC-To-Remote-Facsimile Communications Package Allows Fast, Low-Cost Transmission of Documents”, Sep. 15, 1986, 1 page. |
International Technology Disclosures, vol. 6, No. 5, May 25, 1988, 4 pages. |
Cantata Technology, Inc., “The Future of Electronic Messaging”, print version of Cantata Technology web page: www.Cantata.com/support/productinfo.cfm, printed Jul. 16, 2007, 2006 copyright, 8 pages. |
DID word definition from Webopedia Computer Dictionary, printed on Jul. 16, 2007, 4 pages. |
Matsushita Graphic Communication Systems, Inc., Panasonic Facsimile Operating Instructions Model No. UR-590, 2001 copyright, dated Jan. 2002 on back, 158 pages. |
Matsushita Graphic Communication Systems, Inc., Facsimile Panafax UF-585/595 User's Guide, 1999 copyright, 176 pages. |
“Setting Up Your Machine”, date unknown, pp. 14-25. |
Matsushita Graphic Communication Systems, Inc., How to Use Your Panafax UF-250, includes two copyright notices (1987 & 1988), 51 pages. |
Postel, J., “Rapicon 450 Facsimile File Format”, Sep. 28, 1980, printed on Jun. 2, 2006, http://www.scit.w/v.ac.uk/rfc/rfc7xx/RFC769.html, 3 pages. |
Communication from Erie Cheung to Jack Neurauter re specification for Voice Interface Processor, Aug. 30, 1991, 3 pages. |
United States Patent and Trademark Office, Office Action in U.S. Appl. No. 10/681,562, mailed Aug. 9, 2007, 15 pages. |
Share Communications, Inc., FaxShare User's Guide, Nov. 1989, 146 pages. |
Share Communications, Inc., Why Faxshare?, 1990, 2 pages. |
Shore, Joel, FaxShare NLM for NetWare 386 debuts, Computer Reseller News, Mar. 19, 1990, p. 54. |
The Pan Network, “Don't call us . . . We'll call you”, MIX, Mar. 1990, p. 133. |
Molsa, Terhi, “Telecommuting and the International Educator”, The Advising Quarterly, No. 26, Fall 1993, pp. 1-40. |
Register, Pam, “Fax has area man humming new tune”, Business The Reporter, Aug. 28, 1989, 2 pages. |
The PAN Network, Sending & Receiving FAX thru Email, alt.fax, Jun. 11, 1991, 1 page. |
Gamma Technology, Inc. DBA Gammalink, Invoice 2585, Dec. 15, 1987, 1 page. |
Facsimile, Jun. 9, 1988, 1 page. |
The PAN Network, “Next time you're not at home . . . Give us a call”, MIX, Jul. 1990, p. 35. |
Leopold, Perry, and Teresa Jackson, Facsimile re initial software release, Aug. 1990, 3 pages. |
Leopold, Perry, Letter to Music Week Publisher, Feb. 16, 1998, 1 page. |
Leadley, Simon, “Modems, bits and pieces”, Sonics The Music Magazine, Jul./Aug. 1989, cover and p. 46. |
The PAN Network, “Don't call us . . . We'll call you”, Keyboard, May 1990, p. 35. |
PAN FaxMail Rate Schedule for Dedicated Service, Jul. 12, 1989, 1 page. |
“1-900-MIDI: Dealers Keep Pace With PC Networks”, Music & Sound Retailer, Jan. 1989, 2 pages. |
Newton, F. Roger, IAAM Event Fax to Perry Leopold, Feb. 19, 1990, 1 page. |
Gamma Technology, Inc. DBA Gammalink, Invoice 4069, Oct. 12, 1988, 1 page. |
PAN FaxMail Rate Schedule, Sep. 15, 1990, 1 page. |
The PAN Network Rates & Fees, May 1992, 1 page. |
Dialogic Corporation, Invoice 6174, Aug. 2, 1988, 1 page. |
Newton, F. Roger, “Fax It!! Can we share the event facts by Fax?”, Facility Manager, Winter 1989-1990, p. 44. |
Dialogic Corporation, Invoice 6570, Sep. 12, 1988, 1 page. |
Weber Associates, The Pan Network Marketing Plan Proposal, Nov. 20, 2989, 3 pages. |
Dembicki, Dan, Cancellation Request to The PAN Networks, Jun. 1988, 1 page. |
The PAN Network, PAN Hard Copy, Winter 1990, vol. 7, No. 1, 2 pages. |
Dialogic Corporation, Invoice 6621, Sep. 19, 1988, 1 page. |
Dialogic Corporation, Letter to Pan Networks Accounts Payable, Jul. 13, 1987, 1 page. |
The PAN Network, PAN Hard Copy, Winter 1990, vol. 7, No. 1, 3 pages. |
Werner, Tom, “Just the fax, Ma'am, just the fax—but everywhere”, Philadelphia Business Journal, Oct. 30-Nov. 5, 1989, 1 page. |
Store-and-forward fax service debuts, Network World, Jul. 17, 1989, p. 27. |
American Arbitration Association, Leopold v. Delphi, Transcript Excerpts from Perry Leopold Deposition, Aug. 11, 1997, pp. 146-151. |
Hass, Nancy. “Hooding Up a Sound Idea Music Network Was Montco Singer's Brainchild.” Aug. 1989, 2 pages. |
New # for TSN & PEP Fax, Nov. 6, 1989, 1 page. |
Pan System/2 Command Card, 1988, 4 pages. |
The Advising Quarterly for Professionals in International Education, vol. 26, Fall 1993, pp. 1-40. |
Oaz Communications, NetFAX From Oaz, 1989, 9 pages. |
Fiore, Dave, Letter to Paradox Development Corporation re prepayment and work on NFUser, Jun. 6, 1991, 2 pages. |
Land, Kris, Letter to Dave Fiore at Oaz Communications, Jun. 7, 1991 sent via FedEx, 1 page. |
United States Bankruptcy Court, Northern District of California, In Re Oaz Communications, Inc., Case No. 91-40335T, Notice of Debtor's Application for Order Approving Employment and Compensation of Houlihan Lokey Howard & Zukin, Jun. 10, 1991, 1 page. |
Paradox Development Corporation, Business Plan, Aug. 5, 1990, 43 pages. |
“MHS Provides Key to WAN Communication”, PC Week, Jan. 8, 1990, pp. 66, 70-71. |
Novell, Inc., “NetWare MHS”, 1989, 2 pages. |
Oaz Communications, Inc., Fax Manager User's Guide, Feb. 1989, 48 pages. |
Communication to Larry West re preliminary specification of Xenix System V device, Apr. 21, 1989, 7 pages. |
Communication from Larry West re maximum number of bytes of DTMF codes, Apr. 21, 1989, 2 pages. |
Oaz Communications, Inc., “NetFax Manager”, 1990, 4 pages. |
Paradox Development Corp., “Para-Mail”, Nov. 1989, 1 page. |
Dun & Bradstreet, Inc., Payment Profile, Jun. 17, 1991, 6 pages. |
Steve, “Oaz Source Code Sale”, Contracts between Oaz and Paradox, Nov. 11, 1991, 1 page. |
United States Bankruptcy Court, Northern District of California, In Re Oaz Communications, Inc., Case No. 91-40335T, Hearing Notices, May 14-15, 1991, 2 pages. |
Paradox Development Corp., “Para-Mail Communications Software for Novell Netware Users”, Nov. 1990, 2 pages. |
Oaz Communications, Inc., NetFax Manager Administrators Users Guide, Jun. 1990, 148 pages. |
Fiore, Dave, Facsimile from Oaz Communications, Jun. 3, 1991, 2 pages. |
Burkitt, Nick and Paradox Development Corp., Proprietary Information and Inventions Agreement, Sep. 6, 1989, 6 pages. |
Paradox Development Corp., Work to Be Done, Jun. 5, 1991, 2 pages. |
Novelo, Tonatiuh, Memo re NFUser, Mar. 27, 1991, 2 pages. |
Fiore, Dave, Work to be done on NfUser Facsimile, May 28, 1991, 3 pages. |
ParaEDitor function Paraedit(), 1989, 2 pages. |
The Complete E-mail Program for Novell Networks with MHS. 1985. |
McKenna & Fitting, Claims of Paradox Development Corporation letter, Feb. 7, 1992, 3 pages. |
Paradox Development Corporation, Letter with Licensing and Professional Services Agreement of May 29, 1991, Jun. 7, 1991, 12 pages. |
United States Bankruptcy Court, Northern District of California, In Re Oaz Communications, Inc., Case No. 91-40335T, Notice of Dec. 18, 1991 Hearing, Nov. 26, 1991, 1 p. |
United States Bankruptcy Court, Northern District of California, In Re Oaz Communications, Inc., Case No. 91-40335T, Notice of Jan. 22, 1992 Hearing, Dec. 31, 1991, 1 page. |
Land, Kris, Interoffice Memo re Oaz Communications, Summary of signed agreements, verbal discussions and verbal commitments, Dec. 31, 1991, pp. 1-13. |
Notes on Oaz, Jun. 17-18, 1991, 2 pages. |
Land, Kris, Federal Express Tracking Label, May 21, 1991, 1 page. |
Paradox Development Corp., PM-Remote—Standalone Version of Para-Mail, Oct. 1990, pp. 1-4. |
United States Bankruptcy Court, Northern District of California, In Re Oaz Communications, Inc., Case No. 91-40335T, Notice of Rejection of Contract, Nov. 5, 1991, 2 pages. |
Giordano-Krausz, Eva, Letter re Oaz Communications Chapter 11, Nov. 6, 1991, 1 page. |
United States Bankruptcy Court, Northern District of California, In Re Oaz Communications, Inc., Case No. 91-40335T, Appointment and Notice of Appointment of Committee of Creditors Holding Unsecured Claims, Jun. 25, 1991, 2 pages. |
Land, Kris, Letter to Bankruptcy Court with attached Account Statement, May 10, 1991, 2 pages. |
Land, Kris, Federal Express Tracking Label, May 10, 1991, 1 page. |
Duncan, Thom, “Paramail Creates an E-mail Paradise”, LAN Times, Feb. 4, 1991, vol. 8, Issue 3, 2 pages. |
United States Bankruptcy Court, Northern District of California, In Re Oaz Communications, Inc., Case No. 91-40335T, Debtor's Proposed Disclosure Statement, Oct. 8, 1991, 31 pages. |
Paradox Development Corp., brief description of the program “imp.sub.--cont.exe”, Mar. 21, 1990, pp. 1-4. |
Oaz Communications, Inc., NetFax User Quick Reference Guide, Jun. 1990, 29 pages. |
United States Bankruptcy Court, Northern District of California, In Re Oaz Communications, Inc., Case No. 91-40335T, Proof of Claim, May 21, 1991, 1 page. |
PMenu system, 1989, pp. 1-2. |
United States Bankruptcy Court, Northern District of California, In Re Oaz Communications, Inc., Case No. 91-40335T, Notice of Status Conference, Jun. 6, 1991, 1 page. |
Paradox Development Corp., Para-Mail User's Manual, Version 2.10, Jun. 30, 1989, 180 pages. |
United States Bankruptcy Court, Northern District of California, In Re Oaz Communications, Inc., Case No. 91-40335T, Notice of Telephonic Hearing, Aug. 26, 1991, 1 page. |
Paradox Development Corp., Statement Invoice of Aug. 27, 1991, 1 page. |
United States Bankruptcy Court, Northern District of California, In Re Oaz Communications, Inc., Case No. 91-40335T, Notice of Continued Hearing on Disclosure Statement, Oct. 4, 1991, 1 page. |
United States Bankruptcy Court, Northern District of California, In Re Oaz Communications, Inc., Case No. 91-40335T, Notice of Hearing on Disclosure Statement on Oct. 9, 1991, 1 page. |
Binter, Joe, NotePad: Oaz Communications, Confidential Information, Jun. 1990-Feb. 1991, 1 page. |
Stein, Donald, Letter re Hearing and request by Paradox for Oaz Disclousre Statement, Oct. 22, 1991, 2 pages. |
Oaz Communications, Statement Invoice of Oct. 31, 1991, 1 page. |
McKenna & Fitting, Letter to Don Stein re Oaz Communications Bankruptcy, Nov. 1, 1991, 1 page. |
McKenna & Fitting, Letter to Don Stein re Oaz Communications Bankruptcy, Nov. 4, 1991, 2 pages. |
West, Larry, Price for libraries for Oaz, Jun. 13, 1991, 2 pages. |
United States Bankruptcy Court, Northern District of California, In Re Oaz Communications, Inc., Case No. 91-40335T Plan of Reorganization, Oct. 8, 1991, 13 pages. |
Kramer, Matt, et al., “Facsimile\Routing through Gateway Servers”, PC Week, Oct. 16, 1989, pp. 22, 28. |
Fiore, Dave, NotePad: Oaz Communications, Confidential Information, Jun. 1991-Jul. 1991, 1 page. |
oaz.l14, Jul. 10, 1991, Letter to Dave Fiore at Oaz re NFUser License Agreement, 2 pages. |
oaz.l13, Jul. 3, 1991, Letter to Dave Fiore at Oaz re NFUser License Agreement, 1 page. |
oaz-exh.a, Jun. 7, 1991, Exhibit A, Description of Program, 1 page. |
oaz.l12, Jun. 7, 1991, Letter re Licensing and Professional Service Agreement dated May 29, 1991, 1 page. |
oaz.l11, Jun. 3, 1991, Letter re nonpayment, 1 page. |
Phone Call Notes—Dave B. and Kris, Jul. 9, 1991, 6 pages. |
Handbook for the Palm V Organizer-3Com Corporation, Copyright 1998-1999, pp. 1-244. |
United States Patent and Trademark Office, Non-Final Office Action for U.S. Appl. No. 12/207,921, mailed Nov. 17, 2010, 50 pages. |
United States Patent and Trademark Office, Non-Final Office Action for U.S. Appl. No. 12/207,921, mailed Apr. 27, 2011, 11 pages. |
United States Patent and Trademark Office, Non-Final Office Action for U.S. Appl. No. 12/207,921, mailed Sep. 23, 2011, 10 pages. |
United States Patent and Trademark Office, Final Office Action, U.S. Appl. No. 12/207,921, mailed Jan. 30, 2012, 12 pages. |
United States Patent and Trademark Office, Non-Final Office Action for U.S. Appl. No. 10/795,655, mailed Apr. 20, 2007, 5 pages. |
United States Patent and Trademark Office, Non-Final Office Action for U.S. Appl. No. 10/795,655, mailed Aug. 23, 2007, 7 pages. |
United States Patent and Trademark Office, Non-Final Office Action for U.S. Appl. No. 10/795,655, mailed Feb. 6, 2008, 6 pages. |
United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 10/795,655, mailed Jun. 12, 2008, 8 pages. |
United States Patent and Trademark Office, Non-Final Office Action for U.S. Appl. No. 09/717,195, mailed Feb. 27, 2002, 31 pages. |
United States Patent and Trademark Office, Non-Final Office Action for U.S. Appl. No. 09/235,566, mailed Feb. 27, 2002, 21 pages. |
United States Patent and Trademark Office, Final Office Action for U.S. Appl. No. 09/235,566, mailed Sep. 24, 2002, 14 pages. |
United States Patent and Trademark Office, Non-Final Office Action for U.S. Appl. No. 09/235,566, mailed Nov. 14, 2002, 12 pages. |
United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 09/235,566, mailed Jul. 29, 2003, 10 pages. |
United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 09/235,566, mailed Oct. 28, 2003, 7 pages. |
United States Patent and Trademark Office, Non-Final Office Action for U.S. Appl. No. 09/717,193, mailed Feb. 27, 2002, 45 pages. |
United States Patent and Trademark Office, Final Office Action for U.S. Appl. No. 09/717,193, mailed Aug. 28, 2002, 44 pages. |
United States Patent and Trademark Office, Advisory Action for U.S. Appl. No. 09/717,193, mailed Dec. 30, 2002, 5 pages. |
United States Patent and Trademark Office, Non-Final Office Action for U.S. Appl. No. 09/717,193, mailed Apr. 8, 2003, 13 pages. |
United States Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 09/717,193, mailed Oct. 7, 2003, 11 pages. |
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 13/457,408, mailed Sep. 17, 2012, 28 pages. |
United States Patent and Trademark Office, Final Office Action, U.S. Appl. No. 13/457,408, mailed Feb. 1, 2013, 12 pages. |
United States Patent and Trademark Office, Notice of Allowance, U.S. Appl. No. 13/457,408, mailed Mar. 13, 2013, 11 pages. |
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 13/161,453, mailed Sep. 6, 2011, 6 pages. |
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 13/161,453, mailed Nov. 28, 2011, 9 pages. |
United States Patent and Trademark Office, Final Office Action for U.S. Appl. No. 13/161,453, mailed Apr. 9, 2012, 11 pages. |
United States Patent and Trademark Office, Non-Final Office Action for U.S. Appl. No. 13/161,453, mailed Aug. 1, 2012, 12 pages. |
United States Patent and Trademark Office, Notice of Allowance, U.S. Appl. No. 13/161,453, mailed Feb. 15, 2013, 14 pages. |
International Searching Authority, International Search Report, PCT Application PCT/IB97/001455, mailed Apr. 1, 1998, 4 pages. |
European Patent Office, Supplementary European Search Report, EP Application 97910596, mailed Nov. 7, 2000, 3 pages. |
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 08/839,655, mailed Aug. 20, 1998, 8 pages. |
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 08/839,655, mailed Dec. 10, 1998, 6 pages. |
United States Patent and Trademark Office, Notice of Allowance, U.S. Appl. No. 08/839,655, mailed Jun. 4, 1999, 5 pages. |
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 08/915,196, mailed Feb. 3, 1999, 9 pages. |
United States Patent and Trademark Office, Final Office Action, U.S. Appl. No. 08/915,196, mailed Jun. 22, 1999, 10 pages. |
United States Patent and Trademark Office, Notice of Allowance, U.S. Appl. No. 08/915,196, mailed Sep. 7, 1999, 6 pages. |
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 08/933,460, mailed Dec. 11, 1998, 7 pages. |
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 08/937,124, mailed Jan. 22, 1999, 9 pages. |
United States Patent and Trademark Office, Final Office Action, U.S. Appl. No. 08/937,124, mailed Jun. 22, 1999, 12 pages. |
United States Patent and Trademark Office, Notice of Allowance, U.S. Appl. No. 08/937,124, mailed Sep. 7, 1999, 6 pages. |
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 09/364,342, mailed May 19, 2000, 18 pages. |
United States Patent and Trademark Office, Final Office Action, U.S. Appl. No. 09/364,342, mailed Jan. 17, 2001, 13 pages. |
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 09/364,342, mailed Apr. 27, 2001, 8 pages. |
United States Patent and Trademark Office, Final Office Action, U.S. Appl. No. 09/364,342, mailed Sep. 25, 2001, 9 pages. |
Number | Date | Country | |
---|---|---|---|
20130301084 A1 | Nov 2013 | US |
Number | Date | Country | |
---|---|---|---|
60048064 | May 1997 | US | |
60028405 | Oct 1996 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13457408 | Apr 2012 | US |
Child | 13941403 | US | |
Parent | 12207921 | Sep 2008 | US |
Child | 13457408 | US | |
Parent | 10795655 | Mar 2004 | US |
Child | 12207921 | US | |
Parent | 09717193 | Nov 2000 | US |
Child | 10795655 | US | |
Parent | 09235566 | Jan 1999 | US |
Child | 09717193 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 08915196 | Aug 1997 | US |
Child | 09235566 | US | |
Parent | 08839655 | Apr 1997 | US |
Child | 08915196 | US | |
Parent | PCT/IB97/01455 | Oct 1997 | US |
Child | 08839655 | US |