Single use identifier values for network accessible devices

• US 9,571,275 B1
• Filed: 08/14/2012
• Issued: 02/14/2017
• Est. Priority Date: 08/14/2012
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Ying, Mike, Pattan, Neha, Vemula, Venu
• Primary Examiner(s): Christensen, Scott B
• Assistant Examiner(s): Do, Lam
• Application Number:
  US13/585,053
• Time in Patent Office: 1,645 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04L 2209/42 Anonymization, e.g. involving pseudonyms
• CPC Class Codes: H04L 47/748 Negotiation of resources, e.g. modification of a request
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70
• CPC Class Codes: H04L 9/0866 involving user or device identifiers, e.g. serial number, physical or biometrical information, DNA, hand-signature or measurable physical characteristics
• CPC Class Codes: H04W 4/60 Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
• CPC Class Codes: H04W 8/26 Network addressing or numbering for mobility support

Abstract

Apparatus and method for providing unique device identification values for a network accessible device. In accordance with some embodiments, a unique device identifier value is generated in response to a data exchange operation with a network accessible device. The identifier value is subsequently transmitted by the device as a unique device identifier value in conjunction with the transmitting of a request for a subsequent data exchange operation with the device.

Claims

1. A computer-implemented method comprising:

generating, by a server device, a unique device identifier value for a client device responsive to an initial data exchange operation with the client device, wherein the unique device identifier value for the client device is stored by the server device, is used by the server device to uniquely identify the client device, is configured to mask identifiable information associated with the client device, and comprises an initialized counter value that tracks a total number of data exchange operations between the server device and the client device;

transferring, by the server device, the unique device identifier value for storing in a memory of the client device; and

performing subsequent data exchange operations, wherein the server device subsequently interacts with the client device to receive requests for one or more content items and to transfer one or more content items to the client device, each subsequent data exchange operation between the server device and the client device comprising;

receiving, by the server device and from the client device, the unique device identifier value along with a request for one or more content items;

in response to receiving the unique device identifier value along with the request for one or more content items;

determining, by the server device, that the received unique device identifier value corresponds to a stored unique device identifier value that is stored by the server device, that the received unique device identifier value is valid, including determining that a received counter value in the received unique device identifier value matches a stored counter value in the stored unique device identifier value, and that the received unique device identifier value is currently associated with a single client device; and

generating and storing, by the server device, an updated unique device identifier value for the client device, wherein generating the updated unique device identifier value comprises incrementing the stored counter value and including the incremented counter value in the updated unique device identifier value; and

transferring, by the server device, the updated unique device identifier value for replacing the unique device identifier value in the memory of the client device, along with one or more content items, such that the updated unique device identifier value is usable for identifying the client device for only a subsequent single request for one or more content items.

2. The method of claim 1, in which the initial data exchange operation comprises transferring an application to the memory of the client device.

3. The method of claim 1, in which for a given subsequent data exchange operation, at least one of the one or more content items is transferred for display in a content slot on a display of the client device during execution of an application by the client device.

4. The method of claim 1, in which for a given data exchange operation between the server device and the client device, the unique device identifier value comprises a timestamp value associated with the given data exchange operation.

5. The method of claim 1, in which the unique device identifier value comprises a fixed payload value assigned by the server device.

6. The method of claim 1, in which the unique device identifier value comprises a random number value assigned by the server device.

7. The method of claim 1, in which the unique device identifier value comprises a global component that is stored in encrypted form in a global memory portion of the client device and is accessible by a selected application and one or more other applications stored on the client device, and a local component that is stored in encrypted form in a local memory portion of the client device and is only accessible by said selected application, wherein both the global component and the local component are transferred in encrypted form along with the one or more content items during the subsequent data exchange operation.

8. The method of claim 7, wherein determining that the received unique device identifier value is valid includes decrypting a received global component and a received local component of the received unique device identifier, and determining that the decrypted global component and the decrypted local component match respective stored global and stored local components in the stored unique device identifier.

9. The method of claim 8, wherein generating the updated unique device identifier value comprises generating an updated global component and an updated local component, encrypting the updated global component and the updated local component, and including the encrypted global component and the encrypted local component in different sections of the updated unique device identifier for parsing by the client device.

10. The method of claim 1, further comprising validating, by the server device, the received unique device identifier value against a database stored in a memory.

11. A computer-implemented method comprising:

receiving, by a server device, a request for a first data exchange operation with a client device;

generating, by the server device, a unique device identifier value for the client device responsive to the received request, wherein the unique device identifier value for the client device is stored by the server device, is used by the server device to uniquely identify the client device, is configured to mask identifiable information associated with the client device, and comprises an initialized counter value that tracks a total number of data exchange operations between the server device and the client device;

transferring, by the server device, the unique device identifier value and a first data set associated with the requested first data exchange operation to a memory of the client device;

