# US 2012/0254418 A1 · Relative timestamp when real time clock is unavailable

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254418 A1
- Document ID: US20120254418A1
- Status: Published application
- Kind: A1
- Application number: 13/470,699
- Filed: 2012-05-14
- Published: 2012-10-04
- Earliest claimed: 2011-03-31
- Assignees: Microsoft Corporation
- Inventors: David Callaghan; Sergey Karamov
- Web page: https://patentgrep.com/patent/US20120254418A1

## CPC

- H04L 67/142: Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
- G06F 1/14: Time supervision arrangements, e.g. real time clock
- H04L 41/0686: Additional information in the notification, e.g. enhancement of specific meta-data
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

An operating system or other software resident on an electronic processing device employs aggregated timestamps. In this way timestamps can be generated and compared to one another without the need for a real-time clock with a power backup. Aggregated time includes the last known time that the device synchronized its clock with a reference time available over a network. Aggregated time also includes a relative time value which in part accumulates using a session clock whenever the device is powered-up. When network time becomes available the operating system or other software will use this information to fix up the already generated aggregated timestamps. A comparison of timestamps will most of the time be resolved for stamps generated on the same device and will generally be resolved by comparing time frames when the timestamps being compared are generated by different devices.

## Claims

### Claim 1

A method for generating a timestamp for an event that occurs on an electronic processing device, comprising:
generating event service data upon occurrence of the event, the event service data including a service timestamp denoting a time that has elapsed since initiation of a current session in which the electronic processing device is continuously powered up, said event service data further including a session identifier uniquely identifying the current session;
generating a network timestamp specifying a time when network time become available and a current session timestamp representing a time that has elapsed since initiation of the current session; and
after network time has become available, generating an event timestamp representing a time at which the event occurred, said event timestamp being equal to a difference between the network timestamp specifying the time when network time became available and a time that has elapsed in the current session since the event occurred.

### Claim 2 (depends on 1)

The method of claim 1 in which the time that has elapsed in the current session since the event occurred is equal to a difference in time between the current session timestamp and the service timestamp associated with the event.

### Claim 3 (depends on 1)

The method of claim 1 in which generating the event timestamp is only performed if a session identifier identifying the session in which the event occurred is the same as the session identifier identifying the session when network time became available.

### Claim 4 (depends on 1)

The method of claim 1 further comprising, after network time has become available, generating an event timestamp that is initially unset for each of a plurality of events that occurred during the current session, each event timestamp representing a network time at which the respective event occurred, each of the event timestamps being equal to a difference between the network timestamp specifying when network time became available and a value equal to a difference between the current session timestamp and the service timestamp associated with the respective event.

### Claim 5 (depends on 4)

The method of claim 4 further comprising comparing an event timestamp for a first of the events to an event timestamp for a second of the events if both event timestamps have been set to the network time at which the respective events occurred.

### Claim 6 (depends on 1)

The method of claim 1 in which the event service data further includes a system identifier uniquely identifying the electronic processing device, wherein generating the event timestamp only occurs if a session identifier identifying the session in which the event occurred is the same as the session identifier identifying the session when network time became available and the system identifier identifying the electronic processing device on which the service timestamp was made is the same as the system identifier identifying the electronic processing device on which network time became available.

### Claim 7 (depends on 1)

The method of claim 1 in which current session time used to generate the current session timestamp is only available while the electronic processing device is powered up.

### Claim 8 (depends on 1)

The method of claim 1 in which the electronic processing device includes a clock that generates the timestamps, the clock including resettable battery-less clock circuitry for maintaining non-persistent time records.

### Claim 9

One or more computer-readable media storing computer-readable instructions that when executed by a processor cause the processor to perform a method for comparing a first timestamp for a first event to a second timestamp for a second event, which events occurs on an electronic processing device, the method comprising:
determining a first set of service data associated with the first event and a second set of service data associated with the second event, the service data for each event including a service timestamp denoting a time at which each event respectively occurred during a current session in which the electronic processing device is powered up;
determining a current session time representing a time that has elapsed since initiation of the current session;
determining a first event timestamp representing a network time at which the first event occurred, the first event timestamp being determined based on the first set of service data, the current session time and a network timestamp specifying a time when network time became available during the current session;
determining a second event timestamp representing a network time at which the second event occurred, the second event timestamp being determined based on the second set of service data, the current session time and the network timestamp specifying the time when network time became available during the current session.

### Claim 10 (depends on 9)

The computer-readable media of claim 9 in which the service data associated with each event further includes a session identifier uniquely identifying a session in which the respective event occurred and further comprising generating the event timestamps only if a session identifier identifying the session in which the respective event occurred is the same as the session identifier identifying the session when network time became available.

### Claim 11 (depends on 10)

The computer-readable media of claim 10 further comprising comparing the first event timestamp to the second event timestamp to determine a sequence in which the first and second events occurred.

### Claim 12 (depends on 9)

The computer-readable media of claim 9 in which the first event timestamp is equal to a difference between the network timestamp specifying when network time became available and a time that has elapsed in the current session since the first event occurred.

### Claim 13 (depends on 9)

The computer-readable media of claim 9 in which the service data associated with each event further includes a system identifier uniquely identifying the electronic processing device, wherein generating the event timestamp for each event only occurs if a session identifier identifying the session in which the respective event occurred is the same as the session identifier identifying the session when network time became available and the system identifier identifying the electronic processing device on which the service timestamp was made is the same as the system identifier identifying the electronic processing device on which network time became available.

### Claim 14 (depends on 9)

The computer-readable media of claim 9 in which the current session time is only available while the electronic processing device is powered up.

### Claim 15 (depends on 9)

The computer-readable media of claim 9 in which an initial timestamp associated with the first event and the first set of service data is unset when network time is unavailable when the initial timestamp is generated.

### Claim 16

An apparatus, comprising:
a clock;
a computer-readable storage medium; and
a processor responsive to the computer-readable storage medium and to a computer program, the computer program, when loaded into the process, operable to
generate event service data upon occurrence of the event, the event service data including a service timestamp denoting a time at which the event occurred during a current session in which the electronic processing device is continuously powered up, said event service data further including a session identifier uniquely identifying the current session;
generate a network timestamp specifying a time when network time become available and a current session timestamp representing a time that has elapsed since initiation of the current session; and
after network time has become available, generate an event timestamp representing a time at which the event occurred, said event timestamp being equal to a difference between the network timestamp specifying the time when network time became available and a time that has elapsed in the current session since the event occurred.

### Claim 17 (depends on 16)

The apparatus of claim 16 in which the clock includes resettable battery-less clock circuitry for maintaining non-persistent time records.

### Claim 18 (depends on 16)

The apparatus of claim 16 in which the processor is operable to generate the event timestamp only if a session identifier identifying the session in which the event occurred is the same as the session identifier identifying the session when network time became available.

### Claim 19 (depends on 16)

The apparatus of claim 16 in which, after network time has become available, the processor is further operable to generate an event timestamp that is initially unset for each of a plurality of events that occurred during the current session, each event timestamp representing a network time at which the respective event occurred, each of the event timestamps being equal to a difference between the network timestamp specifying when network time became available and a value equal to a difference between the current session timestamp and the service timestamp associated with the respective event.

### Claim 20 (depends on 16)

The apparatus of claim 16 in which generating the event timestamp only occurs if a session identifier identifying the session in which the event occurred is the same as the session identifier identifying the session when network time became available.
