KR100624978B1 - System for verifing of changed database of Electronic Switching Systems - Google Patents

Abstract

The present invention relates to an apparatus for verifying a changed database of an electronic exchange. Since data used in an electronic exchange is a very important part in terms of stable operation of a corresponding system and provision of subscriber services, data change work by an operator requires careful attention. Verification is also important. However, the program verifying this hassle of modifying the program source accordingly whenever the relation of the electronic exchange database changes. Therefore, the present invention is to find the difference between the existing structure and the newly changed structure based on the catalog (catalog: list) file having the database information or the change of the electronic exchange database, the new database based on the contents By accessing the data of the exchanger, it is possible to manage and verify the changed e-Exchange database with the same program source all the time, eliminating the need to modify the verification program whenever the E-Exchange database changes. Since any version can perform verification and management work, it can be used for other database verification and management work of TDX series where data verification and management program is not developed yet.

Description

System for verifing of changed database of Electronic Switching Systems}

1 is an overall configuration diagram of the present invention, a PLD (Processor Loading Data), that is, a DBMS for extracting and modifying data from an electronic exchange database, a PLD, and providing data and PLD change information to an application, and verifying the data according to the purpose. And an application to be managed and an MMI (man machine interface) to provide an interface with an operator to operate each application.

2 is a diagram illustrating an interworking procedure for exchanging data through a message flow between an MMI, an Application, and a DBMS according to the present invention;

Figure 3 is a flow chart of a program for extracting data and database information to be delivered to the upper application in the DBMS according to the present invention.

Figure 4 is a flow chart for extracting the data required from the data and database information transmitted from the DBMS when performing the verification and management of the database in the Application according to the present invention.

The present invention relates to an apparatus for verifying a changed database of an electronic exchange, and more particularly, to an existing structure and a newly changed structure based on a catalog file having database information in a DBMS or information in a database. This paper relates to a device that can manage and verify the changed electronic exchange database with the same verification / management program source by accessing the data of the new database based on this information.

In recent years, the quantum leap in communication technology has complicated and diversified the functions and data volume of the existing electronic exchange. As a result, new functions of the electronic exchange are frequently added and data is frequently changed, so the area and importance of the program for verifying / managing the integrity of the newly changed electronic exchange database are also important.

However, the structure of the existing database verification and management program has a disadvantage in that the program source is modified every time according to the change of the relation of the database. In other words, when a domain of a database (Domain = Attribute) is added, existing data is changed in order of domain because of newly added data, and thus, existing programs that always search for data in the same location cannot find desired data. In fact, more than half of the 1998 maintenance and maintenance programs were program modifications to handle altered databases.

As a result, the time allotted for program maintenance is increased, and it is difficult to provide new services in a timely manner because it is necessary to wait for the verification and management program to be modified to apply a new database.

Accordingly, the present invention has been made to solve the conventional problems, such as the mall, and even if the change in the electronic exchange database, it is possible to perform the program-specific functions without modification of the verification and management program, effectively the stable and The purpose is to provide a modified database verification method for an electronic exchange that can support continuous exchange service provision.

In order to achieve the above object, the present invention separates the DBMS that can access the electronic exchange database from the application that verifies and manages the actual data, restricts data access only in the DBMS, and clearly defines the configuration information of the database in the DBMS. Based on the catalog file or the data defined in the database, the data required by the application, the first step of delivering the change history, and the application extracts the desired data by referring to the change history received from the DBMS. Perform with two steps.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

1 is an overall configuration diagram applied to the present invention, which is a PLD (Processor Loading Data: 10) in a backed up state, that is, a database to be loaded into a processor of an electronic exchange, data backed up from the electronic exchange to a data management system, and a DBMS. 11 extracts data requested from an application to be described later from the PLD 10 and generates a file for transferring the changed database information to the application 12.

The application program 12 serves to verify and manage actual data using data from the DBMS 11 and change information. Man Machine Interface (MMI) 13 provides an interface between the operator 14 and various applications 12.

The present invention focuses on the correlation between the DBMS 11 and the application 12 to achieve the object of the present invention rather than the data verification method of the MMI 13 and the application 12.

2 is another overall configuration diagram of the present invention, and illustrates an interworking procedure of exchanging data through a message flow between an MMI, an application, and a DBMS.

In the step S20 shows the process of receiving the application selection by operation type (operation type selection by the verification method) according to the operator's request, and the information (Processor name, Relation name, Domain name, tuple number) for obtaining data from the database, In the step S21, it shows a process of delivering the information entered above from the MMI to the Application.

