JPH09146814A - Data base assuarance system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To securely restore a data base in past operation even if a new program is not settled on a communication system and a restart switched-back state is entered. SOLUTION: This security system switches operation by new software back to operation by old software when the new software is not settled within a specific time after the switching from the old software to the new software. The system is equipped with a backup memory 41 which backs up and holds a data base referred to at the time of system operation; and a new data base for new operation is generated from the old data base in the backup memory 41 at the time of switching from the operation by the old software to the operation by the new software, the old data base in the backup memory 41 is held as it is, and after a settlement command is received, the old data base in the backup memory 41 is rewritten with the generated new data base.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a database guarantee system, and more specifically, it relates to a communication system for switching back to the operation by the old software because it is not fixed within a predetermined time after switching from the old software to the operation by the new software. Database guarantee method.

In recent years, the configuration of communication systems (switching devices, transmission devices, etc.) is software-led, and the enhancement or modification of the functions is performed by replacing the software (including the database). In particular, in a communication system that constitutes a network, it is necessary to replace the software of all communication systems at the same time. At that time, switching processing from old software to new software, and when the switching is not normally performed, It is necessary for the switchback process from the new software to the old software to be performed smoothly and reliably.

[0003]

2. Description of the Related Art In a transmission apparatus, for example, new software whose function is improved remotely is downloaded to a standby side, and a bank switch quickly switches between the old software currently used and the new software downloaded. At this time, the old software database and the new software database may be different, but in general, this type of database has upward compatibility, and the setting value of the old database (however, it can be updated by operation) Is inherited as it is, and the version number of the software and database is upgraded at the same time by adding the setting value of the new database to this.

Conventionally, at this point (that is, without waiting for the establishment of new software and new database), the old database of all backup memories is rewritten with the new database. By the way, even if the above new software is switched, if any one of the transmission devices on the network does not successfully switch to the new software, the new software is not fixed to the network. It is necessary to switch back to the old software all at once.

[0005]

However, according to the above-mentioned conventional database guarantee method, since the old database in the backup memory is completely erased at the time of switching to the new software, it will no longer exist when a failback occurs. There was a problem that the old database could not be restored.

Further, for this reason, there is an inconvenience that the operation of the system must be restarted with the default database (initial setting value) of the old software. The purpose of the present invention is that the new program is not established in the communication system,
It is to provide a database guarantee method that can reliably restore the old database even if the restart fails over.

[0007]

[Means for Solving the Problems] The above-mentioned problems are shown in FIG.
It is solved by the configuration of. That is, the database guarantee method of the present invention (1) is a database guarantee method for a communication system in which the old software is switched to the operation by the new software and the operation is not restored within a predetermined time, so that the operation is switched back to the operation by the old software. A backup memory 41 for backing up and holding a database referred to during operation is provided, and when switching from the old software to the operation by the new software, the old database (old DB) of the backup memory 41 is newly used for new operation. While creating a database (new DB),
The old database of the backup memory 41 is retained as it is, and after the fixing command is received, the old database of the backup memory 41 is rewritten with the generated new database.

According to the present invention (1), even when the new program is not fixed in the communication system and the restart / failback occurs, the backup memory 41 retains the backup of the old database as it is. It is possible to reliably restore the database. The above problem is solved by the configuration of FIG. That is, the database guarantee method of the present invention (2) is a database guarantee method for a communication system in which after switching from old software to operation by new software, it is not settled within a predetermined time so that the operation is switched back to old software. A volatile backup memory 41 that backs up and holds a database that is referenced during operation, and first and second non-volatile backup memories 5 that back up and holds a database that is referenced during system operation.
21 and 522, a new database for new operation is generated from the old database of the volatile backup memory 41 at the time of switching from the old software to the operation by the new software, and the first or second The old database of the non-volatile backup memory 521/522 is rewritten with the newly created database.

According to the second aspect of the present invention, even if the new program is not fixed in the communication system and restart restart occurs, the first or second non-volatile backup memory 5 is used.
Since 21/522 retains the backup of the old database as it is, it is possible to surely restore the old database. Moreover, the stored contents of the first and second non-volatile backup memories 521 and 522 are not lost even when the power supply of the communication system is turned off, so that the operation reliability at the time of system switching and failback is high.

