Communication and synchronization in a networked timekeeping environment

• US 8,468,211 B2
• Filed: 10/30/2008
• Issued: 06/18/2013
• Est. Priority Date: 10/30/2007
• Status: Active Grant

• Current Assignee: Schlage Lock Company LLC (Allegion PLC)
• Original Assignee: Schlage Lock Company LLC (Allegion PLC)
• Inventors: Miller, Barrick H.
• Primary Examiner(s): Avellino, Joseph
• Assistant Examiner(s): Park, Jeong S
• Application Number:
  US12/290,350
• Publication Number:
  US 20090157537A1
• Time in Patent Office: 1,692 Days
• Field of Search: 705/32, 709/208, 709/212, 707/613, 707/614
• US Class Current: 709/208
• CPC Class Codes: G06Q 10/109 Time management, e.g. calendars, reminders, meetings or time accounting

Abstract

An optimized time and attendance system and methods. In some embodiments, a networked time and attendance system includes a network services server with a global database and a client device terminal with a local database. The device terminal is configured to create new time keeping records on the local database using information stored in the local database. The device terminal is further configured to initiate a connection to the host server and synchronize the local database with the global database. In some embodiments, the client terminal is configured to continue creating additional new time keeping records in the local database even when a connection to the host server is unavailable. In some embodiments, the client terminal includes a user interface, a local database, a first processor configured to control all system functions except for biometric data processing, and a second processor configured to capture and process biometric data.

Claims

1. A method of synchronizing a local database with a global database in a networked time-keeping environment, the networked time-keeping environment including a server with a computer readable memory that stores the global database and a plurality of client time-keeping terminals each including a computer readable memory storing a local database, wherein the global database and each local database includes a plurality of previously stored data elements and a timestamp corresponding to each previously stored data element, the method comprising:

creating a new data element at a client terminal in response to a time-keeping event at the client terminal, wherein the new data element includes an edited attribute of a previously stored data element and a unique object identifier associated with the previously stored data element;

adding the new data element to the local database of the client terminal;

initiating a connection to the server from the client terminal;

sending the new data element from the client terminal to the server;

sending a previous timestamp associated with the previously stored data element from the client terminal to the server, wherein the previous timestamp was previously received from the server and indicates when the previously stored data element was added to the global database of the server;

if the unique object identifier assigned to the new data element is already stored in the global database,

comparing the previous timestamp to a timestamp stored in the global database for the previously stored data element, and if the timestamps match,

changing the previously stored data element in the global database to include the edited attribute,

generating a new timestamp,

storing the new timestamp in the global database, and

sending a copy of the new timestamp to the client terminal;

receiving a timestamp for the new data element from the server indicating when the new data element was added to a global database of the server; and

storing the timestamp for the new data element to the local database of the client terminal.

2. The method of claim 1, further comprising creating a second new data element at the client terminal in response to a second time-keeping event at the client terminal, wherein the second new data element does not include an edited attribute of any previously stored data element;

selecting a unique object identifier for the new data element from a range of available unique object identifiers assigned to the client terminal by the server; and

sending the second new data element from the client terminal to the server.

3. The method of claim 2, further comprising:

receiving the second new data element sent by the client terminal to the server;

determining if the unique object identifier assigned to the second new data element is already stored in the global database; and

if the unique object identifier assigned to the second new data element is not already stored in the global database,

generating a timestamp,

storing the timestamp and the second new data element in the global database, and

sending a copy of the timestamp for the second net data element from the server to the client terminal.

4. The method of claim 1, further comprising sending an exception message from the server to the client terminal if the timestamps do not match, wherein the exception message indicates that the edited attribute was included in a version of the previously stored data element that was not current.

5. The method of claim 1, further comprising:

sending a request for synchronization from the client terminal to the server;

determining the last time that the client terminal sent a request for synchronization; and

receiving a set of data elements from the server, wherein the set of data elements includes all of the data elements stored in the global database that have a timestamp dated later than the last time that the client terminal sent a request for synchronization.

6. The method of claim 5, further comprising

retrieving an element from the set of data elements from the server, and

adding the element to the local database if the unique object identifier associated with the element is not associated with any other element in the local database.

7. The method of claim 5, further comprising

retrieving an element from the set of data elements from the server;

identifying an element stored in the local database that is associated with the same unique object identifier as the element from the set of data elements from the server; and

replacing the element stored in the local database with the element from the set of data elements from the server if the timestamps associated with the two data elements do not match.

8. The method of claim 1, further comprising:

sending a request for synchronization from the client terminal to the server; and

receiving a set of data elements from the server, wherein the set of data elements includes all of the data elements stored in the global database.

9. The method of claim 8, further comprising:

retrieving an element from the set of data elements from the server, and

adding the element to the local database if the unique object identifier associated with the element is not associated with any other element in the local database.

10. The method of claim 8, further comprising:

retrieving an element from the local database;

identifying an element from the set of data elements from the server that is associated with the same unique object identifier as the element from the local database; and

