Real-time balance on a mobile phone

Abstract
A system, method and prepaid payment mobile phone configured to display a current prepaid balance. The prepaid payment mobile phone receives a debit balance request from input on the mobile phone. After retrieving an encoded current balance, the mobile phone displays the amount. The current balance may be calculated by the phone after a transaction, or the phone may receive a debit balance via a short message service notification.
Description
BACKGROUND

1. Field of the Invention


Aspects of the present invention relate in general to financial services. Aspects include a prepaid payment mobile phone apparatus, system, method and computer-readable medium configured to display a real-time prepaid payment balance. Further aspects of the invention include a method of storing and displaying a real-time prepaid payment balance on a mobile phone.


2. Description of the Related Art


The traditional paper “gift-certificate” is gradually being replaced by prepaid payment mobile phones—debit-account mobile phones with a set limited value associated with a Primary Account Number (PAN). Some mobile phone debit accounts are affiliated with a particular vendor, such as a department store, supermarket or restaurant; yet other mobile phone debit accounts are affiliated with an acquirer, payment processor, or other issuer.


When a mobile phone customer makes a purchase, the prepaid payment mobile phone may be used to pay for the transaction. If the purchase amount equals or exceeds the value of the prepaid payment mobile phone, the customer simply pays the excess amount using cash, credit card, debit card, or other financial instrument accepted by the vendor. However, when the purchase amount is less than the value of the prepaid payment mobile phone account, the purchase price is simply subtracted from the prepaid payment mobile phone account balance, and a new balance remains associated with the mobile phone.


Mobile phone customers who carry prepaid payment mobile phones are often unaware of the debit balance of a prepaid payment mobile phone, especially on non-reloadable mobile phone products. While some issuer and acquirers mandate support for balance inquiries for some gift mobile phones and incentive mobile phones, such support is optional at merchants.


When issuers fail to support these enhancements, or when merchants do not support them, mobile phone customers are restricted to spending the amount that is available on the mobile phone within one transaction often without knowing the balance in advance.


When issuers, acquirers, and processors do not support these enhancements at the point-of-sale, the consumer is inconvenienced, and the process breaks down. Consumer frustration is common, resulting in higher amounts of breakage (resulting in unrecognized sales volume), and alternate forms of payment being used. Worse, consumers are discouraged from purchasing more prepaid payment mobile phones.


In the re-loadable prepaid mobile phone category, the only way a consumer can determine their balance on a mobile phone is by calling their mobile phone issuer/third party agent or looking up the information online.


SUMMARY

Embodiments of the invention include a system, method and prepaid payment mobile phone configured to display a current debit balance. A remarkable aspect of the invention is that a prepaid balance retrieved from an issuer and stored at the prepaid payment mobile phone, as generally no such information is ever stored on such phones. The prepaid payment mobile phone receives a balance request from a button on the mobile phone. After retrieving the current balance encoded within, the mobile phone displays the current balance. The balance may be calculated after a payment transaction or received as a message from an acquirer, payment network, or issuer.





BRIEF DESCRIPTION OF THE DRAWINGS


FIGS. 1A-B illustrate an embodiment of a prepaid payment mobile phone configured to display the current balance.



FIG. 2 is a block diagram of a system embodiment to support the display of a current debit balance on a prepaid payment mobile phone.



FIG. 3 is an expanded view of a merchant's system embodiment to support the display of the current debit balance on a prepaid payment mobile phone.



FIG. 4 is a flow chart of a mobile phone process embodiment configured to calculate and store balance information after a payment transaction.



FIG. 5 illustrates a process embodiment sends a prepaid payment mobile phone balance information after a payment transaction.



FIG. 6 is a flow chart of a mobile phone-writer process embodiment that stores balance information.



FIG. 7 illustrates a process embodiment to display the current debit balance of a prepaid payment mobile phone.





DETAILED DESCRIPTION

One aspect of the present invention includes the realization that displaying a real-time balance on a prepaid payment mobile phone reduces the cost of issuers supporting balance inquiry and balance returns from mobile phone customers. With the balance on a mobile phone display solution, mobile phone customers would be able to check their balance at any time, generating a higher volume of unplanned purchases, and potentially a higher amount of re-loads at the point of sale.


Embodiments of the present invention include a mobile phone apparatus, system, method, and computer-readable medium configured to support the real-time display of a debit balance on a prepaid payment mobile phone. Other embodiments of the present invention may include remote terminals configured to support the real-time display of a debit balance on a prepaid payment mobile phone.