Preferably, in the present invention (3), when switching back to the operation by the old software, the consistency between the old software and the database of the volatile backup memory 41 is checked and the consistency is obtained. In this case, the old database is restored from the database of the volatile backup memory 41, and when the above consistency cannot be obtained, the first and second nonvolatile backup memories 521 and 522 are used.
Check the consistency with the other database and restore the old database from the one with the consistency.

According to the present invention (3), both old and new databases are backed up and held in the system, and after the consistency between the old software and these databases is checked, the old software is switched to the old software. The system boots up safely because it does a revert. Further, the above problem is solved by the configuration of FIG. That is, the present invention (4)
The database guarantee method of is referred to at the time of system operation in the database guarantee method of the communication system in which the old software is not settled within the predetermined time after switching from the old software to the operation by the new software The first and second backup memories 41 and 52 for backing up and holding the database are provided, and when the old software is switched to the operation by the new software, the old database of the first or second backup memory 41/52 is newly updated. In addition to generating a new database for operation, the old database of the first or second backup memory 41/52 is rewritten with the generated new database.

According to the present invention (4), even when the new program is not fixed in the communication system and restart restart occurs, the first or second backup memory 41/52 is used.
Keeps the old database as a backup, it is possible to reliably restore the old database with a small backup memory.

[0013]

BEST MODE FOR CARRYING OUT THE INVENTION Preferred embodiments of the present invention will be described below with reference to the accompanying drawings. Note that the same reference numerals indicate the same or corresponding parts throughout the drawings. FIG. 2 is a diagram showing the configuration of the database guarantee system according to the first embodiment. In the figure, 100 is a transmission device (including an exchange) A to C, 1 is a signal transmission unit for transmitting a main signal, and 2 is a signal transmission unit. A transmission control unit that performs main control of the signal transmission unit 1 by a CPU (not shown), 3 is a common bus of the control unit 2, 4 is an SV unit that mainly performs supervisory control of the entire device, 41 is a primary backup database memory composed of RAM (Primary BUDB
M), 5 is an MP unit that mainly manages a database (station data, subscriber data, etc.), 51 is an operational (active) database memory (operation DBM) consisting of RAM, 52
Is a secondary backup database memory (secondary BUDBM) consisting of EEPROM, 53 is a default database memory for storing the default file of the database, 6 is a PM unit for storing and managing the control program executed by the transmission control unit 2, and 61 is A bank switch that switches the new and old control programs by hardware,
62 is a program memory (SBPG on the standby side
M) and 63 are program memories on the operation side (operation PG
M), 64 is a program expansion section, 65 is a buffer memory (BFRAM) composed of RAM, 7 and 8 are signal lines for exchanging commands and data between units, 20
Reference numeral 0 is a transmission path connecting the transmission devices A to C, and reference numeral 300 is a supervisory control terminal device for performing switching control related to enhancement (function enhancement) of the communication network.

Each unit 4 to 6 has its own C
It is equipped with a PU (not shown) and performs corresponding management / control. In the transmission device A, the bank S is in operation while the device is in operation.
W61 is connected to the operating PGM 63 side, and the transmission control unit 2 performs various communication services while referring to the operating (old) database of the operating DBM 51 according to the operating (old) program of the operating PGM 63. At this time, both the primary and secondary BUDBMs 41 and 52 backup-hold the operational (old) database of the operational DBM 51. The same applies to the transmission devices B and C.

When enhancing the transmission apparatus A, first, a new program (usually compressed) with improved functions is downloaded from the supervisory control terminal apparatus 300. The new program is buffered in the BFRAM 65 via the SV unit 4, further expanded by the expansion unit 64, and expanded in the SBPGM 62 on the standby side. The same new program is also downloaded to the other transmission devices B and C via the signal line 8, the transmission path 200, etc., and expanded / stored on the respective standby sides.

FIG. 3 is a diagram for explaining the operation of the database guarantee system according to the first embodiment, and shows the program switching process / switchback process after the program standby expansion. After the standby deployment of the new program, the supervisory control terminal device 300 makes a reservation for program switching to the transmission device A.

That is, when a predetermined switching command is input from the supervisory control terminal device 300 to the SV unit 4, the SV unit 4 notifies the MP units (M) and (D) of the information. Here, the MP unit (M) is a board on the mother side and includes an operation DBM 51. Further, the MP unit (D) is a daughter side board, and the secondary BUDBM52
including. Further, the switching command includes the switching execution date ACTDAT (eg 95/08/23), the scheduled switching time ACTTM (eg 15:00: 00), and the switching process timeout time VALTM (eg: 00:30:
00). Then, when the MP units (M) and (D) return a request response to the SV unit 4, the SV unit 4 returns a command response to the monitoring control terminal device 300.

