|
|
|
Including funds transfer or credit transaction |
Portable electronic authorization system and method7003495
Abstract
In one embodiment an apparatus includes a housing; a user authenticator, supported by the housing, that authenticates an identity of a user; at least one memory, supported by the housing, that stores transaction information for at least first and second media; and at least one output, supported by the housing, that releases at least a portion of the transaction information to a point-of-sale (POS) terminal after the user authenticator has authenticated the identity of the user. In another embodiment, a method involves steps of: storing transaction information for at least first and second media in a memory of a device; receiving as input a user's selection of one of the at least first and second media; displaying a visual indication to the user regarding which of the at least first and second media has been selected; and transferring at least a portion of the transaction information from the device to a point-of-sale (POS) terminal.
Claims
What is claimed is:
1. A method, comprising steps of:
(A) storing at least first account information for a first media issued by a first media issuer and second account information for a second media issued by a second media issuer in a database in communication with a transfer server so that the first account information and the second account information exist simultaneously in the database;
(B) establishing a communication link via a non-dedicated public communications channel between a controller associated with the database and a portable electronic device distinct and remotely located from the database, and transferring at least the first account information and the second account information from the database to a memory of the portable electronic device via the communication link so that at least the first account information and the second account information are caused to exist simultaneously in the memory of the portable electronic device;
(C) transporting the portable electronic device to a vicinity of a first point-of-sale (POS) terminal;
(D) when the portable electronic device is in the vicinity of the first POS terminal, manipulating a user input of the portable electronic device to select the first media for use in a first transaction at the first POS terminal;
(E1) causing a token attached to the portable electronic device to embody at least a portion of the first account information;
(E2) after performing the step (E1), detaching the token from the portable electronic device, with the token continuing to embody at least the portion of the first account information after the token has been detached from the portable electronic device;
(E3) after performing the step (E2), and when the token is still detached from the portable electronic device, interfacing the token with the first POS terminal and transferring at least the portion of the first account information from the token to the first POS terminal;
(E4) after performing the step (E3), reattaching the token to the portable electronic device;
(F) transporting the portable electronic device to a vicinity of a second POS terminal;
(G) when the portable electronic device is in the vicinity of the second POS terminal, manipulating the user input on the portable electronic device to select the second media for use in a second transaction at the second POS terminal;
(H1) causing the token to embody at least a portion of the second account information;
(H2) after performing the step (H1), detaching the token from the portable electronic device, with the token continuing to embody at least the portion of the second account information after the token has been detached from the portable electronic device;
(H3) after performing the step (H2), and when the token is still detached from the portable electronic device, interfacing the token with the second POS terminal and transferring at least the portion of the second account information from the token to the second POS terminal; and
(H4) after performing the step (H3), re-attaching the token to the portable electronic device.
2. The method of claim 1, further comprising steps of:
(I) employing a user-authenticator included in the first portable electronic device to authenticate an identity of a user of the first portable electronic device; and
(J) enabling each of the steps (E2) and (H2) to be performed only after the user authenticator has authenticated the identity of the user.
3. The method of claim 2, wherein the step (I) comprises:
measuring a biometric characteristic of the user of the portable electronic device; and
comparing the measured biometric characteristic with a representation of a biometric characteristic stored in memory of the portable electronic device.
4. The method of claim 1, wherein the first and second media issuers are unrelated.
5. The method of claim 1, further comprising steps of:
(I) storing at least third account information for a third media issued by a third media issuer and fourth account information for a fourth media issued by a fourth media issuer in the database so that the first account information, second account information, third account information, and fourth account information exist simultaneously in the database;
(J) establishing a second communication link via a non-dedicated public communications channel between the controller associated with the database and a second portable electronic device distinct and remotely located from the database, and transferring at least the third account information and the fourth account information from the database to a memory of the second portable electronic device via the second communication link so that at least the third account information and the fourth account information are caused to exist simultaneously in the memory of the second portable electronic device;
(K) transporting the second portable electronic device to a vicinity of a third POS terminal;
(L) when the second portable electronic device is in the vicinity of the third POS terminal, manipulating a user input of the second portable electronic device to select the third media for use in a third transaction at the third POS terminal;
(M1) causing a second token attached to the second portable electronic device to embody at least a portion of the third account information;
(M2) after performing the step (M1), detaching the second token from the second portable electronic device, with the second token continuing to embody at least the portion of the third account information after the second token has been detached from the second portable electronic device;
(M3) after performing the step (M2), and when the second token is still detached from the second portable electronic device, interfacing the second token with the third POS terminal and transferring at least the portion of the third account information from the second token to the third POS terminal;
(M4) after performing the step (M3), re-attaching the second token to the second portable electronic device;
(N) transporting the second portable electronic device to a vicinity of a fourth POS terminal;
(O) when the second portable electronic device is in the vicinity of the fourth POS terminal, manipulating the user input on the second portable electronic device to select the fourth media for use in a fourth transaction at the fourth POS terminal;
(P1) causing the second token to embody at least a portion of the fourth account information;
(P2) after performing the step (P1), detaching the second token from the second portable electronic device, with the second token continuing to embody at least the portion of the fourth account information after the second token has been detached from the second portable electronic device;
(P3) after performing the step (P2), and when the second token is still detached from the second portable electronic device, interfacing the second token with the fourth POS terminal and transferring at least the portion of the fourth account information from the second token to the fourth POS terminal; and
(P4) after performing the step (P3), re-attaching the second token to the second portable electronic device.
6. The method of claim 1, wherein the step (E1) further comprises causing the token to embody at least the portion of the first account information so that at least the portion of the first account information can be read from the token by a magnetic stripe reader.
7. The method of claim 6, wherein the step (E1) further comprises causing a simulated magnetic stripe to be generated on the token.
8. The method of claim 1, further comprising steps of:
(I) employing a user-authenticator included in the first portable electronic device to authenticate an identity of a user of the first portable electronic device; and
(J) enabling the transfer of at least the first account information and the second account information from the database to the memory of the portable electronic device to be performed only after the user authenticator has authenticated the identity of the user.
9. The method of claim 8, wherein the first and second media issuers are unrelated, and the method further comprises steps of:
enabling the transfer of the first account information from the database to the memory of the portable electronic device to be performed only after the controller associated with the database has received an authorization signal from the first media issuer; and
enabling the transfer of the second account information from the database to the memory of the portable electronic device to be performed only after the controller associated with the database has received an authorization signal from the second media issuer.
10. The method of claim 1, wherein the first and second media issuers are unrelated, and the method further comprises steps of:
enabling the transfer of the first account information from the database to the memory of the portable electronic device to be performed only after the controller associated with the database has received an authorization signal from the first media issuer; and
enabling the transfer of the second account information from the database to the memory of the portable electronic device to be performed only after the controller associated with the database has received an authorization signal from the second media issuer.
11. The method of claim 1, wherein the communications link comprises a secure communications link.
12. A method, comprising steps of:
(A) storing a first version of information including at least first account information for a first media issued by a first media issuer and second account information for a second media issued by a second media issuer in a memory of a portable electronic device so that at least the first account information and the second account information exist simultaneously in the memory;
(B) storing a second version of information including at least the first account information and the second account information in a database in communication with a transfer server distinct and remotely located from the portable electronic device so that at least the first account information and the second account information exist simultaneously in the database;
(C) transporting the portable electronic device to a vicinity of a first point-of-sale (POS) terminal;
(D) when the portable electronic device is in the vicinity of the first POS terminal, manipulating a user input on the portable electronic device to select the first media for use in a first transaction at the first POS terminal;
(E1) causing a token attached to the portable electronic device to embody at least a portion of the first account information;
(E2) after performing the step (E1), detaching the token from the portable electronic device, with the token continuing to embody at least the portion of the first account information after the token has been detached from the portable electronic device;
(E3) after performing the step (E2), and when the token is still detached from the portable electronic device, interfacing the token with the first POS terminal and transferring at least the portion of the first account information from the token to the first POS terminal;
(E4) after performing the step (E3), reattaching the token to the portable electronic device;
(F) transporting the portable electronic device to a vicinity of a second POS terminal;
(G) when the portable electronic device is in the vicinity of the second POS terminal, manipulating the user input on the portable electronic device to select the second media for use in a second transaction at the second POS terminal;
(H1) causing the token to embody at least a portion of the second account information;
(H2) after performing the step (H1), detaching the token from the portable electronic device, with the token continuing to embody at least the portion of the second account information after the token has been detached from the portable electronic device;
(H3) after performing the step (H2), and when the token is still detached from the portable electronic device, interfacing the token with the second POS terminal and transferring at least the portion of the second account information from the taken to the second POS terminal;
(H4) after performing the step (H3), re-attaching the token to the portable electronic device;
(I) altering one of the first version of information stored in the memory of the portable electronic device and the second version of information stored in the database; and
(J) establishing a communication link via a non-dedicated public communications channel between a controller associated with the database and the portable electronic device, and communicating commands between the controller associated with the database and the portable electronic device that cause the alteration in the one of the first version of information stored in the memory of the portable electronic device and the second version of information stored in the database to be reflected in the other of the first version of information stored in the memory of the portable electronic device and the second version of information stored in the database.
13. The method of claim 12, further comprising steps of:
(K) employing a user-authenticator included in the portable electronic device to authenticate an identity of a user of the portable electronic device; and
(L) enabling each of the steps (E2) and (H2) to be performed only after the user authenticator has authenticated the identity of the user.
14. The method of claim 13, wherein the step (K) comprises:
measuring a biometric characteristic of the user of the portable electronic device; and
comparing the measured biometric characteristic with a representation of a biometric characteristic stored in memory of the portable electronic device.
15. The method of claim 12, wherein the first and second media issuers are unrelated.
16. The method of claim 12, wherein the step (E1) further comprises causing the token to embody at least the portion of the first account information so that at least the portion of the first account information can be read from the token by a magnetic stripe reader.
17. The method of claim 16, wherein the step (E1) further comprises causing a simulated magnetic stripe to be generated on the token.
18. The method of claim 12, further comprising steps of:
(K) employing a user-authenticator included in the first portable electronic device to authenticate an identity of a user of the first portable electronic device; and
(L) enabling the communication of commands between the controller associated with the database and the portable electronic device that cause the alteration in the one of the first version of information stored in the memory of the portable electronic device and the second version of information stored in the database to be reflected in the other of the first version of information stored in the memory of the portable electronic device and the second version of information stored in the database to take place only after the user authenticator has authenticated the identity of the user.
19. The method of claim 12, wherein the communications link comprises a secure communications link.
20. A system, comprising:
a transferring server comprising a database and a database controller, the database having stored therein so as to be accessible by the database controller at least first account information for a first media issued by a first media issuer and second account information for a second media issued by a second media issuer; and
a portable electronic device, distinct and remotely located from the network server, comprising a device controller, a memory, a user input device, a port, and a token releasably retained in the port, the device controller being configured to establish a communication link with the network server via a non-dedicated public communications channel and to enable a transfer of at least the first account information and the second account information from the database to the memory of the portable electronic device via the communication link, the device controller being further configured to select one of the first media and the second media for use in a transaction at a point-of-sale (POS) terminal in response to manipulation of the user input device, and to cause the token to embody at least a portion of the one of the first account information and the second account information that corresponds to the selected one of the first media ard the second media, the token being configured so that after the token is released from the port, the token can be interfaced with the POS terminal to transfer the information embodied by the token to the POS terminal.
21. The system of claim 20, wherein the portable electronic device further comprises a user-authenticator to authenticate an identity of a user of the portable electronic device, and the device controller is configured to enable the token embodying the one of the first account information and the second account information to be released from the port only after the user authenticator has authenticated the identity of the user.
22. The method of claim 21, wherein the user authenticator is configured to analyze a biometric characteristic of the user.
23. The system of claim 20, wherein the first and second media issuers are unrelated.
24. The system of claim 20, wherein the device controller is further configured to cause the token to embody at least the portion of the one of the first account information and the second account information that corresponds to the selected one of the first media and the second media so that the information embodied by the token can be read by a magnetic stripe reader included in the POS terminal.
25. The system of claim 24, wherein the device controller is further configured to cause the token to generate a simulate magnetic stripe that represents at least the portion of the one of the first account information and the second account information that corresponds to the selected one of the first media and the second media.
26. The system of claim 20, wherein the portable electronic device further comprises a user-authenticator to authenticate an identity of a user of the portable electronic device, and wherein the network server is configured to enable the transfer of at least the first account information and the second account information from the database to the memory of the portable electronic device to be performed only after the user authenticator has authenticated the identity of the user.
27. The system of claim 26, wherein the first and second media issuers are unrelated, and wherein the network server is further configured to enable the transfer of the first account information from the database to the memory of the portable electronic device to be performed only after the database controller has received an authorization signal from the first media issuer, and to enable the transfer of the second account information from the database to the memory of the portable electronic device to be performed only after the database controller has received an authorization signal from the second media issuer.
28. The system of claim 20, wherein the first and second media issuers are unrelated, and wherein the network server is further configured to enable the transfer of the first account information from the database to the memory of the portable electronic device to be performed only after the database controller has received an authorization signal from the first media issuer, and to enable the transfer of the second account information from the database to the memory of the portable electronic device to be performed only after the database controller has received an authorization signal from the second media issuer.
29. The system of claim 20, wherein the communications link comprises a secure communications link.
30. A system, comprising:
a transferring server comprising a database controller in communication with a database, the database having stored therein a first version of information including at least first account information for a first media issued by a first media issuer and second account information for a second media issued by a second media issuer; and
a portable electronic device, distinct and remotely located from the network server, comprising a device controller, a memory, a user input device, a port, and a token releasably retained in the port, the memory having stored therein a second version of information including at least the first account information and the second account information, the device controller being configured to establish a communication link with the network server via a non-dedicated public communications channel and to enable communication of commands between the database controller and the device controller that cause alterations in one of the first version of information stored in the database and the second version of information stored in the memory to be reflected in the other of the first version of information stored in the database and the second version of information stored in the memory, the device controller being further configured to select one of the first media and the second media for use in a transaction at a point-of-sale (POS) terminal in response to manipulation of the user input device, and to cause the token to embody at least a portion of the one of the first account information and the second account information that corresponds to the selected one of the first media and the second media, the token being configured so that, after the token is released from the port, the token can be interfaced with the POS terminal to transfer the information embodied by the token to the POS terminal.
31. The system of claim 30, wherein the portable electronic device further comprises a user-authenticator to authenticate an identity of a user of the portable electronic device, and the device controller is configured to enable the token embodying the one of the first account information and the second account information to be released from the port only after the user authenticator has authenticated the identity of the user.
32. The system of claim 31, wherein the user authenticator is configured to analyze a biometric characteristic of the user.
33. The system of claim 30, wherein the device controller is further configured to cause the token to embody at least the portion of the one of the first account information and the second account information that corresponds to the selected one of the first media and the second media so that the information embodied by the token can be read by a magnetic stripe reader included in the POS terminal.
34. The system of claim 33, wherein the device controller is further configured to cause the token to generate a simulate magnetic stripe that represents at least the portion of the one of the first account information and the second account information that corresponds to the selected one of the first media and the second media.
35. The system of claim 30, wherein the first and second media issuers are unrelated.
36. The system of claim 30, wherein the portable electronic device further comprises a user-authenticator to authenticate an Identity of a user of the portable electronic device, and the network server is configured to enable communication of commands between the database controller and the device controller that cause alterations in one of the first version of information stored in the database and the second version of information stored in the memory to be reflected in the other of the first version of information stored in the database and the second version of information stored in the memory to take place only after the user authenticator has authenticated the identity of the user.
37. The system of claim 30, wherein the communications link comprises a secure communications link.
38. A system, comprising:
a transferring server in communication with a database having stored therein at least first account information for a first media issued by a first media issuer and second account information for a second media issued by a second media issuer;
a portable electronic device, distinct and remotely located from the database, comprising a memory, a port, and a token releasably retained in the port;
means for establishing a communication link via a non-dedicated public communications channel between a controller associated with the database and the portable electronic device, and for transferring at least the first account information and the second account information from the database to the memory of the portable electronic device via the communication link so that at least the first account information and the second account information are caused to exist simultaneously in the memory of the portable electronic device;
means for selecting one of the first media and the second media for use in a transaction at a point-of-sale (POS) terminal;
means for causing the token to embody at least a portion of one of the first account information and the second account information that corresponds to the selected one of the first media and the second media; and
means for releasing the token from the port so that the token can be used to authorize the transaction at the POS terminal.
39. A system, comprising:
a portable electronic device comprising a memory having stored therein a first version of information including at least first account information for a first media issued by a first media issuer and second account information for a second media issued by a second media issuer, means for selecting one of the first media and the second media for use in a transaction at a point-of-sale (POS) terminal, a port, a token releasably retained in the port, means for causing the token to embody at least a portion of one of the first account information and the second account information that corresponds to the selected one of the first media and the second media, and means for releasing the token from the port so that the token can be used to authorize the transaction at the POS terminal;
a transferring server in communication with a database, distinct and remotely located from the portable electronic device, having stared therein a second version of information including at least the first account information and the second account information; and
means for establishing a communication link via a non-dedicated public communications channel between a controller associated with the database and the portable electronic device, and for causing alterations In one of the first version of information stored in the portable electronic device and the second version of information stored in the database to be reflected in the other of the first version of information stored in the portable electronic device and the second version of information stored in the database.
Description
FIELD OF THE INVENTION
The present inventions are directed to novel systems and methods for engaging in transactions involving financial and/or non-financial media.
BACKGROUND OF THE INVENTION
People often times carry wallets with them when they engage in their day to day activities. A typical wallet is made of leather or other suitable material, and is generally a foldable structure that readily fits into a pocket or purse. A wallet typically includes a number of pockets, pouches, or the like for storing items such as a driver's license, a social security card, identification cards, credit cards, debit cards, membership cards, commuter passes, access tools, business cards, cash, coupons, event tickets, transportation tickets, frequent customer cards (e.g., a frequent flier card), medical information cards, receipts, photographs, etc.
Wallets are frequently stolen, lost, or misplaced. When any of these events occurs, not only must the wallet itself be replaced, but all of the contents of the wallet must be replaced as well. As anyone who has lost a wallet can testify, replacing the contents of a wallet can be cumbersome and expensive. In addition, if a wallet is stolen or if a lost wallet falls into the wrong hands, the contents of the wallet may be used to engage in unauthorized activities which financially detriment the wallet owner, as well as any banks, credit issuers, and/or other institutions that issued financial media to the wallet owner.
While the wallet owner is generally able to "cancel" financial media in such situations by contacting the respective financial media issuers, often times this is done too late, i.e., after one or more media have been exploited by the unauthorized user. In some cases, the wallet owner may not recall all of the contents of the now stolen wallet, and so fail to report the theft of one or more items. Further, in addition to any cash contained in a lost or stolen wallet, many media issued by non-financial media issuers have a significant cash value, e.g., transportation tickets, event tickets, commuter passes, and the like, and therefore represent an immediate (and often times unrecoverable) financial loss to the wallet owner. Moreover, the misappropriation of media issued by non-financial media issuers that contain personal information, e.g., a drivers license, social security card, identification card, etc., present the opportunity for an unauthorized possessor of a wallet to engage in the practice known as "identity theft," whereby the possessor may assume the identity of the wallet owner for various fraudulent purposes, e.g., using the assumed identity to obtain and exploit one or more new financial media.
SUMMARY OF THE INVENTION
According to one aspect of the present invention, an apparatus includes a housing; a user authenticator, supported by the housing, that authenticates an identity of a user; at least one memory, supported by the housing, that stores transaction information for at least first and second media; and at least one output supported by the housing, that releases at least a portion of the transaction information to a point-of-sale (POS) terminal after the user authenticator has authenticated the identity of the user.
According to another aspect of the present invention, a method involves steps of: (a) storing transaction information for at least first and second media in a memory of a device (b) using the device to authenticate an identity of a user; and (c) after authenticating the identity of the user with the device, transferring at least a portion of the transaction information from the device to a point-of-sale (POS) terminal.
According to another aspect of the present invention, an apparatus includes: a housing; at least one memory, supported by the housing, that stores transaction information for at least one media; a user authenticator, supported by the housing, that authenticates an identity of a user of the apparatus; and at least one output, supported by the housing, that, after the user authenticator has authenticated the identity of the user, releases an embedded identification code of the apparatus from the housing that enables a device receiving the embedded identification ID code to authenticate the identity of the apparatus.
According to another aspect of the present invention, a method involves steps of: storing transaction information for at least one media in a memory of a first device; using the first device to authenticate an identity of a user; and after authenticating the identity of the user with the first device, releasing an embedded identification code of the apparatus from the housing that enables a second device receiving the embedded identification code to authenticate the identity of the first device.
According to another aspect of the present invention, an apparatus includes: at least one memory that stores transaction information for at least first and second media; at least one input that enables a user to select one of the at least first and second media; a display that provides a visual indication to the user regarding which of the at least first and second media has been selected with the at least one input; and at least one output that selectively releases at least a portion of the transaction information to a point-of-sale (POS) terminal.
According to another aspect of the present invention, a method involves steps of: storing transaction information for at least first and second media in a memory of a device; receiving as input a user's selection of one of the at least first and second media; displaying a visual indication to the user regarding which of the at least first and second media has been selected; and transferring at least a portion of the transaction information from the device to a point-of-sale (POS) terminal.
According to another aspect of the present invention, an apparatus includes: at least one memory that stores transaction information for at least one financial media and at least one non-financial media; and at least one output that selectively releases at least a portion of the transaction information to a point-of-sale (POS) terminal.
According to another aspect of the present invention, a method involves steps of: storing transaction information for at least one financial media and at least one non-financial media in a memory of a device; and transferring at least a portion of the transaction information from the device to a point-of-sale (POS) terminal.
According to another aspect of the present invention, a system includes: a housing; at least one memory, supported by the housing, that stores transaction information for at least one media; a device releasably attached to the housing; and configuring means, supported by the housing, for selectively configuring the device to hold the transaction information so that the device may be used to engage in a transaction involving the at least one media.
According to another aspect of the present invention, a method involves steps of: (a) storing transaction information for at least one media in a memory of a first device, the first device having a second device releasably attached thereto; (b) while the second device is attached to the first device, configuring the second device to hold the transaction information for the at least one media based on the contents of the memory; (c) detaching the second device from the first device; and (d) using the second device to engage in a transaction involving the at least one media.
According to another aspect of the present invention, a system includes: a first device including a user authenticator that authenticates an identity of a user; and a second device releasably attached to the first device, wherein the second device holds transaction information for at least one media so that the second device may be used to engage in a transaction involving the at least one media, and wherein the second device is detached from the first device after the user authenticator has authenticated the identity of the user.
According to another aspect of the present invention, a method involves steps of: with a first device, authenticating an identity of a user; and after authenticating the identity of a user with the first device, detaching a second device from the first device, the second device holding transaction information for at least one media so that the second device may be used to engage in a transaction involving the at least one media.
According to another aspect of the present invention, a system includes: a first device; a second device that has the first device releasably attached thereto, the second device including means for selectively configuring the first device to hold transaction information for a first media but not for a second media so that the first device may be used to engage in a transaction involving the first media but not the second media, and the second device further including means for selectively configuring the first device to hold transaction information for the second media but not for the first media so that the first device may be used to engage in a transaction involving the second media but not the first media.
According to another aspect of the present invention, a method involves steps of: selectively configuring a device to hold transaction information for a first media but not for a second media so that the device may be used to engage in a transaction involving the first media but not the second media; and selectively configuring the device to hold transaction information for the second media but not the first media so that the device may be used to engage in a transaction involving the second media but not the first media.
According to another aspect of the present invention, a system includes: at least one memory that stores first transaction information for a first media; at least one output that selectively releases at least a portion of the first transaction information to a point-of-sale (POS) terminal; and means for enabling a person to whom the first media is issued to selectively add second transaction information for a second media to the memory.
According to another aspect of the present invention, a method involves steps of: storing first transaction information for a first media in a memory of a device; releasing at least a portion of the first transaction information to a point-of-sale (POS) terminal; and in response to a request by the person to whom the first transaction information is issued, adding second transaction information for a second media to the memory.
According to another aspect of the present invention, a system includes: at least one memory that stores first transaction information for a first media and second transaction information for a second media; at least one output that selectively releases at least a portion of the first transaction information to a point-of-sale (POS) terminal; and means for enabling a person to whom the first media is issued to selectively remove at least a portion of the second transaction information from the memory.
According to another aspect of the present invention, a method involves steps of: storing first transaction information for a first media and second transaction information for a second media in a memory of a device; releasing at least a portion of the first transaction information to a point-of-sale (POS) terminal; and, in response to a request by the person to whom the second media is issued, removing at least a portion of the second transaction information from the memory.
According to another aspect of the present invention, a system includes: at least one memory that stores transaction information for at least one media; at least one output that selectively releases at least a portion of the transaction information to a point-of-sale (POS) terminal; and means for enabling at least one functional characteristic of the at least one media to be altered by altering the contents of the least one memory.
According to another aspect of the present invention, a method involves: storing transaction information for at least one media in a memory of a device; releasing at least a portion of the transaction information to a point-of-sale (POS) terminal; and altering at least one functional characteristic of the at least one media by altering the contents of the least one memory.
According to another aspect of the present invention, an apparatus includes: a housing; a user authenticator, supported by the housing, that authenticates an identity of a user; at least one memory that, supported by the housing, stores first transaction information for a first media and second transaction information for a second media; and at least one output, supported by the housing, that releases the first transaction information only after the user authenticator has authenticated the identity of the user, and that releases the second information without requiring the user authenticator to have authenticated the identity of the user.
According to another aspect of the present invention, a method involves steps of: storing first transaction information for a first media and second transaction information for a second media in at least one memory of a device; using the device to authenticate an identity of a user; releasing the first transaction information only after the identity of the user has been authenticated; and releasing the second transaction information without requiring the identity of the user to be authenticated.
According to another aspect of the present invention, a system includes: a first device; and a second device having the first device releasably attached thereto such that, when the first device is attached to the second device, the second device causes the first device to generate a machine-readable code for only a predetermined, finite period of time after the first device is detached from the second device.
According to another aspect of the present invention, a method involves a step of generating a machine-readable code on a device for only a predetermined, finite period of time.
According to another aspect of the present invention, an apparatus includes: a portable substrate; a power supply supported by the substrate; and at least one controller supported by the substrate and powered by the power supply, the at least one controller being configured to generate a simulated magnetic stripe on the substrate.
According to another aspect of the present invention, an method involves a step of generating a simulated magnetic stripe on a portable device.
According to another aspect of the present invention, a system includes: at least one memory that stores transaction information for at least one media; a user authenticator that authenticates an identity of the user; and a display that provides a visual indication to the user regarding the at least one media, the visual indication being displayed for only a predetermined, finite period of time after the user authenticator has authenticated the identity of the user.
According to another aspect of the present invention, a method involves steps of: authenticating an identity of a user; and displaying a visual indication to the user regarding the at least one media for only a predetermined, finite period of time after authenticating the identity of the user.
According to another aspect of the present invention, a system includes a portable device that can be used to engage in point-of-sale (POS) transactions; and a device remote from the portable device, that can disable an ability of the portable device to engage in POS transactions.
According to another aspect of the present invention, a method involves steps of: providing a portable device that can be used to engage in point-of-sale transactions; and at a location remote from the portable device, disabling an ability of the portable device to engage in POS transactions.
According to another aspect of the present invention, a method involves steps of: storing transaction authorization information for at least two media in a first memory of a first device; and storing the transaction authorization information for the at least two media in a second memory, which is disposed at a location remote from the first device.
According to another aspect of the present invention, a system includes: a first device; and a second device having the first device releasably attached thereto such that, when the first device is attached to the second device, the second device can cause the first device to generate a machine-readable code after the first device is detached from the second device, the second device including at least one controller configured so as to be capable of causing the first device to generate the machine-readable code only for a finite, predetermined period of time.
According to another aspect of the present invention, a method involves a step of configuring a first device such that the first device is capable, for only a predetermined, finite period of time, of generating a machine-readable code on a second device.
According to another aspect of the present invention, a method involves steps of: receiving information at a first device that has been transmitted over an electronic communication link; and after receiving the information at the first device, using a media at the first device to access a quantity of credit or cash reserves that could not be accessed prior to the first device receiving the information.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram illustrating an example of a network system in which a portable electronic authorization device (also referred to herein as a "Pocket Vault") may be employed according to one embodiment of the invention;
FIG. 2 is a block diagram showing an illustrative embodiment of the Pocket Vault shown in FIG. 1;
FIG. 3 is a block diagram showing an illustrative embodiment of one of the interface stations shown in FIG. 1;
FIG. 4 is a block diagram showing an illustrative embodiment of the network server(s) shown in FIG. 1;
FIG. 5 is a diagram showing an example of how the memory of the Pocket Vault shown in FIG. 2 may be configured in accordance with one embodiment of the invention;
FIG. 6 is a block diagram showing an illustrative embodiment of the card associated with the Pocket Vault shown in FIG. 2;
FIG. 7 is a flow diagram illustrating a primary routine that may be executed by the controller of the Pocket Vault shown in FIG. 2;
FIG. 8 is a flow diagram illustrating an example implementation of the PROCESS FINGERPRINT STORAGE routine shown in FIG. 7;
FIG. 9 is a flow diagram illustrating an example implementation of the UNAUTHORIZED HOLDER routine shown in FIG. 7;
FIG. 10 is a flow diagram illustrating an example implementation of the AUTHORIZED HOLDER routine shown in FIG. 7;
FIG. 11 is a flow diagram illustrating an example implementation of the PROCESS CARD TRANSACTION routine shown in FIG. 10;
FIG. 12 is a flow diagram illustrating an example implementation of the VERIFY CARD RETURN routine shown in FIG. 7;
FIG. 13 is a flow diagram illustrating an example implementation of a primary routine that may be executed by the controller of the pocket vault interface unit shown in FIG. 3;
FIG. 14 is a flow diagram illustrating an example implementation of a primary routine that may be executed by the controller of the interface station computer shown in FIG. 3;
FIG. 15 is a flow diagram illustrating an example implementation of the PROCESS REQUEST TO VALIDATE POCKET VAULT routine shown in FIG. 14;
FIG. 16 is a flow diagram illustrating an example implementation of the PROCESS REQUEST TO UPDATE INFO ON POCKET VAULT routine shown in FIG. 14;
FIG. 17 is a flow diagram illustrating an example implementation of the PROCESS REQUEST TO AUTHORIZE TRANSACTION routine in FIG. 14;
FIG. 18 is a flow diagram illustrating an example implementation of the PROCESS UNSUCCESSFUL OPERATOR AUTHENTICATION routine shown in FIG. 14;
FIG. 19 is a flow diagram illustrating an example implementation of a primary routine that may be executed by the controller(s) of the network server(s) shown in FIG. 4;
FIG. 20 is a flow diagram illustrating an example implementation of the PROCESS REQUEST TO REGISTER NEW POCKET VAULT HOLDER routine shown in FIG. 19;
FIG. 21 is a flow diagram illustrating an example implementation of the PROCESS REQUEST BY MEDIA ISSUER/ADVERTISER TO UPDATE NETWORK SERVER routine shown in FIG. 19;
FIG. 22 is a flow diagram illustrating an example implementation of the PROCESS REQUEST TO UPDATE INFO ON POCKET VAULT routine shown in FIG. 19;
FIG. 23 is a flow diagram illustrating an example implementation of the PROCESS REQUEST FROM HOLDER TO LOAD NEW FILE ONTO NETWORK SERVER routine shown in FIG. 19;
FIG. 24 is a flow diagram illustrating an example implementation of the PROCESS REQUEST TO AUTHORIZE TRANSACTION routine shown in FIG. 19;
FIG. 25 is a flow diagram illustrating an example implementation of the AUTHORIZED POCKET VAULT USE? routine shown in each of FIGS. 20, 22, and 24; and
FIGS. 26a-26p are illustrations of the portable electronic authorization device, as well as the token associated therewith, as these items may appear when in use.
DETAILED DESCRIPTION
A new method and system for producing, distributing, storing, and using the typical contents of an individual's wallet is disclosed herein. Essentially, the system may enable individuals to replace nearly all of the paper and plastic contents of their wallets with a single, hand-held portable electronic authorization device. The system may include the portable electronic authorization devices, removable morphing tokens associated with such devices, associated computer peripherals, software and certain network capabilities. As a whole, the system may eliminate virtually all of the distribution costs and security concerns associated with paper and plastic media.
Because the device may incorporate many different media that are commonly stored in a person's wallet, possibly including both financial and non-financial media, it is much more than a simple point-of-sale (POS) device. Therefore, the device may be more appropriately referred to as a multi-purpose, "point-of-transaction" device. In any situation of presentment, whether for purposes such as building security, demonstrating membership or using credit or debit capacity, the system is designed to perform tasks more safely, securely and with greater ease than is possible with prior art systems. Further, while certain computer technologies are involved, the preferred embodiment is such that some people may barely recognize it as a computer, seeing instead a more comfortable to carry, easier-to-use, safer and more securely packaged means of transporting typical wallet contents.
The system's business model may comprise an independent organization acting as a media-neutral multi-service provider of other issuers' various financial and non-financial media, that also may enable individuals and retailers to add or create their own secure (and where appropriate, non-secure media) using a device with a self-contained set of authentication security features, which may even be password-free. This device may operate over existing financial transaction networks, while also having links to a highly secure network system for certain functionality. The self-contained authentication functionality of the device itself ensures privacy, while providing sufficient accountability/traceability to satisfy law enforcement concerns.
A network system 100 configured according to one illustrative embodiment of the invention is shown in FIG. 1. As shown, the network system 100 may include a portable electronic authorization device 102 (alternatively referred to herein as a "Pocket Vault") and an associated token 102a (alternatively referred to herein as a "Chameleon Card"). Each person desiring to use the network system 100 may possess his or her own Pocket Vault 102 and associated token 102a. Some individuals may choose to own multiple Pocket Vaults or Chameleon Cards. The system and software therefore may accommodate the use of multiple Pocket Vaults and multiple Chameleon Cards by one individual.
Referring to FIG. 1, in addition to the Pocket Vault 102, the network system 100 may include one or more network servers 114 to which various other network components are coupled. Although multiple, load-sharing network servers 114 may be employed in a typical application, the network server(s) 114 will hereinafter, for convenience, be referred to as a single network server 114. Coupled to the network server 114 are: several different types of interface stations 104 (i.e., a validation interface station 104a, a personal interface station 104b, and a commercial interface station 104c), one or more commercial card readers 106, one or more commercial bar code readers 107, and several computers 108, 110, and 112 operated by one or more advertisers, non-financial media issuers, and financial media issuers, respectively. The structure and functionality of each of the components of the network system 100 in accordance with one illustrative embodiment of the invention are described below.
As shown in FIG. 1, the network server 114 may form the hub of the network system 100, with each of the interface stations 104, the commercial card reader 106, the commercial bar code reader 107, and the computers 108, 110, and 112 being coupled thereto. As discussed in more detail below, the network server 114 may therefore serve as: (1) a repository of information for the network, (2) the entity that controls access to the stored information by the other network devices, and (3) a service provider for financial and non-financial media issuers, advertisers, as well as Pocket Vault holders.
Any of a number of techniques may be used to interconnect the various elements of the network system 100, and the invention is not limited to any particular networking technique. In one illustrative embodiment, for example, the network server 114 is coupled to the other elements in the network system 100 via the Internet or similar packet-switched communication system. Alternatively, dedicated or selectively established (e.g., using a dial-up modem) communication channels or time slots thereof may be employed between the respective devices. The connections between the network devices may be either hardwired (including fiber optic connections) or wireless (e.g., infrared (IR) or radio frequency (RF) links).
As shown in FIG. 1, the Pocket Vault 102 may be interfaced with any of the interface stations 104a-c so as to permit information to be uploaded from the network server 114 to the Pocket Vault 102, or to be downloaded from the Pocket Vault 102 to the network server 114. In one illustrative embodiment, each of the interface stations 104 includes a docking mechanism that permits a Pocket Vault 102 to by physically, as well as electronically, interfaced therewith. In such an embodiment, once the Pocket Vault 102 is physically "docked" with an interface station 104, the Pocket Vault 102 may communicate with the interface station 104 using any now known or later discovered technique. For example, physical contact may be made between respective electrodes or plugs, a line of sight (e.g., infrared) wireless link may be established, or any other interfacing technique may be employed.
The Pocket Vault 102 may additionally or alternatively be configured such that it need not be physically docked with or even in the same room as the interface station 104, as a wireless network such as Bluetooth may be employed to permit communication between devices on the network system 100. In fact, in some embodiments wherein appropriate networking capabilities are provided, each Pocket Vault 102 may communicate directly with the network server 114, without the interface stations 104a-c facilitating communication therebetween. In addition, in some embodiments, Pocket Vaults 102 may communicate directly with one another. In such embodiments, such inter-device communication may permit value to be exchanged directly between Pocket Vaults 102.
The personal docking station 104b may allow setting or changing of user preferences, recording of miscellaneous information by the Pocket Vault holder, replenishment or deletion of information regarding particular media, and may also permit additional media (e.g., a library card) to be added to the device. The Pocket Vault holder may, for example, directly add non-value-based media (e.g., a membership number for the local Historical Society) and notes. In one embodiment, value-based and certain identification media (a driver's license, passport, building security ID, etc.) may be added or reinstated only through a secure connection to the network server 114 (as described below), in response to an update request from the Pocket Vault holder. In addition, the personal interface station may provide a mechanism to download transaction activity involving the Pocket Vault 102 into an individual's home computer. There are many users of home finance software. These applications can be relatively "data hungry," and commonly require users to download checking and debit card data from their banks (or key it in manually) and to key in the details of credit card and cash purchases. All of this keying and internet file downloading from third parties may be replaced by a simple docking procedure, i.e., when the Pocket Vault 102 is interfaced with the personal docking station 102b.
As shown in FIG. 1, and as described below in more detail, the Pocket Vault 102 may be equipped to generate the token 102a such that the token 102a has transactional information regarding a media (e.g., a simulated magnetic strip or a bar code) produced thereon. In such an embodiment, after the token 102a has been generated, the token 102a may be used by the Pocket Vault holder to engage in a transaction wherein an entity swipes the simulated magnetic stripe of the token 102a through a card reader 106 or scans the bar code on the token 102a using a bar code reader 107. Additionally or alternatively, the token 102a may include a suitable Smartcard interface so that the Chameleon Card 102 may be used with Smartcard compatible devices.
Because the token 102a may be caused to take on a different personality each time it is released from the Pocket Vault 102, a plurality of media may be stored electronically in memory of the Pocket Vault 102, and the token 102a may, upon request, be generated to take on the personality selected by the Pocket Vault holder. The respective media stored on the Pocket Vault may be issued by different and unrelated media issuers. As used herein, two media issuers are "unrelated" if there exists no legal relationship between them. The token 102a may also have display capacity, sufficient to indicate the media personality that it has taken on. This may or may not include display of the specific identity that is temporarily encoded on the token 102a. In some embodiments, value may be exchanged between two Pocket Vaults 102 when one Pocket Vault 102 generates a token 102a having a value-based or value-linked media stored thereon, and the token 102a so generated is passed to the other Pocket Vault 102, which then may then access the media and extract value therefrom or add value thereto. As mentioned above, this sort of value exchange may also be accomplished directly between two Pocket Vaults 102 over a wireless network, such as Bluetooth.
As discussed in more detail below, in addition to or in lieu of the token 102a, the Pocket Vault 102 may also generate a bar code for a selected media on the Pocket Vault's display (not shown in FIG. 1), and the bar code reader 107 may be used to scan the displayed bar code to process a transaction. Further, a transaction may be processes via a commercial interface station 104c either by use of a docking terminal or via a wireless network scheme such a Bluetooth. In one embodiment, some commercial interface stations 104c may comprise an interface station linked to a standard commercial card reader 106 or commercial bar code reader 107, with the card reader 106 or bar code reader 107 being modified to accept input from the station.
To permit the Pocket Vault holder to select from among the various media stored in memory of the Pocket Vault 102, the Pocket Vault 102 may comprise a display (not shown in FIG. 1). By employing either a display having a user-manipulable touch screen or a separate user input device (not shown in FIG. 1), a Pocket Vault holder can effectively flip through the contents of the Pocket Vault 102 to locate and select a desired media (e.g., a credit card, driver's license, library card, frequent flier card, etc.) much like a person can flip through the contents of his or her wallet to do the same.
The use of a display on the Pocket Vault 102 also creates an opportunity for media providers to go from a static presentation of their brand (logo, etc.) to having the option of dynamic branding and messaging. In addition, using the display, the presentment of active marketing at the "moment of buying decision" is possible. Specifically, the logo and message displayed to the Pocket Vault holder may incorporate motion, moving images and messages. To conserve power, moving images may be presented only at certain times, e.g. response to internal or external events or communications.
In the embodiment of FIG. 1, the computers 108, 110, and 1112, together with the network server 114, may represent a secure infrastructure of server databases capable of storing information for purposes of delivering personalized services to holders of Pocket Vaults 102. The network server 114 may also track activity of Pocket Vault holders and compile marketing information based thereupon that may prove useful to media issuers and/or advertisers. The Pocket Vault holder may have control over the ability of the network server 114 to track activity. The information maintained on the network system 100 may originate with the holders of Pocket Vaults 102 and/or may originate with the other entities having access to the network system 100 (e.g., advertisers and media issuers).
As discussed below in more detail, in some embodiments of the invention, certain uses of the Pocket Vault 102, as well as each of the interface stations 104a-c, may be permitted only by pre-authorized individuals. To this end, a suitable user authentication technique may be employed in connection each attempted use of any of these devices. One suitable user authentication technique that may be employed is the analysis of a bio-metric feature of the individual attempting use of the device (e.g., a fingerprint scan, retina scan, a speech pattern analysis, keystroke rhythm, etc.), and validating the identity of the individual on that basis. Alternatively, a personal identification (PIN) code may be entered by the holder to verify the holder's identity. In one illustrative embodiment, authentication information used to validate the holder's identity (e.g., the stored fingerprint or PIN code) is stored within the to-be-accessed device, and the validation is performed in its entirety on-board the same device, such that the user-specific authentication information never leaves the device in which it is stored. Thus, using this technique, the likelihood that such information will be intercepted by unauthorized third parties may be reduced significantly.
As discussed below, great care may be taken to ensure that only authorized individuals are permitted to validate Pocket Vaults 102 by having their authentication information (e.g., their fingerprint data or PIN codes) stored therein. Therefore, after it has been confirmed that the holder's authentication information has been properly stored in the Pocket Vault 102, a trust relationship may be established between the network server 114 and the Pocket Vault 102. This relationship may involve, for example, the registration of a unique encrypted chip ID of the Pocket Vault 102 with the network server 114 through a secure Internet connection, the distribution of a digital certificate to the Pocket Vault 102, and the grant of authority to the Pocket Vault 102 to permanently store the Pocket Vault holder's authentication information.
A similar level of care may also be taken to ensure that only authorized individuals are permitted to validate interface stations 104a-c by having their authentication information (e.g., their fingerprint data or PIN codes) stored therein. Therefore, as with the Pocket Vaults 102, after it has been confirmed that each interface station's authorization information has been properly stored in the interface station 104, a trust relationship may be set up between the network server 114 and the interface station 104. This relationship may also involve, for example, the registration of a unique encrypted chip ID of the interface station 104 with the network server 114 through a secure Internet connection, the distribution of a digital certificate to the interface station 104, and the grant authority to the interface station 104 to permanently store the interface station operator's authentication information. While, in some embodiments, the Pocket Vault 102 and/or the interface stations 104 are each permitted to store authentication information for only one individual, it should be appreciated that, in alternative embodiments, the Pocket Vault 102 and/or the interface stations 104 may each store authentication information for more than one individual, thereby permitting multiple people to use them.
Because of the creation of the above-described trust relationships, each Pocket Vault 102 and each interface station 104 may communicate securely with the network server 114, as well as with any other networked devices or sites that require a high level of trust. Also, the existence of these trust relationships enable individual Pocket Vaults 102 to accept other services provided by the network servers 114, such as the backup and recovery of information stored within the Pocket Vaults 102. That is, the network servers 114 can serve as a repository for all of the information stored on every validated Pocket Vault 102 (except the holder's authentication information—which is stored only in the Pocket Vault 102). To ensure the network server 114 stores an accurate version of the contents of each Pocket Vault 102, information may, for example, be uploaded to from the network server 114 to a Pocket Vault 102 or downloaded from the Pocket Vault 102 to the network server 114 each time the Pocket Vault 102 is interfaced with any of the interface stations 104a-c. Therefore, if a Pocket Vault 102 is lost or stolen, the Pocket Vault holder need only obtain a new Pocket Vault 102, and the entire contents of the lost Pocket Vault 102 can be uploaded thereto, in a single communication, in a matter of seconds. In addition, in the event that a validated Pocket Vault 102 is lost or stolen, the network server 114 may void the chip ID of that Pocket Vault 102, so that the Pocket Vault 102 can not be used by a third party, even if the holder validation security (e.g., the bio-metric scanning or PIN entry requirement) is somehow breached. Voiding the chip ID of the Pocket Vault 102 may prevent the Pocket Vault 102 from assigning any media information to the associated Chameleon Card.
In addition to serving as a repository for Pocket Vault information, the network server 114 may also serve as a repository for information regarding media issuers or advertisers, and may further provide various services to these entities. For example, the network server 114 may facilitate transactions involving media issued by the media issuers, and may permit new media to be issued or lost media to be replaced at a fraction of the cost of generating new physical tokens or replacing lost ones. Additionally, the network server 114 may serve as a conduit for advertisers to target particular classes of Pocket Vault holders, and channel information to them. The network server 114 may also function as an advocate for Pocket Vault holders, advertisers, and/or media issuers when it utilizes its portfolio of Pocket Vault holders, media issuers, and/or Pocket Vault holders to secure privileges. Examples of such advocacy include the ability to secure buying power for Pocket Vault holders as a group or to provide media issuers and advertisers with a highly efficient tool for generating awareness for affinities or causes that fit appropriate holder markets. In sum, the services provided by the network server 114 enable Pocket Vault holders to combine and manage their media data using a single, hand-held device, and enables advertisers and media issuers to understand more about, and more readily reach more of, their customers than ever before.
FIG. 2 shows an example embodiment of the Pocket Vault 102 of FIG. 1. The pocket vault 102 may employ components similar to those used in modern personal digital assistants (PDAs) and palm top computers. Examples of such products include PDAs such as the "Palm Pilot" from Palm, Inc. (www.palm.com), and the "Casiopedia" from Casio, Inc. of Dover, N.J. (www.casio.com). As shown, the Pocket Vault 102 may include a controller 202, as well as a transceiver 204, a user input device 206, a docking interface 208, a read/write memory 210, a write-once memory 212, a power manager 214, an indicator 215, a display 216, a token port 218, and a fingerprint scanner 220, all coupled to the controller 202. In addition, the Pocket Vault 102 may include a hard-wired memory (not shown) to store device serial numbers and key operating system and encryption software components.
Actual views of an example embodiment of the Pocket Vault 102, as well as the token 102a associated therewith, are shown in FIGS. 26A-26P. The views of FIGS. 26A-P, including the items displayed on the display 216, are discussed in more detail below in connection with the flow diagrams of FIGS. 7-12. At this point, however, with reference to FIGS. 26A-L and 26-O, it may be noted that the Pocket Vault 102 may comprise a housing 2602 in which the components shown in FIG. 2 may be disposed. As illustrated in FIGS. 26E and 26F, the housing 2602 may be approximately seventy millimeters wide, approximately one hundred millimeters long, and approximately fifteen millimeters deep. Thus, in the embodiment shown, the housing 2602 has an internal volume of less than 105 cubic centimeters. Of course, in alternative embodiments, the housing 2602 may be slightly larger or smaller than that shown. For example, in different embodiments, the housing 2602 may have an internal volume less than five hundred cubic centimeters, or less than four hundred cubic centimeters, or less than three hundred cubic centimeters, or less than two hundred cubic centimeters, or less than one hundred cubic centimeters, or less than any other volume value that falls between one hundred and five hundred centimeters. In one embodiment, the housing 2602 is sized so that the Pocket Vault 102 may readily fit into the rear pocket of a pair of pants. One feature of the illustrative embodiment of the Pocket Vault 102 shown in FIG. 2 which may permit its size to be reduced below that of a standard personal computer is the fact that the embodiment shown lacks a disk drive (either hard or floppy) or any similar memory storage device (e.g., a tape drive) that consumes a significant volume within the housing 2602. It should be appreciated, of course, that alternative embodiments may include such memory devices, and that the invention is not necessarily limited to embodiments that exclude them. In addition to the lack of a disk drive or the like, in some embodiments, the power manager 214 may reduce the power consumption of the active components of the Pocket Vault 102 well below that of a standard personal computer, thereby enabling a very small and light weight battery to be employed, as opposed to the relatively large and heavy batteries typically employed in personal computers.
The housing 2602 may provide a water-resistant or waterproof environment for the components housed thereby. The housing materials of Pocket Vaults 102 may be brightly colored, in addition to traditional black or brown, thereby helping their holders to make a fashion statement and/or permitting them to be readily spotted if misplaced. Deluxe versions may be clad in leather, Kevlar™, Gortex™, aluminum and/or stainless steel. In some embodiments, the housing 2602 may even be woven into garments.
Referring again to FIG. 2, any of a number of devices may be used to implement the controller 202, and the invention is not limited to any particular type of controller. In one illustrative embodiment, for example, the controller 202 comprises a low-power multiprocessor or microcomputer having an on-board SRAM and/or flash memory and a real time clock calendar. One example of a suitable controller is the "Motorola Dragonball" Processor from Motorola, Inc. (www.motorola.com). The controller 202 may include a software-programmable and encryption-protected or hard-wired unique chip ID. In one embodiment, this chip ID is released from the Pocket Vault 102 only after the fingerprint scanner 220 (discussed below) has successfully authenticated the identity of the holder. A signal processor for Bluetooth or another wireless connection may also be employed within or along with the controller 202.
The transceiver 204 may be any type of transceiver (or separate transmitter and receiver) capable of communicating with the other devices in the network 100 to enable the functionality described herein. For example, either an RF or an IR transceiver may be employed. Some embodiments may, in fact, include both an IR and an RF transceiver to be used in different applications. For example, an IR transceiver may be employed to interface the Pocket Vault with a "docking station" type interface unit, and a separate RF transceiver may be employed to communicate over a wireless network such as Bluetooth.
In one illustrative embodiment, the user input device 206 is implemented as part of a touch-screen display used as the display 216 (described below). Additionally or alternatively, the user input device 206 may include dedicated buttons, a keypad, a touch pad, a microphone and speech recognition software, a wand or joystick, or any other suitable implement that permits a person to provide input to the controller 202. The user input device 206 may also be integrated into the fingerprint scanner 220 or into an alternative bio-metric input device. By manipulating the user input device 206, a Pocket Vault holder may select one of a number of media stored in memory of the Pocket Vault 102 for display and/or use in connection with a transaction, and may otherwise control or provide input to software executing on the controller 202. In one embodiment, a keypad is employed as the user input device 206, thereby permitting the holder to input a PIN code as a means of authenticating the holder's identity.
The docking interface 208 may take on any of numerous forms, and the invention is not limited to any particular type of interface device. The docking interface 208 may, for example, include a multi-pin plug adapted to mate with a receptacle disposed on the interface units 104a-c, or vice versa. The docking interface 208 may also comprise one or more implements (e.g., grooves or keys) to ensure that the plug or other docking interface 208 mates correctly with the reciprocal device on an interface unit 104 when the two are physically mated together.
The read/write memory 210 may take on any of a number of forms, and the invention is not limited to any particular type of memory. The memory 210 may, for example, comprise a suitable non-volatile SRAM. Similarly, any suitable memory device that permits a only single write operation to take place may be employed as the write-once memory 212. The memory 210 may have instructions stored therein which, when executed by the controller 202, cause the controller 202 to implement the routine described below in connection with FIGS. 7-12. Of course, the memory 210 may also contain a suitable operating system (e.g., Palm OS, Microsoft's Windows CE, Microsoft's Windows for Smartcards, or some similar offering), appropriate device drivers, and other software employed in connection with the controller 202 and/or the peripherals thereof. The memory 210 may also be used to store the various media and personal information retained by the Pocket Vault 102. In one illustrative embodiment, the memory 210 stores a plurality of different media issued by different and unrelated media issuers, including both financial (e.g., a credit or debit card) and non-financial media (e.g., a drivers license or a library card). Other examples of media or information that may be stored in the memory 210 include: a social security card, identification cards, membership cards, discount cards, commuter passes, toll passes, transit cards, access tools such as hotel keys, business cards, coupons, concert and theatre tickets, transportation tickets, frequent customer cards (e.g., a frequent flier card), medical information cards, receipt information, photographs, etc.
As used herein, "financial media" refers to any media which can, as a matter of course, be used to purchase goods or services, whereas "non-financial media" refers to any media which, while possibly having some value to the Pocket Vault holder, cannot, as a matter of course, be used to purchase goods or services. Examples of financial media include value-linked and value-based media such as debit or credit cards issued by a bank or other financial institution, telephone calling cards, etc. Examples of non-financial media include: library cards, driver's licenses, building access cards, etc. In one embodiment, the memory 210 is large enough to store as many as one hundred compressed graphic image files, and full data sets for as many as one hundred types of media.
In addition, the memory 210 may store status information, where useful, for each type of media. Examples of this sort of status information include: information regarding the value remaining on a pre-paid phone card, information regarding an accumulated number of frequent flier miles, information regarding a total number of cups of coffee that have been purchased at a particular coffee shop (e.g., in connection with a buy-ten-get-one-free special), etc. The portion of the memory 210 devoted to memory storage may be divided into three sections: (1) a high-security section, (2) a medium security section, and (3) a non-secure section. The high security section may be used to store value-based or value-linked media such as debit and credit cards and certain ID information such as driver's licenses, passports, building security passes, etc. The medium security section may be used to store low-value, limited use media that may be accessed, for example, by retailers to keep track of frequent purchase credits or the like. The non-secure section may, for example, be used to store notes, membership ID records, emergency contact information, etc. Access to the information included in the various sections may require security or user authentication procedures commensurate with the indicated security level. For example, an accurate fingerprint scan and an accurate pin code entry may be required to access the high-security section, only an accurate PIN code entry (even by the retailer) may be required to access the medium-security section, and anyone may be permitted to access the non-secure section.
The power manager 214 may comprise any of numerous devices, and the invention is not limited to any particular type of power supply/management device. The power manager may, for example, employ a flat, rechargeable, lithium battery, and associated regulator and power management software. Alternatively, the battery used may be non-rechargeable and/or coin cell-shaped. Solar powered cells may also be a viable option as at least a supplement to battery power, if not a primary source of power for the Pocket Vault 102. This may be made possible because of the typically modest on-time requirements for a Pocket Vault 102. Power management software may also assist in minimizing the power consumption of the Pocket Vault 102. Such software may, for example, invoke an auto-shutdown feature after a preference-set number of seconds, may control the level of screen back-lighting in response to feedback received from a photo-sensor that registers ambient light, and/or may provide battery charge level warnings to Pocket Vault holders.
The indicator 215 may be any device capable of generating a perceptible indication to the holder such as a bell, chime, buzzer, light, vibration, etc., and the invention is not limited to any particular type of device for accomplishing such a result. In one embodiment, for example, the indicator is a chime generator that generates a "chime" sound that can be heard by the Pocket Vault holder.
Any of a number of devices may also be used for the display 216, and the invention is not limited to any particular type of display. As mentioned above, in one embodiment, a touch-screen display may be employed such that at least a portion of the functionality of the user input device 206 may be incorporated therein. Suitable displays may, for example, include any of a black & white, gray-scaled, or color LCD display, or an LCD bi-stable display.
As mentioned above, the use of the display 216, together with the user input device 206 (which may constitute the touch-screen functionality of the display 216) permits the Pocket Vault holder to flip or scroll through the various media stored in the memory 210 in much the same way as a person flips through the contents of his or her wallet. As mentioned above in connection with the description of the indicator 215, in addition to or in lieu of the display 216, other user output devices may also be employed to provide information to the Pocket Vault holder. For example, light emitting diodes (LEDs), a beeper or buzzer, a speech synthesizer, a vibrator, etc., may be employed in some embodiments of the Pocket Vault 102.
The token port 218 of the Pocket Vault 102 may comprise a cavity or slot in which the token 102a is retained until it is released to be used to engage in a transaction, as well as the hardware employed to secure the token 102a in place when the token 102a has not been authorized to be released. In one embodiment, the token 102a stores a unique (possibly encrypted) embedded unique (and possibly encrypted) chip ID stored which is accessible to another device only when the token 102a is successfully released form the token port 218. In addition to the elements described above, the card port 218 may include additional hardware employed in connection with properly generating or configuring the token 102a prior to its release. This hardware is discussed in more detail below in connection with FIG. 6.
The fingerprint scanner 220 may comprise any device capable of accurately scanning a fingerprint of an individual for comparison with a fingerprint image stored in memory. The fingerprint scanner 220 may, for example, be a solid-state (non-optical) device. Devices that may be suitable for use as the fingerprint scanner 220 are available, for example, from Veridicom, Inc., of Santa Clara, Calif. (www.veridicom.com), from Polaroid Corporation of Cambridge, Mass. (www.polaroid.com), and from Identix Incorporated of Sunnyvale, Calif. (www.identix.com). The fingerprint scanner 220 may incorporate a temperature sensor that enables it to ensure that a live finger is contacting the scanning surface when the scanning function is employed. In addition to or in lieu of a fingerprint scanner, other bio-metric scanning devices may also be employed to verify the identity of the holder. For example, some embodiments may employ a charge coupled device (CCD) to serve as an iris or retina scanner, an optical sensor, and/or a voiceprint. Alternatively or additionally, a keystroke rhythm may be measured, either alone or in combination with another user authentication technique (e.g., a successful PIN code entry requirement), to validate the identity of the holder. The fingerprint scanner 220 and/or other bio-metric scanners may have touch pad capabilities built into them, thereby permitting them to constitute at least a part of the user input device 206 shown in FIG. 2.
FIG. 3 is a block diagram showing an example embodiment of one of the interface stations 104a-c shown in FIG. 1. The hardware employed to implement each of the stations 104a-c may be identical to the others or may be substantially different, depending on the environment in which the station 104 is to be used, as well as the functional requirements of the particular station. Therefore, while the example embodiment described herein may be suitable for use as any of the stations, it should be appreciated that each of the stations may, in fact, be configured quite differently than the others.
As shown in FIG. 3, each interface station 104 may include both an interface station computer 304 and a pocket vault interface unit 302. The interface station computer 304, for example, may be a standard desktop personal computer (PC), and may, as shown, comprise a controller 308, a user input device 318, a memory 320, a modem 322, and a display 324. These components are well known in the art and therefore will not be described in detail herein. The memory 320 of the interface station computer 304 may have instructions stored therein which, when executed by the controller 308, cause the controller to implement the routine described below in connection with FIGS. 14-18.
The pocket vault interface unit 302 is coupled to the interface station computer 304 such that a controller 306 of the pocket vault interface unit 302 can communicate with the controller 308 of the interface station computer 304. The communications interface between these devices may, for example, comprise a Smartcard, Bluetooth or USB interface. As shown, in addition to the controller 306, the pocket vault interface unit 302 may comprise a transceiver 310, a docking interface 312, a finger print scanner 316, and a memory 314. Further, although not shown in FIG. 3, the pocket vault interface unit 302 may also comprise a display and/or another device used to provide feedback to the operator, e.g., an audio indicator or LED.
The memory 314 may be any conventional memory suitable to store the software executed by the controller 306, as well as any data, e.g., stored fingerprint data, used in connection therewith. For example, the memory 314 of the pocket vault interface unit 302 may have instructions stored therein which, when executed by the controller 306, cause the controller 306 to implement the routine described below in connection with FIG. 13.
As with the transceiver 204 of the Pocket Vault 102, the transceiver 310 of the pocket vault interface unit 302 may be any type of transceiver (or separate transmitter and receiver) capable of communicating with the other devices in the network 100 to enable the functionality described herein. For example, either an RF or an IR transceiver may be employed. Some embodiments may even include both an IR and an RF transceiver to be used in different applications. For example, an IR transceiver may be employed to interface the pocket vault interface unit 302 with a Pocket Vault 102, and a separate RF transceiver may be employed to communicate over a wireless network such as Bluetooth.
As with the docking interface 208 of the Pocket Vault 102, the docking interface 312 of the pocket vault interface unit 302 may take on any of numerous forms, and the invention is not limited to any particular type of interface device. The docking interface 312 may, for example, include a multi-pin plug adapted to mate with a receptacle used as the docking interface 208 of a Pocket Vault or vice versa. The docking interface 312 may also comprise one or more implements (e.g., keys or grooves) to ensure that the plug or the like of the docking interface 208 of the Pocket Vault 102 mates correctly with the corresponding implementation I the docking interface 312 when the Pocket Vault 102 and pocket vault interface unit 302 are physically mated together.
Finally, as with the fingerprint scanner 220 of the Pocket Vault 102, the fingerprint scanner 316 of the pocket vault interface unit 302 may comprise any device capable of accurately scanning a fingerprint of an individual for comparison with a fingerprint image stored in memory. The fingerprint scanner 316 may, for example, be a solid-state (non-optical) device. Devices that may be suitable for use as the fingerprint scanner 220 are available, for example, from Veridicom, Inc., of Santa Clara, Calif. (www.veridicom.com), from Polaroid Corporation of Cambridge, Mass. (www.polaroid.com), and by Identix Incorporated of Sunnyvale, Calif. (www.identix.com). The fingerprint scanner may incorporate a temperature sensor that enables it to ensure that a live finger is contacting the scanning surface when the scanning function is performed. In addition to or in lieu of a fingerprint scanner, other bio-metric scanning devices may also be employed to verify the identity of the interface station operator. For example, some embodiments may employ a charge coupled device (CCD) to serve as an iris or retina scanner, an optical sensor, and/or a voiceprint. Alternatively or additionally, a keystroke rhythm may be measured, either alone or in combination with another user authentication technique (e.g., a successful PIN code entry requirement), to validate the identity of the operator. Although not shown, the pocket vault interface unit 302 may additionally comprise one or more user input devices enabling the operator to control or provide input to the pocket vault interface unit 302 or the software executing thereon. The fingerprint scanner 316 and/or other bio-metric scanners may, for example, have touch pad capability capabilities built into them, thereby permitting them to constitute such a user input device. Separate user input devices may also be employed.
FIG. 4 shows an example embodiment of the network server 114 shown in FIG. 1. As shown, the network server 114 may comprise one or more controllers 402, as well as a local memory 404, a database 406, and a transceiver 408 coupled thereto. The illustrated components of the network server 114 are well known, and therefore will not be described in detail. The transceiver 408 may, for example, be used to communicate with other devices in the network system 100 (FIG. 1) using a wireless network such as Bluetooth. The controller 404 may also communicate with other network devices via the Internet or a direct connection such as the type established using a dial up modem.
The local memory 404 may have instructions stored therein which, when executed by the controller 402, cause the controller 402 to implement the routine described below in connection with FIGS. 19-25. The database 406 may, for example, comprise a relational database, and may be used to store the majority, if not all, of the data maintained by the network server 114. The database 406 may, for example, keep a real-time record of critical reference data along with transaction histories, back-up files, and security audit trail information for key events. Examples of specific items that may be stored in the database 406 include: a list of current Pocket Vault holders and appropriate contact information for each; records regarding the versions of software loaded onto each Pocket Vault 102, each pocket vault interface unit 302, and each interface station computer 304; a list of currently authorized or registered Pocket Vaults 102, identified by chip ID and linked to the holder list; a list of currently authorized or registered tokens 102a, identified by chip ID and linked to the holder list; a list of currently authorized locations for interface stations 104 and telephone or other access lines therefor, including business information for each such location and an indication as to the type of interface station 104 it is (e.g., a validation interface station, a personal interface station, or a commercial interface station); a list of currently authorized or registered interface station operators and the interface stations 104 with which they are associated; a list of currently authorized or registered interface stations 104, identified by chip ID and linked to the list of authorized operators therefor, as well as encrypted cookie ID information (if any) for the respective interface stations 104; authorized media data received from media issuers that has not yet been downloaded to individual Pocket Vaults 102; backup data sets for individual Pocket Vault holders; detailed transaction histories for Pocket Vault registrations indicating where each Pocket Vault 102 was shipped from and to, where each Pocket Vault 102 was registered, which authorized interface station operator conducted the registration process, when that authorized operator was added to the list of authorized operators at a particular location, who submitted the key information to add the operator, which corporate representative associated with the network server 114 met with which representative associated with the interface station in establishing each new location for a validation interface station 104a, to whom and when each Pocket Vault 102 was issued; and communication encryption protocols. Each Pocket Vault account defined on the network server 114 may be defined to support multiple Pocket Vaults 102, as well as to identify other family members who may share certain contents of the Pocket Vaults 102 (e.g., family membership in a local museum).
The network server 114 may analyze data regarding consumer transactions, and thereby accumulate demographic information. Using this information, merchants, media issuers, and/or advertisers may, for example, define targeted marketing programs, which the network server 114 may then deliver to Pocket Vault holders that meet particular demographic profiles.
FIG. 5 shows how the memory 210 of the Pocket Vault 102 (FIG. 2) may be organized (conceptually) in accordance with one embodiment of the invention. The purpose of each of the illustrated memory components will be readily understood by those skilled in the art of the invention, and therefore will not be explained in detail.
FIG. 6 is a block diagram showing an example embodiment of the token 102a shown in FIGS. 1 and 2. AS shown, the token 102 may be equipped with a controller 602. In the embodiment shown, the controller 602 may be selectively programmed, for example, via interface terminals 606 to generate a current in a wire loop 608 so as to generate a magnetic field about the wire loop 608 that simulates a magnetic stripe of a standard credit card-like token. In other words, a magnetic field may be generated along the edge of the token 102a as if a magnetic stripe were present on that edge. The location of the simulated magnetic stripe on the token 102a is identified in FIG. 6 as a virtual magnetic stripe 610.
Appropriate software may be loaded onto the controller 602 (e.g., in an on-board memory of the controller 602) so as to enable the controller to generate the virtual magnetic stripe 610. When the token 102a is disposed in the token port 218, the terminals 606 of the token 102a may engage corresponding terminals of the token port 218, thereby enabling the controller 602 to be programmed appropriately. The programming of the controller 602 may be effected, for example, in response to commands from the controller 202 of the Pocket Vault 102, which commands may be generated in response to software executing on the controller 202.
As shown, the controller 602 may be powered by an appropriate resistor-capacitor (RC) circuit which stores a charge that decays over time. The RC circuit may be initially charged via the terminals 606 when the token 102a is disposed in the token port 218 and the controller 602 is being programmed. After the token 102a is removed from the token port 218, the controller 602 will remain powered only so long as sufficient charge remains stored by the RC circuit 604. Because the controller 602 can generate the virtual magnetic stripe 610 only when it is driven by an adequate power supply, the virtual magnetic stripe will disappear after the charge in the RC circuit 604 has decayed beyond a certain threshold level. Because the decay of an RC circuit is reasonably predictable, the virtual magnetic stripe 610 is disposed on the token 102a only for a finite, predetermined period of time after the token 102a is removed from the token port 218. In one embodiment, after the controller 602 loses power, the information with which it was programmed to enable it to generate the virtual magnetic stripe 610 is also lost. Therefore, the virtual magnetic stripe 610 of the token 102a cannot be used again until the controller 602 is again powered up and reprogrammed. Alternatively the controller 602 may cut off the power to the wire loop 608 after a preset amount of time or an amount of time determined by the Pocket Vault holder (possibly within preset limits). Additionally or alternatively, the token 102a may have its own embedded chip ID, which may be accessible only when the token 102a is successfully released form the token port 218.
As mentioned above, FIGS. 7-12 are flow diagrams illustrating an example implementation of software that may be executed by the controller 202 of the Pocket Vault 102. As described below, this proprietary software may enable menu structures, handle preference management, provide the data on and safeguard the programmability of the virtual magnetic stripe 610 (if so equipped), and ensure proper encryption data management. In one embodiment, local software for each Pocket Vault 102 and pocket vault interface station 104 may be upgraded from time to time by automatic download from the network server 114.
During execution of the routines of FIGS. 7-12, various items may be displayed on the display 216, including prompts or icons regarding user input options (when a touch-screen display is employed as the display 216 or a point and click mechanism is employed herewith), and various items may be also be displayed on the token 102a when the token 102a is ejected from the token port 218 of the Pocket Vault 102. FIGS. 26A-P show examples of how the display 216 and the token 102a may appear as the routines of FIGS. 7-12 are executed, and therefore will be discussed in connection with the description of these routines.
FIG. 7 is a flow diagram illustrating an example implementation of a primary routine 700 that may be executed by the controller 202 of the Pocket Vault 102. Instructions for the routine 700 may be stored, for example, in the "applications" section 508 of the memory 210 of the Pocket Vault 102.
As shown, the routine 700 begins at a step 702, wherein it is determined whether the Pocket Vault holder has applied his/her fingerprint to the fingerprint scanner 220 of the Pocket Vault 102. At the step 702, the display 216 of the Pocket Vault 102 may be appear as shown in FIG. 26A. That is, the display 216 may be blank at the step 702, as the Pocket Vault 102 is currently powered down.
When, at the step 702, it is determined that the holder has applied his/her fingerprint to the fingerprint scanner 220, the routine 700 proceeds to a step 704, wherein the power manager 214 powers on the Pocket Vault 102. The routine 700 otherwise waits at the step 702 until the Pocket Vault holder has applied a fingerprint to the fingerprint scanner 220. Is should be appreciated, however, that, in some embodiments, the step 702 may not represent an instruction set exceeded by processor 202. Instead, the step 702 may represent the detection of the occurrence of a physical action, e.g., the activation of a hardware switch, and the power manager 214 may be activated in response to the detector of such an action, without requiring intervention by the processor 202.
After the step 704, the routine 700 proceeds to a step 706, wherein the fingerprint scanner 220 scans the applied fingerprint of the Pocket Vault holder.
After the step 706, the routine 700 proceeds to a step 708, wherein it is determined whether the fingerprint memory (e.g., the write-once memory 212 of FIG. 2) is erased. When, at the step 708, it is determined that the fingerprint memory is erased, the routine 700 proceeds to a step 710, wherein the PROCESS FINGERPRINT STORAGE routine (described below in connection with FIG. 8) is executed. When, at the step 708, it is determined that the fingerprint memory is not erased, (i.e., a fingerprint is currently stored in the fingerprint memory), the routine 700 proceeds to a step 712, wherein it is determined whether the fingerprint scanned at the step 706 matches the fingerprint stored in the fingerprint memory 212.
When, at the step 712, it is determined that the scanned fingerprint does not match the stored fingerprint, the routine 700 proceeds to a step 714, wherein the UNAUTHORIZED HOLDER routine (discussed below in connection with FIG. 9) is executed. FIGS. 26B-D show how the display 216 of the Pocket Vault 102 may appear during the UNAUTHORIZED HOLDER routine, and therefore are also discussed below in connection with FIG. 9.
When, at the step 712, it is determined that the scanned fingerprint matches the stored fingerprint, the routine 700 proceeds to a step 716, wherein it is determined whether the Chameleon Card (i.e., the token 102a) is presently on-board the Pocket Vault 102 (i.e., whether the token 102a is disposed within the card port 218 of FIG. 2).
When, at the step 716, it is determined that the token 102a is not on-board the Pocket Vault 102, the routine 700 proceeds to a step 718, wherein the Pocket Vault holder is informed that the Chameleon Card is not on board, and is asked whether he/she wants to engage in a non-card transaction (i.e., a transaction involving the token 102a).
After the step 718, the routine 700 proceeds to a step 720, wherein it is determined whether the holder has selected to engage in a non-card transaction.
When, at the step 720, it is determined that the holder has selected not to engage in a non-card transaction, routine 700 returns to the step 716 (described above), wherein it is again determined whether the Chameleon Card is on board the Pocket Vault 102. Therefore, the holder is permitted to engage in a transaction involving the Chameleon Card only when it has been confirmed that the Chameleon Card is on board the Pocket Vault 102.
When, at the step 720, it is determined that the holder has selected to engage in a non-card transaction, the routine 700 proceeds to the step 722, wherein the AUTHORIZED HOLDER routine (discussed below in connection with FIGS. 10 and 11) is executed.
When, at the step 716, it is determined that the Chameleon Card is on-board the Pocket Vault 102, the routine 700 also proceeds to the step 722, wherein the AUTHORIZED HOLDER routine (discussed below in connection with FIGS. 10 and 11) is executed. FIGS. 26G-N and 26P show how the display 216 of the Pocket Vault 102 and the token 102a ejected therefrom may appear (when employed) during the AUTHORIZED HOLDER routine, and therefore are also discussed below in connection with FIGS. 10 and 11.
After each of the steps 710, 714, and 720 (only one of which is executed during each iteration of the routine 700), the routine 700 proceeds to a step 724, wherein the VERIFY CARD RETURN routine (discussed below in connection with FIG. 12) is executed. FIG. 260 shows how the display 216 of the Pocket Vault 102 may appear during the VERIFY CARD RETURN routine, and therefore is also discussed below in connection with FIG. 12.
After the step 724, the routine 700 proceeds to a step 726, wherein the screen of the display 216 is caused to flash to indicate that the Pocket Vault 102 is being shut down.
After the step 726, the routine 700 proceeds to a step 728, wherein the Pocket Vault 102 is powered down.
After the step 728, the routine 700 returns to the step 702, wherein the Pocket Vault 102 again waits for a fingerprint to be applied to the fingerprint scanner 220, and wherein the display 216 may again appear as shown in FIG. 26A.
FIG. 8 is a flow diagram illustrating an example embodiment of the PROCESS FINGERPRINT STORAGE routine shown in FIG. 7 (step 710).
As shown, the routine 710 begins at a step 802, wherein the holder is informed (e.g., on the display 216) that the Pocket Vault is not currently validated, and that the holder must interface the Pocket Vault 102 with an appropriate interface station 104 (e.g., a validation interface station 104a) if the holder desires to validate the Pocket Vault 102.
After the step 802, the routine 710 proceeds to steps 804 and 806, wherein it is determined whether the Pocket Vault 102 has received encrypted validation information enabling the storage of a new fingerprint in the Pocket Vault's memory prior to the expiration of a timeout period measured by the step 806. This encrypted validation information may, for example, be received by the Pocket Vault 102 via either the docking interface 208 or the transceiver 204 of the pocket vault interface unit 302 of a validation interface station 104a. As discussed in more detail below, this encrypted validation information may, for example, be generated by the network server 114 and forwarded to the pocket vault interface unit 302 of a validation interface station 104a (via the interface station computer 304 of the validation interface station 104a) after certain conditions have been met. The network server 114 may therefore ultimately determine whether each Pocket Vault 102 is permitted to be authenticated by a new holder.
When, at the step 806, it is determined that the time-out period has elapsed, the routine 710 proceeds to a step 808, wherein an indication (e.g., an audio signal from the indicator 215) is generated to inform the holder that the holder's fingerprint has not been successfully stored in the Pocket Vault's memory, and that the validation attempt was therefore unsuccessful.
After the step 808, the routine 710 terminates.
When, at the step 804, it is determined that encrypted validation information has been received before the timeout period of the step 806 has elapsed, the routine 710 proceeds to a step 810, wherein the scanned fingerprint is stored in memory of the Pocket Vault 102 (e.g., in the write-once memory 212).
After the step 810, the routine 710 proceeds to a step 812, wherein an indication (e.g., an audio signal from the indicator 215 of the Pocket Vault 102) is generated to inform the holder that the holder's fingerprint has been successfully stored in the Pocket Vault's memory.
After the step 812, the routine 710 terminates.
FIG. 9 is a flow diagram illustrating an example implementation of the UNAUTHORIZED HOLDER routine shown in FIG. 7 (step 714).
As shown, the routine 714 begins at a step 902, wherein a menu is displayed on the display 216 that permits the holder to select one of several options: (1) TRY AGAIN, (2) POCKET VAULT RETURN INFORMATION, (3) EMERGENCY INFORMATION, or (4) END SESSION. FIG. 26B shows how the display 216 may appear when the step 902 is reached. As shown, textual information and/or icons representing the various menu options may be displayed to the holder.
After the step 902, the routine 714 proceeds to a step 904, wherein the routine 714 waits for one of the displayed menu items to be selected by the holder (e.g., when the holder touches the location on the screen of the display 216 at which the menu item is displayed).
After one of the menu items has been selected at the step 904, the routine 714 proceeds to a step 906, wherein it is determined whether the TRY AGAIN option was selected. By selecting TRY AGAIN, the holder may request that the holder again be permitted to attempt to access the secure contents of the Pocket Vault 102 by reapplying the holder's fingerprint to the fingerprint scanner 220.
When, at the step 906, it is determined that the user has selected the TRY AGAIN option, the routine 714 proceeds to a step 912, wherein it is determined whether this is the third sequential time that the scanned fingerprint has failed to match the fingerprint stored in memory.
When, at the step 912, it is determined that three sequential failed matches have occurred, the routine 714 proceeds to a step 914, wherein certain security precautions are taken in light of the multiple failed attempts to match the holder's fingerprint with that stored in the Pocket Vault 102. For example, when multiple failed matches have occurred, the Pocket Vault's secure memory may be erased, a security alert message may be broadcast by the transceiver 204 and/or any other prudent steps may be taken to ensure that an unauthorized user does not access the Pocket Vault's sensitive contents.
After the step 914, the routine 714 terminates.
When, at the step 912, it is determined that this is not the third consecutive time that the holder's fingerprint has failed to match that stored in the Pocket Vault's memory, the routine 714 terminates, and the holder may then again attempt (at the step 702) to access the Pocket Vault by reapplying his/her fingerprint to the fingerprint scanner 220.
When, at the step 906, it is determined that the TRY AGAIN option has not been selected, the routine 714 proceeds to a step 908, wherein it is determined whether there exist any nested menu items for the menu item selected at the step 904.
When, at the step 908, it is determined that nested menu items do exist for the selected menu item, the routine 714 proceeds to a step 910, wherein the nested menu items for the selected menu item are displayed to the holder on the display 216.
After the step 910, the routine 714 returns to the step 904, wherein the routine 714 again waits for the holder to select one of the displayed menu items.
When, at the step 908, it is determined that no nested menu items exist for the selected menu item, the routine 714 proceeds to a step 916, wherein it is determined whether the END SESSION option has been selected.
When, at the step 916, it is determined that the END SESSION option has been selected, the routine 714 terminates.
When, at the step 916, it is determined that the END SESSION option has not been selected, the routine 714 proceeds to a step 918, wherein the information, if any, for the selected menu item is displayed to the holder on the display 216. Because the step 918 is reached only after a failed attempt to match the holder's fingerprint with that stored in the memory of the Pocket Vault 102, the information displayed at the step 918 may, for example, include information as to where the Pocket Vault may be returned if it is found by someone other than the Pocket Vault holder (see FIG. 26C), or may be emergency information regarding the holder such as the holder's blood type, allergies, persons to contact in case of an emergency, etc. (see FIG. 26D). It should be appreciated that any of a number of non-secure media may be selected using the menu access routine discussed above in connection with steps 904-910, and may be displayed to the person accessing the Pocket Vault 102, regardless of the identity of that person. Of course, this non-secure information may be information that the holder would not mind falling into the hands of a stranger should the holder misplace or have his/her Pocket Vault 102 stolen.
After the step 918, the routine 714 proceeds to a step 920, wherein after a delay of a certain period of time (e.g., thirty seconds), the holder is prompted to reapply his/her fingerprint within a particular period of time (e.g., ten seconds) to avoid shut down of the Pocket Vault 102.
After the step 920, the routine 714 proceeds to a step 922, wherein it is determined whether a fingerprint has been reapplied to the fingerprint scanner 220 within ten seconds.
When, at the step 922, it is determined that a fingerprint has been reapplied to the fingerprint scanner 220 within ten seconds, the routine 714 returns to the step 918 (discussed above), wherein the selected information is again displayed to the user.
When, at the step 922, it is determined that a fingerprint has not been reapplied to the fingerprint scanner 220 within ten seconds, the routine 714 terminates.
FIG. 10 is a flow diagram illustrating an example implementation of the AUTHORIZED HOLDER routine of FIG. 7 (step 722).
As shown, the routine 722 begins at a step 1002, wherein it is determined whether an advertisement is scheduled for display on the Pocket Vault 102. Information regarding whether certain advertisements are to be displayed by the Pocket Vault 102 may have been uploaded, for example, from the personal interface station 104b in response to the holder previously interfacing the Pocket Vault 102 with the personal interface station 104b to synchronize the contents of the Pocket Vault 102 with information stored on the network server 114. The advertiser 108 (FIG. 1) may, for example, have made arrangements with the company operating the network server 114 to have certain advertising information uploaded to Pocket Vaults 102 when particular Pocket Vault holders interface their Pocket Vaults 102 with their personal interface stations 104b.
When, at the step 1002, it is determined that an advertisement has been scheduled, the routine 722 proceeds to a step 1004, wherein the scheduled advertisement is displayed, for example, for approximately two seconds. FIG. 261 shows an example of how the display 216 may appear when such an advertisement is displayed.
After the step 1004, the routine 722 proceeds to a step 1006, wherein a "welcome screen" is displayed for a brief period (e.g., one second). FIG. 26G shows an example of how the display 216 may appear when such a welcome screen is displayed.
When, at the step 1002, it is determined that an advertisement is not scheduled, the routine 722 proceeds immediately to the step 1006, and no advertisement is displayed to the Pocket Vault holder.
After the step 1006, the routine 722 proceeds to a step 1008, wherein it is determined whether a "preferred" menu has been selected or pre-set for initial display to the Pocket Vault holder.
When, at the step 1008, it is determined that a preferred menu has been selected or pre-set, the routine 722 proceeds to a step 1012, wherein the display 216 fades to the preferred menu. FIGS. 26H and 26J show examples of how the display 216 may appear when such a preferred menu is displayed. In the example of FIG. 26H, the preferred menu immediately shows the holder's preferred credit card as the selected menu item. Should the holder opt to use this media to engage in a transaction, the holder can simply choose the media directly. Alternatively, the holder may opt to access the HOME menu or other menu items by selecting appropriate icons displayed on the screen. In the example of FIG. 26J, the preferred menu immediately shows, perhaps, a selected group of the holder's most frequently used menu items.
When, at the step 1008, it is determined that a preferred menu has not been selected or pre-set, the routine 722 proceeds to a step 1010, wherein the display 216 fades to a standard HOME menu of secure items. FIG. 26L shows an example of how the display 216 may appear when the HOME menu is displayed.
After either one of the steps 1010 and 1012 has been executed, the routine 722 proceeds to a step 1014, wherein the routine 722 waits for the holder to select one of the displayed menu items.
When, at the step 1014, it is determined that the holder has selected a particular menu item, the routine 722 proceeds to a step 1016, wherein it is determined whether the holder has selected to enter or return to the HOME menu.
When, at the step 1016, it is determined that the holder has selected the HOME option, the routine 722 proceeds to the step 1010, wherein the HOME menu of secure items is displayed.
When, at the step 1016, it is determined that the holder has selected a menu item other than the HOME option, the routine 722 proceeds to a step 1018, wherein it is determined whether there exist any nested menu items for the selected menu item.
When, at the step 1018, it is determined that nested menu items do exist for the selected menu item, the routine 722 proceeds to a step 1020, wherein the nested menu items for the selected menu item are displayed. Thus, the holder may work his/her way through various layers of menu items until the desired menu item is reached. It should be appreciated that the menu items on the higher-level layers therefore may be categorized so as to enable the holder to quickly reach the desired media or other menu option.
When, at the step 1018, it is determined that no nested menu items exist for the selected menu item, the routine 722 proceeds to a step 1022, wherein it is determined whether the holder has selected a media from among the available menu items.
When, at the step 1022, it is determined that the holder has not selected a media, the routine 722 proceeds to a step 1040, wherein information relating to the selected non-media item may be displayed, or some other function may performed in accordance with the holder's selection. A non-media menu selection may involve, for example, preference settings for certain functional aspects of the Pocket Vault 102, e.g., whether the holder has a preferred secure menu (see step 1008). Preferences for the services or the device can be selected and, as appropriate, distributed to the Pocket Vault 102 either on the spot or the next time the Pocket Vault is interfaced with an appropriate interface station 104. Preferences may, for example, include definition of home pages, connection of secure and non-secure media, order of media presentment, sort orders, user interface options, synchronization defaults, etc. Preferences that determine which items are displayed on the home page or on other pages may be defined. For example, a Pocket Vault holder may set up three preference sets: one for "business," one for "personal," and one for "vacation." The "personal" and "business" preference sets may be set to be effective at different times of the day and/or different days of the week. The "vacation" preference set may be made effective for specific blocks of time determined by the Pocket Vault holder, possibly overriding the normal timing of the "personal" and "business" sets. The Pocket Vault holder may choose to establish the various preference settings based on his or her judgment or he or she may choose to allow the network server 114, supported by various databases, knowledge of the Pocket vault holder's various media and goals set by the Pocket Vault holder (e.g., minimize interest cost on credit cards or maximize frequent flyer miles, etc.), to determine optimal media use patterns and resulting media menu contents for a particular Pocket Vault holder. Preferences may also be defined between media that will link them for: (a) affiliate credits (like frequent flyer miles) that may be automatically presented to a merchant and tracked for a holder, (b) available discounts afforded by a membership (like senior citizen or AAA discounts), and/or (c) process improvement purposes (e.g., when information needs to be presented in a certain order to work properly). For example, a linkage preference may facilitate presentation of a discount card before presentation of a payment card when buying groceries.
After the step 1040, the routine 722 proceeds to a step 1042, wherein the holder is prompted either to END the session, or to return to the HOME menu.
After the step 1042, the routine 722 proceeds to a step 1044, wherein it is determined whether the holder has opted to END the session or to return to the HOME menu.
When, at the step 1044, it is determined that the holder has selected to return to the HOME menu, the routine 722 proceeds to the step 1010 (discussed above). < |
