System and method for rendering a set of program instructions as executable or non-executable

• US 20100251352A1
• Filed: 03/24/2009
• Published: 09/30/2010
• Est. Priority Date: 03/24/2009
• Status: Abandoned Application

• Current Assignee: Snap-On Incorporated
• Original Assignee: Snap-On Incorporated
• Inventors: Carroll, Michael Anthony, Grier, Jeffrey B., Harpe, Stephen W., Fairbairn, Dylan Josef, Zarchy, Richard R.
• Application Number:
  US12/410,113
• Publication Number:
  US 20100251352A1
• Time in Patent Office: Days
• US Class Current: 726/9
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 2221/2137 Time limited access, e.g. to a computer or data

Abstract

A method and system for rendering a set of computer-readable program instructions on a user device as executable or non-executable. The user device or an intermediary device may transmit an access-token request including a device identifier to a server device. The server device determines whether the device identifier matches a registered device identifier, and if so, transmits an access-token to the user device, or to the intermediary device, which in turn transmits the access-token to the user device. The access-token includes an expiration indicator. Preferably, the expiration indicator is not expired when received by the user device, but expires some time after being received by the user device. The user device executes a first set of program instruction to determine whether the expiration indicator is expired, and if so, renders a second set of program instructions as non-executable, otherwise the second set of program instructions are rendered as executable.

Claims

1. At a user device comprising a data storage device containing a first set of computer-readable program instructions and a second set of computer-readable program instructions, a method comprising:

the user device receiving a first access-token that includes an expiration indicator;

after receiving the first access-token, the user device executing the first set of program instructions to determine that the expiration indicator is not expired and to responsively render the second set of program instructions as executable; and

thereafter, the user device executing the first set of program instructions to determine that the expiration indicator is expired and to responsively render the second set of program instructions as non-executable.

2. The method of claim 1, wherein prior to the user device receiving the first access-token, the method further comprises:

connecting the user device to an intermediary device, wherein the intermediary device is associated with a first device identifier;

the intermediary device transmitting to a server device the first device identifier and an access-token request;

the intermediary device receiving the first access-token from the server device; and

the intermediary device transmitting the first access-token to the user device.

3. The method of claim 2, wherein prior to the intermediary device receiving the first access-token from the server device, the method further comprises:

the server device receiving the first device identifier and the access-token request;

the server device confirming that the received first device identifier is registered with the server device and thereafter generating the first access-token; and

the server device transmitting the first access-token to the intermediary device.

4. The method of claim 3,

wherein the user device is associated with a second device identifier,

the method further comprising:

prior to the server device generating the first access-token, the intermediary device transmitting the second device identifier to the server device;

the server device storing data that associates the access-token request with the first device identifier and the second device identifier; and

the server device using the stored data to generate a report that indicates how many access-token requests were received by the server device and which devices are associated with each of the received access-token requests.

5. The method of claim 2, wherein the first device identifier is selected from the group consisting of (i) an internet protocol (IP) address, (ii) a media access control (MAC) address, (iii) a personal identification number (PIN), (iv) a user name and password, (v) a uniform resource locator for a given network domain, (vi) a disc drive serial number, and (vii) a license number associated with the intermediary device.

6. The method of claim 1, wherein the expiration indicator comprises data representing (i) an amount of time, (ii) a time of day, (iii) a calendar date, or (iv) the time of day and the calendar date.

7. The method of claim 1,

wherein the first access-token further includes a list of the second set of computer-readable program instructions, and

wherein the user device identifies the second set of computer-readable program instructions from the list.

8. The method of claim 1,

wherein, while the second set of program instructions are rendered as executable, the method further comprises the user device executing at least a portion of the second set of program instructions, and

wherein, while the second set of program instructions are rendered as non-executable, the method further comprises the user device prohibiting execution of the second set of program instructions.

9. A user device comprising:

a communications interface operable to receive an access-token that includes an expiration indicator;

a data storage device that contains a first set of computer-readable program instructions and a second set of computer-readable program instructions; and

a processor that is operable to execute the first set of program instructions and the second set of program instructions,

wherein the first set of program instructions includes program instructions that cause the processor to (i) determine whether the expiration indicator is expired, (ii) render the second set of program instructions as executable if the processor determines that the expiration indicator is not expired, and (iii) render the second set of program instructions as non-executable if the processor determines that the expiration indicator is expired.

10. The user device of claim 9, further comprising:

a user interface,

wherein, if the second set of program instructions are rendered as executable, the user interface is operable to display a message that indicates the second set of program instructions are rendered as executable, and

wherein, if the second set of program instructions are rendered as non-executable, the user interface is operable to display a message that indicates the second set of program instructions are rendered as non-executable.

11. The user device of claim 9,

wherein the data storage device further contains a device identifier that identifies the user device,

wherein the communications interface connects to an intermediary device and is operable to transmit the device identifier to the intermediary device,

wherein the intermediary devices transmits to a server device the device identifier and an access-token request, and the server device thereafter generates the access-token and transmits the access-token to the intermediary device, and

wherein the intermediary device transmits the access-token to the communications interface after receiving the access-token from the server device.

12. The user device of claim 9, wherein the second set of computer-readable program instructions includes program instructions that are executable for servicing a vehicle that transports one or more persons.

13. At a server device comprising a data storage device, a method comprising:

at the data storage device, maintaining at least one registered device identifier;

the server device receiving a first access-token request including a first device identifier that identifies a first remote device;

the server device determining that the first device identifier matches a registered device identifier being maintained at the data storage device;

after the server device determines that the first device identifier matches a registered device identifier being maintained at the data storage device, the server device generating an access-token including an expiration indicator, and thereafter transmitting the generated access-token to a communications network for transmission, in turn, to the first remote device.