performing subsequent data exchange operations, wherein the server device subsequently interacts with the client device to receive requests for subsequent data sets and to transfer the subsequent data sets to the client device, each subsequent data exchange operation between the server device and the client device comprising;

receiving, by the server device and from the client device, the unique device identifier value along a request for the subsequent data exchange operation;

in response to receiving the unique device identifier value along with the request for the subsequent data exchange operation;

determining, by the server device, that the received unique device identifier value corresponds to a stored unique device identifier value that is stored by the server device, that the received unique device identifier value is valid, including determining that a received counter value in the received unique device identifier value matches a stored counter value in the stored unique device identifier value, and that the received unique device identifier value is currently associated with a single client device; and

generating and storing, by the server device, an updated unique device identifier value for the client device, wherein generating the updated unique device identifier value comprises incrementing the stored counter value and including the incremented counter value in the updated unique device identifier value; and

transferring, by the server device, the updated unique device identifier value for replacing the unique device identifier value in the memory of the client device, along with a subsequent data set associated with the requested subsequent data exchange operation, such that the updated unique device identifier value is usable for identifying the client device for only a subsequent single request for a subsequent data exchange operation.

12. The method of claim 11, in which the unique device identifier value and the subsequent data set are respectively transferred across the network from the server device to the client device.

13. The method of claim 11, in which the requested first data exchange operation is a request to transfer an application from the server device to the client device, and the first data set comprises said application in the form of programming code adapted for execution by a processor of the client device.

14. The method of claim 11, in which the unique device identifier value comprises a global component adapted for storage in the memory of the client device for access by multiple applications in said memory and a local component adapted for storage in the memory of the client device for access by less than all of the multiple application in said memory.

15. The method of claim 11, in which the unique device identifier value comprises a count value portion associated with a total accumulated number of data exchange operations carried out with the client device and the server device.

16. The method of claim 11, in which generating a unique device identifier value for the client device by the server device comprises generating a multi-bit value and encrypting the multi-bit value to provide the generated unique device identifier value.

17. The method of claim 11, in which the unique device identifier value comprises at least a selected one of a fixed payload, a random number, an accumulated count of data exchange operations carried out with the client device and the server device, or a timestamp value associated with a selected data exchange operation.

18. An apparatus comprising:

a processor; and

a memory which stores programming for the processor adapted to perform steps of;

receiving a request for a first data exchange operation with a client device;

generating a unique device identifier value for the client device responsive to the received request, wherein the unique device identifier value for the client device is stored, is used to uniquely identify the client device on a network, is configured to mask identifiable information associated with the client device, and comprises an initialized counter value that tracks a total number of data exchange operations between the server device and the client device;

transferring the unique device identifier value and a first data set associated with the requested first data exchange operation over the network to a memory of the client device;

performing subsequent data exchange operations, wherein the server device subsequently interacts with the client device to receive requests for subsequent data sets and to transfer the subsequent data sets to the client device, each subsequent data exchange operation between the server device and the client device comprising;

receiving, over the network and from the client device, the unique device identifier value along with a request for the subsequent data exchange operation;

in response to receiving the unique device identifier value along with the request for the subsequent data exchange operation;

determining that the received unique device identifier value corresponds to a stored unique device identifier value, that the received unique device identifier value is valid, including determining that a received counter value in the received unique device identifier value matches a stored counter value in the stored unique device identifier value, and that the received unique device identifier value is currently associated with a single client device; and

generating and storing an updated unique device identifier value for the client device, wherein generating the updated unique device identifier value comprises incrementing the stored counter value and including the incremented counter value in the updated unique device identifier value; and

transferring, over the network, the updated unique device identifier value for replacing the unique device identifier value in the memory of the client device, along with a subsequent data set associated with the requested subsequent data exchange operation, such that the updated unique device identifier value is usable for identifying the client device for only a subsequent single request for a subsequent data exchange operation.

19. The apparatus of claim 18, in which the programming is further adapted to retrieve a count value from the received unique device identifier value and compare the retrieved count value to a previously stored count value to determine whether the unique device identifier value has been maliciously copied.

20. The apparatus of claim 18, in which the unique device identifier value comprises a global component adapted for storage in the memory of the client device for access by multiple applications in said memory and a local component adapted for storage in the memory of the client device for access by a single application in said memory.

21. The apparatus of claim 18, in which the stored counter value corresponds to a total accumulated number of data exchange operations carried out with the client device, wherein the incremented counter value forms a portion of the updated unique device identifier value.

22. The apparatus of claim 18, in which the programming is further adapted to encrypt the unique device identifier value prior to being transferred to the client device.

23. The apparatus of claim 18, in which the unique device identifier value comprises at least a selected one of a fixed payload, a random number, an accumulated count of data exchange operations carried out with the client device, or a timestamp value associated with a selected data exchange operation.