Recording and Serializing Events

• US 20110246651A1
• Filed: 06/20/2011
• Published: 10/06/2011
• Est. Priority Date: 11/27/2007
• Status: Abandoned Application

• Current Assignee: Gueorgui N. Djabarov, Omer Shakil, Yevgeniy Gutnik
• Original Assignee: Gueorgui N. Djabarov, Omer Shakil, Yevgeniy Gutnik
• Inventors: Shakil, Omer, Djabarov, Gueorgui N., Gutnik, Yevgeniy
• Application Number:
  US13/164,737
• Publication Number:
  US 20110246651A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06F 11/3075 the data filtering being achieved in order to maintain consistency among the monitored data, e.g. ensuring that the monitored data belong to the same timeframe, to the same system or component
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 2201/835 Timestamp
• CPC Class Codes: G06F 2201/86 Event-based monitoring

Abstract

Event information with respect to events that occur at a client is recorded. A current client real time clock (RTC) timestamp at the occurrence of each event is also recorded. Each event is assigned a unique sequence identification. Event data including the event information and the associated RTC timestamp and sequence identification information are transmitted to a server. The server reconstructs at least one of: a chronological order of the events on the client and the time when each event occurred at the client.

Claims

1. A computer-implemented method, comprising:

at a client system or device having memory and one or more processors;

recording event information with respect to events that occur at the client;

recording a current client real time clock (RTC) timestamp at the occurrence of each event;

assigning each event a unique sequence identification; and

transmitting event data, including the event information and associated RTC timestamp and sequence identification information to a server system, when a network connection is established between the client and the server system and any of a plurality of trigger conditions is met, the plurality of trigger conditions including;

collection of a predetermined amount of event data at the client and occurrence of a particular event or events at the client.

2. The method of claim 1, wherein the event data includes event information with respect to an event at the client comprising a user-initiated change to the client RTC time.

3. The method of claim 1, further comprising:

assigning each successive event a monotonically increasing integer value as its unique sequence identification.

4. The method of claim 1, further comprising:

assigning each successive event two integer values as its unique sequence identification.

5. The method of claim 4, wherein the two integer values comprise a session value, which remains constant in value between executions of a client application and which changes value when a new execution of the client application begins, and a sequence value, which changes monotonically in value while the session value remains constant and successive events occur at the client.

6. The method of claim 1, further comprising:

removing personal identifiable information (PII) from the event information to produce event data before transmitting event data to the server system.

7. The method of claim 6, wherein the PII removed from the event information includes user information selected from the group consisting of a user name, a user account identifier, and user account identification information.

8. A client system, comprising:

one or more processors;

memory storing one or more programs having instructions to be executed by the one or more processors, the one or more programs including instructions for;

recording event information with respect to events that occur at the client;

recording a current client real time clock (RTC) timestamp at the occurrence of each event;

assigning each event a unique sequence identification; and

transmitting event data, including the event information and associated RTC timestamp and sequence identification information to a server system, when a network connection is established between the client and the server system and any of a plurality of trigger conditions is met, the plurality of trigger conditions including;

collection of a predetermined amount of event data at the client and occurrence of a particular event or events at the client.

9. The client system of claim 8, wherein the event data includes event information with respect to an event at the client comprising a user-initiated change to the client RTC time.

10. The client system of claim 8, the one or more programs further comprising instructions for:

assigning each successive event a monotonically increasing integer value as its unique sequence identification.

11. The client system of claim 8, the one or more programs further comprising instructions for:

assigning each successive event two integer values as its unique sequence identification.

12. The client system of claim 11, wherein the two integer values comprise a session value, which remains constant in value between executions of a client application and which changes value when a new execution of the client application begins, and a sequence value, which changes monotonically in value while the session value remains constant and successive events occur at the client.

13. The client system of claim 8, the one or more programs further comprising instructions for:

removing personal identifiable information (PII) from the event information to produce event data before transmitting event data to the server system.

14. The client system of claim 13, wherein the PII removed from the event information includes user information selected from the group consisting of a user name, a user account identifier, and user account identification information.

15. A non-transitory computer readable storage medium storing on or more programs, the one or more programs comprising instructions, which when executed by a client system, cause the client system to:

record event information with respect to events that occur at the client;

record a current client real time clock (RTC) timestamp at the occurrence of each event;

assign each event a unique sequence identification; and

transmit event data, including the event information and associated RTC timestamp and sequence identification information to a server system, when a network connection is established between the client and the server system and any of a plurality of trigger conditions is met, the plurality of trigger conditions including;

collection of a predetermined amount of event data at the client and occurrence of a particular event or events at the client.

16. The computer readable storage medium of claim 15, wherein the event data includes event information with respect to an event at the client comprising a user-initiated change to the client RTC time.

17. The computer readable storage medium of claim 15, the one or more programs further comprising instructions, which when executed by the client system, cause the client system to:

assigning each successive event a monotonically increasing integer value as its unique sequence identification.

18. The computer readable storage medium of claim 15, the one or more programs further comprising instructions which when executed by the client system, cause the client system to:

assign each successive event two integer values as its unique sequence identification.

19. The computer readable storage medium of claim 18, wherein the two integer values comprise a session value, which remains constant in value between executions of a client application and which changes value when a new execution of the client application begins, and a sequence value, which changes monotonically in value while the session value remains constant and successive events occur at the client.

20. The computer readable storage medium of claim 15, the one or more programs further comprising instructions which, when executed by the client system, cause the client system to:

removing personal identifiable information (PII) from the event information to produce event data before transmitting event data to the server system.

21. The computer readable storage medium of claim 20, wherein the PII removed from the event information includes user information selected from the group consisting of a user name, a user account identifier, and user account identification information.