Source: http://patents.com/us-8566250.html
Timestamp: 2019-08-26 10:36:49
Document Index: 778767387

Matched Legal Cases: ['Application No. 2', 'Application No. 00', 'Application No. 00', 'Application No. 00992162', 'Application No. 00', 'Application No. 00', 'Application No. 2', 'Application No. 60', 'art 1030', 'art 1230', 'art 1330']

US Patent # 8,566,250. Biometric identification device and methods for secure transactions - Patents.com
United States Patent 8,566,250
Russell , et al. October 22, 2013
Inventors: Russell; David C. (Portsmouth, VA), Johnson; Barry W. (Charlottesville, VA), Petka; David M. (Arlington, VA)
Assignee: Privaris, Inc. (Charlottesville, VA)
Appl. No.: 12/187,806
US 20080319915 A1 Dec 25, 2008
Current U.S. Class: 705/67 ; 340/5.52; 340/5.53; 340/5.8; 340/5.81; 340/5.82; 340/5.83; 340/5.84; 382/115; 705/64; 705/65; 705/66; 902/3
Field of Search: ;705/64-67 ;340/5.52-5.53,5.8-5.84 ;902/3 ;382/115
4189270 February 1980 Ehrlich
4408203 October 1983 Campbell
4961142 October 1990 Elliott et al.
5144680 September 1992 Kobayashi et al.
5386104 January 1995 Sime
5481265 January 1996 Russell
5493621 February 1996 Matsumura
5659626 August 1997 Ort et al.
5757278 May 1998 Itsumi
5869822 February 1999 Meadows et al.
5870723 February 1999 Pare et al.
5878157 March 1999 Mukohzaka
5949335 September 1999 Maynard
5966697 October 1999 Fergerson et al.
6002344 December 1999 Bandy et al.
6011554 January 2000 King et al.
6018739 January 2000 McCoy et al.
6021212 February 2000 Ho
6031519 February 2000 O'Brien
6040783 March 2000 Houvener et al.
6084967 July 2000 Kennedy et al.
6102286 August 2000 Hammond
6111506 August 2000 Yap et al.
6111977 August 2000 Scott et al.
6157871 December 2000 Terranova
6201484 March 2001 Russell
6202151 March 2001 Musgrave et al.
6601037 July 2003 Kolls
6745936 June 2004 Movalli et al.
7003495 February 2006 Burger et al.
7234640 June 2007 Pentel
7240022 July 2007 Bistriceanu et al.
2001/0000535 April 2001 Lapsley et al.
2001/0029493 October 2001 Pare, Jr. et al.
2001/0032115 October 2001 Goldstein
2002/0035542 March 2002 Tumey et al.
2002/0046118 April 2002 Minte
2002/0129285 September 2002 Kuwata et al.
2002/0138768 September 2002 Murakami et al.
2002/0143567 October 2002 Maritzen et al.
2003/0054879 March 2003 Schneier et al.
2003/0097350 May 2003 ShamRao
2003/0139984 July 2003 Seigel
2004/0064415 April 2004 Abdallah et al.
2005/0109835 May 2005 Jacoby et al.
2006/0143101 June 2006 Johanns et al.
2007/0145121 June 2007 Dallal et al.
2007/0260888 November 2007 Giobbi et al.
2008/0319872 December 2008 Russell et al.
2008/0319906 December 2008 Russell et al.
2008/0319907 December 2008 Russell et al.
195 35 803 Mar 1997 DE
0 704 788 Apr 1996 EP
0 779 497 Jun 1997 EP
0 945 818 Sep 1999 EP
WO 97/05541 Feb 1997 WO
WO 97/45814 Dec 1997 WO
WO 99/08238 Feb 1999 WO
WO 99/56429 Nov 1999 WO
WO 99/60503 Nov 1999 WO
L Walker, "Cloaking Devices Designed for Wary Web Shoppers," The Washington Post, Oct. 10, 2000. cited by applicant .
Biosec News, "BioNetrix Launches BioSEC Alliance," BioNetrix.Com, Nov. 1999. cited by applicant .
A. Levinsohn, "Who Will Control Electronic Payments," ABA Banking Journal, Sep. 1998. cited by applicant .
R. Hettinga, "A Market Model for Digital Bearer Instrument Underwriting," Philodox Financial Tech. Evangelism, May 1998. cited by applicant .
Sony, "Fingerprint Identification Unit (FIU-710)", Sony.Com, Japan 2001. cited by applicant .
D. Gray, "Security and Convenience at Kroger," E-Payments 2000, Jun. 1999. cited by applicant .
L. Fickenscher, "Visa Shores Up Web Position, Ends Fees on Theft of Card Numbers," American Banker, Feb. 22, 2000. cited by applicant .
K. Kiesnoski, "Digital Wallets," Bank Systems+Technology, Oct. 1999. cited by applicant .
B. Curley, "Paying At the PC," Bank Systems+Technology, Oct. 1999. cited by applicant .
J. Ashboum, "The Biometric Whitepaper," ntlworld.com, 1999. cited by applicant .
International Search Report and Written Opinion for PCT/US00/42323, mailed on Apr. 27, 2001; 2 pages. cited by applicant .
Schneier, B., "Applied Cryptography: Protocols, Algorithms, and Source Code in C," Second Edition, 1996, John Wiley & Sons, Inc., pp. 31-34. cited by applicant .
Office Action for Canadian Patent Application No. 2,392,229, mailed on Dec. 10, 2007; 3 pages. cited by applicant .
Office Action for European Patent Application No. 00 992 162.8, mailed on Oct. 30, 2006; 4 pages. cited by applicant .
Office Action for European Patent Application No. 00 992 162.8, mailed on Sep. 13, 2007; 8 pages. cited by applicant .
Summons to Attend Oral Proceedings for European Patent Application No. 00992162.8, mailed on May 9, 2008; 7 pages. cited by applicant .
Decision to Refuse a European Patent Application for European Patent Application No. 00 992 162.8; mailed on Nov. 10, 2008; 29 pages. cited by applicant .
Communication for European Patent Application No. 00 992 162.8, mailed on Oct. 1, 2008; 4 pages. cited by applicant .
Office Action for U.S. Appl. No. 12/187,808, mailed on Feb. 3, 2009; 6 pages. cited by applicant .
Office Action for U.S. Appl. No. 12/187,808, mailed on Jul. 30, 2009; 26 pages. cited by applicant .
Office Action for U.S. Appl. No. 12/187,812, mailed on Feb. 10, 2009; 7 pages. cited by applicant .
Office Action for U.S. Appl. No. 12/187,812, mailed on Aug. 19, 2009; 21 pages. cited by applicant .
Office Action for U.S. Appl. No. 12/187,817, mailed on Feb. 25, 2009; 6 pages. cited by applicant .
Office Action for U.S. Appl. No. 12/187,817, mailed on Sep. 22, 2009; 16 pages. cited by applicant .
Office Action for U.S. Appl. No. 10/148,512, mailed on Mar. 22, 2007; 16 pages. cited by applicant .
Office Action for U.S. Appl. No. 10/148,512, mailed on Nov. 23, 2007; 15 pages. cited by applicant .
Office Action for U.S. Appl. No. 10/148,512, mailed on Aug. 6, 2008; 18 pages. cited by applicant .
Office Action for U.S. Appl. No. 10/148,512, mailed on Apr. 28, 2009; 29 pages. cited by applicant .
Office Action for U.S. Appl. No. 10/148,512, mailed on Dec. 1, 2009; 35 pages. cited by applicant .
Office Action for Canadian Patent Application No. 2,392,229, mailed on Feb. 2, 2011; 5 pages. cited by applicant .
Office Action for U.S. Appl. No. 10/148,512, mailed on Aug. 16, 2010, 30 pages. cited by applicant .
Office Action for U.S. Appl. No. 10/148,512, mailed on Dec. 17, 2010, 35 pages. cited by applicant .
Office Action for U.S. Appl. No. 12/187,808, mailed on Apr. 26, 2010, 28 pages. cited by applicant .
Office Action for U.S. Appl. No. 12/187,808, mailed on Oct. 1, 2010; 26 pages. cited by applicant .
Office Action for U.S. Appl. No. 12/187,808, mailed on Aug. 31, 2011; 29 pages. cited by applicant .
Office Action for U.S. Appl. No. 12/187,812, mailed on May 4, 2010, 20 pages. cited by applicant .
Office Action for U.S. Appl. No. 12/187,812, mailed on Feb. 23, 2011; 24 pages. cited by applicant .
Office Action for U.S. Appl. No. 12/187,812, mailed on Jul. 18, 2011; 24 pages. cited by applicant .
Office Action for U.S. Appl. No. 12/187,817, mailed on Apr. 27, 2010, 20 pages. cited by applicant .
Office Action for U.S. Appl. No. 12/187,817, mailed on Nov. 10, 2010; 20 pages. cited by applicant .
Office Action for U.S. Appl. No. 12/187,817, mailed Sep. 6, 2011; 23 pages. cited by applicant .
Avolio, F. M., "Buyer's guide: Biometrically speaking", Network Computing, Manhasset, Aug. 23, 1999, [online], [retrieved on Sep. 27, 2010]. Retrieved from the Internet: <URL:http://proquest.umi.com/pdqweb?did=44184637&sid=5&Fmt=4&clientId=- 19649&RQT=309&VName-PQD. cited by applicant .
Business Editors/High-tech Writers COMDEX Fall 99, "Identix Delivers the Ultimate Security with Biometrics for the Mobile Computer; Compaq Endorses Technology as a Critical Next Step in Taking Biometrics on the Road", Business Wire, New York, Nov. 16, 1999, [online], [retrieved on Sep. 27, 2010]. Retrieved from the Internet: <URL:http://proquest.umi.com/pdqweb?did=46387378&sid=2&Fmt=3&clientId=- 19646&RQT=309&VName=PQD. cited by applicant .
Zalud, B., "Biometric shift: Integration, computer access affect uses", Security, Troy, Dec. 1997, [online], [retrieved on Sep. 27, 2010]. Retrieved from the Internet: <URL:http://proquest.umi.com/pdqweb?did=23923917&sid=5&Fmt=4&clientId=- 19649&RQT=309&VName=PQD. cited by applicant .
Office Action for U.S. Appl. No. 12/187,808, mailed on Aug. 19, 2013; 48 pages. cited by applicant .
Office Action for U.S. Appl. No. 12/187,817, mailed Sep. 5, 2013; 37 pages. cited by applicant.
This application claims priority to and is a divisional of U.S. patent application Ser. No. 10/148,512, entitled "Methods, Systems and Apparatuses for Secure Transactions," which is a U.S. national-stage application of PCT Application No. PCT/US00/42323, filed on Nov. 29, 2000, entitled "Methods, Systems and Apparatuses For Secure Transactions," which claims priority of U.S. Patent Application No. 60/168,082 filed Nov. 30, 1999, entitled "Apparatus for Controlling Converged Media Systems Including Payment Applications, Using a Privacy and Security-Oriented, Customer-Centered Authentication Architecture for Users of Pointing Identifying Devices and Biometrics Pointing Identifying Devices," each of which is incorporated herein by reference in their entireties.
This application is related to U.S. patent application Ser. No. 12/187,808, entitled "Biometric Identification Device," Ser. No. 12/187,812, entitled "Biometric Identification Device And Methods Associated With Inventory" and Ser. No. 12/187,817, entitled "Secure Transaction Method And System Including Biometric Identification Devices And Device Readers," each filed on the same date, and each of which is incorporated herein by reference in their entirety.
1. A method, comprising: authenticating, at a personal identification device owned by a user, a biometric input of the user of the personal identification device based on a biometric template of the user stored at the personal identification device, the biometric input being stored at the personal identification device during the authenticating, the personal identification device being configured to prevent the biometric input and the biometric template from being output from the personal identification device, the personal identification device being portable and having financial data associated with funds of the user stored thereon; and sending, from the personal identification device, the financial data associated with the funds of the user to a receiving party such that the receiving party receives funds based on the financial data associated with the funds when the biometric input of the user is authentic.
2. The method of claim 1, wherein: the financial data associated with the user includes an identifier associated with the personal identification device; and the sending, from the personal identification device, the financial data associated with the user to the receiving party is performed such that the receiving party confirms that the identifier associated with the personal identification device has been registered in association with the user and that the user is privileged to access an account of the user associated with the funds.
3. The method of claim 1, wherein: the financial data associated with the user includes an identifier associated with the personal identification device; and the sending, from the personal identification device, the financial data associated with the user to the receiving part is performed such that the receiving party consults a certificate repository database based on the identifier associated with the personal identification device.
4. The method of claim 1, wherein the receiving party is a vendor, the method further comprising: selecting, at the personal identification device, an item for purchase; determining, at the personal identification device, a payment amount based on the item before the sending, from the personal identification device, financial data associated with the user, the financial data associated with the user being configured to debit an account of the user by the payment amount; and receiving, at the personal identification device, from the vendor an acknowledgement.
5. The method of claim 1, wherein the financial data associated with the user is configured such that a financial intermediary receives funds associated with a surcharge.
6. The method of claim 1, further comprising: requiring the user to re-authenticate at the personal identification device; and the sending, from the personal identification device, the financial data associated with the user being performed within a preset time period before the requiring.
7. The method of claim 1, wherein the financial data associated with the user is configured to authorize a payment for a deliverable; and the sending, from the personal identification device, the financial data associated with the user to the receiving party is performed such that the receiving party verifies that an account of the user specified by the financial data associated with the user has sufficient funds to make the payment for the deliverable.
8. The method of claim 1, wherein the financial data associated with the user is associated with the biometric template of the user.
9. The method of claim 1, wherein the personal identification device is configured to deny an alteration to the financial data associated with the user unless the alteration is performed by a verification authority.
10. A method, comprising: authenticating, at a personal identification device owned by a user, a biometric input of the user of the personal identification device based on a biometric template of the user stored at the personal identification device, the biometric input being stored at the personal identification device during the authenticating, the personal identification device being configured to prevent the biometric input and the biometric template from being output from the personal identification device, the personal identification device being portable; producing, at the personal identification device, a payment packet associated with the user, the payment packet including an account of the user and a payment amount; and sending, from the personal identification device, the payment packet associated with the user to a receiving party such that the payment amount is transferred from the account of the user to an account of the receiving party.
11. The method of claim 10, wherein the payment packet includes an identifier associated with the personal identification device, the sending, from the personal identification device, the payment packet to the receiving party is performed such that the receiving party confirms that the user is privileged to access the account of the user based on the identifier associated with the personal identification device.
12. The method of claim 10, wherein the payment packet includes an identifier associated with the personal identification device, the sending, from the personal identification device, the payment packet to the receiving party is performed such that the receiving party confirms that the identifier associated with the personal identification device corresponds to a personal identification device that has been registered to the user.
13. The method of claim 10, wherein the receiving party is a vendor, the method further comprising: selecting, at the personal identification device, an item for purchase; determining, at the personal identification device, a payment amount based on the item before the sending the payment packet; and receiving, at the personal identification device, from the vendor an acknowledgement when the payment amount has been successfully transferred from the account of the user to the account of the vendor.
14. The method of claim 10, wherein the payment packet is configured to permit transmission of funds associated with a surcharge from the account of the user to an account of a financial intermediary.
15. The method of claim 10, wherein the biometric template includes at least one of a digit-print, a handprint, a voice data, a retinal data, and a DNA data.
16. A method, comprising: receiving, at a personal identification device owned by a user, a biometric input of the user; authenticating, at the personal identification device, the biometric input of the user of the personal identification device based on a biometric template of the user stored at the personal identification device, the biometric template being associated with account data of the user, the biometric input being stored at the personal identification device during the authenticating, the personal identification device being configured to prevent output of the biometric input and the biometric template stored at the personal identification device, the personal identification device being portable; and sending, from the personal identification device, the account data to a receiving party when the biometric input is authentic such that funds associated with the account data is received by an account of the receiving party.
17. The method of claim 16, further comprising: sending, from the personal identification device, an identifier associated with the personal identification device to the receiving party such that the receiving party confirms that the identifier associated with the personal identification device has been registered to the user and that the user is privileged to access the account data.
18. The method of claim 16, wherein the account data is configured to permit transmission of funds associated with a plurality of surcharges from the account of the user to an account of each financial intermediary from a plurality of financial intermediaries, each surcharge from the plurality of surcharges being associated with a financial intermediary from the plurality of financial intermediaries.
19. The method of claim 16, further comprising: requiring the user to re-authenticate a biometric input of the user at the personal identification device, the sending, from the personal identification device, the account data to the receiving party being performed within a preset time period before the requiring.
20. The method of claim 16, wherein the personal identification device has a weight of less than two ounces and a volume of less than two cubic inches.
Although most traditional vendors use the data provided to them by their customers only to secure the payment due to them from the transaction, the data collected has additional valuable potential, even if clearly fraudulent activities--such as using the customer's credit-card data to make unauthorized purchases--are not considered. For instance, a vendor could track the frequency, amount, location, type, and other data about purchases for each particular customer. This data could be used to develop targeted advertising strategies designed to get the customer into the store immediately and/or after a prolonged absence. In addition, mailing lists of customers could be developed that could be sold to financial institutions or other vendors who want to promote their credit cards. Until recently, the cost and tedium involved in compiling and processing such data discouraged aggressive use of personal data. However, due to recent technological advances, this has completely changed. Over the past several years, the plummeting cost of computing hardware, and the increasing sophistication of data warehousing and data mining software, in combination with exponential growth in digitally-processed and internet-processed customer purchase transactions, has put the security and privacy of the customer at extreme risk, despite contrary assertions of many vendors.
According to The Forrester Report (April, 1999 published by Forrester Research Inc.) 48% of both U.S. and European Internet retail companies interviewed indicated that they save customer name, address, and account information for use in an express checkout system. Although such systems help to speed customers through checkout, many of the retail companies admitted, "[their] transactions systems have limited scalability, poor fraud detection, high ongoing costs, and lack of real-time authorization."
Perhaps one of the greatest concerns over the warehousing of customer data and information is the highly lucrative target that such a concentration of personal and financial information presents to hackers and other thieves. According to the Washington Post ("Cloaking Devices Designed for Wary Web Shoppers," The Washington Post, Oct. 19, 2000, page E01), hackers stole 15,600 credit-card numbers from a Western Union web site during the month of September 2000. Credit card fraud represents a huge loss to both the credit-card industry and individual consumers. An estimated 0.06% of point-of-sale credit-card purchases and as much as 1% of online credit-card purchases are fraudulent ("VISA Shores up Web Position, Ends Fees on Theft of Credit Cards," American Banker, February, 2000; "Equity Research Report on First Data Corp.," Morgan Keegan, January, 2000.). Other estimates by vendor symposia (e.g., the "Card Tech/Secure Tech" trade show on Dec. 1, 1999) estimate much higher figures, generally estimating that "Card Not Present" transactions experience 6 (six) times greater incidence of fraud than actual physical "Card Present" transactions. Although most individual consumers face limited financial liabilities if unauthorized use of their credit-card information is promptly reported, dealing with instances of fraud can be frustrating and time-consuming. Notwithstanding, in the final analysis, all consumers eventually pay for credit-card fraud in the form of higher vendor prices and less attractive credit-card terms than might otherwise be available.
Shawn Abbott ("The Debate for Secure E-Commerce," Performance Computing February 1999) discusses both SSL and Secure Electronic Transactions (SET) protocols for electronic commerce. As stated in the article, "SSL is widely used because it is built into all major Web browsers and servers and is easy to apply." However, beyond verifying that the vendor is a bona fide company and that the customer's computer is dealing with the vendor's server, SSL protocol does little more than facilitate encrypted and reliable interaction between computers. On the other hand, SET is a messaging protocol specifically designed by financial institutions to facilitate bankcard transactions over open networks such as the Internet.
According to Kenneth Kiesnoski ("Digital Wallets," Bank Systems+Technology, October 1999) both client-based and server-based digital wallets have a number of proponents. The digital wallet is an application that stores financial account information, account-owner names, billing and shipping information, and other information that might typically be required to make an electronic transaction. At the customer's direction, all or part of this set of information is transferred to the vendor at the time of purchase. This saves the customer the trouble of typing all that information and possibly making an error.
Bob Curley ("Paying at the PC," Bank Systems+Technology, October, 1999) discusses two systems designed to interact with personal computers.
In "The Biometrics White Paper," Ashbourn discusses a large number of generic issues associated with biometric identification for use in security applications. Ashbourn defines biometrics "as measurable physiological and/or behavioral characteristics that can be utilized to verify the identity of an individual. They include fingerprints, retinal and iris scanning, hand geometry, voice patterns, facial recognition and other techniques." Our use of the term "biometrics" and related forms of the word are intended to be consistent with the above-quoted definition. However, an individual's written signature and/or handwriting are not to be considered biometrics in the context of this application.
Other embodiments of the invention involve methods by which a payment may be conveyed from a payer to a payee by means of a financial institution or other financial intermediary. The words "payer" and "payee" are intended to be very general terms to identify the party making the payment (the payer) and the party receiving the payment (the payee). In typical circumstances, the payee is a vendor and the payer is a customer, although the payment method is intended to be inclusive of arrangements that include multiple additional parties.
For the purpose of this method of payment, a PID is a portable device that authenticates that a user of the device is privileged to make a payment from the payer account(s) specified in the payer account data. As used in the context of a PID, the word "portable" means that the size and weight of the PID is such that an individual can conveniently carry the PID on his/her person.
Other embodiments of the invention include methods of interacting with a "simulated inventory". A simulated inventory is defined for the purposes of this application and according to this invention, as a visual representation of a catalog, index, directory, or other content. The contents of the simulated inventory are not limited in this invention.
The visual representation includes all kinds of visual representations, including two-dimensional displays or projection images, three-dimensional displays or projection representations using perspective for the third dimension, and holographic representations. In most embodiments, the visual representation involves a pictographic graphical user interface in which the user virtually travels, or equivalently perambulates, through the simulated inventory by manipulating a cursor. In this application, the term "cursor" includes all displayed control indicia. Typically a cursor is represented by an arrowhead although other representations are used. In some embodiments the cursor is represented by an "avatar" (an icon or representation of a user in a sharable virtual reality environment). Using the cursor, (or in some embodiments, the avatar), the customer can travel about the domain of the simulated inventory, browse the inventory, command any inventory item to detail its properties (sizes, price, etc.), fill a shopping basket or other purchase enabler, and at end-of-shopping-session, pay for the selected item(s).
In one preferred embodiment of a simulated inventory using such a graphical user interface, a multiplicity of such icons are used to represent elements in the inventory. The phrase "graphical user interface" is to be interpreted broadly in this application. The phrase "holographic graphical user interface" will be understood to be a subset of graphical user interfaces and will be used in embodiments in which holographic representations are used similar to two-dimensional graphical user interfaces. All these methods for a user to interact with a simulated inventory include the step of authenticating a user to a PID. The authenticated user provides inputs to the PID allowing the user to travel at any speed they choose through the simulated inventory.
Other embodiments of the invention include verification systems. Embodiments of verification systems comprise: (1) an "actuator" for performing a user-initiated action, (2) a PID that transmits signals that encode an identification and an instruction that one or more user-initiated actions be taken, and (3) a verification processor that receives the signals from the PID and verifies that the identification is associated with a PID that is authorized to request that the one or more user-initiated actions be taken.
After verification, the verification processor signals the actuator to perform the user-initiated action. In preferred embodiments, the identification is the PID control designation, but the term "identification" is intended to be interpreted broadly. The term "actuator" should also be interpreted broadly. The actuators envisioned include those that result in mechanical actions and/or electrical actions, as well as those that result in actions that only involve transfer or manipulation of data.
Still other system embodiments of the invention include simulated inventory systems. Simulated inventory systems include: (1) a "simulated inventory display", (2) a simulated inventory controller that controls the interaction of at least one cursor interacting with at least one icon on the simulated inventory display, and (3) a PID that transmits instructions to the simulated inventory controller.
Many preferred embodiments of PIDs authenticate a user through the use of a biometric. This type of embodiment is referred to as a "biometric personal identifying device" (BPID). In a BPID, the stored identity data would be considered a biometric template and the verification input component would collect a live biometric sample, which will typically be referred to as a biometric sample. As discussed by Ashbourn, we will use the phrase "biometric template" and variations thereof to refer to a reference sample of a chosen biometric against which a future live biometric sample is compared. Preferably, neither the biometric template nor the biometric sample is available outside the BPID. Keeping these data local to the BPID reduces the chance that an individual's biometric becomes accessible to the public.
In this application, the acronyms PID (personal identifying device) and BPID (biometric personal identifying device) are used extensively. In a prior provisional application (Ser. No. 60/168,082, filed Nov. 30, 1999), entitled, "Apparatus for Controlling Converged Media Systems Including Payment Applications, Using a Privacy and Security-Oriented, Customer-Centered Authentication Architecture for Users of Pointing Identifying Devices and Biometrics Pointing Identifying Devices," which is incorporated by reference herein in its entirety, these same acronyms refer to "Pointing Identifying Device" and "Biometric Pointing Identifying Device." The PID and/or BPID discussed herein, are generalizations and extensions of the specific embodiments of Pointing Identifying Devices and Biometric Pointing Identifying Devices discussed in the provisional application. In particular, as will be further discussed herein, the "pointing" capability of the original Pointing Identifying Device and Biometric Pointing Identifying Device need not be present in all embodiments of PIDs and/or BPIDs. Even in the provisional application, the pointing capability of the devices was not required for all embodiments of the invention. The devices called PIDs and BPIDs in the provisional application should be interpreted as specific embodiments of the more general PIDs and BPIDs discussed herein.
Reference numerals used in the drawings refer to the corresponding components listed below unless otherwise specified. 100 personal identifying device (PID) 110 processor 120 transmitter 125 transceiver 130 receiver 140 user input module 142 joy stick 144 activation button 146 mode switch 148 slide bar 149 positional sensor 150 identity verification module 152 identity data module 153 self-destruct element 154 comparator 156 keypad 160 data storage medium 170 display device 180 power source 190 biometric input device 200 biometric personal identifying device (BPID) 210 kill switch 220 bar-code reader 230 magnetic-stripe reader 300 information processor 310 processor of the information processor 320 information transmitter 330 information receiver 340 vendor connection 350 financial intermediary connection 360 certification repository connection 400 verification processor 410 processor of the verification processor 420 verification processor transmitter 430 verification processor receiver 460 certification repository connection 470 actuator connection 500 verification system 510 actuator 600 financial intermediary component 610 payee 620 certification repository database 650 simulated inventory system 660 simulated inventory controller 670 simulated inventory display 710 steps in determining prescribed discount and prescribed personal data fields 712 step of specifying customer benefit function 714 step of specifying customer non-negotiable constraints 716 step of specifying customer benefit function normalization value 720 step of maximizing a function subject to constraints 722 step of specifying discounter benefit function 724 step of specifying discounter non-negotiable constraints 726 step of specifying discounter benefit function normalization value 730 step of receiving values for prescribed personal data fields 740 step of certifying that the value of a personal data field corresponds to the customer 750 step of reducing the price by the prescribed discount 810 step of receiving payer payment information 820 step of confirming the PID control designation 830 step of forming a payee payment packet 835 step of sending the payee payment packet to payee financial intermediary 840 step of sending the payee payment packet to payer financial intermediary 850 step of accepting payment 910 step of receiving a payee payment packet 920 step of debiting the payer account 1010 step of selecting items for purchase 1020 step of adding selected items to electronic shopping cart 1030 step of determining the payment amount 1040 step of authenticating the customer identity to a PID 1050 step of transferring data from the PID to the information processor 1060 step of transferring data from the vendor to the information processor 1070 step of forming a vendor payment packet 1080 step of sending the vendor payment packet to the vendor financial intermediary 1090 step of sending the vendor payment packet to the customer financial intermediary 1100 step of debiting the customer account 1110 step of crediting the vendor account 1210 step of selecting items for purchase 1220 step of adding selected items to electronic shopping cart 1230 step of determining the payment amount 1240 step of authenticating the customer identity to a PID 1250 step of sending customer data to a receiver 1260 step of receiving acknowledgement that the transaction was approved 1310 step of selecting items for purchase 1320 step of adding selected items to electronic shopping cart 1330 step of determining the payment amount 1340 step of authenticating the customer identity to a PID 1345 step of certifying payment capability 1350 step of traveling through the simulated inventory
In many embodiments both wired and wireless transmitters and receivers are provided. For instance, when used in conjunction with a computer, the PID 100 might be connected to the computer through an RJ-11 phone jack in the PID 100 and the computer's phone jack. Alternatively, a Universal Serial Bus (USB), serial port, or parallel port connection may be used to provide a wired connection to the computer. The wired alternatives might be particularly useful in electronically noisy environments. Preferably, signals received by the receiver 120 and signals transmitted by the transmitter 130 are encrypted. Preferably, an asymmetric encryption scheme, such as a public key/private key scheme is used. In particular, the RSA algorithm (which is described in detail in Schneier, B. C., Applied Cryptography--Protocols, Algorithms, and Source Code in C, Second Edition, John Wiley and Sons, Inc., New York, N.Y., 1996, which is incorporated herein by reference) is one preferred approach for encrypting information transmitted and received by the PID 100. However, other encryption schemes may be used in alternative embodiments.
Because of the sensitivity of the user identity data stored on the identity data module 152, preferably the identity data module 152 can be coupled to a self-destruct element 153 that destroys the identity data if unauthorized access to the stored identity data is attempted. For instance, the PID 100 can be built so as to render the identity data unreadable if identity data module 152 is probed by anyone but a qualified technician who follows a pre-determined sequence of actions. Additionally or alternatively, in some preferred embodiments, protective packaging tactics can be used to protect some or all of identity verification module's 150 components. One typically used delicate electronics protection tactic is known as "conformal coating". In this approach, an extremely thin polymer or rubber-like "shrink wrap" is completely superimposed over the electronic components to be protected. Attempts by any unauthorized party to gain physical access to the conformal coating-protected electronics will usually result in the destruction of the coating-protected electronics. In some embodiments, the identity data module 152 is combined with the personal data storage medium 160. In such embodiments, both elements are considered to be present, in spite of the fact that they share a single physical device.
In some advanced versions of the PID 100, optional embodiments include the capacity to provide other data and signal outputs beyond the abovementioned outputs of transmitter 120. Such embodiments can provide additional functions, e.g., bar-code writer and magnetic-stripe writer outputs, targeted for use with auxiliary output destination mechanisms such as "PID-readable/writable" smart shelf labels or smart product labels" (in conjunction with PID-initiated bar-code reader/writer functions) (not shown) and/or PID-readable/writable" magnetic cards (in conjunction with PID-initiated magnetic-stripe reader/writer functions) or other optional PID-initiated output target destination devices (not shown).
Preferred embodiments of PID 100 employ at least one biometric as the user identity data. In these embodiments, a biometric input component must be used as part of the verification input component, either instead of--or in addition to--the keypad 156 of FIG. 1. The biometric input component can vary widely, depending upon the biometric used. Example biometrics that might be used include: digit-prints (thumb- or finger-prints), voice data, retinal data, iris data, and DNA data. Preferably, the biometric is a digit-print--and therefore--the biometric input component is a component that can determine a user's digit-print. Various technologies are available for determining a user's digit-print. For instance, an optical scanner can be used to optically determine the digit-print. More preferably, a capacitive sensor is used. Capacitive digit sensors and their associated circuitry and software are available commercially, for instance the FPS 110 Sensor sold by Veridicom, the FINGERTIP Sensor, sold by Infineon, and the FINGERLOC AF-S1, sold by Authentec Inc.
Preferably, the information processor 300 serves as a bilaterally trusted intermediary between parties, most often, between a payer and a vendor. In some cases it serves as a "unit transaction processor" for a single transaction only, while in other cases it serves as an "ongoing transactions processor" for multiple transactions for that payer/vendor combination. In some embodiments it serves as a "privacy processor" that receives pre-agreed payment transaction information from both the payer and the payee, and transfers only pre-agreed types of information to other parties.
If the verification processor transmitter 420 and receiver 430 or transceiver (not shown) communicate with a PID wirelessly, then the generic verification processor 400 shown in FIG. 5 is a WVP. The WVP discussed in the context of FIG. 4 employs the financial intermediary connection 350 as an actuator connection 470 (as illustrated in FIG. 5). In the context of this invention, the term "actuator" is used very broadly and the financial intermediary is considered an actuator because it performs a user-initiated action, e.g., transferring money from the user account to the vendor account (either account possibly being located at another financial intermediary).
To increase trust and credibility for PID users and vendors alike, and in most preferred PID product distribution models, optimally, personal documentation that provides evidence of identity is required at registration. Such trust and credibility evidence might include (but is not limited to) presentation of a picture ID issued by a trusted party (such as a driver's license issued by a state and/or a passport issued by a country), a "social security card" (or other evidence of a personal control number), and/or other necessary and appropriate documentation satisfactory to any or all of the owners of applications intended for receiving PID access inputs by each PID user. Because so many uses and applications are anticipated, the extent of registration credential requirements will vary widely between one individual and another, and will depend on the number and type of security needed to satisfy all applications each PID owner expects to access.
Preferably, in most PID registration scenarios and for most applications, the VA does not maintain any of the personal information, except possibly what is loaded into the certification repository database. However, for "private systems" (usually private, internal company, and custom vertical market applications) it is likely that additional strictures and/or control policies can be implemented, e.g., in a company-wide system for personnel time card management, or in highly secure applications serving necessarily secretive and closed communities (e.g., intelligence agencies, some military and government applications, some private security companies). Additional strictures may also apply for some commercial in-house applications (in-store inventory and control systems, banks, brokerages, high-technology labs, etc.).
At registration, the user initializes the device with user identity data, which will become the stored identity data against which future comparisons are made to establish user identity. The VA will associate the user identity data with the user's identity (name, personal control number, and/or other form of identification) on the PID. Preferably, the PID is designed so that tampering with PID in an attempt to extract the user identity data will result in the destruction of that data. Preferably, the VA does not maintain the user identity data, except possibly for some private applications. Retained user identity data--at least in most "conventional" application environments--are only available only on the PID, in accordance with the spirit of the invention. Again, other custom arrangements are possible to suit needs of the application owner and implementer (particularly in private and custom vertical-market applications, which are usually privately owned).
The user selects items for purchase and places them into a shopping cart, (which may be an electronic shopping cart). The vendor sums the purchase prices and any other appropriate charges (e.g., shipping, handling, tax, etc.) to determine a purchase price. The purchase price is communicated to the user either directly, or through a WVP to which the vendor is connected. For an online or Internet purchase, the WVP might be connected to the user's computer and only indirectly connected to the vendor. For a conventional store, the WVP is preferably connected to the cash register or similar equipment. The user activates his/her BPID and indicates a credit card account that the user wishes to use to make the payment. The BPID transmits an encrypted data stream of credit card account data (including the financial intermediary address), date/time stamp, and BPID control designation, and etc. to the WVP. The data stream is encrypted with a BPID private key that was assigned to the BPID either at manufacturing time, or upon registration. The encrypted date/time stamp keeps a "dynamic" data stream (i.e. the same data stream can never be duplicated). The WVP receives the encrypted data stream and decrypts the data with a public key, which is located in a certification repository database, which in this example is a database that contains public keys for each PID. After the WVP verifies that the data came from the appropriate BPID user, the WVP provides the financial intermediary with the necessary account data. The financial intermediary is provided these data in any suitable manner, but most preferably these data are packaged to match the presently used data streams for making financial payments. The financial intermediary is considered the actuator in this case. The financial intermediary takes the implied user-initiated action of checking the data and either approving or disapproving the requested financial transaction, depending upon the status of the user's account. Then an approval/disapproval data stream is returned to the WVP, which further relays the approval/disapproval message appropriately encrypted to the BPID and to the vendor. The user then indicates with the BPID go forward with the purchase. The appropriately encrypted message is sent to the WVP, which forwards the message to the vendor (which is the actuator for this portion of the process). The vendor then completes the sale as usual. In some embodiments, a record of the transaction is maintained on the BPID. This record can later be downloaded to the user's choice of personal accounting system.
In a preferred procedure, each account included on the PID will be associated with a public key provided by the financial intermediary that issued the account, or provided indirectly via a public key repository. When the user of a PID selects an account to use in a specific financial transaction, the PID appends date and time information to the account information and encrypts the data stream with the public key associated with the selected account. The use of date and time information forces the encrypted bit pattern to be different every time the PID is used to make a financial transaction. The differing bit patterns guarantees that a signal intercepted by a third party cannot be simply repeated to gain access to the account (a.k.a. "replay attack").
Preferably the simulated inventory takes the form of either a two-dimensional or three-dimensional graphical user interface that is displayed on the simulated inventory display 670. Three-dimensional graphical user interfaces can be produced with perspective on a surface (either flat or curved) or (in advanced, premium applications) through the use of holographic images. The use of the phrase "on the simulated inventory display 670" is intended to include both projections onto a surface and holographic projections, in which the preposition "in" would be more appropriate.
The term "cursor" is used here to mean an easily recognizable indicator of the user's position in the simulated inventory. In this application, the cursor, (or an avatar in embodiments in which an avatar is used as the cursor), is displayed on the simulated inventory display 670, allowing the PID user to manipulate product images and icons.
As shown with reference numeral 720 in FIG. 9, mathematically, the optimization algorithm maximizes: CB(CBF/CBFNV)+DB(DBF/DBFNV)
TABLE-US-00001 TABLE 1 Field Discount 1 2 3 4 1 & 3 1, 2, & 3 1% 1 1 1 1 0 0 2% 1 2 1 2 1 1 3% 2 3 1 2 2 4% 3 4 2 3 3 2
The most preferred embodiments employ a BPID (biometric personal identifying device) rather than a non-biometric PID. In these embodiments, the PID authenticates that the user of the device is privileged to make a payment from the payer account by determining that a biometric sample collected from the user sufficiently matches a biometric template associated with the payer account data, and wherein the biometric template is stored locally on the PID. To reduce the possibility of fraud, preferably the biometric sample collected from the user is collected within a preset time period, prior to payer payment information reception by any payee. Without such a "time-out" period, unauthorized transactions could be made by others after the BPID had authenticated a particular user.
In some preferred embodiments, the bearer financial instrument takes the form of electronic script, as described in U.S. Pat. No. 6,122,625 to Rosen, which is included herein by reference in its entirety. In other preferred embodiments, the bearer financial instrument takes the form of digital bearer cash, a model for which is described by Hetting a ("A Market Model for Digital Bearer Instrument Underwriting,"<www.philodox.com/modelaper.html>, revised on Sep. 8, 1998), which is included herein by reference in its entirety. The particular form of the bearer financial instrument is not critical to its use in the invention. However, preferred forms of bearer financial instruments to be used with the invention can be transferred between parties without the direct involvement of a financial intermediary.
In the following claims, the use of the articles "a" and "an" should be interpreted to mean "at least one" of the designated element unless the claim specifically limits the number of the designated element. The use of the phrase "at least one" in any claim is intended to emphasize the possible plurality of the specified element, but its use does not limit the possible plurality of other elements specified with "a" or "an."
Previous Patent US 8,566,249 | Next Patent US 8,566,251