Data base for persistent data

• US 7,127,478 B1
• Filed: 03/31/1999
• Issued: 10/24/2006
• Est. Priority Date: 04/29/1998
• Status: Expired due to Fees

• Current Assignee: Xieon Networks S.A.R.L. (Infinera Corp.)
• Original Assignee: Siemens AG
• Inventors: Schoenwolf, Gerd, Ziemski, Stefan, Brendel, Petra
• Primary Examiner(s): Corrielus, Jean M.
• Application Number:
  US09/282,145
• Time in Patent Office: 2,764 Days
• Field of Search: 707/103, 707/104, 707/200, 707/201, 709/227, 709/217
• US Class Current: 1/1
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: G06F 9/4493 Object persistence
• CPC Class Codes: G11C 29/74 using duplex memories, i.e. using dual copies
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

A data base for permanent data has a first memory from which date is written into a buffer. Data is transferred from the buffer store into at least two permanent memories.

Claims

1. A data base for storing persistent data, corresponding to configuration data that is complete for configuring a terminal, comprising:

a buffer into which is written persistent data to be permanently stored;

a permanent memory connected to the buffer, the permanent memory having at least two storage areas, into which the persistent data alternately written, each storage area storing the configuration data that is complete for configuration of at least one of;

(a) functions of the terminal,

(b) characteristics of the terminal, and

(c) cards of the terminal, at least one of the permanent configuration stored having a complete configuration available and being selected for hardware implementation,

wherein the configuration data that is complete for configuration is alternately written into the storage areas by writing the complete configuration data into one of the storage areas completely and thereafter a later version of the configuration data is stored in the other storage area completely such that if the later version is lost during loading, the persistent data that is complete for configuration stored in at least one of the storage areas continues to exist and is recoverable, and wherein the persistent data stored in the buffer is alternately written into one of the storage units of the permanent memory; and

a control mechanism with a first application process for management of a first memory controls writing of the data to be persistently stored into the buffer, the data being generated or modified by the first application process alone or also by other application processes running simultaneously with the first application process, wherein only modified data sequences are alternately written into storage segments of the permanent memory.

2. The data base according to claim 1, wherein the modified data sequences are written into the storage segments of the permanent memory at predetermined time intervals.

3. The data base according to claim 1, wherein the modified data sequences are written into the storage segments of the permanent memory after a predetermined number of modifications.

4. The data base according to claim 1, wherein only the persistent data, if necessary including reconstruction data, is transferred into the buffer from a first memory which contains a run-time program and associated permanent data.

5. The data base according to claim 4, wherein the persistent data is stored in a space-saving manner as a data sequence in the buffer and in the permanent memory.

6. The data base according to claim 1, wherein if construction data which is useable for reconstruction is present in the buffer, the configuration data to be written into the first memory is automatically recovered from the reconstruction data stored in the buffer.

7. The data base according to claim 1, wherein the permanent memory is a loadable Flash Erasable Programmable Read Only Memory chip.

8. The data base according to claim 1, wherein a number of configuration changes are only performed at a data management side and thereafter at least one of a functional and a hardware change comprising all configuration changes is performed in the terminal.

9. A data base for storing persistent data corresponding to configuration data that is complete for configuring a terminal, comprising:

a buffer into which is written persistent data to be permanently stored;

a permanent memory connected to the buffer, the permanent memory having at least first and second storage units, into which the persistent data is alternately written, each storage unit storing the configuration data that is complete for configuration of at least one of;

(a) functions of the terminal,

(b) characteristics of the terminal, and

(c) a hardware implementation, of a terminal or cards of the terminal, at least one of the permanent configurations stored having a complete configuration available and being selected for hardware implementation, wherein the configuration data that is complete for configuration is alternately written into the storage units by writing the complete configuration data into one of the storage units completely and thereafter a later version of the configuration data is stored in the other storage unit completely such that if the later version is lost during loading, the persistent data that is complete for configuration stored in at least one of the storage units continues to exist and is recoverable; and

a control mechanism within a first application process for management of a first memory controls writing of the data to be persistently stored into the buffer, the data being generated or modified by the first application process alone or also by other application processes running simultaneously with the first application process.

10. The data base according to claim 9, wherein all of the persistent data is stored in the buffer is alternately written into one of the storage units of the permanent memory.

11. The data base according to claim 10, wherein only modified data sequences are alternately written into storage segments of the permanent memory.

12. The data base according to claim 11, wherein the modified data sequences are written into the storage segments of the permanent memory at predetermined time intervals.

13. The data base according to claim 11, wherein the modified data sequences are written into the storage segments of the permanent memory after a predetermined number of modifications.

14. The data base according to claim 9, wherein only the persistent data, if necessary including reconstruction data, is transferred into the buffer from a first memory which contains a run-time program and associated permanent data.

15. The data base according to claim 14, wherein the persistent data is stored in a space-saving manner as a data sequence in the buffer and in the permanent memory.

16. The data base according to claim 9, wherein the permanent memory is a loadable Flash Erasable Programmable Read Only Memory chip.

17. The data base according to claim 9, wherein a number of configuration changes are only performed at a data management side and thereafter at least one of a functional and a hardware change comprising all configuration changes is performed in the terminal.

18. A data base for storing persistent data corresponding to configuration data that is complete for configuring a terminal, comprising:

a buffer into which is written persistent data to be permanently stored;

a permanent memory connected to the buffer, the permanent memory having at least first and second storage units, into which the persistent data is alternately written, each storage unit being storing the configuration data that is complete for configuration of at least one of;

(a) functions of the terminal,

(b) characteristics of the terminal, and

(c) a hardware implementation, of a terminal or cards of the terminal, at least one of the permanent configurations stored having a complete configuration available and being selected for hardware implementation, wherein the buffer has at least first and second random access memories functionally connected in series, persistent data stored in the first random access memory being written into the second random access memory so that the first random access memory is available for reloading while persistent data from the second or a further random access memory is written into the permanent memory; and

a control mechanism within a first application process for management of a first memory controls writing of the data to be persistently stored into the buffer, the data being generated or modified by the first application process alone or also by other application processes running simultaneously with the first application process.

19. The data base according to claim 18, wherein all of the persistent data is stored in the buffer is alternately written into one of the storage units of the permanent memory.

20. The data base according to claim 19, wherein only modified data sequences are alternately written into storage segments of the permanent memory.

21. The data base according to claim 20, wherein the modified data sequences are written into the storage segments of the permanent memory at predetermined time intervals.

22. The data base according to claim 20, wherein the modified data sequences are written into the storage segments of the permanent memory after a predetermined number of modifications.

23. The data base according to claim 18, wherein only the persistent data, if necessary including reconstruction data, is transferred into the buffer from a first memory which contains a run-time program and associated permanent data.

24. The data base according to claim 23, wherein the persistent data is stored in a space-saving manner as a data sequence in the buffer and in the permanent memory.

25. The data base according to claim 18, wherein if construction data which is useable for reconstruction is present in the buffer, the configuration data to be written into the first memory is automatically recovered from the reconstruction data stored in the buffer.

26. The data base according to claim 18, wherein the permanent memory is a loadable Flash Erasable Programmable Read Only Memory chip.

27. The data base according to claim 18, wherein a number of configuration changes are only performed at a data management side and thereafter at least one of a functional and a hardware change comprising all configuration changes is performed in the terminal.