KR20030008111A - A system and method for checking data in distributed database on a memory - Google Patents

Abstract

PURPOSE: A method and system for examining data of a memory-resident distributed database is provided to inform a result to an operator by examining a scope of a specific attribute with respect to one relation in one sub system, examining scope of all attributes with respect to one relation in one sub system, examining scope of all attributes with respect to all relations in one sub system, or examining scope of all attributes with respect to all relations in all sub systems mounted in a system. CONSTITUTION: A DB scope examination of an ATM switching system is started(S301). Data for examining a DB scope are initialized(S302). A command or an examination request signal of an operator is registered(S303). A request signal is waited in a signal waiting state(S304). If the signal being inputted through an HMI is a DB scope examination operator command(S305), a command process procedure is called for a command analysis(S306). If the DB scope examination operator command is inputted, an OMP(Operation and Maintenance Process) processor examines distributed database data of an ATM area exchanging sub system through a call connection control processor. If the signal being inputted through the HMI is a DB scope examination request signal(S307), a DB scope examination procedure is called(S308). If the DB scope examination request signal is inputted, the OMP processor examines distributed database data of an ATM area exchanging sub system in which the processor is positioned. A signal waiting state is returned again(S309).

Description

A system and method for checking data in distributed database on a memory}

The present invention relates to a method for checking an attribute of a memory-resident distributed database during execution of an ATM exchange. More specifically, the present invention relates to a method and a system for checking a data of a memory-resident distributed database for providing data integrity of a range of attributes of a database. It is about.

The basic building block of a database is a two-dimensional table (or relation). A table consists of a set of data rows (tuples), each of which in turn consists of several data elements (attributes). At this time, each attribute is configured to have a basic data type such as a string, a number, a date, and the like.

In the conventional ATM switching system, there is no specific inspection method for periodically and on-demandly checking the attributes of a distributed database online, and some passive methods of examining data are partially used. Because of this, there was no way to find attribute biolations that occur in the entire database.

SUMMARY OF THE INVENTION An object of the present invention to solve the above problems of the prior art is to check the scope of a specific attribute for a relation in one subsystem, or to check the scope of all attributes for a relation in a subsystem. A memory-resident distributed database that checks the scope of attributes for all relations in a subsystem, or checks the scope of attributes for all relations of all subsystems in the system and notifies the operator of the results. To provide a data inspection method and system.

1 is a structural diagram of a general ATM switch system;

2 is a structural diagram of a database attribute range checking system according to the present invention;

3 is an operation flowchart showing a data inspection method according to the present invention;

4 is an operation flowchart showing a DB range check command processing procedure shown in FIG.

5 is an operation flowchart showing the subsystem inspection procedure shown in FIG. 4;

6 is an operation flowchart illustrating a DB range checking procedure operated by the DB range checking request signal of FIGS. 3 and 5;

7 is a flowchart illustrating a relation inspection procedure shown in FIG. 6;

FIG. 8 is a flowchart illustrating an attribute range checking procedure shown in FIG. 7;

FIG. 9 is a flowchart illustrating an attribute range checking procedure illustrated in FIG. 8.

※ Explanation of code about main part of drawing ※

210: operator graphics and command interface

220: operation maintenance processor

230: call / connection control processor

221, 231: ADDBF block

222, 232: relation interface

223, 233: data extraction interface

224, 234: DB initialization data (PLD: Processor Loading Data)

In an ATM switch system comprising an ATM central switching subsystem and distributed ATM regional switching subsystems, according to the present invention for achieving the above object, an operation maintenance processor and a call connection control processor of an ATM regional switching subsystem are described. The method of examining distributed databases located in distributed ATM regional switching subsystems is:

Initializing, by the operation maintenance processor, data for DB range checking of the distributed database;

When the DB range check command signal for requesting the attribute range check for any subsystem is input from the operator, the operation maintenance processor verifies the input parameters input from the operator and searches the DB check function and the inspection performing subsystem. ; And

And performing, by the operation maintenance processor, a subsystem inspection procedure for all the inspection performing subsystems found.

According to the present invention, there is provided a computer-readable recording medium having recorded thereon a program for executing a data inspection method of a memory resident distributed database as described above in an operation maintenance processor of an ATM switching system.

