SECURE NEAR FIELD TRANSACTION

• US 20080041937A1
• Filed: 08/21/2006
• Published: 02/21/2008
• Est. Priority Date: 08/21/2006
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: MCI Financial Management Corp.
• Inventors: Vawter, Jamison
• Granted Patent: US 7,748,618 B2
• Time in Patent Office: Days
• US Class Current: 235/380
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/327 Short range or proximity payments by means of M-devices
• CPC Class Codes: G06Q 20/367 involving electronic purses or money safes
• CPC Class Codes: G06Q 20/3672 initialising or reloading thereof
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 20/4012 Verifying personal identification numbers [PIN]

Abstract

A managed service for a near field transaction that may include a server to register a wireless device with the managed service, provide authentication information to the wireless device for use in establishing an identity of the wireless device. The server may provide authorization information to a register on behalf of the wireless device to establish the identity to the register, where the identity, when valid, allows the wireless device to participate in the near field transaction via a secure near field communication session with the register, receive transaction information from the register or the wireless device, and store the transaction information with a transaction identifier, where the transaction identifier is used to recall the transaction information on behalf of the register or the wireless device.

Claims

1. A managed service for a near field transaction, comprising:

a server to;

register a wireless device with the managed service,

provide authentication information to the wireless device for use in establishing an identity of the wireless device,

provide authorization information to a register on behalf of the wireless device to establish the identity to the register, where the identity, when valid, allows the wireless device to participate in the near field transaction via a secure near field communication session with the register,

receive transaction information from the register or the wireless device, and

store the transaction information with a transaction identifier, where the transaction identifier is used to recall the transaction information on behalf of the register or the wireless device.

2. The managed service of claim 1, wherein the server is adapted to:

send a token, a password, personal identification number, a name, an address, a telephone number, a seed, a secure ID value, or code to the wireless device for use with the authentication information.

3. The managed service of claim 1, wherein the server provides the managed service to an enterprise that operates the register and a plurality of other registers.

4. The managed service of claim 1, wherein the server is operated by a communication provider.

5. A transaction device, comprising:

an interface to;

receive identity information from a handheld device via a near field communication link,

send transaction information to the handheld device during a secure near field communication session carried via the near field communication link when the identity is validated,

receive payment from the handheld device during the near field communication session, and

send completed transaction information to a server for storage thereon; and

a processing module to;

process the identity information, where the identity information identifies the handheld device,

process an authorization related to the handheld device to validate the identity,

process transaction items on behalf of the handheld device,

generate the transaction information,

process the payment, and

produce the completed transaction information.

6. The transaction device of claim 5, wherein the processing module is configured to:

process a token, a personal identification number, a watermark, a name, an address, a phone number, a serial number, a secure ID value, a secure identification value (SIV), or code received from the handheld device as part of the identity information.

7. The transaction device of claim 5, wherein the interface is configured to:

initiate an exchange of information with the handheld device by sending a radio frequency identification (RFID) query to the handheld device over the near field communication link.

8. The transaction device of claim 5, wherein the interface is configured to:

send authentication information, authorization information, transaction information, completed transaction information, or other information to an enterprise.

9. The transaction device of claim 5, wherein the interface comprises:

a RFID reader to receive identity information from the handheld device.

10. The transaction device of claim 9, wherein the RFID reader is configured to:

activate radio frequency identification logic in the handheld device to cause the handheld device to transmit the identity information.

11. The transaction device of claim 5, wherein the interface is configured to:

detect a presence of the handheld device.

12. The transaction device of claim 5, wherein the interface is configured to:

receive a personal identification number from the handheld device, where the personal identification number augments the identity information to establish the identity of the handheld device.

13. The transaction device of claim 5, wherein the interface is configured to:

receive retrieved completed transaction information from the server, where the retrieved completed transaction information is related to the handheld device and the transaction information.

14. The transaction device of claim 5, wherein the interface is configured to:

send the completed transaction information to the server, where the completed transaction information is adapted for recall by the transaction device when an item related to the completed transaction information is returned or exchanged on behalf of the handheld device.

15. The transaction device of claim 5, wherein the authorization or the completed transaction information is provided to the server via a managed service.

16. The transaction device of claim 5, wherein the transaction device is one of a plurality of registers operating in an enterprise.

17. A portable device, comprising:

first logic to;

provide a presence indication to a register, where the presence indication identifies that the portable device is proximate to a portion of the register,

receive a query on behalf of the register requesting identifying information,

provide the identifying information,

receive transaction information from the register via a near field link when the identifying information is valid, where the transaction information identifies transaction items related to the portable device, and

send payment information to the register via the near field link;

second logic to;

send the transaction information or payment information to a server, where the server stores the transaction information or the payment information on behalf of the portable device; and

third logic to;

store the transaction information, the payment information, or the identifying information.

18. The portable device of claim 17, wherein the first logic is configured to:

provide the identifying information via a secure near field communication link.

19. The portable device of claim 17, wherein the second logic is configured to:

receive a token, a personal identification number, a watermark, a name, an address, a phone number, a serial number, a secure ID value, a secure identification value (SIV), or code from the server for use as the identifying information.

20. The portable device of claim 17, wherein the third logic is configured to:

display the transaction information on a display to mirror transaction information on a register display.

21. The portable device of claim 17, wherein the third logic is configured to:

process retrieved transaction information received from the server, and

display the retrieved transaction on a display.

22. The portable device of claim 17, wherein the first logic is configured to:

receive information from a wireless device during a peer-to-peer transaction.

23. The portable device of claim 17, wherein the second logic is configured to:

send the transaction information, the payment information, or other information to the server, where the server stores the transaction information, the payment information, or the other information on behalf of the portable device.

24. The portable device of claim 23, wherein the second logic is further configured to:

send the transaction information, the payment information, or the other information to the server via a far field communication link.

25. A transaction device, comprising:

first logic to;

sense a terminal,

send a radio frequency identification (RFID) query to the terminal based on the sensing,

receive identification information from the terminal in response to the query,

send transaction information to the terminal during a purchase transaction, where the terminal displays the transaction information during the transaction, and

receive payment information from the terminal in response to a payment request related to the transaction;

second logic to;

send an authorization request to a server, where the authorization request includes a portion of the identification information,

receive an authorization from the server indicating that the identity is valid when the identification information matches stored identification information,

send the transaction information and the payment information to a destination device, and

receive stored transaction information or payment information from the destination device; and

third logic to;

process transaction items related to the terminal during the transaction,

generate the transaction information,

display the transaction information on a display device, and

process the stored transaction information or the payment information during a return transaction.