Secure data translation using machine-readable identifiers
First Claim
1. A system, comprising:
- a client device comprising at least one hardware processor;
a reader device comprising at least one hardware processor; and
program instructions executable in the client device that, when executed, cause the client device to;
store a cryptographic key associated with a device profile;
access input data from a data store of the client device, the input data stored in association with the device profile and being in a first data format in accordance with a first data format setting, the first data format setting specifying a first language specified by an operator of the client device;
translate the input data in the first data format to data in a universal data format, the universal data format comprising an identifier that uniquely identifies a value of a field from which the input data was provided on the client device;
encrypt the data in the universal data format using the cryptographic key such that the data in the universal data format is only accessible by the reader device having the cryptographic key; and
generate a machine-readable identifier using the data as encrypted for rendering in a display accessible by the client device, the machine-readable identifier being a bar code or a quick response (QR) code; and
wherein the reader device is configured to;
capture an image of the machine-readable identifier;
decrypt the data as encrypted to access the data in the universal data format; and
translate the input data from the universal data format to a second data format in accordance with a second data format setting for display on the reader device, the second data format setting specifying a second, different language specified by an operator of the reader device using a reader application executable on the reader device.
2 Assignments
0 Petitions
Accused Products
Abstract
Disclosed are various embodiments for providing secure data translation using machine-readable identifiers, such as barcodes or quick response (QR) codes. A client device may be configured to translate input data stored in a first data format to data in a universal data format and encrypt the data in the universal data format using the cryptographic key such that the data in the universal data format is only accessible by the reader device having the cryptographic key. The client device may further generate a machine-readable identifier using the data as encrypted for rendering in a display accessible by the client device. A reader device may be configured to decrypt the data as encrypted to access the data in the universal data format, and translate the input data from the universal data format to a second data format in accordance with a second format setting.
-
Citations
11 Claims
-
1. A system, comprising:
-
a client device comprising at least one hardware processor; a reader device comprising at least one hardware processor; and program instructions executable in the client device that, when executed, cause the client device to; store a cryptographic key associated with a device profile; access input data from a data store of the client device, the input data stored in association with the device profile and being in a first data format in accordance with a first data format setting, the first data format setting specifying a first language specified by an operator of the client device; translate the input data in the first data format to data in a universal data format, the universal data format comprising an identifier that uniquely identifies a value of a field from which the input data was provided on the client device; encrypt the data in the universal data format using the cryptographic key such that the data in the universal data format is only accessible by the reader device having the cryptographic key; and generate a machine-readable identifier using the data as encrypted for rendering in a display accessible by the client device, the machine-readable identifier being a bar code or a quick response (QR) code; and wherein the reader device is configured to; capture an image of the machine-readable identifier; decrypt the data as encrypted to access the data in the universal data format; and translate the input data from the universal data format to a second data format in accordance with a second data format setting for display on the reader device, the second data format setting specifying a second, different language specified by an operator of the reader device using a reader application executable on the reader device. - View Dependent Claims (2, 3, 4)
-
-
5. A computer-implemented method, comprising:
-
storing, by a client device comprising at least one hardware processor, a cryptographic key associated with a device profile; accessing, by the client device, input data from a data store of the client device, the input data stored in association with the device profile and being in a first data format in accordance with a first data format setting, the first data format setting specifying a first language specified by an operator of the client device; translating, by the client device, the input data in the first data format to data in a universal data format, the universal data format comprising an identifier that uniquely identifies a value of a field from which the input data was provided; encrypting, by the client device, the data in the universal data format using the cryptographic key such that the data in the universal data format is only accessible by a reader device having the cryptographic key; generating, by the client device, a machine-readable identifier using the data as encrypted for rendering in a display accessible by the client device, the machine-readable identifier being a bar code or a quick response (QR) code; capturing, by the reader device comprising at least one hardware processor, an image of the machine-readable identifier; decrypting, by the reader device, the data as encrypted to access the data in the universal data format; and translating, by the reader device, the input data from the universal data format to a second data format in accordance with a second data format setting for display on the reader device, the second data format setting specifying a second, different language specified by an operator of the reader device using a reader application executable on the reader device. - View Dependent Claims (6, 7, 8)
-
-
9. A non-transitory computer-readable medium embodying program code executable in a reader device that, when executed by the reader device, causes the reader device to:
-
capture an image of a machine-readable identifier displayed on a client device, wherein the machine-readable identifier is generated by the client device by; storing a cryptographic key associated with a device profile; accessing input data from a data store of the client device, the input data stored in association with the device profile and being in a first data format in accordance with a first data format setting, the first data format setting specifying a first language specified by an operator of the client device; translating the input data in the first data format to data in a universal data format; encrypting the data in the universal data format using the cryptographic key such that the data in the universal data format is only accessible by the reader device having the cryptographic key, the universal data format comprising an identifier that uniquely identifies a value of a field from which the input data was provided on the client device; and generating the machine-readable identifier using the data as encrypted for rendering in a display accessible by the client device, the machine-readable identifier being a bar code or a quick response (QR) code; and decrypt the data as encrypted to access the data in the universal data format; and translate the input data from the universal data format to a second data format in accordance with a second format setting for display on the reader device, the second format setting specifying second, different language specified by an operator of the reader device using a reader application executable on the reader device. - View Dependent Claims (10, 11)
-
Specification