replacing the element stored in the local database with the element from the set of data elements from the server if the timestamps associated with the two data elements do not match.

11. The method of claim 8, further comprising:

retrieving an element from the local database; and

deleting the element from the local database if the set of data elements from the server does not include an element associated with the same unique object identifier as the element from the local database.

12. The method of claim 1, further comprising:

performing a partial synchronization between the client terminal and the server, the partial synchronization including

receiving a set of data elements from the server, wherein the set of data elements includes all of the data elements stored in the global database that have a timestamp dated later than the last time that the client terminal synchronized with the server,

retrieving an first element from the set of data elements from the server,

adding the first element to the local database if the unique object identifier associated with the first element is not associated with any other element in the local database, and

replacing the first element stored in the local database with the first element from the set of data elements from the server if the timestamps associated with the two data elements do not match; and

performing a full synchronization between the client terminal and the server, the full synchronization including

receiving a full set of data elements from the server including all of the data elements stored in the global database,

retrieving a second element from the full set of data elements from the server,

adding the second element to the local database if the unique object identifier associated with the second element is not associated with any other element in the local database, and

replacing the second element stored in the local database with the second element from the set of data elements from the server if the timestamps associated with the two data elements do not match.

13. The method of claim 12, wherein the partial synchronization is performed after adding the new data element to the local database of the client terminal, and further comprising:

receiving a synchronization schedule identifying at least one time at which to perform a full synchronization and wherein the full synchronization is performed at the at least one time.

14. The method of claim 1, wherein the edited attribute of the previously stored data element includes a new clock-out event including a clock-out time, and wherein the previously stored data element includes a previously stored clock-in event including a clock-in time.

15. A method of synchronizing a global database with a plurality of local databases in a networked time-keeping environment, the networked time-keeping environment including a. server with a computer readable memory that stores the global database and a. plurality of client terminals each including a computer readable memory storing a local database, wherein the global database and each local database includes a plurality of previously stored data elements and a timestamp corresponding to each previously stored data element, the method comprising:

receiving a first data element from a first client terminal, the first data element including a timestamp and a first unique object identifier;

determining whether a data element in the global database includes the first unique object identifier;

when a data element in the global database includes the first unique object identifier, comparing the timestamp of the first data element to a timestamp of the data element in the global database;

when the data element in the global database includes the first unique object identifier and the timestamp of the data element in the global database matches the timestamp of the first data element, replacing the data element in the global database with the first data element;

when the data element in the global database includes the first unique object identifier and the time stamps of the data element in the global database matches the timestamp of the first data element, assigning a new timestamp to the first data element stored in the global database, the new timestamp indicating the time that the first data element was added to the global database; and

when the data element in the global database includes the first unique object identifier and the timestamp of the data element in the global database does not match the timestamp of the first data element, sending an exception message from the server to the client terminal indicating that the first data element is an edited version of an obsolete data element.

16. The method of claim 15, further comprising, when no data element in the global database includes the first unique object identifier, adding the first data element to the global database as anew data element.

17. The method of claim 15, further comprising:

determining whether a value is assigned to the timestamp of the first data element;

when no value is assigned to the timestamp of the first data element, adding the first data element to the global database as a new data element; and

when no value is assigned to the timestamp of the first data element, generating a timestamp for the first data element indicating when the new data element was added to the global database.

18. A method of synchronizing a global database with a local database in a networked time-keeping environment, the networked time-keeping environment including a server storing the global database, a first client terminal storing a first local database, and a second client terminal storing a second local database, wherein the global database, the first local database, and the second local database each include a plurality of previously stored data elements, and wherein a timestamp is assigned to each of the previously stored data element, the method comprising:

receiving, by the first client terminal, a first change to a data element at a first time;

storing the first change to the data element in the first database;

receiving, by the second client terminal, a second change to the same data element at a second time, wherein the second time is after the first time;

storing the second change to the data element in the second database;

performing a synchronization between the second client terminal and the server at a third time, wherein the third time is after the first time and after the second time and wherein the synchronization between the second client terminal and the server includes

transmitting the data element including the second change stored in the second local database from the second client terminal to the server,

comparing the timestamp of the data element including the second change from the second client terminal to the data element stored in the global database on the server,

determining that the timestamps match,

replacing the data element stored in the global database with the data element including the second change, and

assigning a new timestamp to the data element including the second change stored in the global database; and

performing a synchronization between the first client terminal and the server at a fourth time, wherein the fourth time is after the first time, after the second time, and after the third time, and wherein the synchronization between the first client terminal and the server includes

transmitting the data element including the first change stored in the first local database from the first client terminal to the server,

comparing the timestamp of the data element including the first change from the first client terminal to the data element including the second change stored in the global database,

determining that the timestamps do not match, and

sending an exception message from the server to the first client, wherein the data element including the first change is not added to the global database when the timestamps do not match.

19. The method of claim 18, wherein the first change to the data element includes adding a clock-out event including a clock-out time, wherein the clock-out time is the first time, wherein the second change is a duplicate clock-out event including a new clock-out time, and wherein the new clock-out time is the second time.