KR100305912B1 - Object-Oriented Program Interface for Relational Devices - Google Patents

Abstract

The present invention relates to an Object Oriented Program Language Interface (Object Oriented Program Language Interface) for a relational database management system (DBMS), and more particularly, to a relational DBMS that enables the relational DBMS to be used in an object-oriented programming language (OOPL) environment. An object oriented program interface.

The present invention provides a database tuple that provides a template capable of displaying table characteristics of all databases in a relational DBMS; A shape conversion preservation detection unit for changing the attribute form of the tuple of the relational DBMS into an object-oriented concept and preserving side effects according to the shape change without considering the SSP module application; Represent each relationship on the relational DBMS to provide the SSP module application with the functions of selecting, inserting, deleting, and updating the respective relations, and modifying the changes made in the middle layer at the request of the SSP module application. It is characterized by including the database manager to update the DBMS.

Description

Object-Oriented Program Interface for Relational DMS

The present invention relates to an Object Oriented Program Language Interface for a relational DBMS, and in particular, to allow the relational DBMS to be used even in an Object Oriented Program Language (OOPL) environment. An object-oriented program interface for a relational DBMS.

In general, a database performs insertion, deletion, and update of new data to keep it as the latest accurate data, and allows data to be shared by different users having different purposes. You can also access data by content without having to know the physical address or location within that database. The database is managed by a software system called DBMS.

The DBMS is a mediator of applications and data. It is a software system that collects and manages data used by multiple applications in one place so that all applications can share data. A comprehensive data management system that retrieves or modifies and always provides consistent results to applications.

In the DBMS, there are relational model, network model, and hierarchic model. Among them, the relational DBMS developed and widely used to date is a data item or a data item. It is expressed as a table consisting of tuples that have the same concept as an attribute and record representing a field. The table is called a relation, and the relationship between data and data Consists of relationships.

Relational features in the relational DBMS can not be duplicated tuples can be listed in any order, attributes can be listed in any order, and one attribute value can have only one value.

On the other hand, the use of OOPL with an object-oriented concept is increasing. The OOP is a program technique for solving various problems by using a computer in a natural form by modeling a phenomenon of the real world as an object on a computer. Here, the object includes both an entity (eg, data) and operations (eg, procedures, methods, and functions) related to the entity.

For example, when looking at the ticket release at the train station, the entity 'guest' and the procedure 'ordering tickets' are one object, and the entity 'staff officer' and the procedure 'release ticket' are also one object. In order to handle a task, a message is exchanged between objects, and the object receiving the message executes an action.

As mentioned above, the OOP defines entities and actions as objects and performs information processing with a focus on the exchange of messages between them, that is, object-oriented is not a procedure-oriented design, but a design that focuses on entities (eg data). to be. In addition, as another feature of the OOP, an object having a common property is defined as an object class, and objects belonging to the same class perform similar operations on the received message. The OOP is also written in an object-oriented language such as Smalltalk.

As such, as the use of the OOP written in the OOPL increases, when a new function is implemented using the OOPL in a system developed using the relational DBMS, the interface supported by the relational DBMS has the OOPL. Since it cannot support concepts such as abstract data types and code reuse, it is not possible to take advantage of the general advantages of the OOPL and is constrained to make new functions traditional.

In order to solve the problems described above, the present invention provides a relational DBMS for an application using OOPL by using an effective wrapping technique for the relational DBMS while utilizing the characteristics of OOPL. Its purpose is to provide an object-oriented program interface.

1 is a block diagram illustrating a switch associated with an object oriented program interface for a relational DRAM according to an embodiment of the present invention.

2 is a diagram illustrating an object-oriented program interface model for a relational DBMS according to an embodiment of the present invention.

3 is an exemplary view showing a database relationship in FIG.

4 is a diagram illustrating a DBMS layer of AIP in FIG. 1; FIG.

Explanation of symbols on the main parts of the drawings

10: OMS (Operation & Maintenance Subsystem)

20: AIP (Advanced Intelligent Processor)

21: Unix Database Engine (UDBE)

22: relational database management system library

23: Service Switching Point Module Application Program

24: Database Manager

25: Database Tuple

26: Type Conversion Integrity Check

The present invention provides a middle layer between a relational DBMS and an application using OOPL to provide an OOPL interface to a relational DBMS for all applications. That is, the present invention maintains the data of the relational DBMS in the form of data that can be used by the OOPL application in the middle layer. In the middle layer, the application updates the relational DBMS with the change of the data maintained in the middle layer. By providing the ability to update, applications that use OOPL can maintain object-oriented advantages while using relational DBMSs.