In addition, the data inspection system of the memory-resident distributed database according to the present invention, the HMI in charge of graphic and command interfacing function with the operator, and receives the operator's command from the HMI to perform the control and management functions and all devices in the system And a plurality of CCCP processors that manage the OMP processor, and which communicate with the OMP processor and control subscribers connected to the respective regions and calls thereto.

The OMP processor and CCCP processor, respectively,

PLD storing DB initialization data;

An ADDBF block that finds a desired relation from the PLD and reads attribute data to perform the attribute range check;

A relation interface under control of the ADDBF block to find a relation in the PLD and provide the relation to the ADDBF block; And

Under the control of the ADDBF block is characterized in that it comprises a data extraction interface to read the attribute data in the PLD, check the range and provide it to the ADDBF block.

Hereinafter, with reference to the accompanying drawings will be described in more detail "data inspection method and system of the memory resident distributed database" according to an embodiment of the present invention.

1 is a structural diagram of an ATM switch system to which a check method for providing range integrity of attributes of a memory resident distributed database is executed during execution of an ATM switch, FIG. 2 is a structure for data checking processing of a database, and FIG. 4 is an operation flowchart showing a data inspection method according to the present invention, FIG. 4 is an operation flowchart showing the DB range inspection command processing procedure shown in FIG. 3, and FIG. 5 is an operation flowchart showing the subsystem inspection procedure shown in FIG. 6 is an operation flowchart showing the DB range checking procedure shown in FIG. 3, FIG. 7 is an operation flowchart showing the relation checking procedure shown in FIG. 6, and FIG. 8 is an attribute range checking shown in FIG. 7. 9 is a flowchart illustrating a procedure, and FIG. 9 is a flowchart illustrating an attribute range checking procedure illustrated in FIG. 8.

1 is a structural diagram of an ATM switch system to which the present invention is applied, wherein an ATM Central Switching Subsystem (ACS) 10 has a centralized switch structure, and an ATM Local Switching Subsystem (ATM Local). Switching Subsystem (hereinafter referred to as ALS) 20 has a distributed structure.

The ALS 20 includes an ALS # 0 (21) having an operation and maintenance process (hereinafter referred to as OMP) that performs control and management functions and manages all devices in the system. It consists of ALS # 1 (22) to ALS # 64 (24) having a connected subscriber and a call control processor (call CCCP), the ATM switch is a plurality of distributed local switch And centralized switch.

The distributed database relations of interest in the present invention are located in a distributed manner in the CCCP and the OMP, which only reside in the main memory of the CCCP and the OMP, respectively, and record only the disk backup request among the changed information. In case of error recovery, the data stored in the disk, the most recently backed up data, are restored.

2 is an internal structure diagram of CCCP and OMP for the database attribute check processing to which the present invention is applied. DB inspection accepts inspection requests through the operator's graphic and command interface (HMI), and analyzes these requests and performs the following inspection process. Automated checks are handled by asking the ADDBF block (AuDit DataBase Function Block) to use a signal from the associated function block. ADDBF block, a software block subject that performs DB range checking, is located in OMP and CCCP, finds the desired relation in the DB Loading Data (PLD) through the relation interface, and reads the attribute data through the data extraction interface. Check if it is normal. The ADDBF block of CCCP and the ADDBF block of OMP have the same structure except that the PLD data is different because it is data corresponding to each subsystem.

3 is an operation flowchart illustrating a DB range checking process of the ADDBF block of the operation maintenance processor according to the present invention. First, when the system starts, the DB range check of the ATM switch is started (S301). First, data for DB range check is initialized (S302), and the operator's command or check request signal is registered (S303). The process waits for a request signal (S304).