In the same manner as above, the supervisory control terminal device 300
Reserves the program switching for the transmission devices B and C. Eventually, at the scheduled switching time (15:00: 00), in all the transmission devices A to C, each unit simultaneously starts restart switching processing, and the MP unit (M) stores the old database of the primary BUDBM 41. Operate while converting according to the new database format D
Build a new database on BM51.

Here, a mode of constructing a new database will be described with reference to FIG. At the beginning of the operation of this system, the initial settings (1) to (5) of the old default file according to the old program are addresses 1 to 5 of the operation DBM 51.
Had been deployed to. This content is immediately backed up and held in each of the primary and secondary BUDBMs 41 and 52.

After that, when the transmission apparatus A is operated by the old program, a maintenance person changes the database and the like, and along with this, the initial setting (1) to
The contents of necessary parts of (5) are updated, and the whole is called operations (1) to (5). This content is immediately backed up and held in each of the primary and secondary BUDBMs 41 and 52.

When the restart switching process is started after the standby development of the above new program, the first B
The operations (1) to (5) of the UDBM 41 are copied to the addresses 1 to 5 of the operation DBM 51. Next, the initial settings (6) and (7) of the new default file are additionally expanded to the addresses 6 and 7 of the operation DBM 51, and the new database is constructed in this way.

Returning to FIG. 3, when a new database is constructed on the operation DBM 51, the bank SW 61 is switched and the transmission device A is started up by the new program while keeping the old database of the primary BUDBM 41. At the same time, the switching LED of the SV unit 4 is turned on. Then, the user management registration request A is sent from the monitor control terminal device 300.
When CT-USER is input, MP is sent from SV unit 4.
The unit 5 is notified of the user management registration request. MP
When the device startup by the new program (including the new database) is normal, the unit 5 registers the user management table and returns the registration response. S that received this
The V unit 4 returns the registered command response COMPLD to the monitor control terminal device 300.

As a result, the monitor control terminal device 300 is
The transmission device A determines that the new program and new database can be fixed. The supervisory control terminal device 300 also requests the other transmission devices B and C for user management registration request ACT.
-If USER is performed and the registration command response COMPLD is obtained from all the transmission devices A to C in this way, it is determined that the new program and new database can be fixed in all the systems.

As a result, the supervisory control terminal device 300 sends a fixing command to all the transmission devices A to C at the same time to fix the new program and new database to each device.
In response to this, the transmission apparatus A backs up (copies) the new database of the operation DBM 51 to each of the primary and secondary BUDBMs 41 and 52, and turns off the switching LED. The same applies to the other transmission devices B and C. Thus, the function enhancement of the network is normally terminated.

However, in any one of the transmission devices of the network, the switching to the new program ends abnormally, which causes the response COMPLD to the fixing command.
Is not returned, the supervisory control terminal device 300
Unable to send fixing command by 5:30:00.
As a result, time-outs occur in all of the transmission devices A to C, and the restart / return processing to the old program starts.

Even in this case, according to the present embodiment, since the old database exists in the primary BUDBM 41, this is copied (restored) to the operation DBM 51. Next, the old database of the operation DBM 51 is backed up and retained in the secondary BUDBM 52. Then, the system is started up with the old program and the old database. FIG. 5 is a diagram showing the configuration of the database guarantee system according to the second embodiment, and shows a case where two secondary backup database memories are provided.

In the figure, 521 is a first secondary backup database memory 522 composed of an EEPROM.
Is a second secondary backup database memory consisting of an EEPROM. 6 and 7 are diagrams (1) for explaining the operation of the database guarantee method according to the second embodiment,
(2).

In FIG. 6, when the restart switching process is started after the standby development of the new program, the primary BU
A new database is constructed in the operational DBM 51 based on the old database of the DBM 41. Next, the new database of the operation DBM 51 is backed up and held in the primary BUDBM 41 and the second secondary backup database memory 522. However, the first secondary backup database memory 521 holds the old database. The old database of the primary BUDBM 41 may be left as it is.

