Single use identifier values for network accessible devices

• US 9,979,731 B1
• Filed: 01/20/2017
• Issued: 05/22/2018
• Est. Priority Date: 08/14/2012
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Pattan, Neha, Vemula, Venu, Ying, Mike
• Primary Examiner(s): Christensen, Scott B
• Assistant Examiner(s): Do, Lam
• Application Number:
  US15/411,087
• Time in Patent Office: 487 Days
• 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 and in response to a request for a data exchange operation received from a client device, a unique identifier for the client device that is stored by the server device and that 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 identifier and data associated with the requested data exchange operation, for storing in a memory of the client device;

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

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

determining, by the server device, that the received unique identifier corresponds to a stored unique identifier for the client device that is stored by the server device and that the received unique identifier is invalid, including determining that a received counter value in the received unique identifier does not match a stored counter value in the stored unique identifier; and

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

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

2. The computer-implemented method of claim 1, wherein the unique identifier and the data associated with the requested data exchange operation are respectively transferred across a network from the server device to the client device.

3. The computer-implemented method of claim 1, wherein the requested data exchange operation is a request to transfer an application from the server device to the client device, and the data associated with the requested data exchange operation includes the application in the form of programming code adapted for execution by a processor of the client device.

4. The computer-implemented method of claim 1, wherein the request for a subsequent data exchange operation is a request to transfer content from the server device to the client device.

5. The computer-implemented method of claim 4, further comprising transferring one or more content items from the server device to the client device.

6. The computer-implemented method of claim 1, in which the unique identifier includes a global component adapted for storage in the memory of the client device for access by multiple applications and a local component adapted for storage in the memory of the client device for access by less than all of the multiple applications.

7. The computer-implemented method of claim 1, wherein generating the updated unique identifier includes generating an updated global component and an updated local component of the updated unique identifier, 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 identifier.

8. The computer-implemented method of claim 7, wherein generating the updated unique identifier includes generating an updated fixed identifier that is included in both the updated global component and the updated local component of the updated unique identifier.

9. The computer-implemented method of claim 7, wherein generating the updated unique identifier includes generating a first random number that is included in the updated global component and a second, different, random number that is included in the updated local component of the updated unique identifier.

10. The computer-implemented method of claim 7, wherein generating the updated unique identifier includes including the reinitialized counter in the updated global component of the updated unique identifier and excluding the reinitialized counter from the updated local component of the updated unique identifier.

11. A computer system comprising:

one or more processors; and

one or more memory elements in communication with the one or more processors and which store programming for the one or more processors and that upon such execution cause the one or more processors to perform operations comprising;

generating, in response to a request for a data exchange operation received from a client device, a unique identifier for the client device that is stored by a server device and that 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 identifier and data associated with the requested data exchange operation, for storing in a memory of the client device;

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

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

determining that the received unique identifier corresponds to a stored unique identifier for the client device that is stored by the server device and that the received unique identifier is invalid, including determining that a received counter value in the received unique identifier does not match a stored counter value in the stored unique identifier; and

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

transferring the updated unique identifier for replacing the unique identifier in the memory of the client device, such that the updated unique identifier is usable for identifying the client device for only a subsequent single request for a subsequent data exchange operation.

12. The computer system of claim 11, wherein generating the updated unique identifier includes generating an updated global component and an updated local component of the updated unique identifier, 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 identifier.

13. The computer system of claim 12, wherein generating the updated unique identifier includes generating an updated fixed identifier that is included in both the updated global component and the updated local component of the updated unique identifier.

14. The computer system of claim 12, wherein generating the updated unique identifier includes generating a first random number that is included in the updated global component and a second, different, random number that is included in the updated local component of the updated unique identifier.

15. The computer system of claim 12, wherein generating the updated unique identifier includes including the reinitialized counter in the updated global component of the updated unique identifier and excluding the reinitialized counter from the updated local component of the updated unique identifier.

16. One or more non-transitory computer-readable media encoded with instructions that when executed by one or more computers cause the one or more computers to perform operations comprising:

generating, in response to a request for a data exchange operation received from a client device, a unique identifier for the client device that is stored by a server device and that 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 identifier and data associated with the requested data exchange operation, for storing in a memory of the client device;

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

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

determining that the received unique identifier corresponds to a stored unique identifier for the client device that is stored by the server device and that the received unique identifier is invalid, including determining that a received counter value in the received unique identifier does not match a stored counter value in the stored unique identifier; and

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

transferring the updated unique identifier for replacing the unique identifier in the memory of the client device, such that the updated unique identifier is usable for identifying the client device for only a subsequent single request for a subsequent data exchange operation.

17. The non-transitory computer-readable media of claim 16, wherein generating the updated unique identifier includes generating an updated global component and an updated local component of the updated unique identifier, 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 identifier.

18. The non-transitory computer-readable media of claim 17, wherein generating the updated unique identifier includes generating an updated fixed identifier that is included in both the updated global component and the updated local component of the updated unique identifier.

19. The non-transitory computer-readable media of claim 17, wherein generating the updated unique identifier includes generating a first random number that is included in the updated global component and a second, different, random number that is included in the updated local component of the updated unique identifier.

20. The non-transitory computer-readable media of claim 17, wherein generating the updated unique identifier includes including the reinitialized counter in the updated global component of the updated unique identifier and excluding the reinitialized counter from the updated local component of the updated unique identifier.