In addition, the object-oriented program interface for a relational DBMS according to an embodiment of the present invention is called a DBMS interface service package among a plurality of service packages (program configuration units) constituting a service switching point (SSP), and the corresponding DBMS interface service package. Provides an interface between the SSP module, an object-oriented application, and the distributed relational database of the Mobile Switching Center (MSC) exchange. Hereinafter, an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram showing a switch associated with an object-oriented program interface for a relational DBMS according to an embodiment of the present invention, Figure 2 is a view for explaining the DBMS interface service package analysis model of the present invention, Figure 3 FIG. 2 is an exemplary diagram illustrating trigger processing performed at an SSP of AIN, and FIG. 4 is a diagram illustrating a DBMS layer of AIP in FIG. 1.

As shown in FIG. 1, the switch associated with the DBMS operation of the present invention is a sub-system in charge of the operation and maintenance of the switch. The switch is redundantly present in each processor together with a local database. It includes an OMS 10 that is in charge of integrated management of Replication Type (Data) data, and an AIP 20, which is a processor that performs an AIN (Ddvanced Intelligent Network) function (SSP) of an exchange. In addition, the AIP 20 is an object-oriented program interface that performs an interface role so that the SSP module application program 23, the relational DBMS, and the SSP module application 23 created by the OOPL technique can use the relational DBMS. Is done.

The present invention provides a middle layer between a relational DBMS and an application using OOPL to provide an OOPL interface to a relational DBMS for all applications. That is, the present invention maintains the data of the relational DBMS in the form of data that can be used by the OOPL application in the middle layer. In the middle layer, the application updates the relational DBMS with the change of the data maintained in the middle layer. By providing the ability to update, applications using OOPL can maintain the object-oriented benefits while using a relational DBMS.

In addition, the object-oriented program interface for a relational DBMS according to an embodiment of the present invention is called a DBMS interface service package among a plurality of service packages (program configuration units) constituting a service switching point (SSP), and the corresponding DBMS interface service package. Provides an interface between the SSP module, an object-oriented application and a distributed relational database of the Mobile Switching Center (MSC) exchange. Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram showing an exchange associated with an object-oriented program interface for a relational DBMS according to an embodiment of the present invention, Figure 2 is an analysis model of an object-oriented program interface for a relational DBMS in accordance with an embodiment of the present invention 3 is an exemplary diagram illustrating a database relationship in FIG. 2, and FIG. 4 is a diagram illustrating a DBMS layer of AIP in FIG. 1.

As shown in FIG. 1, the switch associated with the DBMS operation of the present invention is a sub-system in charge of the operation and maintenance of the switch. The switch is redundantly present in each processor together with a local database. It includes an OMS (10) that is in charge of the integrated management of Replication Type (Data) data and an AIP (20) that is a processor that performs the Advanced Intelligent Network (AIN) function (SSP) of the exchange. In addition, the AIP 20 is an object-oriented program interface that serves as an interface for allowing the SSP module application program 23, the relational DBMS, and the SSP module application 23, which are written by the OOPL technique, to use the relational DBMS. Is done.

The SSP module application program 23 is an application program for performing SSP functions using a database tuple 25 realized in an object-oriented program interface of a middle layer, and is provided by the database manager 24 in the object-oriented program interface. The operation updates its database relational data, i.e. by simply inheriting the corresponding database tuple 25, it is provided with an object-oriented program interface of the specific relation that it needs.

The relational DBMS receives a request of an application program in the OMS 10 to retrieve a database and to control access to the database, and a relational DBMS library 22 that interfaces with the UDBE 21. ) Here, the database is a local database that exists locally on each processor together with the UDBE 21 for controlling access to the database.

The object-oriented program interface may include a database manager 24, a database tuple 25, and a shape conversion integrity detection unit 26 to display tables (ie, relations) of databases in the relational DBMS. The module manager 23 maintains data in the form of the database tuple 25 by a function provided by the database manager 24 in a memory space of the application program so that the module application 23 can directly use it.