If the signal input through the HMI in step S304 is a DB range check operator command (S305), the command processing procedure is called for command analysis (S306). When this DB range check operator command is entered, the OMP processor checks the distributed database data of the ATM regional switching subsystem through the call connection control processor. On the other hand, if the signal input through the HMI is a DB range check request signal (S307), the DB range check procedure is called (S308). When this DB range check request signal is input, the OMP processor checks the distributed database data of its located ATM regional switching subsystem (ALS # 0). When the procedures of steps S306 and S308 are completed, the signal goes back to the signal waiting state (S309).

4 is a flowchart illustrating an operation of processing a DB range checking command shown in FIG. 3. First, when the command processing procedure is started (S401), the input parameter of the operator is verified (S402), the inspection function information is searched to check the current inspection execution state (S403), and if possible, the type of subsystem to be performed. Search for (S404) and check the subsystem number (S405).

If the subsystem number is ALL in step S405 (S406), and outputs a check start message (S406), and checks the status of each call connection control processor (CCCP) for the 16 ATM regional switching subsystems (ALS00 to ALS15) (S407) If is normally alive (S408) performs the subsystem check procedure of Figure 5 (S409), and if not normal, proceeds to the next subsystem. In addition, after checking all 16 ALS, the test completion message is output (S410), and the process is returned to a higher process (S414).

If the subsystem number is not ALL in step S405 (not All), check the state of the processor (S411). If the state is normal (S412), perform the subsystem check procedure (S413). Return to (S414).

FIG. 5 is an operation flowchart showing the subsystem inspection procedure shown in FIG. 4. This procedure is a check procedure performed at the ADDBF 231 of the call connection control processor 230 used when the operator has requested all attribute range checks corresponding to the entire relation to the subsystem. When the subsystem check procedure is started (S501), the DB range check request signal is transmitted to the processor of the subsystem to check the range of attributes for all relations to the subsystem to be checked (S502), and from the subsystem. In order to wait for the signal reception of the signal enters the standby state (S503). If a timeout signal is received in the middle of step S503 (S504), the number of repetitions is checked and the number of repetitions is compared with the limit value (S505). If the number of repetitions is greater than the limit value, an error is output (S506) and the process is returned to the upper process ( S515).

If the number of repetitions is not greater than the limit in step S505, the DB range check request signal is retransmitted (S507), and the signal wait state (S503) is returned. When an acknowledgment (ACK) signal is received in step S503 (S508), it is normal, so the timer ends (S509) and enters a signal waiting state in order to receive a test result (S510). When the timeout signal is received in step S510 (S511), an error message is output (S512), and the process returns to a higher process (S515). On the other hand, when the test execution result is received from the corresponding subsystem in the signal waiting state (S510) (S513), and outputs the test execution result (S514) and returns (S515).

FIG. 6 is a flowchart illustrating a DB range checking procedure operated by the DB range checking request signal of FIGS. 3 and 5. This check procedure is a check procedure of an ADDBF block that checks the relation in each subsystem. When the DB range check procedure is started (S601), the ADDBF block retrieves DB check function information of the corresponding subsystem (S602) and checks the relation parameters (S603). If the result of the check is ALL, the first relation is selected (S604) and the selected relation is the last (S605). If not, the relation check procedure is called (S606), and the next relation is selected (S607). In step S605, if the relation selected in S605 is the last relation, the process returns to a higher process (S609). If it is not ALL (ELSE) in step 603, the relation check procedure is called (S608), the relation check is performed and returned to the higher process (S609).

FIG. 7 is an operation flowchart illustrating the relation checking procedure shown in FIG. 6. This check procedure is a check procedure of an ADDBF block that checks each relation. First, when the relation checking procedure is started (S701), the relation exists and is examined (S702). If the relation does not exist, it is returned to the upper process immediately (S717), and if there is an attribute parameter to check whether the relation is examined. Check (S703).

If the entire attribute is examined (ALL), the number of attributes is counted (S704) and the names of the attributes are taken one by one (S705), and the boundary of the attributes is obtained (S706). In addition, an attribute range checking procedure as shown in FIG. 8 is performed (S707) to determine whether an error has occurred (S708). If an error occurs in step S708, the corresponding attribute value is output (S709) and the wrong value where the error occurs is erased (S710). However, if no error occurred in step S708, the process proceeds to the next attribute. The above step S705 to step S710 performs a check on the range of all the attributes of the number of fingered in step S704.

In step S703, if the attribute is not all but a specific attribute (ELSE), the name of the attribute is taken (S711), the boundary is taken (S712), and the attribute range checking procedure as shown in FIG. It performs (S713). At this time, if an error occurs (S714), the value of the attribute is output (S715), the error value is cleared (S716), and then returned to the upper process (S717), and if an error does not occur, it simply goes to the upper process. It returns (S717).

8 is an attribute range checking procedure diagram shown in FIG. 7, which is an inspection procedure of an ADDBF block that checks a range of attributes constituting a relation. When the attribute range checking procedure is started (S801), a buffer for storing the index and the value of the tuple (Tuple) in which the range error occurs (S802), and checks whether the attribute search method is the index type (S803) If it is not the index type, since the memory is not allocated inside the actual PLD, the process is returned to the higher process (S812). If the index type is the index type, the first tuple pointer for the attribute is taken to perform a range check (S804).

At this time, it is checked whether the corresponding tuple is the last tuple (S805), and if it is not the last tuple, it is checked whether the tuple is a valid tuple (S806). If it is a valid tuple, a range checking procedure of the value of the corresponding attribute is performed (S807), and the result value is again checked if it exceeds the range (S808). If the value exceeds the range, the index and attribute values of the tuple are taken (S809), and the index and the value of the tuple over the range are stored in the buffer (S810). Then, the next tuple pointer for the attribute is obtained (S811), and the flow proceeds to step S805.

If the tuple is the last tuple in step S805 (S812), and if it is not a valid tuple in step S806, or if the value does not exceed the range in step S808, the process proceeds to step S811 to obtain the next tuple pointer for the attribute. Step 805 is repeated.

FIG. 9 is a diagram illustrating an attribute range checking procedure of FIG. 8. This inspection procedure is an inspection procedure of an ADDBF block that checks whether a range is exceeded by searching for an actual value stored in a PLD for each attribute type.

When the attribute range checking procedure is started (S901), the attribute type is checked (S901). If the type is a character, string, or bit type, the range is returned immediately without checking the range (S911). If not, the size of the attribute type is checked again (S903). If the attribute type is a byte type, the value for one byte is searched (S904), the range of the attribute is searched (S905), and whether the range is normal (S910). ), If abnormal, excess return (S912). If the attribute type is word type, the value of 2 bytes is searched (S906) to search the range of the attribute (S907), and if the range is normal (S910), if it is normal, the normal return (S911) is performed. If abnormal, excess return (S912). If the attribute type is a long type, a value of 4 bytes is searched (S908), and a range of the attribute is searched (S909), and if the range is normal (S910), if it is normal, a normal return (S911) is performed. If abnormal, excess return (S912).

