RF transaction system and method for storing user personal data

• US 9,024,719 B1
• Filed: 10/15/2004
• Issued: 05/05/2015
• Est. Priority Date: 07/10/2001
• Status: Expired due to Fees

• Current Assignee: Liberty Peak Ventures, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Xatra Fund MX LLC (Intellectual Ventures LLC)
• Inventors: Saunders, Peter D
• Primary Examiner(s): Zimmerman, Brian
• Assistant Examiner(s): Khan, Omer S
• Application Number:
  US10/711,964
• Time in Patent Office: 3,854 Days
• Field of Search: 340/5.61, 340/10.3, 235/381, 235/382, 235/382.5
• US Class Current: 340/5.61
• CPC Class Codes: G06Q 10/0631 Resource planning, allocation, distributing or scheduling for enterprises or organisations
• CPC Class Codes: G06Q 20/00 Payment architectures, schemes or protocols apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/14 specially adapted for billing systems
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/28 Pre-payment schemes, e.g. "pay before"
• CPC Class Codes: G06Q 20/321 using wearable devices
• CPC Class Codes: G06Q 20/327 Short range or proximity payments by means of M-devices
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/342 Cards defining paid or billed services or quantities
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/40145 Biometric identity checks
• CPC Class Codes: G06Q 40/08 Insurance
• CPC Class Codes: G07C 9/26 using a biometric sensor integrated in the pass
• CPC Class Codes: G07C 9/28 the pass enabling tracking or indicating presence
• CPC Class Codes: G07C 9/29 the pass containing active electronic elements, e.g. smartcards
• CPC Class Codes: G07F 7/025 by means, e.g. cards, providing billing information at the time of purchase, e.g. identification of seller or purchaser, quantity of goods delivered or to be delivered
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 10/65 stored on portable record carriers, e.g. on smartcards, RFID tags or CD
• CPC Class Codes: H04L 2209/12 : Details relating to cryptographic hardware or logic circuitry
• CPC Class Codes: H04L 2209/56 : Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 2209/805 : Lightweight hardware, e.g. radio-frequency identification [RFID] or sensor
• CPC Class Codes: H04L 9/3234 : involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853

Abstract

A system and method for a RF transaction device for storing user personal data is disclosed. The invention includes a system and method for facilitating a healthcare transaction using a transponder system configured to store different healthcare information in different storage areas on a database. The invention includes providing account information in ISO/IEC 7816 magnetic stripe Track 1/Track 2 format. The invention also includes an RFID reader for transmitting account and database information. In one embodiment the invention provides an RFID reader as a free standing or a computer implemented device. In another embodiment, biometric security measures are used in conjunction with the transponder system. In another embodiment, the transponder system communicates with one or more third-party healthcare providers to facilitate the transfer of healthcare and personal information.

Claims

1. A method comprising:

receiving, at a Radio Frequency (RF) reader, a transaction request from an RF Transaction device configured to store a first data set associated with a first data set owner in a first data storage area on the RF transaction device;

searching the RF transaction device to determine if at least one of the first data set or a second data set is available for use in connection with the transaction request;

receiving an add request from the RF transaction device to add the second data set to the RF transaction device in response to the second data set not being available for use;

allocating a second data storage area on the RF transaction device in response to the add request from the RF transaction device and in response to an issuer system indicating that the first data set is available for addition to the RF transaction device;

receiving, at the RF reader, the second data set from a point of interaction terminal of the merchant system, wherein the second data set is inputted into the point of interaction terminal by a transaction device distinct from the RF transaction device;

adding, by the RF reader, the second data set to the RF transaction device in the second data storage area, wherein the second data storage area is reserved for use by a second data set owner distinct from the first data set owner; and

processing the transaction request in response to the adding the second data set.

2. The method of claim 1, further comprising displaying a message on a user interface of the RF Identification (RFID) reader in response to the second data set not being available.

3. The method of claim 1, further comprising storing a first transaction device account code in the first data storage area, and storing a second transaction device account code in the second data storage area.

4. The method of claim 2, further comprising receiving the add request in response to the displaying the message on the RFID reader user interface.

5. The method of claim 1, wherein at least one of the first data set or the second data set includes healthcare information to facilitate a healthcare transaction.

6. The method of claim 1, further comprising enrolling the first data set owner and the second data set owner in multiple transaction accounts on the RF transaction device.

7. The method of claim 1, wherein the processing the transaction request comprises processing the transaction request with a first account identifier stored in the first data set.

8. The method of claim 1, wherein the processing the transaction request comprises processing the transaction request with a second account identifier stored in the second data set.

9. The method of claim 5, wherein the healthcare information includes at least one of personal information, medical history, medical information, insurance information, and financial information.

10. The method of claim 1, wherein the first data set includes multiple healthcare transaction accounts associated with a single healthcare account identifier.

11. The method of claim 1, further comprising receiving the second data set from the issuer system.

13. The method of claim 1, further comprising modifying the first data set without involving the second data set owner.

14. The method of claim 1, wherein the transaction device includes at least one of a credit card, a debit card, and an insurance card.

15. The method of claim 1, wherein the first data storage area is not accessible by the second data set owner, and wherein the second data storage area is not accessible by the first data set owner.

16. The method of claim 1, further comprising instructing a control device on the RF transaction device to allocate the second data storage area on the RF transaction device.

12. A non-transitory memory element having stored thereon a plurality of instructions for execution by a processor, the plurality of instructions comprising:

instructions to receive, at a Radio Frequency identification (RFID) reader, a transaction request from an RF transaction device configured to store a first data set associated with a first data set owner in a first data storage area on the RF transaction device;

instructions to search the RF transaction device to determine if at least one of the first data set or a second data set is available for use in connection with the transaction request;

instructions to receive an add request from the RF transaction device to add the second data set to the RF transaction device in response to the second data set not being available for use;

instructions to allocate a second data storage area on the RF transaction device in response to the add request from the RF transaction device and in response to an issuer system indicating that the first data set is available for addition to the RF transaction device;

instructions to receive, at the RF reader, the second data set from a point of interaction terminal of the merchant system, wherein the second data set is inputted into the point of interaction terminal by a transaction device distinct from the RF transaction device;

instructions to add, by the RF reader, the second data set to the RF transaction device in the second data storage area, wherein the second data storage area is reserved for use by a second data set owner distinct from the first data set owner; and

instructions to process the transaction request in response to the instructions to add the second data set.