Here, the database manager 24 expresses each relationship on the relational DBMS to provide the SSP module application 23 with selection, insertion, deletion, and update functions for the respective relations. At the request of (23), the relational DBMS library 22 in the relational DBMS is used to update the relational DBMS to the relational DBMS, that is, at the request of the SSP module application 23, the relational DBMS is updated. The relational DBMS is accessed using the relational DBMS library 22 and object-oriented so that the SSP module application 23 directly uses data (ie, tuple contents of relations) of the database in the accessed relational DBMS. It converts into a tuple object of concept type and converts the changed tuple object into table (ie relation) unit. It is loaded into the memory area of the SSP module application program 23 so that the table of the relational database can be used as the data area of the SSP module application program 23. In this case, the selected function is searched for a tuple object that meets a specific criterion, and the result of the query is returned. The specific criterion indicates that the connection of two relations is required. Insert into the relationship based on the SSP module application 23, the delete function deletes the tuple in the relationship that meets the specific criteria, the update function updates the specific properties of the tuples in the relationship that meets the specific criteria .

Specifically, in order to interoperate with the relational database, the database manager 24 uses the relational DBMS library 22 in the relational DBMS to display the contents of data stored in the database in the relational DBMS. 23 is changed into a tuple object that can be recognized as a data type and loaded into the memory area of the SSP module application program 23, and the data loaded into the memory area of the SSP module application program 23 is stored in the SSP module. If changes are made during the operation of the application 23, the changes are stored again in the database in the relational DBMS, and the data loaded in the memory area of the SSP module application 23 and the data stored in the database in the relational DBMS. Check for inconsistencies in the To give notice to the operator. In addition, although the configuration of the database manager 24 is not shown for convenience of description, a relational storage database in a list format for storing the relations loaded by the database manager 24 from a database in the relational DBMS in units of database tuples; In order to perform the functions (loading, storing and checking) provided by the database manager 24, the relational database operation processing unit performing the necessary functions through the relational DBMS library 22 in the relational DBMS, and a multi-thread technique. It includes a synchronization processing unit that provides a sequential database access to the operating SSP application 23.

The database tuple 25 provides a template, that is, a base class, that can display table (ie, relational) characteristics of all databases in the relational DBMS. The relational DBMS provides a tuple object of an object-oriented type which is read by the database manager 24 from the relational DBMS, and copied into the memory area of the SSP module application 23.

The SSP module application program 23 does not consider the side effects of the shape change while changing the attribute form of the tuple of the relational DBMS to the object-oriented concept. We preserve so that we can use without.

Then, the operation of the object-oriented program interface configured as described above will be briefly described.

First, in the initialization process, each SSP module application program 23 loads a relation required by the database manager 24 from a relational DBMS and stores it as a tuple object of a required format.

Thus, the data stored for use in the SSP module application 23 of OOPL can be used directly in various forms during the execution of the application, and the contents updated in the tuple object in the application is the database manager (24). Using the facilities provided by), the changed contents are reflected in the relational DBMS.

At this time, the database tuple 25 that provides the tuple object has the form of data inherited from one or more attributes. This attribute provides a basic rule that represents the attributes of all relationships, that is, it provides a basic object-oriented interface for each attribute of a relationship that is converted to a database tuple. In addition, the provided interface allocates or reads the actual data for each attribute object, examines the range and size of the data held by the attribute, and the alignment of the database in the relational DBMS is determined by the SSP module application ( If it is not the same as that of 23), the size of the alignment that matches the SSP module application 23 is calculated.

Meanwhile, a schematic configuration of how a DBMS interface service package, that is, an object-oriented program interface for a relational DBMS according to an embodiment of the present invention, is related to the rest of the SSP module may be represented as shown in FIG. 2. 2 illustrates an analysis model of an object-oriented program interface for a relational DBMS according to an embodiment of the present invention.

First, each relationship in a database is held by a database manager object, which encapsulates the mechanism for updating or accessing a database in a relational DBMS. In addition, there are classes of objects that correspond to individual tuples of relationships, and the actual objects in the application hierarchy use tuple classes (that is, database tuple objects) that correspond to application classes.

In addition, the DBMS interface service package is composed of three objects, namely, an application object, a database manager class, and a database tuple class. The application object uses its own operation using the operations of the objects in the object-oriented program interface. Update tuple values and use the object-oriented program interface to insert new tuples into the database based on their tuple values, and the behavior of the actual database is performed within the database manager object using the relevant library functions provided by the relational DBMS. Is summarized.

