IP Library Patent Application 13889086
Patent Application
App. No. 13/889,086

EVENT-BASED RECORDS MANAGEMENT

Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US None
App. No.
13/889,086
Abstract

Systems and methods of managing operational records, for example of a private response center. In one implementation the system includes one or more processors, memory holding instructions executable by the one or more processors, distributed storage holding a plurality of event stores storing records of events, and one or more electronic communication links between locations at which the event stores are stored. The instructions, when executed by the one or more processors, cause the system to receive a request for a view of a state of the system, and construct the view from the records in at least one of the event stores.

Claims (41)

1 . A system for managing operational records, the system comprising:

one or more processors;

memory holding instructions executable by the one or more processors;

distributed storage holding a plurality of event stores storing records of events; and

one or more electronic communication links between locations at which the event stores are stored;

wherein the instructions, when executed by the one or more processors, cause the system to

receive a request for a view of a state of the system; and

construct the view from the records in at least one of the event stores.

2 . The system for managing operation records of claim 1 , wherein the events include calls by clients of a private response center requesting assistance from the private response center.

3 . The system for managing operation records of claim 1 , wherein the instructions, when executed by the one or more processors, further cause the system to synchronize the event stores to reflect changes made at one of the event stores such that eventually a view resulting from a request made at any of the event stores will be consistent with a view resulting from a like request made at any other of the event stores.

4 . The system for managing operation records of claim 1 , wherein upon receipt of a write of a new event record to the event stores, the event is applied to any affected views.

5 . The system for managing operation records of claim 1 , wherein events are applied to affected views in conjunction with constructing a snapshot of a state of the event stores.

6 . The system for managing operation records of claim 1 , wherein the instructions, when executed by the one or more processors, further cause the system to construct a snapshot of a state of the event stores.

7 . The system for managing operation records of claim 6 , wherein the instructions, when executed by the one or more processors, further cause the system to construct the requested view in relation to the most recent snapshot.

8 . A method of maintaining records of events, the method comprising:

maintaining in distributed storage a plurality of computerized event stores storing records of events in a non-hierarchical list;

constructing views of the records in the event stores in response to view requests;

synchronizing the event stores, via electronic messages sent over a data network, to reflect changes made at one of the event stores such that eventually a view resulting from a request made at any of the event stores will be consistent with a view resulting from a like request made at any other of the event stores.

9 . The method of claim 8 , further comprising applying an event record to an affected view upon receipt of a write of the new event record to the event stores.

10 . The method of claim 8 , further comprising periodically preparing a snapshot of the state of an aspect of the event records in the event stores.

11 . The method of claim 10 , further comprising applying an event record to an affected view in conjunction with constructing a snapshot of an aspect of the event records in the event stores.

12 . The method of claim 8 , further comprising auditing a state of the event stores by reconstructing the state from event records in the event stores.

13 . The method of claim 8 , further comprising:

receiving event records independently at one of the event stores during a time when network connectivity is lost between the event stores; and

when network connectivity is restored, synchronizing the event records in the event stores.

14 . The method of claim 8 , wherein constructing views of the records in the event stores comprises constructing a view that includes a listing of event records from the event stores.

15 . The method of claim 8 , wherein constructing views of the records in the event stores comprises constructing a view that includes state information derived from event records in the event stores.

16 . The method of claim 8 , further comprising grouping related events in the event stores into incidents.

17 . A system for managing records, the system comprising:

one or more processors;

memory holding instructions executable by the one or more processors;

distributed storage holding a plurality of event stores storing records of events in a non-hierarchical list; and

an electronic network connecting the distributed event stores;

wherein the instructions, when executed by the one or more processors, cause the system to

receive a request for a view of a state of the system;

construct the view from the records in at least one of the event stores;

receive at one of the event stores a record of a new event; and

synchronize the event stores to reflect the new event such that eventually a view resulting from a request made at any of the event stores will be consistent with a view resulting from a like request made at any other of the event stores.

18 . The system of claim 17 , wherein the event stores are synchronized upon receipt of the new event record.

19 . The system of claim 17 , wherein the event stores are synchronized in conjunction with constructing a snapshot of the state of an aspect of the event records in the event stores.

20 . The system of claim 17 , wherein no event records are deleted from the event stores.

Assignments (3)
RELEASE OF SECURITY INTEREST Recorded Nov 8, 2017
From: SILICON VALLEY BANK
To: GREATCALL, INC.
Reel/Frame 044071/0393 →
SECURITY INTEREST Recorded Mar 28, 2014
From: GREATCALL, INC.
To: SILICON VALLEY BANK
Reel/Frame 032555/0452 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 10, 2013
From: BRENTON, SCOTT; VAN DER RAADT, KRIJN; GYOKOV, KALIN
To: GREATCALL, INC.
Reel/Frame 030396/0902 →