Turning to FIGS. 1A-B, these figures depict a prepayment mobile phone 1000 configured to display of a balance on a real-time balance, constructed and operative in accordance with an embodiment of the present invention. In this example, prepayment mobile phone 1000 is depicted as a two-piece “flip” phone, but it is understood that the principles herein may be applied to any style mobile phone capable of electronic payment.


As shown in FIG. 1A, the payment mobile phone 1000 includes a housing 1002, a display 1004, and an input 1006. It is understood that housing 1002 may comprise one or more components. Some embodiments of housing 1002 may be plastic or any other suitable material known in the art.


Display 1004 may be a liquid crystal display (LCD), light-emitting-diode (LED), organic light-emitting-diode (OLED), surface-conduction electron-emitter display (SED), digital light processing (DLP), interferometric modulator display (IMOD) or any other display known in the art that can be used within the form factor required by the payment mobile phone 1000.


Input 1006 may be any sensor or input device known in the art, including, but not limited to buttons 1006a, trackballs 1006b, scroll-wheels 1006c, touch-pads or the like. In some embodiments, input 1006 and display 1004 may be merged as a touch-screen input device.


Internal components of payment mobile phone 1000 are shown in FIG. 1B. Contained within housing 1002, a processor or central processing unit 1008 is electrically coupled to the display 1004, input 1006, Read-Only-Memory (ROM) 1010, Random Access Memory (RAM) 1012, a non-volatile programmable memory 1014, input/output circuitry 1016, an input/output port 1018, power supply 1020, cellular transceiver 1022, and radio-frequency transceiver 1024. It is understood by those familiar with the art that some or all of these elements may be embedded together in some combination as an integrated circuit (IC).


Processor 1008 may be any central processing unit, microprocessor, micro-controller, computational device or circuit known in the art.


Read only memory 1010 is embedded with an operating system.


Non-volatile programmable memory 1014 is configured to be an application memory device, and may store information such as the primary account number and/or current debit balance information. Examples of non-volatile programmable memory 1014 include, but not limited to: a magnetic stripe, flash memory, Electrically Erasable Programmable Read-Only Memory (EEPROM), or any other non-volatile computer memory or storage known in the art.


Random access memory 1012 is any temporary memory storage medium element known in the art. Random access memory is usually (but does not have to be) volatile memory.


The processor 1008, the read only memory 1010, the random access memory 1012 and the non-volatile programmable memory 1014 may coupled to one another through an internal bus system. Data can be interchanged between the input/output unit 1016, the processor 1008 and the non-volatile programmable memory 1014. Furthermore, data can be interchanged between the processor 1008 and the non-volatile programmable memory 1014.


Additionally, in some embodiments, the input/output circuitry 1016 is further coupled to an input/output port 1018 being formed in a surface area of the plastic housing 1002. Input/output port 1018 may be any data communications port known in the art, including, but not limited to: a serial port, a parallel port, a Universal Serial Bus (USB) interface, an the Institute of Electrical and Electronics Engineers (IEEE) 1394 (“firewire”) interface, or any port known in the art.


Cellular transceiver 1022 may be any cellular, personal communications system (PCS), Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Enhanced Data for GSM Evolution (EDGE), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency-Division Multiplexing (ODFM), or any other wireless communications protocol known in the art able to support voice communications.


Radio frequency transceiver 1024 may use any wireless data protocol known in the art, such as: Bluetooth, Wireless Application Protocol (WAP), IEEE 802.11 (“WiFi”), IEEE 802.16 (“WiMax”), or any other wireless data communications standard known in the art.


Power supply 1020 may be any electrical power supply, including a battery, fuel cell, long-term capacitor or any other power storage known in the art. Power supply 1020 may be recharged by applying a direct current voltage.



FIG. 2 illustrates a system to support the display of a real-time prepaid payment balance on a mobile phone, constructed and operative in accordance with an embodiment of the present invention. A customer 2100 receives a prepaid payment mobile phone 1000. In some instances the mobile phone 1000 is purchased from an issuer 2500; in other instances the customer receives the mobile phone 1000 indirectly from the issuer 2500, as a gift or as the result of a promotion. When the customer 2100 uses the prepaid payment mobile phone 1000 at a merchant 2200 to pay for a product or service, the merchant 2200 contacts an acquirer 2300 (for example, a commercial bank) to determine whether there is sufficient funds on the mobile phone to pay for the transaction or a portion of the transaction. The acquirer 2300 forwards the details of the payment transaction to a payment processor 2400 for processing. Payment processor may be any payment network known in the art. An example of a payment network includes, but is not limited to: Visa™, MasterCard™, American Express™, Club™, or Discover™. In some instances, the payment processor 2400 determines whether the transaction should be allowed; in other instances, the payment processor 2400 queries the 2500 to determine whether the prepayment mobile phone has enough funds to allow the transaction.



