Time-ordered data base

• US 4,646,229 A
• Filed: 11/15/1982
• Issued: 02/24/1987
• Est. Priority Date: 11/15/1982
• Status: Expired due to Term

• Current Assignee: Bell Telephone Laboratories, Inc. (Nokia Corporation)
• Original Assignee: AT&T, Inc.
• Inventors: Boyle, Gerald C.
• Primary Examiner(s): NOT, DEFINED
• Assistant Examiner(s): Niessen, William G.
• Application Number:
  US06/441,731
• Time in Patent Office: 1,562 Days
• Field of Search: 364/200 MS, 364/300 MS, 364/900 MS, 364/407, 340/825, 340/28
• US Class Current: 1/1
• CPC Class Codes: G06F 16/9024 Graphs; Linked lists G06F16/9027 takes precedence
• CPC Class Codes: H04Q 3/47 using translators
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A data base system includes future versions of the data base which are maintained currently in response to orders for future execution. All transactions against the data base are time stamped to assure access to the proper version of the data base. Information concerning the various versions are stored as delta nodes or lists. The application of this data base system to the assignment of outside plant telephone facilities to telephone subscribers is also described.

Claims

1. An electronic data base system comprising a plurality of data records, at least some of said records including pointers to a plurality of others of said records,

means for selectively accessing each of said data records,

means for representing a plurality of time-dependent versions of each of said data records, said time-dependent versions comprising a single version of said data base and the incremental changes to said current version, and

means, utilizing said accessing means and responsive to said time-dependent record versions, for making transactions against a consistent, time-dependent version of said data base representing the state of physical entitities at some future time.

2. The data base system according to claim 1 wherein said representing means further includes

means for generating at least one delta record for representing the relationship between a prior unchanged version of one of said data records and a subsequent changed version of the same data record.

3. The data base system according to claim 1 further comprising

means for maintaining a list of identifications of those data records affected by said transactions,

means for maintaining a list of data record versions of the same transaction, and

means, utilizing said lists to identify said consistent, time-dependent versions of said data base.

4. The data base system according to claim 1 wherein

said data records represent physical facilities to be assigned over time to a plurality of users, and

said transactions comprises the creation, modification or deletion of assignments of said physical facilities.

5. The data base system according to claim 4 wherein

said physical facilities comprise equipment utilized to provide telephone service to telephone subscribers.

6. The data base system according to claim 1 wherein each said data record comprises

a body portion identifying the nature and attributes of the physical entity represented by that data record, and

a plurality of edge portions identifying other data records and their specific relationship to the said data record.

7. The method of assigning physical facilities to a plurality of users for future use comprising the steps of

(1) creating a current version of a data base including a record to represent each of said physical facilities and the current assignments to each of said physical facilities to said users, at least some of said records thereby including pointers to a plurality of others of said records representing a particular one of said current assignments,

(2) for each new request for future assignment of facilities to one of said users,

(a) generating a future version of those records in said data base affected by the future assignment of the represented facility to said one user,

(b) maintaining a record of each fully consistent set of said data records corresponding to each of a plurality of future times,

(c) making future assignments of said facilities by utilizing the appropriate one of said fully consistent sets, and

repeating step (2) for all requests received prior to but due for execution subsequent to said new request.

8. The method of claim 7 wherein said step of maintaining fully consistent sets of data records further comprises the step of

(4) creating separate records in said data base identifying the data record version before each said future assignment and the data record version after each said future assignment.

9. The method of claim 7 wherein said step of maintaining fully consistent sets of data records further comprises the steps of

(4) creating separate lists of identifications of all versions of each data record, and

(5) creating a list of all data records affected by each said future assignment.

10. The method according to claim 7 wherein said steps of creating a current version or generating a future version further comprises the steps of

(4) creating a head portion of said data record including the identification and attributes of the physical facility therein represented, and

(5) creating a plurality of edge portions of said data record including the identification of related records and the attributes of the relationships with said related record.