IP Library Granted Patent US 8,739,262
Granted Patent B2
US 8,739,262 · App. 12/973,725 · Granted May 27, 2014

Tokenized data security

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 8,739,262
App. No.
12/973,725
Granted
May 27, 2014
Kind
B2
Abstract

Provided are devices, methods, systems, computer readable storage media and other means for tokenizing data. In some examples, credit card numbers are tokenized using a pre-generated token map and absent the use of a networked database that stores a relatively large quantity of credit card numbers in a central location. The token map may be generated by a token map generator such that the token map can be used by a tokenizer to replace a portion of an account number with a token, and by a detokenizer to replace the token with the original portion of the account number. A pre-parser and parser may also be used to locate an account number and/or token in a message received over a network.

Claims (43)

1. A method of tokenizing an account number comprising:

receiving at least a portion of the account number, wherein the at least a portion of the account number comprises a version identifier;

accessing, by a processor, a token map associated with the version identifier;

retrieving, from the token map, a randomly assigned token value that was pre-associated with the at least a portion of the account number;

converting the token value to a different numeric system;

generating a token by combining the version identifier with the token value; and

transmitting at least the token.

2. The method of claim 1 further comprising:

determining a length of the account number; and

selecting the token map based on the length of the account number.

3. The method of claim 2 , wherein the token value's length is dependent on the length of the account number.

4. The method of claim 1 , wherein the receiving at least the portion of the account number comprises receiving the entire account number and the method further comprising:

extracting a middle digits value from the account number, wherein retrieving the token value comprises using the middle digits value as a linking mechanism.

5. The method of claim 1 , wherein:

receiving at least the portion of the account number comprises receiving a binary representation of a base10 number; and

converting the token value to the different numeric system comprises converting the token to a base36 numeric system.

6. The method of claim 1 , wherein:

receiving at least the portion of the account number is from a source device; and

transmitting at least the token is to the source device.

7. The method of claim 1 , wherein:

receiving at least the portion of the account number is from a source device; and

transmitting at least the token to a device that is different than the source device.

8. The method of claim 1 , wherein accessing the token map comprises decrypting the token map.

9. The method of claim 1 further comprising storing the entire token map on a server's random access memory.

10. The method of claim 1 , wherein generating the token comprises generating the token to have a length that is the same as the entire account number.

11. A system comprising:

a storage device configured to store a token map associated with a version identifier, wherein the token map comprises at least one token value pre-associated with a partial account number, wherein the partial account number comprises the version identifier; and

a processor configured to generate a token for an account number associated with the partial account number by retrieving the token value from the token map.

12. The system of claim 11 , wherein the storage device is random access memory of a server.

13. The system of claim 11 , wherein the processor is further configured to generate the token map by randomly associating token values with array location values.

14. The system of claim 11 , wherein the processor is further configured to parse the account number and extract the partial account number, wherein the partial account number is a string of middle digits.

15. The system of claim 11 , wherein the processor is further configured to receive a tokenized account number and extract a second token using the token map.

16. A method of detokenizing a token comprising:

receiving at least a portion of a tokenized account number;

parsing, by a processor, a token from the tokenized account number;

parsing a version identifier from the token;

accessing a token map associated with the version identifier;

retrieving, from the token map, a portion of a detokenized account number associated with the token; and

transmitting at least the portion of the detokenized account number.

17. The method of claim 16 further comprising converting the token from a base36 numerical scheme to a base10 numerical scheme before retrieving the portion of the detokenized account number.

18. The method of claim 16 further comprising constructing the detokenized account number by inserting the portion of the detokenized account number between two sets of digits included in the tokenized account number.

19. A method of transmitting an account number, comprising transmitting, by a communication interface configured for at least one of wired or wireless communication, a string of characters comprising between ten and nineteen numeric digits that represent the account number, wherein at least six of the numeric digits are tokenized characters and at least four of the numeric digits are untokenized characters.

20. The method of claim 19 , wherein the tokenized characters are represented alphanumerically and the untokenized characters are represented numerically with a base10 numerical scheme.

