Back to results
US 8,595,812 B2Granted
Tokenized data security
AssigneeSabre Inc.
InventorsKevin B. Bomar, Glenn E. Harper
Life of this patent
Estimating the term…
Abstract
Provided are devices, methods, systems, computer readable storage media 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.
Claims17
A method of tokenizing an account number comprising:
- receiving a message;
- determining, by a hardware processor, that the message includes an account number;
- determining a length of the account number;
- selecting a token map based on the length of the account number;
- determining a size of a targeted segment based on the length of the account number;
- extracting the targeted segment from the account number;
- replacing the targeted segment with a token value and a token map version identifier associated with the token map;
- receiving a second message;
- determining that the second message includes at least a first predetermined number of characters;
- determining that the second message includes a second account number;
- determining a second length of the second account number;
- locating a vendor code within the second account number;
- extracting the vendor code;
- analyzing the vendor code to determine an expected length of the second account number;
- determining whether the second length of the second account number is the same as the expected length;
- executing a Luhn test after determining the second length of the second account number is the same as the expected length;
- and
- providing the second account number to a parser after determining the second length is the same as the expected length.
15 more elements
A method of tokenizing an account number comprising:
- receiving a message;
- determining, by a hardware processor, that the message includes an account number;
- determining a length of the account number;
- selecting a token map based on the length of the account number;
- determining a size of a targeted segment based on the length of the account number;
- extracting the targeted segment from the account number;
- replacing the targeted segment with a token value and a token map version identifier associated with the token map;
- receiving a second message;
- determining that the second message includes at least a first predetermined number of characters;
- determining that the second message includes a second account number;
- determining a second length of the second account number;
- locating a vendor code within the second account number;
- extracting the vendor code;
- analyzing the vendor code to determine an expected length of the second account number;
- determining whether the second length of the second account number is the same as the expected length;
- and
- removing digits from the second account number to define a new length after determining the second length of the second account number is different than the expected length.
14 more elements
A method of detokenizing an account number comprising:
- receiving a message;
- searching, by a hardware processor, for a token pattern in the message;
- finding the token pattern in the message;
- after finding the token pattern in the message, locating a tokenized account number;
- parsing a token from the tokenized account number;
- extracting a token map identifier from the token;
- retrieving a token map based on the token map identifier;
- replacing the token with a targeted segment in the account number;
- and
- validating the token map identifier before retrieving the token map.
7 more elements
A method of detokenizing an account number comprising:
- receiving a message;
- searching, by a hardware processor, for a token pattern in the message;
- finding the token pattern in the message;
- after finding the token pattern in the message, locating a tokenized account number;
- parsing a token from the tokenized account number;
- extracting a token map identifier from the token;
- retrieving a token map based on the token map identifier;
- replacing the token with a targeted segment in the account number;
- and
- converting the token to a base 10 number.
7 more elements
A system comprising:
- at least one hardware processor configured to:
- determine that a message includes an account number;
- determine a length of the account number;
- select a token map based on the length of the account number;
- determine a size of a targeted segment based on the length of the account number;
- extract the targeted segment from the account number;
- receive a second message;
- determine that the second message includes at least a first predetermined number of characters;
- determine that the second message includes a second account number;
- determine a second length of the second account number;
- locate a vendor code within the second account number;
- extract the vendor code;
- analyze the vendor code to determine an expected length of the second account number;
- determine whether the second length of the second account number is the same as the expected length;
- execute a Luhn test after determining the second length of the second account number is the same as the expected length;
- and
- parse the second account number after determining the second length is the same as the expected length.
14 more elements
A system comprising:
- at least one hardware processor configured to:
- determine that a message includes an account number;
- determine a length of the account number;
- select a token map based on the length of the account number;
- determine a size of a targeted segment based on the length of the account number;
- extract the targeted segment from the account number;
- receive a second message;
- determine that the second message includes at least a first predetermined number of characters;
- determine that the second message includes a second account number;
- determine a second length of the second account number;
- locate a vendor code within the second account number;
- extract the vendor code;
- analyze the vendor code to determine an expected length of the second account number;
- determine whether the second length of the second account number is the same as the expected length;
- and
- remove digits from the second account number to define a new length after determining the second length of the second account number is different than the expected length.
13 more elements
Dependencies are inferred from the claim text.