Content-based association of device to user
View Patent ↗Example methods and systems for content-based association of a device to a user are presented. In an example method, data corresponding to each of a plurality of items of content stored within a user device are accessed. A device identifier for the user device is generated based on the data. The device identifier is transmitted from the user device to a service device to associate the user device with a user.
1. A method comprising:
accessing, using one or more processors of a user device, first data corresponding to each of a first group of content items to which access by a first application installed on the user device is confined by a first set of permissions;
accessing, using the one or more processors of the user device, second data corresponding to each of a second group of content items to which access by a second application installed on the user device and distinct from the first application is confined by a second set of permissions, the second group of content items and the first group of content items being distinct but overlapping proper subsets of a third group of content items accessible by the user device;
generating, using the one or more processors of the user device via execution of a first module associated with the first application and confined by the first set of permissions, a first device identifier of the user device based on the first data;
generating, using the one or more processors of the user device via execution of a second module distinct from the first module and associated with the second application and confined by the second set of permissions, a second device identifier of the user device based on the second data; and
transmitting, using the one or more processors of the user device, the first and second device identifiers of the user device from the user device to a service device configured to associate the user device with a user identifier of a user based on a determination that the first and second device identifier both correspond to the user device.
2. The method of claim 1 , wherein:
the generating of the first device identifier comprises hashing the first data.
3. The method of claim 1 , further comprising:
receiving, from the service device, the user identifier of the user; and
personalizing, within the second application, at least one operation for the user based on the user identifier.
4. The method of claim 1 , further comprising:
combining the first device identifier and the second device identifier to generate a single device identifier.
5. The method of claim 4 , further comprising:
transmitting, from the user device to the service device, the single device identifier.
6. The method of claim 1 , further comprising:
selecting the first group of content items from the third group of content items based on dates associated with each of the first group of content items.
7. The method of claim 6 , wherein the selecting of the first items is based on the dates associated with each of the first group of content items being older than a predetermined date.
8. The method of claim 1 , wherein:
the first group of content items includes audio files; and
the first data includes metadata specifying play counts of the audio files.
9. The method of claim 1 , wherein:
the first group of content items includes image files; and
the first data includes metadata specifying sizes of the image files and capture dates of the image files.
10. The method of claim 1 , wherein:
the first group of content items includes video files; and
the first data includes metadata specifying sizes of the video files and capture dates of the video files.
11. The method of claim 1 , wherein:
the first group of content items includes contact information items; and
the first data includes metadata specifying contact names of the contact information items.
12. A non-transitory computer-readable memory device comprising instructions that, when executed by at least one processor of a machine, cause the machine to perform operations comprising:
receiving, from a user device, a first device identifier of the user device, the first device identifier being associated with a first application installed on the user device, the first device identifier being generated based on a first group of content items to which access by the first application is confined by a first set of permissions, the first identifier being generated by the user device via execution of a first module associated with the first application and confined by the first set of permissions;
assigning, in response to receiving the first device identifier of the user device, a user identifier of a user of the user device to the first device identifier of the user device;
receiving, from the user device, a second device identifier of the user device, the second device identifier being associated with a second application installed on the user device and distinct from the first application, the second device identifier being generated based on a second group of content items to which access by the second application is confined by a second set of permissions, the second identifier being generated by the user device via execution of a second module distinct from the first module and associated with the second application and confined by the second set of permissions, the second group of content items and the first group of content items being distinct but overlapping proper subsets of a third group of content items accessible by the user device;
determining that the first device identifier and the second device identifier both correspond to the user device, the determining being based on a comparison of the first device identifier and the second device identifier; and
assigning, based on the determining that the second device identifier corresponds to the user device, the user identifier of the user to the second device identifier of the user device.
13. A system comprising:
at least one processor; and
memory comprising instructions that, when executed by the at least one processor, cause the system to perform operations comprising:
receiving, from a user device, a first device identifier of the user device, the first device identifier being associated with a first application installed on the user device, the first device identifier being generated based on a first group of content items to which access by the first application is confined by a first set of permissions, the first identifier being generated by the user device via execution of a first module associated with the first application and confined by the first set of permissions;
assigning, in response to receiving the first device identifier of the user device, a user identifier of a user of the user device to the first device identifier of the user device;
receiving, from the user device, a second device identifier of the user device, the second device identifier being associated with a second application installed on the user device and distinct from the first application, the second device identifier being generated based on a second group of content items to which access by the second application is confined by a second set of permissions, the second identifier being generated by the user device via execution of a second module distinct from the first module and associated with the second application and confined by the second set of permissions, the second group of content items and the first group of content items being distinct but overlapping proper subsets of a third group of content items accessible by the user device;
determining that the first device identifier and the second device identifier both correspond to the user device, the determining being based on a comparison of the first device identifier and the second device identifier; and
associating, based on the determining that the second device identifier corresponds to the user device, the second device identifier with at least one of the first device identifier or the user identifier.