IP Library Granted Patent US 9,904,923
Granted Patent B2
US 9,904,923 · App. 15/632,690 · Granted Feb 27, 2018

Tokenization in mobile environments

Inventors: Ulf Mattsson (Cos Cob, CT); Yigal Rozenberg (Wilton, CT)
Assignee: Protegrity Corporation
G06Q20/405G06F21/6245G06Q20/3223G06Q20/367G06Q20/4014G06F21/606G06Q20/34G06Q20/3829G06Q2220/00H04L2209/56
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,904,923
App. No.
15/632,690
Granted
Feb 27, 2018
Kind
B2
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 (37)

1. A method for tokenizing data, comprising:

receiving, at an input/output interface of a communication system, information associated with an interaction between a user and the communication system;

generating, by a token server of the communication system, a first set of token tables, each token table in the first set of token tables mapping each of a plurality of input values to a different token value;

tokenizing, by a security engine of the communication system, the received information using the first set of token tables to form first tokenized information;

transmitting, by the input/output interface of the communication system, the first set of token tables to a central security system communicatively coupled to both the communication system and a central server communicatively coupled to a network associated with the interaction; and

transmitting, by the input/output interface of the communication system, the first tokenized information to the central server, the central server configured to receive the first set of token tables and a second set of token tables from the central security system, each token table in the second set of token tables mapping each of a plurality of input values to a different token value, and further configured to tokenize the first tokenized information using the second set of token tables to form second tokenized information and to transmit the second tokenized information to the network.

2. The method of claim 1 , wherein the received information comprises information associated with a user account.

3. The method of claim 1 , wherein the received information comprises information identifying the user.

4. The method of claim 1 , wherein the received information comprises information describing the interaction.

5. The method of claim 1 , wherein the received information comprises information describing the network.

6. The method of claim 1 , wherein the first set of token tables and the second set of token tables are each generated based on a type of the interaction.

7. The method of claim 1 , wherein the first set of token tables further comprises a first encryption algorithm and wherein the second set of token tables further comprises a second encryption algorithm.

8. The method of claim 7 , further comprising:

encrypting, by the communication system, the first tokenized information based on the first encryption algorithm;

decrypting, by the central server, the first tokenized information based on the first encryption algorithm; and

encrypting, by the central server, the second tokenized information based on the second encryption algorithm.

9. The method of claim 1 , wherein the first set of token tables further comprises a first initialization vector (“IV”) and a first IV modification operation, and wherein the second set of token tables further comprises a second IV and a second IV modification operation.

10. The method of claim 9 , further comprising:

modifying, by the communication system, the first tokenized information with the first IV based on the first IV modification operation;

demodifying, by the central server, the first tokenized information with the first IV based on the first IV modification operation; and

modifying, by the central server, the second tokenized information with the second IV based on the second IV modification operation.

11. A system for tokenizing data, comprising:

a communication system, configured to:

receive, at an input/output interface of the communication system, information associated with an interaction between a user and the communication system;

generate, by a token server of the communication system, a first set of token tables, each token table in the first set of token tables mapping each of a plurality of input values to a different token value;

tokenize, by a security engine of the communication system, the received information using on the first set of token tables to form first tokenized information;

transmit, by the input/output interface of the communication system, the first set of token tables to a central security system communicatively coupled to both the communication system and a central server communicatively coupled to a network associated with the interaction; and

transmit, by the input/output interface of the communication system, the first tokenized information to the central, the central server configure to receive the first set of token tables and a second set of token tables from the central security system, each token table in the second set of token tables mapping each of a plurality of input values to a different token value, and further configured to tokenize the first tokenized information using the second set of token tables to form second tokenized information and to transmit the second tokenized information to the network.

12. The system of claim 11 , wherein the received information comprises information associated with a user account.

13. The system of claim 11 , wherein the received information comprises information identifying the user.

14. The system of claim 11 , wherein the received information comprises information describing the interaction.

15. The system of claim 11 , wherein the received information comprises information describing the network.

16. The system of claim 11 , wherein the first set of token tables and the second set of token tables are each generated based on a type of the interaction.

17. The system of claim 11 , wherein the first set of token tables further comprises a first encryption algorithm and wherein the second set of token tables further comprises a second encryption algorithm.

18. The system of claim 17 , wherein the communication system is further configured to encrypt the first tokenized information based on the first encryption algorithm, and wherein the central server is further configured to decrypt the first tokenized information based on the first encryption algorithm and encrypt the second tokenized information based on the second encryption algorithm.

19. The system of claim 11 , wherein the first set of token tables further comprises a first initialization vector (“IV”) and a first IV modification operation, and wherein the second set of token tables further comprises a second IV and a second IV modification operation.

20. The system of claim 19 , wherein the communication system is further configured to modify the first tokenized information with the first IV based on the first IV modification operation, and wherein the central server is further configured to demodify the first tokenized information with the first IV based on the first IV modification operation and modify the second tokenized information with the second IV based on the second IV modification operation.

Assignments (3)
SECURITY INTEREST Recorded Aug 2, 2024
From: PROTEGRITY USA, INC.; PROTEGRITY LIMITED HOLDING, LLC; PROTEGRITY US HOLDING, LLC; PROTEGRITY CORPORATION; KAVADO, LLC
To: CANADIAN IMPERIAL BANK OF COMMERCE
Reel/Frame 068326/0020 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 29, 2024
From: PROTEGRITY CORPORATION
To: PROTEGRITY US HOLDING, LLC
Reel/Frame 067566/0462 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 15, 2017
From: MATTSSON, ULF; ROZENBERG, YIGAL
To: PROTEGRITY CORPORATION
Reel/Frame 043600/0129 →
Continuity (7)
Continuation 15344980 · Nov 7, 2016
Continuation 14516489 · Oct 16, 2014
Continuation 13761011 · Feb 6, 2013
Provisional Application 61597588 · Feb 10, 2012
Provisional Application 61597592 · Feb 10, 2012
Provisional Application 61609677 · Mar 12, 2012
Related Publication 20170293915A1 · Oct 12, 2017