Firstly, the application object maintains its own data and reconstructs it during system operation, which action creates and updates itself based on tuples from one or more relationships, i.e. The application program object is an application program created using OOPL, and maintains its own data using a relational DBMS access function provided by a database manager class generated according to each relationship.

For example, FIG. 3 shows an example of a trigger processing performed in an ASP's SSP, that is, a database relationship based on a service and a relationship with service control point groups (SCPs). Has a property and that property is stored in a service relationship. The service object is also associated with several SCP groups, which are stored in a separate Service SCP Group Relation. Also, loading a corresponding service object into the application program object is a process of constructing a service object for each tuple in a service relationship.

Secondly, the database manager class is generated for each relationship from the base database manager class and controls the operation in that relationship.

Thirdly, the database tuple class provides an intermediate object between the application object and the database, the attributes of the tuple being in accordance with the tuple of the database. In addition, reading or setting each domain of the corresponding tuple object means shape conversion between the application object and the database as well as the actual reading / setting of the corresponding domain and other integrity checks. This is necessary because it only supports types, that is, integer or character types.

The objects of the database tuple class audit themselves for the relationship, and the check is used when updating data. In addition, the application using OOPL receives a signal indicating that its data has been updated, and based on this, the application object is updated, and after the update, the updated object is examined for the database and the same update is made. We check whether each is applied to the application object and the relational DBMS. At this time, if the check fails, an alarm occurs in the failure management package.

On the other hand, Figure 4 shows a database layer in the AIP using the object-oriented program interface for a relational DBMS according to an embodiment of the present invention, the configuration is the object-oriented program interface 31 and the relational DBMS library 32 ), A plurality of message queues 33-1 to 33-3, a UDBE interface (Unix DBMS Interface; 34), a UDBE 35, a database 36 which is shared memory, and a backup log memory. 37, a database backup unit 38, an AIP hard disk 39, and an IPC server 40. As shown in FIG.

First, an application program accesses a database 36 locally present in AIP during normal operation, and a library function call transmits a database operation to the UDBE 35 in order to transmit a Unix message. Using queues 31-1 and 31-2, the UDBE 35 handles operations in the database 36 residing in shared memory.

In addition, the database backup unit 38 confirms that the update is applied to the database backup, and the backup copy exists on both the AIP and the OMS hard disk.

The database engine 35 also handles operations required by other processors, for which database application protocols are implemented by the UDBE interface 34.

As described above, the relational DBMS can be used in the OOPL environment by allowing the application program using the OOPL to use the relational DBMS while utilizing the characteristics of the OOPL using an effective wrapping technique.

Claims (5)

A database tuple that provides a template that can display table characteristics of all databases in a relational DBMS; A shape conversion preservation detection unit for changing the attribute form of the tuple of the relational DBMS into an object-oriented concept and preserving side effects according to the shape change without considering the SSP module application; Represent each relationship on the relational DBMS to provide the SSP module application with the functions of selecting, inserting, deleting, and updating the respective relations, and modifying the changes made in the middle layer at the request of the SSP module application. An object-oriented program interface for a relational DBMS, comprising a database manager that updates the DBMS. The method of claim 1, The selection function indicates that a tuple object matching a specific criterion is returned and the search result is returned, and the specific criterion indicates that the connection of two relations is required, and the insertion function is a relation based on the SSP module application program. Insert into, wherein the delete function deletes tuples in a relationship that meets the particular criteria, and wherein the update function updates specific attributes of tuples in a relationship that meets the particular criteria. . The method of claim 1, The database manager accesses the relational DBMS using the relational DBMS library in the relational DBMS according to the request of the SSP module application, and makes the SSP module application directly use the data of the database in the accessed relational DBMS. An object-oriented program interface for a relational DBMS, wherein the object is changed into a tuple object having a concept, and the corresponding tuple object is loaded into a memory area of the SSP module application program in a table unit. The method of claim 3, When the data loaded in the memory area of the SSP module application is changed during the operation of the SSP module application, the database manager stores the changes again in a database in the relational DBMS, and the memory of the SSP module application. An object-oriented program interface for a relational DBMS, characterized in that for checking an inconsistency between the data loaded in the region and the data stored in the database in the relational DBMS, an error message is notified to the operator when an abnormal inconsistency occurs. The method of claim 1, The database tuple provides an object-oriented type tuple object which is read by the database manager from the relational DBMS and copied to the memory area of the SSP module application by the database manager during system initialization. An object-oriented program interface for a relational DBMS.