After that, the bank SW61 is switched and the transmission device A is started up by the new program. In addition, SV
The switching LED of the unit 4 is turned on. After that, when a fixing command is received, the new database of the operation DBM 51 is updated to the first secondary backup database memory 5
The backup is held at 21. In FIG. 7, however,
If the fixing command is not input within the time and restart restart is performed, the consistency between the old program and the database of the primary BUDBM41 is checked. If the consistency is obtained, the old database of the primary BUDBM41 is checked. It is expanded (copied) to the operation DBM 51. And operation DB
The old database of M51 is backed up and held in the first and second secondary backup database memories 521 and 522.

If the above-mentioned matching is not obtained,
The consistency between the old program and the databases of the first and second secondary backup database memories 521 and 522 is checked, and one of them is obtained (in this example, the second secondary backup database memory 522). The old database of is expanded (copied) to the operation DBM 51. Then, the old database of the operational DBM 51 is changed to the primary B
The backup is held in the UDBM 41 and the first secondary backup database memory 521.

Then, start up the device with the old program,
The switching LED is turned off. Although not shown, the first secondary backup database memory 521 is deleted, the new database at the time of restart switching is backed up and retained in the primary BUDBM 41 or the second secondary backup database memory 522, and the old database is retained. Second secondary backup database memory 5
It is obvious that it may be configured to remain in the 22 or primary BUDBM 41.

Although a plurality of preferred embodiments of the present invention have been described above, it goes without saying that various changes in the configuration, control, and combinations thereof can be made without departing from the spirit of the present invention. There is no.

[0033]

As described above, according to the present invention, even after switching to the operation of a new file and then switching back to the operation of the old file, the database of the old operation remains in the system. The operation reliability of the communication system of this kind is remarkably improved.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating the principle of the present invention.

FIG. 2 is a diagram showing a configuration of a database guarantee system according to the first embodiment.

FIG. 3 is a diagram illustrating an operation of the database guarantee method according to the first embodiment.

FIG. 4 is a diagram illustrating an aspect of new database construction according to the first embodiment.

FIG. 5 is a diagram showing a configuration of a database guarantee system according to a second embodiment.

FIG. 6 is a diagram (1) explaining the operation of the database guarantee method according to the second embodiment.

FIG. 7 is a diagram (2) for explaining the operation of the database guarantee method according to the second embodiment.

[Explanation of symbols]

 1 Signal Transmission Unit 2 Transmission Control Unit 41 Primary Backup Database Memory 51 Operation Database Memory 52 Secondary Backup Database Memory 100 Transmission Device 200 Transmission Line 300 Monitoring Control Terminal Device

Claims (4)

[Claims] 1. A database referred to during system operation in a database guarantee method of a communication system in which the old software is not fixed within a predetermined time after switching from the old software to the operation by the new software, and thus the operation is switched back to the old software. With a backup memory that retains the backup memory, when switching from the old software to the new software operation, a new database for the new operation is created from the old database of the backup memory, and the old database of the backup memory remains unchanged. A database guarantee method, characterized in that the old database of the backup memory is rewritten with the newly created database after holding and receiving a fixing command. 2. A database referred to during system operation in a database guarantee method of a communication system in which the old software is not fixed within a predetermined time after switching from the old software to the operation by the new software so that the old software is switched back to the old software. It is equipped with a volatile backup memory that backs up and holds the first and second non-volatile backup memory that backs up and holds the database that is referenced during system operation. When switching from old software to new software operation, A database for generating a new database for new operation from the old database of the volatile backup memory, and rewriting the old database of the first or second non-volatile backup memory with the generated new database. Protection Proof method. 3. When switching back to the operation by the old software, the consistency between the old software and the database of the volatile backup memory is checked, and if the consistency is obtained, the database of the volatile backup memory is checked. The old database is restored, and if the above consistency cannot be obtained, the consistency between the first and second non-volatile backup memory databases is checked, and the old database is restored from the one with the consistency obtained. The database guarantee method according to claim 2, wherein 4. A database referred to at the time of system operation in the database guarantee method of the communication system in which the old software is not fixed within a predetermined time after switching from the old software to the operation by the new software and the old software is switched back to the old software. The first and second backup memories for backing up and holding the new database for the new operation from the old database of the first or the second backup memory when switching from the old software to the operation by the new software. A database guarantee method, characterized in that the old database in the first or second backup memory is rewritten with the new database created as described above.