FIG. 3 depicts merchant 2200 in greater detail, where merchant 2200 includes a system to support the display of a real-time prepaid payment balance on a mobile phone, constructed and operative in accordance with an embodiment of the present invention. As shown, in FIG. 3, merchant 2200 comprises a mobile phone point-of-sale read/writer 2210 that communicated with a merchant central computer 2230 via the merchant's private network 2220. In some embodiments, merchant central computer 2230 may be coupled to hot list storage 2240.


Mobile phone point-of-sale read/writer 2210 is any device capable of reading a personal account number off a prepaid payment mobile phone 1000, and write balance information to the prepaid payment mobile phone 1000.


Merchant central computer 2230 is a networked device capable of communicating transaction data with mobile phone point-of-sale read/writer 2210 and transmitting the transaction data over network 3100 to acquirer 2300.


Hot list storage 2240 may be any list, database, or memory structure containing either invalid or valid primary account numbers.


Operation of these prepayment mobile phone and system embodiments of the present invention may be illustrated by example.


We now turn our attention to method or process embodiments. It is understood by those known in the art that instructions for such method embodiments may be stored on a non-volatile programmable memory 1014 and executed by a processor 1008.



FIG. 7 illustrates a process embodiment to display the current debit balance of a prepaid payment mobile phone 1000, constructed and operative in accordance with an embodiment of the present invention. When a user wants to know the balance of prepaid payment mobile phone 1000, the user requests the balance through pressing button 1006. The mobile phone receives the balance request, block 7002.


In mobile phone 1000 embodiments that utilize a personal identification number (PIN), display 1004 prompts the user for the PIN number, block 7004. The personal identification number may be stored in non-volatile programmable memory 1014. At this point, the user may enter a PIN number using buttons 1006a.


In some embodiments, an error message is displayed when an invalid PIN number is entered, block 7010, and flow returns to block 7004.


Upon receipt of a valid PIN number as determined at decision block 7006, the display shows the remaining prepaid balance, block 7008.


Turning to FIG. 4, a flow chart depicts a mobile phone-writer process embodiment configured to calculate and store balance information on a prepaid payment mobile phone after a payment transaction, constructed and operative in accordance with an embodiment of the present invention.


When a prepaid payment mobile phone 1000 is presented for payment at a merchant 2200, the primary account number and other data may be read at a mobile phone point-of-sale read/writer 2210, block 4002. The mobile phone 1000 may be presented in a variety of different methods, such as transmitting personal account data or via a contactless (“paywave”) radio-frequency presentation, as are known in the art.


The transaction amount is subtracted from the pre-paid balance on the phone, block 4004, and the new remaining balance is stored at block 4006.



FIG. 5 illustrates a process embodiment in which the acquirer 2300, payment processor 2400 or issuer 2500 sends the prepaid payment phone 1000 a Short Message Service (SMS) notification containing updated balance information, constructed and operative in accordance with an embodiment of the present invention. In some embodiments the balance information is subsequently stored on the prepaid payment mobile phone. As part of the payment transaction, primary account number and other information is read by merchant 2200, block 5002. Prepaid payment mobile phone 1000 is received from a mobile phone point-of-sale read/writer 2210, via the RF transceiver 1024, block 5002.


A payment card validation, as is known in the art, is performed using the data retrieved from the prepaid payment phone 1000. In some embodiments, merchant central computer 2230 consults with hot list storage 2240 to determine whether the transaction may be validated. In other embodiments, merchant central computer 2230 contacts acquirer 2300 to determine whether the transaction is valid. If the transaction is invalid as determined at decision block 5004, an error message is returned at block 5006. When the transaction is valid, flow continues at block 5008.


At block 5008, the payment transaction occurs.


Either after the payment transaction is completed, or during the transaction, acquirer 2300, payment processor 2400 or issuer 2500 sends the prepaid payment, phone 1000 an SMS notification containing updated balance information, block 5010. The SMS notification may be saved to the phone as either an SMS notification, or as data for the phone's payment program.



