The present invention is a wearable device for secure execution of Near Field Communications identity-based data transactions including but not limited to executing financial transactions and gaining access to secured facilities.
The current prevalent method for making cashless payments is by the use of a debit card, credit card, or Smart Card (hereafter referred to as a card or card system). A card transaction requires the card bearer to physically slide a card through a card reader, referred to here as the primary authentication method. A secondary level of authentication may be required that consists of either keying in a personal identification number (PIN) or by writing a signature with a digital stylus. The fundamental authentication method is based on the assumption that the card is in the possession of the owner of the associated financial account.
The security risk of the card system is that both the primary and secondary authentication methods are easily thwarted. Cards may be stolen and thus possession authentication is defeated. The secondary authentication method of PIN entry can be defeated by the fact that users are required to enter the code in public where the entry can be viewed by other customers or even recorded on video with a smartphone, or by inconspicuous placement of a small video camera, such as a GoPro camera. Many keypads on payment terminals include shrouds to limit the view of the keypad entry, but they are imperfect and the PIN can be usually be derived from the motion of the fingers.
The secondary authentication method of a written signature, either with ink or a digitized written signature, is inherently defeated if the card is stolen, since the card owner's written signature is on the back of the card. A motivated thief can easily mimic the card owner's signature.
Problems exist beyond the security risks of the card system, as the effort of producing the card is time-consuming. Many card users store the card in a wallet which in turn is kept in a pocket or purse. Executing the transaction requires extracting the wallet, extracting the card, swiping the card, placing the card back into the wallet and placing the wallet back in a pocket or purse.
Another problem with the card system is that banks now track consumer transactions and tend to error on the side of caution and may disable a consumer's card based on the appearance of fraudulency. In this case the consumer must wait to receive a new card in the mail and will not be able to make card transactions until the card is received.
An increasingly popular alternative to the card system is the use of a smartphone with a secure NFC communication sub-system. An example of this is the iPhone 6 manufactured by Apple, Inc. of Cupertino, Calif. The iPhone 6 includes a biometric fingerprint identification sub-system, software, and payment network infrastructure. However smartphone-based identity authentication systems also have problems. Methods for acquiring fingerprints and for creating fingerprint replicas able to defeat fingerprint sensors are widely disseminated on the internet. One example is Why I Hacked TouchID (again) and still thinks it's awesome—(https://blog.lookout.com/blog/2014/09/23/iphone-6-touchid-hack!).
Also smartphone payment systems have the same inconvenience as card systems in that the device has to be physically accessed and held up to an NFC reader with a finger placed on the fingerprint sensor, requiring time and effort by the user. One additional inconvenience unique to the smartphone-based payment system is that if the phone's battery runs down, the user cannot make payments. And obviously, if a smartphone is stolen, the user loses the ability to make payments.
WIPO Patent Application WO/2005/117527 entitled AN ELECTRONIC DEVICE TO SECURE AUTHENTICATION TO THE OWNER AND METHODS OF IMPLEMENTING A GLOBAL SYSTEM FOR HIGHLY SECURED AUTHENTICATION discloses a finger ring with internal electronics for secure communication with external base stations, for example by the use of USB and an IrDA (infra-red) communication mediums. The ring must be physically connected to the base station to receive power, which is inconvenient for the user. Another problem is that use of this device requires “one or more biometric cross-checks to verify the wearer as the genuine owner of the device of invention called as WIPAD (Wearable Identity Protection & Authentication Device)”. The use of this device is even more complicated than the existing card system and smartphone-based identity authentication.
What is required is a more convenient and secure method for authentication of a person's identity in a variety of situations. The method should be an inconspicuous wearable device that may be worn indefinitely, that is, not donned and doffed on a daily basis. The device should perform the basic transaction functions, similar to the card system, without requiring charging. And the device should cease to function for authenticating transactions if and when it is removed from the user's body, and provide a method for enabling authentication when the device is donned again.
The present invention solves the aforementioned problems by providing a user identity authentication ring that provides encrypted NFC identity and data authentication when worn, and ceases to provide that function when removed from the user's body. The function can be re-enabled when the ring is again donned via an encrypted Bluetooth link to a user's smartphone or other device.
The user identity authentication ring includes an NFC radio-frequency (hereafter RF) communication sub-system for providing encrypted communication with an NFC base station, and a Bluetooth Low Energy RF sub-system for providing encrypted communication with a digital device such a smartphone or personal computer. The user identity authentication ring includes a battery but does not use battery power when used to authenticate transactions, as the NFC sub-system is passively powered by the NFC base station. The user identity authentication ring also includes a passive expansion sensor configured to apply battery power to the internal NFC and Bluetooth sub-systems when the expansion sensor senses the expansion of the ring, that is, when it is passed over the user's knuckle when it is removed or donned. The expansion sensor in combination with software programming in the Bluetooth and NFC chips, acts to disable the NFC authentication function when the expansion sensor is triggered. If the expansion sensor is triggered when the NFC authentication function is in a disabled state, i.e., when it is placed onto the finger, the Bluetooth LE sub-system is activated and a PIN must be entered into a software application running on a Bluetooth-connected device to enable the NFC authentication function.
Other objects and features of the present invention will become apparent by review of the specification, appended figures, and claims.
Referring now to
In another embodiment, each of ring top cap 8, ring bottom cap 4, ring bottom cavity 12, and ring top cavity 16 are made of a composite material comprised of an epoxy resin binder with internal aramid fibers. In this embodiment top cap 8 is fastened to top cavity 16, and bottom cap 4 is fastened to bottom cavity 12, respectively, by the use of an epoxy resin. In another embodiment, top cap 8, top cavity 16, bottom cavity 12, and bottom cap 4 are comprised of a ceramic material with epoxy resin as the fastening material.
Referring now to
A Near-Field-Communication (NFC) integrated circuit (IC) 40 is soldered to small board 76. NFC IC 40 is a custom secure dual interface IC that is identical in basic function to ICs used in SmartCards, but with several additional functions. NFC IC 40 includes the following sub-systems: ARM® SecurCore® SC000™ 32-bit RISC core; radio-frequency universal asynchronous receiver (RFUART); flash memory; ISO/IEC 14443 Type A and Type B compliant communication sub-system; AES cryptographic accelerator; SPI slave communication port with AES encryption; and a DC power sub-system for powering NFC IC 40 from a battery. NFC IC 40 therefore can be powered by battery 44A and 44B, or from the RF energy source provided by an NFC reader 40. Note that for conventional 14443 compliant contactless communication, only NFC IC 40 is utilized and is powered completely by the AC magnetic field generated by NFC reader 40—power from battery 44A and 44B is not used.
Referring now to
In another embodiment, NFC IC 156 includes integrated energy harvesting and battery charging sub-systems for accumulating charge from the RF energy received during NFC communications or from an inductive charging station 36, to charge battery 44A and 44B.
In another embodiment, an energy harvesting and battery charging IC 160 is included in flexible PCBA 12 for the purpose of accumulating charge from the RF energy received during NFC communications or from an inductive charging station 36, to charge battery 44A and 44B.
where fres is the resonance frequency, Lcoil is the inductance of NFC coil 36, and CNFC is the combined capacitance of NFC IC 40 and other system capacitance.
Ring 4 will be provided in a range of sizes corresponding to conventional ring sizes based on internal ring diameter. NFC coil 36 parameters including effective diameter, number of coils, coil pitch, and wire diameter will be adjusted for various size rings, and in combination with varying system capacitances, will produce a circuit that substantially resonates at 13.56 Mhz, so that communication with NFC reader 40 is accomplished.
Referring now to
Due to the flexibility of hinge 24 and expander 20, bottom enclosure 24 can rotate with respect to top enclosure 26.
Epoxy adhesive is used to attach wide, vertical portion of flexible circuit 56 to the vertical inner wall of top cavity 16 in the area where flex circuit 56 and top cavity 16 are in apposition. Gasket 54 is comprised of polyurethane closed cell foam, and gasket 54 narrow edge is adhered to the rear inner wall of top cavity 16 and the narrow edge on the opposite side of gasket 54 is adhered to the inner wall of top cap 8.
As shown in
As bottom enclosure 24 moves to the expanded state, expansion flex 52 slides with respect to flexible circuit 56 and gasket 54, and the substantially vertical portion of NFC coil 20 slides with respect to gasket 54.
In this embodiment NFC coil 20 must flex to allow rotation of the bottom enclosure 24.
PIN confirmation app 112 is a software application that runs on a smartphone, such as an Android OS device or an Apple device running iOS, or other mobile device 22 such as a tablet. PIN app 112 utilizes the Bluetooth LE communication subsystem found on most mobile devices.
NFC software application 108 runs on the ARM core processor in NFC IC 40 and includes an NFC communication application 120 with a function identical to that found in conventional contactless Smart Card ICs that executes encrypted 14443-compliant data communication for the purpose of enabling financial and other transactions. Additionally, NFC application 108 includes a control application 116 for communicating with Bluetooth SoC 48 via an encrypted SR communication link and for enabling and disabling the 14443 communication function and for other functions associated with setup and control of device 4. NFC IC 40 includes an ENABLE status register 162, the status of which is stored in flash memory. The state of ENABLE register is either TRUE—NFC secure transaction function enabled, or FALSE—NFC secure transaction function disabled.
Bluetooth LE application 96 runs on the ARM Cortex MO 32-bit processor in Bluetooth SoC 48, and includes a Bluetooth LE stack 100 portion that provides the basic functions for a Bluetooth LE peripheral including PHY control, advertising, responding to a scan, linking, and bonding with a Bluetooth master (central) device 22. The Bluetooth LE stack 100 and function is described in detail in the Bluetooth© Core Specification, available on the Bluetooth SIG website—www.bluetooth.org—and is incorporated here by reference.
Bluetooth application 96 also includes a custom state control program 104 portion for communicating and controlling the power state (via power management component 50) and functional state of NFC IC 40, for communicating with PIN app 112 via the Bluetooth LE RF link, and for modifying the functional state of BLE IC 48.
When device 4 is removed from the finger, expansion sensor 16 is triggered and BLE IC 48 is activated by V+ (1.85V battery) connected to BLE IC 48 wake port 70. Device 4 now exits OFF mode and executes control program 104. BLE control program 104 then connects NFC IC 40 to battery power by switching on load switch 50. Next, BLE IC 48 reads state of the ENABLE register 162 in NFC IC 40 via the encrypted SPI link. If NFC IC 40 ENABLE register 162 state is TRUE, then BLE program 104 writes an ENABLE FALSE 164 (disable) instruction to NFC IC 40 ENABLE register 162, turns off power to NFC IC 40, and instructs BLE IC 48 to enter OFF mode. When NFC IC 40 is disabled, NFC data transfers to enable secure, authenticated transactions will not occur.
If BLE program 104 reads FALSE from NFC IC 40 ENABLE register 162, BLE program 104 enables the radio and commences broadcasting BLE encrypted advertising packets for a maximum of 30 seconds. If after 30 seconds device 4 is not able to connect with central device 22, BLE program 104 powers off NFC IC 40 (NFC function still disabled) and instructs BLE IC 48 to enter OFF mode.
If central device 22 connects and bonds to device 4, BLE program 104 sends a PIN VALID REQUEST message to central device 22 and starts a 30 second timer. Note that all communication over a bonded BLE RF link is encrypted. PIN confirmation app 112 must be running on the mobile device 22 to respond to the PIN VALID REQUEST message. The function of PIN app 112 will be described below.
If BLE program 104 receives a PIN VALID RESPONSE message from central device 22 in response to the PIN VALID REQUEST message, BLE program 104 writes ENABLE TRUE instruction to ENABLE register 162, turns off power to NFC IC 40, tears down the BLE connection, and instructs BLE IC 48 to enter OFF mode. NFC IC 40 is now enabled to communicate with NFC readers 40 for executing transactions.
If BLE program 104 does not receive a PIN VALID RESPONSE message from central device 22 within the 30 second time period (PIN app 112 is not running on mobile device 22, the user does not respond or inputs an incorrect PIN), BLE program 104 powers down NFC IC 40 (NFC function still disabled), tears down the BLE connection to central device 22, and then instructs BLE IC 48 to enter OFF mode.
Referring now to
The function of device 4 will be described from the point of view of the user's experience. The internal functions of ring 4 have been described in detail, therefore only pertinent new technical functional information will be included here.
When ordering ring 4 from the supplier, the user creates an account on ring 4 supplier's website, creating a username and password, and provides identity information, for example the user's SSN, and the bank account information for the account that will be used to make payments with ring 4. Ring 4 is shipped from the factory with a Bluetooth pairing code 132 and a unique factory device code 128 stored in ROM that is associated with the user's identity information and bank account data the supplier's database. In the factory state, battery 44A and 44B are fully charged, and NFC IC 40 is in a disabled state. The user is instructed install and start up PIN app 112 on mobile device 22 that they will use regularly. The user is required to sign in to the app using the username and password for the ring 4 supplier online account.
During the application process the user selects a size from a ring size chart using an existing ring, or uses a ring measurement strip, such as shown in
When device 4 is placed on the finger for the first time, ring 4 expands and BLE IC 48 is powered on. Mobile device 22 operating system responds to ring 4 BLE advertisements and generates a pairing code input interface on mobile device 22 display. When factory pairing code 132 is input correctly by the user, device 4 will be connected and bonded with mobile device 22. Next, a PIN entry interface generated by PIN app 112 is presented to the user on mobile device 22 display. The user will create and enter a six digit PIN which is stored in mobile device 22 memory and also backed up in supplier's cloud database. PIN app 112 then sends a PIN VALID RESPONSE message to device 4 which enters a fully functional state and can be used for transactions with valid NFC reader 40 devices.
Alternatively, the user may acquire a ring 4 device at a retail location, such as a bank or a mobile device carrier store (AT&T, Verizon, and the like). In this retail setting the user may initially try on non-functional rings for determining the correct ring size before receiving a functional ring 4 device.
When NFC IC 40 is enabled, ring 4 can be used to make various NFC transactions, such as financial transactions that require secure identity authentication as well as financial data. For example, to make a payment in a grocery store checkout line, the user places their left hand with ring 4 on the left ring finger, in close proximity to NFC reader 40 as shown in
When removed from the finger (ring is expanded) ring 4 no longer functions for transactions. Ring 4 is disabled for transactions until ring 4 is placed back on the finger (ring is expanded) and the correct PIN is entered into PIN app 112 running on mobile device 22.
In this embodiment ring 4 is meant to be worn permanently, much like a wedding band or other ring that is ornamental. When worn permanently and used for NFC transactions, virtually no battery 44A and 44B power is used.
The power consumption for one cycle of removing ring 4 (disabling NFC IC 40) and donning ring 4 (enabling NFC IC 40 by BLE communication with mobile device 22) will use approximately 0.17 mAh, or 0.6% of the charge stored in battery 44A and 44B. For example removing ring 4 once per week for a year would reduce the battery life of ring 4 down to approximately 3.5 years.
In another embodiment where ring 4 includes an energy harvesting sub-system, energy from the NFC transaction is captured and returned to charge battery 44A and 44B. An example of such an energy harvesting sub-system is included in the M24LR16E-R, a Dynamic NFC/RFID tag IC, manufactured by ST Microelectronics of Geneva, Switzerland. The M24LR16E-R routes excess energy (energy that the IC does not use to operate) to an analog power output pin. This sub-system is combined with an LTC3588 Nanopower Energy Harvesting Power Supply IC, provided by Linear Technology of Milpitas, Calif.
Referring now to
In another embodiment ring 4 includes an external gold-plated charging contact 180A and 180B that mate with a charging adapter 184 that is powered by an AC-DC converter or a USB connection. In this embodiment, ring includes a 5V battery charging IC and related components.
In another embodiment, jewel ring 28 includes all of the components and functions described herein but also includes one or more ornamental jewel.
In another embodiments, separate NFC IC 40, BLE IC 48, energy harvesting IC 84, and battery management and charging IC 50 are all integrated onto a single integrated circuit. The advantage is a reduction in size and power consumption.
In another embodiment, a latching circuit is used to apply power to the Bluetooth IC, so that the IC can be powered off, thereby using no electrical energy in everyday use for executing NFC transactions.
In another embodiment, the wearable authentication device need not be in a ring format. It could for example be in the form of a bracelet, or wrist watch with an expansion sensor similar in function to expansion sensor 16.
The sensor that senses the removal of the device need not be an expansion sensor such as the one described in the above embodiment. In another embodiment, a bracelet or watch includes a clasp with a metal contact that makes and breaks a conductive connection that is connected to BLE IC 48 when the device is donned, and makes and breaks the conductive connection when the device is removed. But the function of BLE IC 48, NFC IC 40 and BLE application 96, NFC application 108, and mobile device app 112 remains the same.
In another embodiment, the fingerprint identification function on a smartphone, such as an iPhone 6, is used to validate the identity of the ring wearer, in place of or in addition to entering a PIN. Upon successful confirmation validation of the user's fingerprint, PIN app 112 then sends a PIN VALID RESPONSE message to device 4 which enters a fully functional state and can be used for transactions with valid NFC reader 40 devices.
It is to be understood that the present invention is not limited to the embodiment(s) described above and illustrated herein, but encompasses any and all variations falling within the scope of the appended claims.
This application claims the benefit of U.S. Provisional Application No. 62/085,497, filed Nov. 28, 2014, entitled Wearable Identity Authentication Device and System.
Number | Date | Country | |
---|---|---|---|
62085497 | Nov 2014 | US |