14. The method of claim 13, wherein the first remote device is selected from the group consisting of (i) a user device, and (ii) an intermediary device that connects to the user device.

15. The method of claim 13, wherein the user device comprises a handheld diagnostic tool and the intermediary device comprises a personal computer.

16. The method of claim 13, further comprising:

the server device receiving a second access-token request including a second device identifier that identifies a second remote device;

the server device determining that the second device identifier does not match a registered device identifier being maintained at the data storage device; and

after the server device determines that the second device identifier does not match any registered device identifier being maintained at the data storage device, the server device responsively generating a notification message to notify the second remote device that the second access-token request is denied, and thereafter transmitting the notification message to the communications network for transmission, in turn, to the second remote device.

17. The method of claim 16, further comprising:

the server device causing the data storage device to maintain data that is associated with (i) the server device receiving the server device receiving the first access-token request including the first device identifier, and (ii) the server device receiving the second access-token request including the second device identifier; and

the server device generating a report that includes the data that is associated with (i) the server device receiving the server device receiving the first access-token request including the first device identifier, and (ii) the server device receiving the second access-token request including the second device identifier.

18. The method of claim 13, further comprising:

the server device encrypting the generated access-token prior to transmitting the generated access-token to the communications network,

wherein the first remote device decrypts the encrypted generated access-token to recover the generated access-token.

19. The method of claim 13,

wherein the first remote device comprises an intermediary device that connects to the communications network and to a user device,

wherein the user device is associated with a second device identifier,

the method further comprising:

the server device receiving the second device identifier; and

prior to the server device generating the access-token, the server device determining that the second device identifier matches another device identifier that is being maintained at the data storage device as a registered device identifier.

20. The method of claim 13, wherein maintaining at least one registered device identifier includes maintaining a plurality of consecutive internet protocol (IP) addresses.

21. The method of claim 13, further comprising:

the server device generating one or more other access-tokens,

wherein each of the one or more other access-tokens includes a respective expiration indicator, and

wherein the expiration indicator included within the access-token and the respective expiration indicator included in each of the one or more other access-tokens indicates a common amount of time.

22. The method of claim 13, further comprising:

the server device generating one or more other access-tokens,

wherein each of the one or more other access-tokens includes a respective expiration indicator,

wherein the expiration indicator included within the access-token indicates a first amount of time, and

wherein the respective expiration indicator included in at least one of the one or more other access-tokens indicates a second amount of time that is different than the first amount of time.

23. A server device comprising:

a processor;

a data storage device that contains computer-readable program instructions and at least one registered device identifier; and

a communications interface that is operable to receive a first access-token request including a first device identifier,

wherein the first device identifier identifies a first remote device, and

wherein the computer-readable program instructions comprise program instructions that are executable by the processor to (i) determine that the first device identifier matches a registered device identifier contained at the data storage device, and responsively generate a first access-token that includes an expiration indicator, and (ii) cause the communications interface to transmit the first access-token to a communications network for transmission, in turn, to the first remote device.

24. The server device of claim 23,

wherein the communications interface is further operable to receive a second device identifier and a second access-token request,

wherein the second device identifier identifies a second remote device,

wherein the computer-readable program instructions comprise program instructions that are executable by the processor to (i) determine that the second device identifier does not match a registered device identifier contained at the data storage device, and responsively generate a notification message to notify the second remote device that the second access-token request has been denied, and (ii) cause the communications interface to transmit the notification message to the communications network for transmission, in turn, to the second remote device.

25. The server device of claim 23,

wherein the first access-token request comprises a second access-token,

wherein generation of the second access-token occurs prior to generation of the first access-token,

wherein execution of the program instructions to responsively generate the first access-token causes the processor to modify the second access-token, and

wherein the first access-token comprises the modified second access-token.

26. The server device of claim 25,

wherein the second access-token comprises a text file,

wherein the processor modifies the second access-token by modifying the text file, and

wherein the modified second access-token comprises the modified text file.

27. At an intermediary device that interfaces to a user device and to a server device, a method comprising:

the intermediary device obtaining a device identifier that identifies the user device;

the intermediary device transmitting to the server device an access-token request including (i) the device identifier that identifies the user device, and (ii) a device identifier that identifies the intermediary device;

the intermediary device receiving from the server device an access-token including an expiration indicator; and

the intermediary device transmitting the access-token including the expiration indicator to the user device,

wherein the user device uses the expiration indicator to determine whether a set of computer-readable program instructions maintained at the user device should be rendered as executable or as non-executable.

28. The method of claim 27, wherein prior to the intermediary device receiving the access-token from the server device, the method further comprises:

the intermediary device receiving from the user device an access-token that includes an expired expiration indicator; and

the intermediary device transmitting to the sever device the access-token that includes the expired expiration indicator.

29. The method of claim 27, wherein the device identifier that identifies the intermediary device is maintained as a registered device identifier at a data storage device accessible to the server device.

30. An intermediary device comprising:

a communications interface that interfaces to a user device and to a server device;

a processor; and

a data storage device that contains a first device identifier and computer-readable program instructions that are executable by the processor,

wherein the first device identifier identifies the intermediary device,

wherein the computer-readable program instructions include instructions that (i) cause the processor to determine a second device identifier that identifies the user device, (ii) cause the communications interface to transmit to the server device the first device identifier, the second device identifier, and an access-token request, and (iii) cause the communications interface to transmit to the user device an access-token that is received by the communications interface after the communications interface transmits to the server device the access-token request,

wherein the received access-token includes an expiration indicator, and

wherein the user device uses the expiration indicator to determine whether a set of computer-readable program instructions maintained at the user device should be rendered as executable or as non-executable.