Assignments (22)
SECURITY INTEREST Recorded Feb 13, 2026
From: SABRE GLBL INC.; TVL LP
To: COMPUTERSHARE TRUST COMPANY, N.A.
Reel/Frame 073787/0584 →
SECURITY INTEREST Recorded Dec 8, 2025
From: SABRE GLBL INC.; TVL LP
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 073146/0059 →
TERMINATION AND RELEASE OF SECURITY INTERESTIN PATENTS Recorded Sep 2, 2025
From: COMPUTERSHARE TRUST COMPANY, N.A., AS COLLATERAL AGENT
To: SABRE GLBL INC.; TVL LP
Reel/Frame 072809/0498 →
SECURITY INTEREST Recorded Jun 5, 2025
From: SABRE GLBL INC.; TVL LP
To: COMPUTERSHARE TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 071325/0435 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS [REEL/FRAME 064091/0576] Recorded Jun 4, 2025
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS ADMINISTRATIVE AGENT
To: SABRE GLBL INC.; TVL LP
Reel/Frame 071481/0949 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Apr 15, 2025
From: COMPUTERSHARE TRUST COMPANY, N.A., AS COLLATERAL AGENT
To: SABRE GLBL INC.; TVL LP
Reel/Frame 070851/0247 →
PATENT SECURITY AGREEMENT (NOTES EXCHANGE) Recorded Dec 16, 2024
From: GETTHERE L.P.; TVL LP; SABRE GLBL INC.
To: COMPUTERSHARE TRUST COMPANY, N.A. AS COLLATERAL AGENT
Reel/Frame 069712/0948 →
SECURITY INTEREST Recorded Sep 11, 2023
From: SABRE HOLDINGS CORPORATION; SABRE GLBL INC.; GETTHERE INC.; GETTHERE L.P.; LASTMINUTE.COM HOLDINGS, INC.; LASTMINUTE.COM LLC; SABRE INTERNATIONAL NEWCO, INC.; SABREMARK G.P., LLC; SABREMARK LIMITED PARTNERSHIP; TVL COMMON, INC.; SABRE GDC, LLC; PRISM TECHNOLOGIES, LLC; PRISM GROUP, INC.; NEXUS WORLD SERVICES, INC.; IHS US INC.; INNLINK LLC; TRAVLYNX LLC; RSI MIDCO, INC.; RADIXX SOLUTIONS INTERNATIONAL, INC.; TVL HOLDINGS, INC.; TVL LLC; TVL HOLDINGS I, LLC; TVL LP
To: COMPUTERSHARE TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 064859/0026 →
SECURITY INTEREST Recorded Jun 28, 2023
From: SABRE HOLDINGS CORPORATION; SABRE GLBL INC.; TVL LP; GETTHERE L.P.
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS ADMINISTRATIVE AGENT
Reel/Frame 064091/0576 →
SECURITY INTEREST Recorded Dec 6, 2022
From: SABRE GLBL INC.
To: COMPUTERSHARE TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 061999/0533 →
RELEASE OF SECURITY INTEREST Recorded Jan 12, 2021
From: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
To: SABRE GLBL INC.
Reel/Frame 054897/0418 →
RELEASE OF SECURITY INTEREST Recorded Sep 11, 2020
From: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
To: SABRE GLBL INC.
Reel/Frame 053750/0716 →
SECURITY INTEREST Recorded Sep 11, 2020
From: SABRE GLBL INC.
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 053751/0325 →
SECURITY INTEREST Recorded Apr 17, 2020
From: SABRE GLBL INC.
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 052429/0274 →
SECURITY INTEREST Recorded Nov 9, 2015
From: SABRE GLBL INC.
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 036992/0128 →
SECURITY INTEREST Recorded Apr 14, 2015
From: SABRE GLBL INC.
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 035407/0376 →
RELEASE OF SECURITY INTEREST Recorded Apr 14, 2015
From: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
To: SABRE HOLDINGS CORPORATION; SABRE GLBL INC.; TVL LP; GETTHERE L.P.; SITE59.COM, LLC
Reel/Frame 035424/0844 →
CHANGE OF NAME Recorded Feb 11, 2014
From: SABRE INC.
To: SABRE GLBL INC.
Reel/Frame 032239/0138 →
AMENDMENT OF SECURITY INTEREST IN PATENTS Recorded Feb 19, 2013
From: DEUTSCHE BANK AG NEW YORK BRANCH
To: BANK OF AMERICA, N.A.
Reel/Frame 029834/0757 →
SECURITY AGREEMENT Recorded May 11, 2012
From: SABRE INC.
To: WELLS FARGO BANK, NATIONAL ASSOCIATION
Reel/Frame 028194/0505 →
SECURITY AGREEMENT Recorded Mar 16, 2011
From: SABRE INC.
To: DEUTSCHE BANK AG NEW YORK BRANCH, AS ADMINISTRATIVE AGENT
Reel/Frame 025968/0381 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 20, 2010
From: HARPER, GLENN E.; BOMAR, KEVIN B.
To: SABRE INC.
Reel/Frame 025531/0715 →