FIG. 6 depicts a flow chart of a mobile phone-writer process 6000 embodiment that stores new balance information on a prepaid payment mobile phone 1000 after a transaction or fund reload, constructed and operative in accordance with an embodiment of the present invention. FIG. 6 assumes that the mobile phone reload is occurring at merchant 2200 in communication with issuer 2500; it is understood that the reload mobile phone may also occur at other locations. It is also understood that process 6000 may also be used during the activation of pre-payment mobile phones 1000 when such mobile phones are initially purchased.


At first, prepaid payment mobile phone 1000 provides its transaction data to a mobile phone point-of-sale read/writer 2210, block 6002. Such transaction data may include the primary account number or other identifier. The new balance of the prepaid mobile phone is sent to the mobile phone 1000, block 6004. The amount of the new balance may be received as data from payment processor 2400, issuer 3400 or calculated by the merchant 2200 using information received from issuer 2500 or payment processor 2400. In mobile phone embodiments that use RF ID, the receipt of the new balance may be accomplished via the RF transceiver 1024. In other embodiments, the new balance may be received as a SMS notification, or any other data transmission known in the art. The new balance is written to non-volatile programmable storage media 1014, block 6006, and process 6000 ends.


The previous description of the embodiments is provided to enable any person skilled in the art to practice the invention. The various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without the use of inventive faculty. Thus, the present invention is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims
  • 1. A prepaid payment mobile phone comprising: a processor;a non-volatile programmable memory coupled to the processor and configured to store a current balance associated with a primary account number;an input device coupled to the processor and configured to receive a request for the current balance of the prepaid payment mobile phone;a display coupled to the processor and configured to show the current balance;a radio frequency (RF) transceiver coupled to the processor and configured to transmit transaction data associated with a transaction comprising the primary account number to a point of sale device, wherein the primary account number is stored on the non-volatile programmable memory; anda cellular transceiver coupled to the processor and configured to receive information regarding the current balance after the transaction, wherein the information regarding the current balance is received via a Short Message Service (SMS) message and the current balance is encoded onto the non-volatile programmable memory using the processor.
  • 2. The prepaid payment mobile phone of claim 1, wherein the SMS message is received from an issuer or a payment processor.
  • 3. The prepaid payment mobile phone of claim 2, wherein the SMS message comprises a transaction amount representing an amount of a last transaction completed using the prepaid payment mobile phone;wherein the last transaction amount is subtracted from a previous balance using the processor; andwherein the result of the subtraction comprises the current balance.
  • 4. The prepaid payment mobile phone of claim 1, wherein the transaction is a reload transaction initiated at the point of sale device and the prepaid payment mobile phone is loaded with additional funds.
  • 5. The prepaid payment mobile phone of claim 1, wherein the display is further configured to prompt for input of a personal identification number (PIN).
  • 6. The prepaid payment mobile phone of claim 5, wherein the processor is configured to determine whether the PIN is valid and display the current balance if the PIN is determined to be valid.
  • 7. The prepaid payment mobile phone of claim 6, wherein the PIN is stored in the non-volatile programmable memory on the prepaid payment mobile phone.
  • 8. The prepaid payment mobile phone of claim 1, wherein the current balance is a debit balance of the prepaid payment mobile phone, indicating an amount of currency remaining on the prepaid payment mobile phone.
  • 9. The prepaid payment mobile phone of claim 1, wherein the SMS message is sent in response to initiating a transaction at the point of sale device.
  • 10. The prepaid payment mobile phone of claim 9, wherein the SMS message is received from an issuer or a payment processor.
  • 11. A method of encoding a current balance on a prepaid payment mobile phone comprising: storing a primary account number on a non-volatile programmable memory;transmitting, with a radio frequency (RF) transceiver, transaction data associated with a transaction to a point of sale device, the transaction data comprising the primary account number;receiving, with a cellular transceiver, information regarding a current balance of an account associated with the primary account number, wherein the receiving of information regarding the current balance comprises receiving a Short Message Service (SMS) message;encoding, with a processor, the current balance in the non-volatile programmable memory on the prepaid payment mobile phone.
  • 12. The method of claim 11, wherein the receiving of information regarding the current balance comprises receiving the SMS message comprising the current balance as calculated by an issuer, an acquirer, a merchant, or a payment network.
  • 13. The method of claim 11, wherein the SMS message is saved to the prepaid payment mobile phone as a SMS notification or as data for a payment program.
  • 14. The method of claim 11, wherein the SMS message comprises a transaction amount and the current balance is determined, using the processor, by subtracting the transaction amount from a previous balance.
  • 15. The method of claim 11, wherein the SMS message is received from an issuer or a payment processor.
  • 16. The method of claim 11, wherein the SMS message is sent in response to initiating a payment transaction or a reload transaction request at the point of sale device.
  • 17. The method of claim 11, further comprising displaying a current balance of the prepaid payment mobile phone, wherein in response to receipt of a balance request from an input device on the prepaid payment mobile phone, the current balance is retrieved from the non-volatile memory within the prepaid payment mobile phone and the current balance is displayed on a screen.
  • 18. The method of claim 11, further comprising prompting for input of a personal identification number (PIN), determining whether the PIN is valid, and displaying the current balance of the prepaid payment mobile phone if the PIN is determined to be valid.
  • 19. The method of claim 11 wherein, when a customer uses the prepaid payment mobile phone in a transaction at a merchant, the merchant sends a message to a payment processing network to determine whether there are sufficient funds on the prepaid payment mobile phone to pay for the transaction or a portion of the transaction.
  • 20. The method of claim 11 wherein, the balance is calculated after the SMS is received from the issuer, the acquirer, the merchant, or the payment network, using the information regarding the current balance.
  • 21. The method of claim 11, wherein the payment processing network analyzes whether there are sufficient funds on the prepaid payment mobile phone to pay for the transaction or a portion of the transaction after determining whether the primary account number is valid by using a hot list storage database containing valid and invalid primary account numbers.