In step S22, G_CAT (information linking a relation name and a relation number), which is a catalog file, and R_A_CAT (information linking a domain (Attribute) name belonging to a relation and a domain number so that the DBMS can recognize the information input from the MMI. It is the process of conversion by using.

In step S23, a process of transmitting the transformed information and job type to the DBMS is shown. Step S24 is a process of extracting the requested data from the PLD. In step S25, the database stores information (relation name, relation number, domain name, domain number, domain range, number of tuples) as a file in order to deliver the extracted data and changes of the database to the application, and responds to the application. (Ack) Indicates the delivery of a message together.

In step S26, the application finds the location of the desired data by using the database information delivered from the DBMS. Even if the database is changed (addition or deletion of a domain), the changed details are found from the database information delivered from the DBMS, and the data is exactly the desired data. You will find.

Step S27 is a process of requesting to the MMI to show the processed data to the operator. Step S28 is a process of showing the operator the results of the operation requested by the operator.

FIG. 3 is a flowchart illustrating a program for extracting data and database information to be transferred from a DBMS to a higher application, corresponding to step S25 of FIG. 2.

First, when the electronic exchange database is produced, shape information about it is generated as a catalog file. Since this catalog exists for each database version, DBMS and Application refer to this catalog file, no matter how complicated the database changes. You can find exactly what you want in relation to the relation and domain.

S300 enters a catalog for a database version. G_CAT has all relation names, relation numbers, relation location, tuple number, and domain number. In addition, R_A_CAT has all domain names and domain numbers belonging to each relation.

S301 processes an error when the DBMS receives a request that the DBMS cannot process. If an error occurs, the error is transmitted to the application, and the application outputs the corresponding error.

When the DBMS receives a request that can be processed, the domain information of the desired relation is found as R_A_CAT in the request, and the desired domain is searched by searching the relation number and the domain number as a key (S302).

If the desired information is found, the information is stored as a file for transferring to the application (S303). In this file, the relation number, domain name, domain number, and data range of the domain are stored so that the application can find the corresponding domain by identifying the location according to the domain number in Rel_dat.msg.

After processing the domain information, the relation information is found in the G_CAT (S304). The relation information is found using the relation number as the key in the same manner as the domain. If the desired relation information is found, the information is stored as a file for transferring to the application (S305). This file stores the relation number, relation name, total tuple number, domain number, and relation location to match the relation number to the relation name in the application.

Since database information file has information that is appropriate for the database such as unique relation number and domain number for each version, Application has this information and extracts data from Rel_dat.msg, so it extracts accurate data regardless of relation variation. Done.

In other words, after processing the database information from step S302 to S305, and finally extracts the data used in the actual exchange, this method uses the existing method as it is, and the extracted data is stored in tuple units and delivered to the application It is to be used for data verification and management (S306).

FIG. 4 corresponds to step S26 of FIG. 2 as a flowchart of extracting data necessary for performing verification and management of a database from an application from data transmitted from a DBMS and database information.

First, if an error is transmitted from the DBMS in step S400, an error message corresponding to the error message is output.

Since the exchange data (Rel_dat.msg) received from the DBMS has all the data of the relation, it is necessary to determine the location of the desired data in Rel_dat.msg in order to obtain specific domain data of a specific tuple required by the Applicaton.

In step S401, in order to obtain the location of the data and other data required by the application, information is received from Rel_inf.msg and Att_inf.msg received from the DBMS. In particular, the location of the desired domain can be known by the domain number. If a change occurs in the database and the domain number is changed, the existing verification and management program uses a fixed domain number and cannot obtain accurate data. However, since the changed domain number is inputted from the catalog (Att_inf.msg) and data is extracted from Rel_dat.msg in the corresponding domain number order (S402), accurate data can be extracted from the changed database.

In addition, Rel_inf.msg and Att_inf.msg contain information defining the characteristics of each domain, so that various verification tools that were difficult to implement in previous programs can be easily implemented.

According to the present invention, it is possible to verify the program without modifying the existing verification and management program, which was able to verify the changed e-Exchange database only by modifying the program, thereby significantly reducing the number and time of maintenance of the exchange database verification and management program. To provide new exchange services.

In addition, the application of the present invention makes it easy to implement many verification tools, including data range checking, which could not be performed in the past, thereby increasing the effectiveness of integrity verification of newly created databases when changing the software version of the exchange system. It became. In addition, any version of the database can be used to verify and manage any version, so it can be used for other data verification and management programs in the TDX series that have not yet been developed. Can be.

In addition, preferred embodiments of the present invention are disclosed for the purpose of illustration, those skilled in the art will be able to make various modifications, changes, additions, etc. within the spirit and scope of the present invention, such modifications and modifications belong to the following claims Should be seen.

Claims (8)

DBMS which monopolizes the access right to the database, extracts the database information and the requested exchanger data to inform the change history of the database when the data request message is received and transmits it as a reply message to the data request message. Database Management System); And At least one application unit generating the data request message and transmitting the data request message to the DBMS and finding the subject data to be verified in the switch data based on the database information when receiving the database information and the exchange data from the DBMS. Modified database verification apparatus of the electronic exchange. The method of claim 1, And an MMI (Man Machine Interface) for providing an interface between an operator and the applications. The method of claim 2, wherein the MMI is And receiving information for obtaining application selection information and data for each job type from the operator, and transmitting the received information to the selected application. The method of claim 3, wherein the MMI is And a processor name, a relation name, a domain name, and a tuple number as information for obtaining the data. The method of claim 3, wherein the MMI is And converting the DBMS so that the DBMS can recognize the information using the information linking the relation name and the relation number and the information linking the domain name and the domain number belonging to the relation. Changed Database Verifier. The method of claim 1, wherein the DBMS is And the relation information and domain information of the relation are found as the database information and stored in a file for transmission in the reply message. The method of claim 6, wherein the DBMS is And the domain information of the relation is found using a relation number and a domain number as a key, and the relation information is found using the relation number as a key. The method of claim 7, wherein the application is And the verification target data is found in the switch data using the relation information and the domain information.

Images