GENERATING BRIDGE MATCH IDENTIFIERS FOR LINKING IDENTIFIERS FROM SERVER LOGS
2 Assignments
0 Petitions
Accused Products
Abstract
Systems and methods of matching identifiers between multiple datasets are described herein. A system can transmit a first identifier vector to a third party server. The first identifier vector can include a first identifier, first parameters, and second parameters. The system can receive, from the third party server, the first identifier vector encrypted based on a third-party encryption. The system can receive, from the third party server, a second identifier vector encrypted based on the third-party encryption associated with the third party server. The second identifier vector can include a second identifier, third parameters, and fourth parameters. The system can determine a correlation count between the first identifier vector and the second identifier vector. The system can determine that the first identifier corresponds to the second identifier based on the correlation count. The system can generate one identifier key for both the first identifier and the second identifier.
-
Citations
40 Claims
-
1-20. -20. (canceled)
-
21. A system to bridge encrypted datasets, comprising:
-
a data processing system comprising one or more processors and memory, the data processing system configured to; transmit a first identifier vector to a server, the first identifier vector encrypted with a first encryption that is commutative and comprising a first identifier, a plurality of first parameters, and a plurality of second parameters; receive from the server, an encrypted first identifier vector comprising the first identifier vector encrypted based on the first encryption and further encrypted by a second encryption associated with the server, the second encryption commutative and different from the first encryption; receive a second identifier vector, encrypted based on the second encryption associated with the server, the second identifier vector comprising a second identifier, a plurality of third parameters, and a plurality of fourth parameters; encrypt the second identifier vector with the first encryption to generate an encrypted second identifier vector that is encrypted based on the second encryption and further encrypted based on the first encryption; determine a correlation count between the encrypted first identifier vector and the encrypted second identifier vector based on a match between at least some of the plurality of first parameters and at least some of the plurality of the third parameters of the encrypted first identifier vector and between at least some of the plurality of the second parameters and at least some of the plurality of fourth parameters of the encrypted second identifier vector; determine that the first identifier corresponds to the second identifier based on the correlation count between the first identifier vector and the second identifier vector; generate, responsive to the determination that the first identifier corresponds to the second identifier, one identifier key for both the first identifier and the second identifier; and provide the one identifier key for input into an application to process interactions, the one identifier key generated based on the correlation between the encrypted first identifier vector encrypted with the first encryption and further encrypted with the second encryption, and the encrypted second identifier vector encrypted with the second encryption and further encrypted with the first encryption. - View Dependent Claims (22, 23, 24, 25, 26, 27, 28, 29, 30, 31)
-
-
32. A method of bridging encrypted datasets, comprising:
-
transmitting, by a data processing system comprising one or more processors and memory, a first identifier vector to a server, the first identifier vector encrypted with a first encryption that is commutative and comprising a first identifier, a plurality of first parameters, and a plurality of second parameters; receiving, by the data processing system from the server, an encrypted first identifier vector comprising the first identifier vector encrypted based on the first encryption and further encrypted by a second encryption associated with the server, the second encryption being commutative and different from the first encryption; receiving, by the data processing system, a second identifier vector, encrypted based on the second encryption associated with the server, the second identifier vector comprising a second identifier, a plurality of third parameters, and a plurality of fourth parameters; encrypting, by the data processing system, the second identifier vector with the first encryption to generate an encrypted second identifier vector that is encrypted based on the second encryption and further encrypted based on the first encryption; determining, by the data processing system, a correlation count between the encrypted first identifier vector and the encrypted second identifier vector based on a match between at least some of the plurality of first parameters and at least some of the plurality of the third parameters of the encrypted first identifier vector and between at least some of the plurality of the second parameters and at least some of the plurality of fourth parameters of the encrypted second identifier vector; determining, by the data processing system, that the first identifier corresponds to the second identifier based on the correlation count between the first identifier vector and the second identifier vector; generating, by the data processing system, responsive to determining that the first identifier corresponds to the second identifier, one identifier key for both the first identifier and the second identifier; and providing, by the data processing system, the one identifier key for input into an application to process interactions, the one identifier key generated based on the correlation between the encrypted first identifier vector encrypted with the first encryption and further encrypted with the second encryption, and the encrypted second identifier vector encrypted with the second encryption and further encrypted with the first encryption. - View Dependent Claims (33, 34, 35, 36, 37, 38, 39, 40)
-
Specification