US Referenced Citations (309)
Number Name Date Kind
4044231 Beck et al. Aug 1977 A
4613904 Lurie Sep 1986 A
4614861 Pavlov et al. Sep 1986 A
4674041 Lemon et al. Jun 1987 A
4701601 Francini et al. Oct 1987 A
4868376 Lessin et al. Sep 1989 A
5034597 Atsumi et al. Jul 1991 A
5305196 Deaton et al. Apr 1994 A
5327508 Deaton et al. Jul 1994 A
5353218 DeLapa et al. Oct 1994 A
5359183 Skodlar Oct 1994 A
5388165 Deaton et al. Feb 1995 A
RE34915 Nichtberger et al. Apr 1995 E
5420606 Begum et al. May 1995 A
5430644 Deaton et al. Jul 1995 A
5448471 Deaton et al. Sep 1995 A
5465206 Hilt et al. Nov 1995 A
5477038 Levine et al. Dec 1995 A
5483444 Heintzeman et al. Jan 1996 A
5500513 Langhans et al. Mar 1996 A
5502636 Clarke Mar 1996 A
5530438 Bickham et al. Jun 1996 A
5564073 Takahisa Oct 1996 A
5577266 Takahisa et al. Nov 1996 A
5579537 Takahisa Nov 1996 A
5592560 Deaton et al. Jan 1997 A
5604921 Alanara Feb 1997 A
5615110 Wong Mar 1997 A
5621201 Langhans et al. Apr 1997 A
5621812 Deaton et al. Apr 1997 A
5627549 Park May 1997 A
5638457 Deaton et al. Jun 1997 A
5642485 Deaton et al. Jun 1997 A
5644723 Deaton et al. Jul 1997 A
5649114 Deaton et al. Jul 1997 A
5659165 Jennings et al. Aug 1997 A
5659469 Deaton et al. Aug 1997 A
5675662 Deaton et al. Oct 1997 A
5678939 Ross Oct 1997 A
5687322 Deaton et al. Nov 1997 A
5708422 Blonder et al. Jan 1998 A
5710886 Christensen et al. Jan 1998 A
5717866 Naftzger Feb 1998 A
5761648 Golden et al. Jun 1998 A
5777903 Piosenka et al. Jul 1998 A
5791991 Small Aug 1998 A
5793972 Shane Aug 1998 A
5806044 Powell Sep 1998 A
5822735 De Lapa et al. Oct 1998 A
5855007 Jovicic et al. Dec 1998 A
5870030 DeLuca et al. Feb 1999 A
5884277 Khosla Mar 1999 A
5905246 Fajkowski May 1999 A
5907830 Engel et al. May 1999 A
5924080 Johnson Jul 1999 A
5959577 Fan et al. Sep 1999 A
5974399 Giuliani et al. Oct 1999 A
5991749 Morrill, Jr. Nov 1999 A
6002771 Nielsen Dec 1999 A
6009411 Kepecs Dec 1999 A
6009415 Shurling et al. Dec 1999 A
6012038 Powell Jan 2000 A
6014634 Scroggie et al. Jan 2000 A
6018718 Walker et al. Jan 2000 A
6029151 Nikander Feb 2000 A
6035280 Christensen Mar 2000 A
6041309 Laor Mar 2000 A
6049778 Walker et al. Apr 2000 A
6055505 Elston Apr 2000 A
6062991 Moriarty et al. May 2000 A
6064990 Goldsmith May 2000 A
6067526 Powell May 2000 A
6067529 Ray et al. May 2000 A
6076068 DeLapa et al. Jun 2000 A
6076069 Laor Jun 2000 A
6076101 Kamakura et al. Jun 2000 A
6128599 Walker et al. Oct 2000 A
6185290 Shaffer et al. Feb 2001 B1
6185541 Scroggie et al. Feb 2001 B1
6227447 Campisano May 2001 B1
6237145 Narasimhan et al. May 2001 B1
6247129 Keathley et al. Jun 2001 B1
6267292 Walker et al. Jul 2001 B1
6279112 O'Toole, Jr. et al. Aug 2001 B1
6292786 Deaton et al. Sep 2001 B1
6307958 Deaton et al. Oct 2001 B1
6318631 Halperin Nov 2001 B1
6321208 Barnett et al. Nov 2001 B1
6330543 Kepecs Dec 2001 B1
6330550 Brisebois et al. Dec 2001 B1
6334108 Deaton et al. Dec 2001 B1
6336098 Fortenberry et al. Jan 2002 B1
6336099 Barnett et al. Jan 2002 B1
6341724 Campisano Jan 2002 B2
6351735 Deaton et al. Feb 2002 B1
6377935 Deaton et al. Apr 2002 B1
6378775 Hayashida Apr 2002 B2
6381324 Shaffer et al. Apr 2002 B1
6424949 Deaton et al. Jul 2002 B1
6424951 Shurling et al. Jul 2002 B1
6434534 Walker et al. Aug 2002 B1
6470181 Maxwell Oct 2002 B1
6484146 Day et al. Nov 2002 B2
6488203 Stoutenburg et al. Dec 2002 B1
6505046 Baker Jan 2003 B1
6516302 Deaton et al. Feb 2003 B1
6529725 Joao et al. Mar 2003 B1
6535855 Cahill et al. Mar 2003 B1
6560581 Fox et al. May 2003 B1
6584309 Whigham Jun 2003 B1
6587835 Treyz et al. Jul 2003 B1
6601759 Fife et al. Aug 2003 B2
6609104 Deaton et al. Aug 2003 B1
6611811 Deaton et al. Aug 2003 B1
6631849 Blossom Oct 2003 B2
6647257 Owensby Nov 2003 B2
6647269 Hendrey et al. Nov 2003 B2
6664948 Crane et al. Dec 2003 B2
6684195 Deaton et al. Jan 2004 B1
6685093 Challa et al. Feb 2004 B2
6736322 Gobburu et al. May 2004 B2
6747547 Benson Jun 2004 B2
6775539 Deshpande Aug 2004 B2
6832721 Fujii Dec 2004 B2
6837425 Gauthier et al. Jan 2005 B2
6868391 Hultgren Mar 2005 B1
6877665 Challa et al. Apr 2005 B2
6912398 Domnitz Jun 2005 B1
6920611 Spaeth et al. Jul 2005 B1
6975852 Sofer et al. Dec 2005 B1
6990330 Veerepalli et al. Jan 2006 B2
7003497 Maes Feb 2006 B2
7007840 Davis Mar 2006 B2
7013286 Aggarwal et al. Mar 2006 B1
7025256 Drummond et al. Apr 2006 B1
7028906 Challa et al. Apr 2006 B2
7039611 Devine May 2006 B2
7040533 Ramachandran May 2006 B1
7051923 Nguyen et al. May 2006 B2
7055031 Platt May 2006 B2
7076329 Kolls Jul 2006 B1
7089208 Levchin et al. Aug 2006 B1
7099850 Mann et al. Aug 2006 B1
7104446 Bortolin et al. Sep 2006 B2
7107250 Harrison Sep 2006 B2
7110954 Yung et al. Sep 2006 B2
7121456 Spaeth et al. Oct 2006 B2
7124937 Myers et al. Oct 2006 B2
7150393 Drummond et al. Dec 2006 B1
7152780 Gauthier et al. Dec 2006 B2
7159770 Onozu et al. Jan 2007 B2
7194437 Britto et al. Mar 2007 B1
7201313 Ramachandran Apr 2007 B1
7203300 Shaffer et al. Apr 2007 B2
7207477 Ramachandran Apr 2007 B1
7231357 Shanman Jun 2007 B1
7231372 Prange et al. Jun 2007 B1
RE39736 Morrill, Jr. Jul 2007 E
7243853 Levy et al. Jul 2007 B1
7257545 Hung Aug 2007 B1
7280981 Huang et al. Oct 2007 B2
7290704 Ball et al. Nov 2007 B1
7308254 Rissanen Dec 2007 B1
7343149 Benco et al. Mar 2008 B2
7350702 Bortolin et al. Apr 2008 B2
7353187 Emodi et al. Apr 2008 B1
7356516 Richey et al. Apr 2008 B2
7357310 Calabrese et al. Apr 2008 B2
7407094 Myers et al. Aug 2008 B2
7440771 Purk Oct 2008 B2
7447662 Gibson Nov 2008 B2
7464867 Kolls Dec 2008 B1
7945240 Klock et al. May 2011 B1
20010013542 Horowitz et al. Aug 2001 A1
20020013711 Ahuja et al. Jan 2002 A1
20020065713 Awada et al. May 2002 A1
20020091569 Kitaura et al. Jul 2002 A1
20020128903 Kernahan Sep 2002 A1
20020161701 Warmack Oct 2002 A1
20020165775 Tagseth et al. Nov 2002 A1
20020190118 Davenport et al. Dec 2002 A1
20020198777 Yuasa Dec 2002 A1
20030004808 Elhaoussine Jan 2003 A1
20030058261 Challa et al. Mar 2003 A1
20030120593 Bansal et al. Jun 2003 A1
20030126078 Vihinen Jul 2003 A1
20030144907 Cohen et al. Jul 2003 A1
20030172040 Kemper et al. Sep 2003 A1
20030212595 Antonucci Nov 2003 A1
20030212642 Weller et al. Nov 2003 A1
20030225618 Hessburg et al. Dec 2003 A1
20030230630 Whipple et al. Dec 2003 A1
20030233292 Richey et al. Dec 2003 A1
20040019522 Bortolin et al. Jan 2004 A1
20040030601 Pond et al. Feb 2004 A1
20040044621 Huang et al. Mar 2004 A1
20040049455 Mohsenzadeh Mar 2004 A1
20040050922 Gauthier et al. Mar 2004 A1
20040054575 Marshall Mar 2004 A1
20040054581 Redford et al. Mar 2004 A1
20040054590 Redford et al. Mar 2004 A1
20040054591 Spaeth et al. Mar 2004 A1
20040064406 Yates et al. Apr 2004 A1
20040117254 Nemirofsky et al. Jun 2004 A1
20040133653 Defosse et al. Jul 2004 A1
20040139021 Reed et al. Jul 2004 A1
20040148224 Gauthier et al. Jul 2004 A1
20040153715 Spaeth et al. Aug 2004 A1
20040186770 Pettit et al. Sep 2004 A1
20040199470 Ferry, Jr. et al. Oct 2004 A1
20040220964 Shiftan et al. Nov 2004 A1
20040243519 Perttila et al. Dec 2004 A1
20040254848 Golan et al. Dec 2004 A1
20040260653 Tsuei et al. Dec 2004 A1
20050021456 Steele et al. Jan 2005 A1
20050029344 Davis Feb 2005 A1
20050035847 Bonalle et al. Feb 2005 A1
20050036611 Seaton, Jr. et al. Feb 2005 A1
20050045718 Bortolin et al. Mar 2005 A1
20050058427 Nguyen et al. Mar 2005 A1
20050071225 Bortolin et al. Mar 2005 A1
20050071226 Nguyen et al. Mar 2005 A1
20050071227 Hammad et al. Mar 2005 A1
20050071228 Bortolin et al. Mar 2005 A1
20050071235 Nguyen et al. Mar 2005 A1
20050075958 Gonzalez Apr 2005 A1
20050097473 Malik et al. May 2005 A1
20050102233 Park et al. May 2005 A1
20050102234 Devine May 2005 A1
20050121506 Gauthier et al. Jun 2005 A1
20050149455 Bruesewitz et al. Jul 2005 A1
20050177510 Hilt et al. Aug 2005 A1
20050199714 Brandt et al. Sep 2005 A1
20050210387 Alagappan et al. Sep 2005 A1
20050219061 Lai et al. Oct 2005 A1
20050222933 Wesby Oct 2005 A1
20050283416 Reid et al. Dec 2005 A1
20050283430 Reid et al. Dec 2005 A1
20050283431 Reid et al. Dec 2005 A1
20050283432 Reid et al. Dec 2005 A1
20050283433 Reid et al. Dec 2005 A1
20060053056 Alspach-Goss et al. Mar 2006 A1
20060059110 Madhok et al. Mar 2006 A1
20060080243 Kemper et al. Apr 2006 A1
20060085260 Yamagishi Apr 2006 A1
20060111967 Forbes May 2006 A1
20060155644 Reid et al. Jul 2006 A1
20060163345 Myers et al. Jul 2006 A1
20060178957 LeClaire Aug 2006 A1
20060179007 Davis Aug 2006 A1
20060202025 Calabrese et al. Sep 2006 A1
20060206376 Gibbs et al. Sep 2006 A1
20060218086 Campbell et al. Sep 2006 A1
20060224449 Byerley et al. Oct 2006 A1
20060247981 Singh et al. Nov 2006 A1
20060248007 Hofer et al. Nov 2006 A1
20060253390 McCarthy et al. Nov 2006 A1
20060270421 Phillips et al. Nov 2006 A1
20060282382 Balasubramanian et al. Dec 2006 A1
20060290501 Hammad et al. Dec 2006 A1
20060293027 Hammad et al. Dec 2006 A1
20070001000 Nguyen et al. Jan 2007 A1
20070001001 Myers et al. Jan 2007 A1
20070005613 Singh et al. Jan 2007 A1
20070005774 Singh et al. Jan 2007 A1
20070012764 Bortolin et al. Jan 2007 A1
20070017970 Gauthier et al. Jan 2007 A1
20070034679 Gauthier et al. Feb 2007 A1
20070055597 Patel et al. Mar 2007 A1
20070055630 Gauthier et al. Mar 2007 A1
20070057034 Gauthier et al. Mar 2007 A1
20070057051 Bortolin et al. Mar 2007 A1
20070083465 Ciurea et al. Apr 2007 A1
20070100691 Patterson May 2007 A1
20070125842 Antoo et al. Jun 2007 A1
20070194104 Fukada Aug 2007 A1
20070203836 Dodin Aug 2007 A1
20070205270 Kemper et al. Sep 2007 A1
20070241189 Slavin et al. Oct 2007 A1
20070244811 Tumminaro Oct 2007 A1
20070250380 Mankoff Oct 2007 A1
20070276764 Mann Nov 2007 A1
20070288373 Wilkes Dec 2007 A1
20080003987 Mechaley Jan 2008 A1
20080006685 Rackley, III et al. Jan 2008 A1
20080021784 Hessburg et al. Jan 2008 A1
20080040265 Rackley, III et al. Feb 2008 A1
20080114657 Forzley May 2008 A1
20080120182 Arnold et al. May 2008 A1
20080126145 Rackley, III et al. May 2008 A1
20080133366 Evans et al. Jun 2008 A1
20080154727 Carlson Jun 2008 A1
20080154735 Carlson Jun 2008 A1
20080154772 Carlson Jun 2008 A1
20080163257 Carlson Jul 2008 A1
20080167991 Carlson et al. Jul 2008 A1
20080183480 Carlson Jul 2008 A1
20080201226 Carlson Aug 2008 A1
20080208762 Arthur et al. Aug 2008 A1
20080300973 DeWitt et al. Dec 2008 A1
20080319843 Moser et al. Dec 2008 A1
20090076896 DeWitt et al. Mar 2009 A1
20090076925 DeWitt et al. Mar 2009 A1
20090078777 Granucci et al. Mar 2009 A1
20090112721 Hammad et al. Apr 2009 A1
20090119170 Hammad et al. May 2009 A1
20090182634 Park et al. Jul 2009 A1
20090314840 Granucci et al. Dec 2009 A1
20100042540 Graves et al. Feb 2010 A1
Foreign Referenced Citations (11)
Number Date Country
1 096 439 May 2001 EP
1 136 961 Sep 2001 EP
2 348 781 Nov 2003 GB
WO 9613814 May 1996 WO
WO 9745814 Dec 1997 WO
WO 9951038 Jul 1999 WO
WO 0003328 Jan 2000 WO
WO 0077697 Dec 2000 WO
WO 2004077369 Sep 2004 WO
WO 2005052869 Jun 2005 WO
WO 2006024080 Mar 2006 WO
Related Publications (1)
Number Date Country
20090081990 A1 Mar 2009 US