Restricting devices utilizing a device-to-server heartbeat

• US 20070192652A1
• Filed: 02/14/2006
• Published: 08/16/2007
• Est. Priority Date: 02/14/2006
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Pastrana, Rodrigo, Kao, Sandy
• Application Number:
  US11/354,477
• Publication Number:
  US 20070192652A1
• Time in Patent Office: Days
• US Class Current: 714/4.2
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0757 by exceeding a time limit, i.e. time-out, e.g. watchdogs
• CPC Class Codes: G06F 21/88 Detecting or preventing theft or loss
• CPC Class Codes: H04L 63/0492 by using a location-limited connection, e.g. near-field communication or limited proximity of entities
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226

Abstract

A method of automatically locking a client can include a step of a client automatically establishing a heartbeat interval. A determination can be automatically made regarding whether a proper server response is received within the heartbeat interval. When no proper response is received, the client can be automatically placed in a locked state. All client functions accessible by a user other than those functions relating to unlocking the client can be disabled while the client is in the locked state. A remotely located server can unlock the client by conveying an unlock message to the client.

Claims

1. A method of automatically locking a client comprising:

a client automatically establishing a heartbeat interval;

automatically determining whether a proper server response is received within the heartbeat interval; and

when no proper response is received, automatically placing the client in a locked state, wherein all client functions accessible by a user other than those functions relating to unlocking the client are disabled while the client is in the locked state, and wherein unlocking the client requires a remotely located server to provide an unlock message to the client.

2. The method of claim 1, wherein the placing step further comprises:

automatically securing data contained within the client so that the secured data is not accessible while the client is in a locked state.

3. The method of claim 1, wherein the client and the remotely located server both include a wireless communication ability, wherein messages including the server response and the unlock message are wirelessly exchanged between the client and the remotely located server.

4. The method of claim 1, wherein a communication range is established within which the client is able to become communicatively linked to a server configured to provide heartbeat responses to at least one client to prevent the at least one client from entering a locked state, wherein the client is unable to receive the proper server response when located outside the communication range.

5. The method of claim 4, wherein the communication range is based upon a range of a wireless communication network to which the server is communicatively linked.

6. The method of claim 1, wherein said steps of claim 1 are performed by at least one machine in accordance with at least one computer program having a plurality of code sections that are executable by the at least one machine.

7. The method of claim 1, wherein the steps of claim 1 are performed by at least one of a service agent and a computing device manipulated by the service agent, the steps being performed in response to a service request.

8. A method of restricting access to a computing device comprising:

automatically generating a heartbeat event within a client;

determining whether a server response is received by the client for the heartbeat event; and

automatically altering a lock state of the client based upon the determining step, wherein a server response to the heartbeat event is required to prevent the client from automatically adjusting from an unlocked state to a locked state.

9. The method of claim 8, further comprising:

establishing a custom restriction profile upon the client, wherein the determining step is based upon the restriction profile.

10. The method of claim 9, further comprising:

authenticating a user for the client; and

ascertaining that the user possesses privileges to modify the custom restriction profile, wherein the client includes an interface through which the authenticated user is able to configure the custom restriction profile.

11. The method of claim 8, wherein the altering step alters the lock state of the client to a locked state, and wherein the client is configured to remain in the locked state until a communication pathway is established between the client and the server and until the server provides an unlock response to the client via the communication pathway.

12. The method of claim 11, wherein the client iteratively polls the server to receive the unlock response.

13. The method of claim 11, wherein all client functions accessible by a user other than those functions relating to unlocking the client are disabled while the client is in the locked state.

14. The method of claim 8, further comprising:

responsive to the heartbeat event, the client automatically attempting to wirelessly transmit a heartbeat message to which the server response is expected, wherein the server response prevents the client from automatically adjusting from the unlocked state to the locked state.

15. The method of claim 14, further comprising:

identifying an expected response time and a retransmission time, wherein the retransmission time is less than the expected response time;

when the client fails to receive the server response to the heartbeat message within the expected response time, the client retransmitting the heartbeat message; and

when the client fails to receive the server response to the retransmitted heartbeat message within the retransmission time, the client executing at least one of the altering step and a step of again retransmitting the heartbeat message.

16. The method of claim 8, wherein said steps of claim 8 are performed by at least one machine in accordance with at least one computer program having a plurality of code sections that are executable by the at least one machine.

17. The method of claim 8, wherein the steps of claim 8 are performed by at least one of a service agent and a computing device manipulated by the service agent, the steps being performed in response to a service request.

18. A storage space upon a machine-readable medium local to a client, the machine-readable medium comprising a plurality of code instructions for causing a machine to perform the steps of:

identifying a heartbeat interval;

starting a heartbeat timer within the client;

when a heartbeat response is received from a remotely located server, resetting the heartbeat timer; and

when the heartbeat timer exceeds the heartbeat interval, automatically adjusting the client from an unlocked state to a locked state, wherein all client functions accessible by a user other than those functions relating to unlocking the client are disabled while the client is in the locked state.

19. The storage space of claim 18, wherein the client is configured so that a user of the client is unable to disable the heartbeat timer and is unable to prevent the client from entering the locked state in absence of a heartbeat response being received from the remotely located server.

20. The storage space of claim 18, wherein the identifying, starting, and adjusting steps are performed as a background process executing upon the client, wherein users of the device are not authorized to remove the background process and are not authorized to disable the background process.