Tokenization in mobile environments

• US 9,430,767 B2
• Filed: 11/02/2015
• Issued: 08/30/2016
• Est. Priority Date: 02/10/2012
• Status: Active Grant

• Current Assignee: Protegrity USA, Inc. (Xcelera Inc.)
• Original Assignee: Protegrity USA, Inc. (Xcelera Inc.)
• Inventors: Mattsson, Ulf, Rozenberg, Yigal
• Primary Examiner(s): LE, CHAU D
• Application Number:
  US14/929,676
• Publication Number:
  US 20160055482A1
• Time in Patent Office: 302 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/606 by securing the transmission between two devices or processes
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/326 Payment applications installed on the mobile devices
• CPC Class Codes: G06Q 20/34 using cards, e.g. integrated circuit [IC] cards or magnetic cards
• CPC Class Codes: G06Q 20/367 involving electronic purses or money safes
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/3821 Electronic credentials
• CPC Class Codes: G06Q 20/3823 combining multiple encryption tools for a transaction
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography postage metering system using cryptography G06Q2250/05
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04W 12/02 Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
• CPC Class Codes: H04W 12/03 Protecting confidentiality, e.g. by encryption

Abstract

Data can be protected in mobile and payment environments through various tokenization operations. A mobile device can tokenize communication data based on device information and session information associated with the mobile device. A payment terminal can tokenize payment information received at the payment terminal during a transaction based on transaction information associated with the transaction. Payment data tokenized first a first set of token tables and according to a first set of tokenization parameters by a first payment entity can be detokenized or re-tokenized with a second set of token tables and according to a second set of tokenization parameters. Payment information can be tokenized and sent to a mobile device as a token card based on one or more selected use rules, and a user can request a transaction based on the token card. The transaction can be authorized if the transaction satisfies the selected use rules.

Claims

1. A mobile device configured for operation in a mobile environment comprising a central server configured to communicatively couple to and communicate with a plurality of mobile devices, comprising:

a hardware display configured to;

display an interface configured to enable an interaction with the mobile device by a user, the interaction generating sensitive data representative of the interaction; and

display, by the hardware display, information corresponding to the interaction;

a memory configured to store the sensitive data, one or more attributes of the interaction, and a set of token tables each mapping each of a plurality of input values to a different token value;

a token server coupled to the memory and configured to;

access, from the memory, a token table from the set of token tables in response to a request for the token table from a security engine of the mobile device; and

provide the accessed token table to the security engine; and

the security engine comprising at least one hardware processor coupled to the memory and configured to;

access the sensitive data in the memory;

request a token table from the token server via an internal communications bus coupling the token server to the security engine, the requested token table selected from the set of token tables based on one or more attributes of the interaction;

receive the selected token table from the token server via the internal communications bus;

modify the sensitive data using the selected token table by querying the selected token table with a value of a portion of the sensitive data to identify a token value mapped to the value of the portion of the sensitive data by the selected token table and replacing the portion of the sensitive data with the identified token value; and

responsive to a determination that the mobile device is communicatively coupled to the central server, providing the modified sensitive data to the central server via a communications network using the a communications interface of the mobile device.

2. The mobile device of claim 1, wherein the token server is configured to receive the set of token tables from the central server via the communications network using the communications interface.

3. The mobile device of claim 1, wherein the token server is configured to generate a token table seed value based on one or more attributes of the interaction, and to generate the selected token table using the token table seed value.

4. The mobile device of claim 1, wherein the one or more attributes of the interaction upon which the token table is selected comprises an identity of the user.

5. The mobile device of claim 1, wherein the one or more attributes of the interaction upon which the token table is selected comprises an identity of a second user associated with the interaction.

6. The mobile device of claim 1, wherein the one or more attributes of the interaction upon which the token table is selected comprises a time and date associated with the interaction.

7. The mobile device of claim 1, wherein the one or more attributes of the interaction upon which the token table is selected comprises a type of the interaction.

8. The mobile device of claim 1, wherein the central server is configured to receive via the communications network, and store in a storage device coupled to the central server, modified sensitive data received from each of the plurality of mobile devices.

9. The mobile device of claim 1, wherein the security engine is further configured to:

responsive to a determination by the communications interface that the mobile device is not communicatively coupled to the central server, store the modified sensitive data in the memory until the mobile device subsequently communicatively couples to the central server.

10. The mobile device of claim 1, wherein the modified data is provided via the communications network to the central server further in response to a request from the central server.

11. The mobile device of claim 1, wherein the communications network comprises a wireless communications network, and wherein the communications interface comprises a wireless communications interface.

12. A method for improving the performance of a mobile device in a mobile environment comprising a central server configured to communicatively couple to and communicate with a plurality of mobile devices, comprising:

accessing, by the mobile device, sensitive data representative of an interaction between a user and the mobile device;

storing, by a memory of the mobile device, the sensitive data, one or more attributes of the interaction, and a set of token tables each mapping each of a plurality of input values to a different token value;

selecting, by a token server coupled to the memory of the mobile device, a token table from the set of token tables based on one or more attributes of the interaction;

modifying, by a security engine coupled to the memory of the mobile device, the sensitive data using the selected token table by querying the selected token table with a value of a portion of the sensitive data to identify a token value mapped to the value of the portion of the sensitive data by the selected token table and replacing the portion of the sensitive data with the identified token value; and

responsive to a determination that the mobile device is communicatively coupled to the central server, providing, by the mobile device, the modified sensitive data to the central server.

13. The method of claim 12, wherein the set of token tables is received from the central server.

14. The method of claim 12, further comprising:

generating, by the mobile device, a token table seed value based on one or more attributes of the interaction; and

generating the selected token table based on the token table seed value.

15. The method of claim 12, wherein the one or more attributes of the interaction upon which the token table is selected comprises an identity of the user.

16. The method of claim 12, wherein the one or more attributes of the interaction upon which the token table is selected comprises an identity of a second user associated with the interaction.

17. The method of claim 12, wherein the one or more attributes of the interaction upon which the token table is selected comprises a time and date associated with the interaction.

18. The method of claim 12, wherein the one or more attributes of the interaction upon which the token table is selected comprises a type of the interaction.

19. The method of claim 12, wherein the central server is configured to receive and store modified sensitive data received from each of the plurality of mobile devices.

20. The method of claim 12, further comprising:

responsive to a determination that the mobile device is not communicatively coupled to the central server, storing, by the mobile device, the modified sensitive data until the mobile device subsequently communicatively couples to the central server.