While the invention has been described above based on the preferred embodiments thereof, these embodiments are intended to illustrate rather than limit the invention. It will be apparent to those skilled in the art that various changes, modifications, or adjustments to the above embodiments can be made without departing from the spirit of the invention. Therefore, the protection scope of the present invention will be limited only by the appended claims, and should be construed as including all such changes, modifications or adjustments.

As described above, according to the present invention, DB attribute resolution problem is solved, DB attribute range consistency on demand is verified, and periodic DB attribute range check provides automatic consistency and DB data consistency. This can reduce errors. In addition, it is possible to recover due to the early detection of abnormal attributes, to improve the quality of service by improving the exchange performance due to the reduction of DB errors, and to be applied to other large switching systems.

Claims (13)

In an ATM switch system comprising an ATM central switching subsystem and distributed ATM regional switching subsystems, a distributed maintenance location processor and call connection control processor of the ATM regional switching subsystem are distributed in the distributed ATM regional switching subsystem. In the method of checking the database, Initializing, by the operation maintenance processor, data for DB range checking of the distributed database; When the DB range check command signal for requesting the attribute range check for any subsystem is input from the operator, the operation maintenance processor verifies the input parameters input from the operator and searches the DB check function and the inspection performing subsystem. ; And And performing, by the operation maintenance processor, a sub-system inspection procedure for all the search-performing subsystems retrieved. The method of claim 1, wherein performing the subsystem inspection procedure comprises: If the retrieved check performing subsystem is an entire subsystem, perform the subsystem checking procedure on a subsystem in which the call connection control processor state is normal among all the subsystems, If the search inspection subsystem is not the whole, check the call connection control processor state of the inspection performing subsystem, and if the call connection control processor state is normal, the memory resident distributed database Method of data inspection. The method of claim 1 or 2, wherein the subsystem inspection procedure, Sending, by the operation maintenance processor, a DB range check request signal to check the range of all attributes for all relations to the inspection target subsystem; Waiting, by the operation maintenance processor, for a response signal from the inspection target subsystem which has transmitted the DB range inspection request signal; Waiting for a test result from the test target subsystem when the response signal is normally received by the operation maintenance processor; And And outputting and returning the test execution result when the test operation result signal is received from the test target subsystem by the operation maintenance processor. The method of claim 3, wherein If the normal operation signal is not received within a predetermined time after the DB range check request signal is transmitted, the operation maintenance processor waits for a response signal after retransmitting the DB range check request signal, and if the number of retransmissions exceeds the limit, an error. A data checking method of a memory resident distributed database further comprising the step of outputting a message and returning the message. The method of claim 3, wherein And in response to the operation maintenance processor outputting an error message and returning an error message if a test execution result signal is not received within a predetermined time after the response signal is normally received. The method of claim 3, wherein The call connection control processor of the subsystem to be inspected receiving the DB range test request signal performs a DB range test procedure for each relation and transfers the result of the test to the operation maintenance processor. Data inspection method of resident distributed database. The method of claim 6, wherein the DB range inspection procedure, Wherein the call connection control processor retrieves DB inspection function information of the corresponding subsystem, selects a relation to be inspected, and performs a relation inspection procedure on the relation to be inspected. The method of claim 1, If a DB range check request signal is input from the operator for requesting attribute range check for the subsystem in which the operation maintenance processor is located, select a relation to be inspected and check relation to the selected relation to be inspected. A data inspection method of a memory resident distributed database, characterized in that to perform a procedure. The method of claim 7 or 8, wherein the relation inspection procedure is Selecting an attribute to be inspected by checking an attribute parameter of the relation to be inspected; Performing a corresponding attribute range checking procedure using the name and boundary of the attribute to be inspected; And And outputting an error attribute value if an error occurs as a result of performing the inspection, and then deleting and returning the error generated value. The method of claim 9, wherein the attribute range checking procedure comprises: Creating a buffer for storing an index and an attribute value of a tuple having a range error; If a method of searching the attribute is an index, performing a procedure of checking a range of the attribute with respect to a valid tuple of all tuples for the attribute; And And checking and storing the tuple's index and attribute values in the buffer if the range of the attribute is exceeded. The method of claim 10, wherein the attribute range checking procedure comprises: Sensing the type of the attribute; Returning if the attribute type is character, string, bit size; and If the attribute type is byte size, the value of 1 byte is searched for the range of the corresponding attribute. If the word size is the value of 2 bytes, the value is searched for the range of the attribute. A method for examining data in a memory-resident distributed database, comprising: searching a value to retrieve a range of a corresponding attribute. In an operation maintenance processor of an ATM switch system including an ATM central switching subsystem and distributed ATM regional switching subsystems, Initializing, by the operation maintenance processor, data for DB range checking of the distributed database; When the DB range check command signal for requesting the attribute range check for any subsystem is input from the operator, the operation maintenance processor verifies the input parameters input from the operator and searches the DB check function and the inspection performing subsystem. ; And A computer-readable recording medium having recorded thereon a program which causes the operation maintenance processor to perform a step of performing a subsystem inspection procedure for all of the searched subsystems. HMI for graphic and command interfacing with the operator, OMP processor that receives operator commands from the HMI, performs control and management functions, and manages all the devices in the system, and communicates with the OMP processor. Includes a plurality of CCCP processors controlling the connected subscribers and their calls; The OMP processor and CCCP processor, respectively, PLD storing DB initialization data; An ADDBF block that finds a desired relation from the PLD and reads attribute data to perform the attribute range check; A relation interface under control of the ADDBF block to find a relation in the PLD and provide the relation to the ADDBF block; And And a data extraction interface for reading the attribute data from the PLD under the control of the ADDBF block, checking the range thereof, and providing the ADDBF block to the ADDBF block.