1. Field of the Invention
This invention relates generally to telecommunications systems used in connection with facsimile (fax) transmissions. More particularly, it relates to additional capabilities and/or options for handling faxes.
2. Description of the Related Art
The electronic transmission of documents by way of fax systems continues to be commonplace and, often, an essential component of many business activities. With the emergence of electronic mail in the business environment, many predicted the demise of fax. This has not been the case.
However, there continue to be shortcomings among the fax systems currently in use in the business and consumer markets. In the business setting, fax machines may be busy or out of paper, preventing the receipt of incoming faxes. Furthermore, there generally is no real-time notification to a recipient that a fax has been sent to the recipient. That is, a fax recipient generally is not aware that a fax exists until it is hand delivered or picked up at the fax machine. If the recipient is expecting a fax, it is inconvenient for him to constantly check whether the fax has arrived if the fax machine is located far away from the recipient. Fax machines may also be shared by many users and, as a result, the sender of the fax often will feel obligated to take the additional step of drafting a cover page to identify the recipient of the fax. In some cases, faxed documents are of such a sensitive nature that the sender would like to have some control over who might see those documents as they move from the receiving fax machine to the actual recipient. In the consumer setting, individuals may not have access to a dedicated or shared fax machine and/or a dedicated fax line. This can make it difficult or impossible to receive faxes. These circumstances result in a number of practical problems for fax users.
In recent years, Fax-to-Email services such as that provided by CallWave, Inc. of Santa Barbara, Calif., have been introduced to address these problems for users with access to electronic mail systems. Typically, faxes are converted to email attachments and then sent to the recipient's email address. However, these services are only as reliable as the underlying email delivery system. Some email systems automatically reject messages with attachments, some email systems strip off attachments and some categorize fax-to-email messages as spam and discard the inbound message. In addition, if the email capacity of an individual's mailbox is full, the email system will reject the fax-to-email message. Furthermore, fax recipients typically do not receive a notification and/or fax until the entire fax has been delivered to the Fax-to-Email service and then sent through a private or public network (e.g., the Internet) to the recipient. Email delivery delays can occur when the Internet is used. Fax-to-Email services may provide the phone number from which the fax was sent in the header or body of the email message. However, in many cases, the recipient will not recognize this phone number because voice calls are not normally made from the same phone number. Furthermore, the phone number is provided with the fax attachment, rather than in advance, so that the recipient's ability to screen faxes is limited.
As a result, there is a need for fax systems that support real-time notification and/or reception of faxes by recipients, preferably by communications channels other than to fax machines or by email. There is also a need for fax systems with more sophisticated fax handling capabilities than are currently available.
In the present invention, a fax processing system overcomes some or all of the drawbacks discussed above. Faxes that are originally destined for a recipient's phone number are received by the fax processing system, which can provide more sophisticated fax handling capabilities. The fax processing system communicates with the fax recipient (aka, a subscriber) via a data communications network.
For example, in one implementation, the fax processing system interfaces to a PSTN on the one hand, and to the Internet on the other hand. Faxes sent to subscribers are received via the PSTN at the fax processing system. For example, fax calls may be forwarded from the subscriber's phone number to the fax processing system, or the subscriber's phone number may terminate in the fax processing system. Regardless, the fax processing system, in turn, transmits the fax and/or a fax notification to the subscriber via the Internet. Optionally, the subscriber can instruct the fax processing system to execute different fax handling instructions.
In one aspect of the invention, faxes are streamed to the subscriber, assuming s/he is online. Alternately, a fax notification rather than the entire fax can be streamed to the subscriber. Streaming allows notification or delivery of a fax in real-time or near real-time, which has advantages. For example, the resulting display may include information about the sender (e.g., as obtained from caller identification information) and allow the subscriber to take different actions with respect to the fax.
As a few examples of fax handling features, the subscriber may instruct the fax processing system to forward the fax, either to a different phone number(s) and/or to a different network address(es). Alternately, the subscriber can halt the fax receipt or the fax delivery, or block all future calls coming from the same phone number. Faxes can also be stored for future delivery, for example if the subscriber is not online when the fax is received. Different data rates can be used for delivery. In one approach, faxes are trickled down to the subscriber in the background so as not to fully consume the bandwidth of the subscriber's network connection. In another embodiment, the fax notification and/or fax could be broadcast to multiple locations.
Other aspects of the invention include other methods, devices and systems corresponding to the above.
The drawings summarized below, along with the detailed description that follows, are provided to illustrate the other advantages and features of the invention and the appended claims.
A sender's fax device 2 is connected to the public telephone network 4 and a subscriber's data device 10 is connected to the data communications network 6. A fax processing system 24 is connected to both networks 4,6. The connections can be made either directly or indirectly. For example, the sender's fax device 2 could be a fax machine plugged into a telephone jack or routed through a PBX. It could also be a computer with fax transmission software that is connected to the public telephone network 4 via a LAN and a gateway (between the LAN and the telephone network). On the subscriber side, examples of the subscriber's data device 10 include computers, PDAs, and devices that combine both voice and data (e.g., a Handspring Treo). The data device 10 can be connected to the data communications network 6 by any means, including for example by a dial-up connection, a broadband connection (e.g., DSL, cable, or direct fiber), a direct connection to the core of the data communications network 6, or wireless access. The connections can be either permanent or temporary. In addition, although the fax processing system 24 is shown in
The sender would like to send a fax to the subscriber. The terms sender and subscriber are used loosely and may include people, companies, and computers, for example. In a direct fax-to-fax transmission, the sender's fax device 2 would dial the phone number for the subscriber's fax device 12, and the fax would be routed through the public telephone network 4 to the subscriber's fax device 12, which would then print out or otherwise display the fax.
In
Use of the fax processing system 24 allows for more sophisticated fax handling options.
As part of its fax handling, the fax processing system 24 may also determine 54 whether the subscriber is connected to the data communications network 6 and, if connected, the network address being used by the subscriber. If the subscriber is connected, the fax processing system 24 can immediately or in real-time notify 56 the subscriber of the incoming fax call at the subscriber's network address. Upon receipt of the notification, the subscriber may send 60 additional instructions to the fax processing system 24. In this way, the subscriber will not have to wait for the fax processing system 24 to receive the entire fax. After notifying the subscriber, the fax processing system 24 can begin streaming the incoming fax to the subscriber for display as it is being received. The subscriber may send additional instructions 60 to the fax processing system 24 in response to either receipt of the fax or the notification. In an alternate embodiment, the fax processing system 24 may automatically transmit the fax to the subscriber without first sending a fax notification.
If the subscriber is not connected to the data communications network 6, the fax processing system 24 can store 62 the fax. When the subscriber later connects 54 to the data communications network 6, fax handling can proceed as before.
The use of a fax processing system 24 has many advantages over direct fax-to-fax transmission or over current fax-to-email systems. The fax processing system 24 can be used to implement more sophisticated call handling features, for example using rules based on the sender's phone number or time of day. If the fax processing system 24 is accessible by the subscriber (e.g., over the Internet), then it may be simple for the subscriber to change the rules whenever he likes. The fax processing system 24 also allows the subscriber to more easily change or use different phone numbers and network addresses. For example, the subscriber may use different phone numbers for different purposes (e.g., one for business faxes, one for personal faxes, one for faxes from creditors). Different rules may apply to the different phone numbers, but faxes from all phone numbers may be sent to the same network address so that the subscriber can view all faxes from a single network address. Alternatively, the subscriber can use multiple network addresses so that he can vie faxes from a number of different locations or data devices.
The streaming aspect, if implemented, allows subscribers to handle faxes in a more real-time fashion. For example, two colleagues may be working on a document and one wants to share a drawing with the other. He can fax the drawing to his coworker's phone number, and the drawing is streamed to the coworker's desktop. Compare this to a fax-to-email system where the entire fax must first be received, then packaged as an attachment to an email, and then sent to the coworker. Assuming that the email with attachment is not stripped by firewalls or other protections, the coworker must then wait for delivery (which often can be delayed), and then must open the email and then the attachment. Other advantages will be apparent.
Referring back to
A ten-digit North American telephone number (shown as 131) is assigned to the subscriber during the FL registration process. Calls to the FL phone number 131 route through the PSTN via InterExchange Carrier (IXC) switches and/or Local Exchange Carrier (LEC) switches to eventually terminate at the fax processing system 124. The fax machine 102 and the assigned FL phone number 131 can be connected to the same switch or different switches. If the fax machine 102 and FL number 131 are coupled to the same switch, the switch will be local to both the calling and called parties, as with intra-LATA or local calls. If the fax machine 102 and FL number 131 are coupled to different switches, each switch may be local only to one of the parties, as is the case for non-local calls such as inter-LATA (long-distance) calls.
In the example of
The FL trunk circuits 118 are not limited to a particular signaling convention. For example, the present invention can be utilized with a Common Channel Signaling (CCS) system, such as Signaling System 7 (SS7), that has separate voice/user data and signaling channels. In addition, the present invention can be used with other signaling methods, such as the following trunk-side signaling interfaces: ISDN-PRI, Advanced Intelligent Network (AIN), and/or Service Node architectures. Preferably, the selected signaling system provides a suite of call-presentation information to the fax processing system 124, including one or more of the following:
The telephone line 114 may be shared with one or more computer terminals. For example, telephone 112 shares the telephone line 114 with a computer terminal 110. In this example, the telephone line 114 is used to establish a dial-up connection for a computer terminal 110, via the computer modem, to an Internet Service Provider (ISP) offering dial-in remote-access service connections from the PSTN 104 via trunk interface circuits 120. The computer terminal 110 can also be connected to the Internet 106 via a broadband connection (such as a DSL or cable modem service, or a T1 line). While the subscriber's data device is shown as a computer terminal 110 in
In this implementation, a client application 116 for the fax processing system 124 resides and executes on the computer terminal 110. The client application 116 is connected to, and communicates with, the fax processing system 124 via the Internet 106.
The fax processing system 124 optionally hosts a web site used by subscribers of the FL service to set up and manage their accounts. Set-up and management functions can be implemented by the client application 116 as well.
The SM subsystem 122 monitors the Internet for online IP devices registered to subscribers to determine their availability for receiving faxes. When a subscriber connects to the Internet using a dial-up ISP, for example, the client application 116 makes the subscriber's online presence known to the fax processing system 124. Presence detection can be performed by the SM subsystem 122 polling or pinging the client application 116, or by the client application 116 transmitting a “Login/I'm alive” message and/or subsequent periodic “Keep alive” messages to the SM subsystem 122. This is just one example of presence management. Broader presence management techniques could be employed including IETF SIMPLE technology.
If, rather than using a dial-up connection, the subscriber is using a broadband, always-on connection, such as a DSL or cable modem service, the client application 116 typically becomes active when the computer terminal 110 is turned on or powered up, and it stays on until the subscriber manually shuts down the client application 116 or the computer 110 is turned off or powered down.
The sending party initiates a fax call using his fax machine 102 by dialing 401 the subscriber's FL number 131. The PSTN 104 routes 402 this call to the FM subsystem 108 in the fax processing system 124. The fax processing system 124 receives 403 the incoming call and based at least in part on the phone number called (obtainable by DNIS for example), the FM subsystem 108 queries the SM subsystem 122 and the DB subsystem 136 to determine whether the called number is registered to a subscriber, what the subscriber's fax handling preferences are, and whether the subscriber is online.
If the FL subscriber's computer terminal 110 is online, the FM subsystem 108 opens a communication channel over the Internet 106 to the client application 116 running on the subscriber's computer terminal 110. The fax processing system 124 transmits 404 a fax call notification to the subscriber's computer terminal 110.
If available, and if not designated as private, the Caller ID of the sending party is transmitted 404 to the client application 116 and displayed along with an optional sound notification. The Caller ID may come from different sources. For example, the sending fax device may provide caller identification information, or it may be provided during setup of the call by the telephone network. The information may also be automatically entered into the subscriber's address book. The sound notification can be in the form of ringing, which is produced through the called party's computer terminal 110 speakers. In addition, the FM subsystem 108 performs a Caller Name database lookup using the Caller ID of the calling party. The Caller Name, if available, is transmitted 404 to the client application 116 and displayed to the subscriber.
Around the same may be before or after), the fax processing system 124 answers 405 the incoming call and establishes 405 a full duplex, (two-way) talk path with the sending party. The fax processing system 124 negotiates 406 a fax transmission session with the fax machine 102 and begins to receive the fax. The FM subsystem 108 records and stores the caller's fax message in the MS subsystem 138 while simultaneously streaming 408 the fax through the opened Internet channel to the client application 116 on the subscriber's computer terminal 110. The client application 116 launches the computer terminal's 110 image-viewing software (for example, Adobe Acrobat) to display the streamed fax pages on the computer terminal's 110 monitor. The fax transmission 408 to the subscriber can begin regardless of whether the entire fax has been received 407 by the fax processing system 124.
When the sending fax machine 102 completes the fax transmission, it terminates 409 the call. The fax processing system 124 then releases trunk resources and signals 410 Call termination to the PSTN 104. The fax processing system 124 also signals 411 completion of the fax transmission to the subscriber by sending a corresponding control message which is displayed to the subscriber via the client application 116 as an entry in the call log (for example, 5 page fax 610).
Steps 401-411 illustrate one approach for streaming of a fax to a subscriber. Many variations will be apparent. For example, if the subscriber's connection to the Internet 106 is a narrow-band dial-up connection over a telephone line 114, a hybrid real-time solution can be used. Instead of transmitting the fax to the subscriber's computer terminal 110 at the maximum data rate possible, the FM subsystem 108 working in conjunction with the client application 116 begins to “trickle” download the fax from the MS subsystem 138 to the subscriber's computer terminal 110 over the open Internet communication channel 106. In one approach, the fax is divided into smaller files that are downloaded and reassembled by the client application 116 on the subscriber's computer terminal 110. In another, the fax is simply transmitted at a lower data rate than the maximum available, for example in order to reduce congestion across the subscriber's Internet connection. Whatever the implementation, trickle download helps ensure that bandwidth is available to the subscriber for other purposes. The trickle download can transition to a faster download, for example if the subscriber requests to view the fax immediately. The trickle download may also be interrupted if the Internet connection 114, 120, 142 is terminated. On the next Internet connection, the client application 116 can resume the trickle download where it left off. In some cases, downloads will be visible to the subscriber as an active call state, as shown for example in a pop-up window. Alternately, the subscriber can determine the data rate used to download the fax.
In another variation, a client/server protocol can be designed to operate through private and public firewalls. In this approach, the client application 116 opens a channel through the firewall by initiating “trusted” communication from inside the firewall to the fax processing system 124 outside the firewall. The client application 116 sends a “keep alive” packet through the firewall, over the Internet channel 106 to the SM subsystem 122. This “keep alive” message creates an open channel through the firewall along with a back channel from the SM subsystem 122 to the client application 116 to allow a reply with an acknowledgement message. When a new fax call is presented at the FM subsystem 108, the FM sends a call presented message to the SM subsystem 122, which relays the message to the client application 116 over this back channel. The call presented message includes the network address of the FM and can be used by the client application 116 to initiate streaming of the fax message by directly sending a new message to the FM subsystem 108 thereby opening an additional pair of communication paths. The FM subsystem 108 then acknowledges receipt of this message from the client and begins delivering the stream of fax content on the additional back channel.
In addition to receiving faxes or fax notifications, the subscriber may also be presented with different fax handling options.
If the subscriber ignores the notification pop-up menu, the fax processing system 124 will handle the fax according to the subscriber's default rules. For example, the subscriber may have selected for the fax to be automatically streamed to his computer terminal. Alternately, the subscriber may have selected for the fax to be stored until the subscriber affirmatively elects to retrieve the fax.
Alternately, the subscriber may choose to ignore the incoming fax. For example, the fax may not have been urgent enough to interrupt what the subscriber was doing, or the fax may have been intended for another member of the household. The subscriber can close the fax handling options dialog box shown in
As another option, the subscriber may choose not to accept calls from the sending party. Referring to
The options dialog box could pop an additional query to determine if the subscriber would like the fax processing system 124 to always apply this treatment to future calls from this sender phone number. This automatic fax handling rule can be stored in a table of subscriber preference settings for the fax processing system 124, for example in DB subsystem 136 as a simple extension table of the subscriber's address book. If directed to do so, the fax processing system 124 would automatically block future calls from this sender and relieve the subscriber from having to handle them.
As another variation, the subscriber can monitor the Caller ID and Caller Name of the incoming call and decide not to accept calls from this sender. The fax processing system 124 could be optionally configured to delay answering the incoming fax for a fixed time interval or for a specific number of ring cycles in order to allow the subscriber time to review the Caller ID and Caller Name. If the client application 116 instructs the fax processing system 124 to block the call before the incoming call has been answered, the fax processing system 124 will ignore the call (that is, let it ring) or reject it with an appropriate error tone and/or audible error message; e.g. a network reorder tone or special information tone along with a system error announcement (these methods can defeat fax spam systems). If the client application 116 instruction comes after the incoming call has been answered, the fax processing system 124 will handle the fax as described above.
Finally, the client application 116 provides the subscriber with additional utility including but not limited to: the ability from the menu option 690 to forward the fax as an attachment to an email address or fax to another fax number, delete the fax from the call log 660, launch a viewer 650 to display the fax on the computer or on a printer, scroll through a list of voice and fax calls 680, and undelete a previously deleted fax from the menu option 690.
As another variation of fax handling, the following process describes a scenario when the subscriber's computer terminal 110 is offline. When the fax call arrives on one of the FL trunks 118, along with the signaling information, the FM subsystem 108 queries the SM subsystem 122 and/or the DB subsystem 136 using the incoming call's DNIS (called number) to determine whether the call is for a registered subscriber, what the subscriber's online/offline presence status is, and to retrieve that subscriber's fax handling preference rules. If the fax processing system 124 determines that the subscriber is not connected (i.e., he is offline or otherwise unavailable), the fax processing system will carry out default rules for handling the call. These default rules may be the same for all subscribers or they may be individually determined by subscribers.
An example default rule is to answer the call and record the fax, for later notification and/or transmission when the subscriber comes online. Other fax handling rules could include the fax handling options described previously. For example, the CM subsystem 108 may optionally block the incoming fax based on the Caller ID. Regardless, when the subscriber subsequently connects to the Internet over a broadband or dial-up connection 114, 120, the client application 116 checks in with the SM subsystem 122. Client synchronization allows faxes not previously received by the client application 116 to be presented. In this implementation, new faxes delivered by synchronization are treated in the same fashion as new calls that were received directly by the client application 116 when the subscriber's computer terminal 110 was online. Furthermore, the process of trickle or burst downloading of faxes can begin as described above. As an additional option, a message-waiting indication can be activated or a Short Message Service (SMS) message or paging alert sent if any new faxes are placed into the call log. Message-waiting indication is active until the faxes have been viewed or the message-waiting light/con has been deactivated by the subscriber.
The detailed description contains many specifics. These should not be construed as limiting the scope of the invention but merely as illustrating different examples and aspects of the invention. It should be appreciated that the scope of the invention includes other embodiments not discussed in detail above. Various other modifications, changes and variations which will be apparent to those skilled in the art may be made in the arrangement, operation and details of the method and apparatus of the present invention disclosed herein without departing from the spirit and scope of the invention as defined in the appended claims. Therefore, the scope of the invention should be determined by the appended claims and their legal equivalents. Furthermore, no element, component or method step is intended to be dedicated to the public regardless of whether the element, component or method step is explicitly recited in the claims.
The present application is a continuation of Ser. No. 12/355,470, filed Jan. 11, 2009, entitled “Facsimile Telecommunications System and Method”, which is a continuation of U.S. patent application Ser. No. 10/795,025, filed Mar. 5, 2004 (now U.S. Pat. No. 7,480,065), the contents of which are incorporated herein in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
3936613 | Nishigori et al. | Feb 1976 | A |
3956595 | Sobanski | May 1976 | A |
4009337 | Sakai et al. | Feb 1977 | A |
4022983 | Braun et al. | May 1977 | A |
4485470 | Reali | Nov 1984 | A |
4736405 | Akiyama | Apr 1988 | A |
4809321 | Morganstein et al. | Feb 1989 | A |
4893336 | Wuthnow | Jan 1990 | A |
4994926 | Gordon et al. | Feb 1991 | A |
5040208 | Jolissaint | Aug 1991 | A |
5046087 | Sakai | Sep 1991 | A |
5291302 | Gordon et al. | Mar 1994 | A |
5404537 | Olnowich et al. | Apr 1995 | A |
5434908 | Klein | Jul 1995 | A |
5459584 | Gordon et al. | Oct 1995 | A |
5467388 | Redd, Jr. et al. | Nov 1995 | A |
5526524 | Madduri | Jun 1996 | A |
5533102 | Robinson et al. | Jul 1996 | A |
5577111 | Iida et al. | Nov 1996 | A |
5583918 | Nakagawa | Dec 1996 | A |
5619557 | Van Berkum et al. | Apr 1997 | A |
5640677 | Karlsson | Jun 1997 | A |
5644404 | Hashimoto et al. | Jul 1997 | A |
5651054 | Dunn et al. | Jul 1997 | A |
5668861 | Watts | Sep 1997 | A |
5751795 | Hassler et al. | May 1998 | A |
5761312 | Zelikovitz et al. | Jun 1998 | A |
5774067 | Olnowich et al. | Jun 1998 | A |
5805587 | Norris et al. | Sep 1998 | A |
5809128 | McMullin | Sep 1998 | A |
5812551 | Tsukazoe et al. | Sep 1998 | A |
5825867 | Epler et al. | Oct 1998 | A |
5832060 | Corlett et al. | Nov 1998 | A |
5835573 | Dee et al. | Nov 1998 | A |
5894504 | Alfred et al. | Apr 1999 | A |
5946106 | Itoh et al. | Aug 1999 | A |
5946386 | Rogers et al. | Aug 1999 | A |
5960064 | Foladare et al. | Sep 1999 | A |
5960073 | Kikinis et al. | Sep 1999 | A |
5963629 | Jung | Oct 1999 | A |
5995594 | Shaffer et al. | Nov 1999 | A |
5995603 | Anderson | Nov 1999 | A |
6014436 | Florence et al. | Jan 2000 | A |
6032051 | Hall et al. | Feb 2000 | A |
6034956 | Olnowich et al. | Mar 2000 | A |
6035031 | Silverman | Mar 2000 | A |
6043902 | Sato | Mar 2000 | A |
6044059 | Olnowich | Mar 2000 | A |
6078581 | Shtivelman et al. | Jun 2000 | A |
6104800 | Benson | Aug 2000 | A |
6144644 | Bajzath et al. | Nov 2000 | A |
6160881 | Beyda et al. | Dec 2000 | A |
6167127 | Smith et al. | Dec 2000 | A |
6169795 | Dunn et al. | Jan 2001 | B1 |
6169796 | Bauer et al. | Jan 2001 | B1 |
6178183 | Buskirk, Jr. | Jan 2001 | B1 |
6181691 | Markgraf et al. | Jan 2001 | B1 |
6208638 | Rieley et al. | Mar 2001 | B1 |
6212261 | Meubus et al. | Apr 2001 | B1 |
6230009 | Holmes et al. | May 2001 | B1 |
6243378 | Olnowich | Jun 2001 | B1 |
6253249 | Belzile | Jun 2001 | B1 |
6278704 | Creamer et al. | Aug 2001 | B1 |
6304565 | Ramamurthy | Oct 2001 | B1 |
6310939 | Varney | Oct 2001 | B1 |
6333973 | Smith et al. | Dec 2001 | B1 |
6350066 | Bobo, II | Feb 2002 | B1 |
6353660 | Burger et al. | Mar 2002 | B1 |
6353663 | Stevens et al. | Mar 2002 | B1 |
6363414 | Nicholls et al. | Mar 2002 | B1 |
6405035 | Singh | Jun 2002 | B1 |
6411601 | Shaffer et al. | Jun 2002 | B1 |
6411805 | Becker et al. | Jun 2002 | B1 |
6438216 | Aktas | Aug 2002 | B1 |
6438222 | Burg | Aug 2002 | B1 |
6477246 | Dolan et al. | Nov 2002 | B1 |
6483600 | Schuster et al. | Nov 2002 | B1 |
6496569 | Pelletier et al. | Dec 2002 | B2 |
6496576 | Tanaka et al. | Dec 2002 | B2 |
6501750 | Shaffer et al. | Dec 2002 | B1 |
6505163 | Zhang et al. | Jan 2003 | B1 |
6510162 | Fijolek et al. | Jan 2003 | B1 |
6510417 | Woods et al. | Jan 2003 | B1 |
6512930 | Sandegren | Jan 2003 | B2 |
6519258 | Tsukazoe et al. | Feb 2003 | B1 |
6539084 | Long | Mar 2003 | B1 |
6546087 | Shaffer et al. | Apr 2003 | B2 |
6549612 | Gifford et al. | Apr 2003 | B2 |
6553222 | Weiss | Apr 2003 | B1 |
6564264 | Creswell et al. | May 2003 | B1 |
6564321 | Bobo, II | May 2003 | B2 |
6567505 | Omori et al. | May 2003 | B1 |
6574319 | Latter et al. | Jun 2003 | B2 |
6594351 | Bhogal et al. | Jul 2003 | B1 |
6603837 | Kesanupalli et al. | Aug 2003 | B1 |
6621892 | Banister et al. | Sep 2003 | B1 |
6643034 | Gordon et al. | Nov 2003 | B1 |
6662232 | Nicholls et al. | Dec 2003 | B1 |
6690785 | Stelter et al. | Feb 2004 | B1 |
6711154 | O'Neal | Mar 2004 | B1 |
6751299 | Brown et al. | Jun 2004 | B1 |
6775370 | Burg | Aug 2004 | B2 |
6782088 | Gabara | Aug 2004 | B1 |
6785021 | Gordon et al. | Aug 2004 | B1 |
6785379 | Rogers et al. | Aug 2004 | B1 |
6792094 | Kirkpatrick | Sep 2004 | B1 |
6798870 | Lines et al. | Sep 2004 | B1 |
6801932 | Picoult et al. | Oct 2004 | B1 |
6853714 | Liljestrand et al. | Feb 2005 | B2 |
6857074 | Bobo, II | Feb 2005 | B2 |
6898275 | Dolan et al. | May 2005 | B2 |
6928479 | Meyer et al. | Aug 2005 | B1 |
6968174 | Trandal et al. | Nov 2005 | B1 |
7003087 | Spencer et al. | Feb 2006 | B2 |
7136475 | Rogers et al. | Nov 2006 | B1 |
7180638 | Hou et al. | Feb 2007 | B1 |
7230745 | Street, Jr. | Jun 2007 | B1 |
7245611 | Narasimhan et al. | Jul 2007 | B2 |
7283270 | Boire-Lavigne et al. | Oct 2007 | B2 |
7474432 | Kirchhoff et al. | Jan 2009 | B1 |
7480065 | Trandal et al. | Jan 2009 | B1 |
7492473 | Ferlitsch et al. | Feb 2009 | B2 |
7742184 | Seki et al. | Jun 2010 | B2 |
7869076 | Trandal et al. | Jan 2011 | B1 |
20020010616 | Itzhaki | Jan 2002 | A1 |
20020041391 | Bannai | Apr 2002 | A1 |
20020093674 | Ferlitsch et al. | Jul 2002 | A1 |
20020097710 | Burg | Jul 2002 | A1 |
20020126321 | Trachtman | Sep 2002 | A1 |
20020131561 | Gifford et al. | Sep 2002 | A1 |
20030039339 | Luehrig et al. | Feb 2003 | A1 |
20030048484 | Seki et al. | Mar 2003 | A1 |
20030071117 | Meade, II | Apr 2003 | A1 |
20030072432 | Kelly | Apr 2003 | A1 |
20030095541 | Chang et al. | May 2003 | A1 |
20030123622 | Gifford et al. | Jul 2003 | A1 |
20030156700 | Brown et al. | Aug 2003 | A1 |
20030215078 | Brahm et al. | Nov 2003 | A1 |
20040001221 | McCallum | Jan 2004 | A1 |
20040028203 | Wurster et al. | Feb 2004 | A1 |
20040051912 | Schlank et al. | Mar 2004 | A1 |
20040125924 | McMullin et al. | Jul 2004 | A1 |
20040146153 | Solin | Jul 2004 | A1 |
20040184096 | Choi | Sep 2004 | A1 |
20040190706 | Fleischer, III et al. | Sep 2004 | A1 |
20040205169 | Machida | Oct 2004 | A1 |
20040252349 | Green et al. | Dec 2004 | A1 |
20040258220 | Levine et al. | Dec 2004 | A1 |
20050041643 | Noguchi et al. | Feb 2005 | A1 |
20050053216 | Spencer et al. | Mar 2005 | A1 |
20050123118 | Terry et al. | Jun 2005 | A1 |
20050153739 | Halsell | Jul 2005 | A1 |
20050154599 | Kopra et al. | Jul 2005 | A1 |
20050190404 | Nakamura | Sep 2005 | A1 |
20050207556 | Gonzalez et al. | Sep 2005 | A1 |
20050275871 | Baird et al. | Dec 2005 | A1 |
20050275878 | Hiatt et al. | Dec 2005 | A1 |
20060013374 | Fleischer et al. | Jan 2006 | A1 |
20060099971 | Staton et al. | May 2006 | A1 |
20060209342 | Ferlitsch et al. | Sep 2006 | A1 |
20060268007 | Gopalakrishnan | Nov 2006 | A1 |
20060268831 | Ulybin | Nov 2006 | A1 |
20060290974 | Kano et al. | Dec 2006 | A1 |
20070002077 | Gopalakrishnan | Jan 2007 | A1 |
20070013960 | Gordon et al. | Jan 2007 | A9 |
20070067738 | Flynt et al. | Mar 2007 | A1 |
20070116213 | Gruchala et al. | May 2007 | A1 |
20070202898 | Bae et al. | Aug 2007 | A1 |
20070223053 | Jin | Sep 2007 | A1 |
20070223056 | Arimoto | Sep 2007 | A1 |
20070229910 | Ulybin | Oct 2007 | A1 |
20080075250 | Kent et al. | Mar 2008 | A1 |
20080184270 | Cole et al. | Jul 2008 | A1 |
20100159900 | Seki et al. | Jun 2010 | A1 |
20100177879 | Liljestrand et al. | Jul 2010 | A1 |
20100214609 | Ratnam et al. | Aug 2010 | A1 |
20100296121 | Shaheen, III et al. | Nov 2010 | A1 |
Number | Date | Country |
---|---|---|
1329852 | Sep 1989 | CA |
1120954 | Aug 2001 | EP |
10513632 | Dec 1998 | JP |
11506292 | Jun 1999 | JP |
2001168989 | Jun 2001 | JP |
WO-0060840 | Oct 2000 | WO |
WO-0176210 | Oct 2001 | WO |
Number | Date | Country | |
---|---|---|---|
20110096369 A1 | Apr 2011 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12355470 | Jan 2009 | US |
Child | 12985958 | US | |
Parent | 10795025 | Mar 2004 | US |
Child | 12355470 | US |