KR20000041891A - Object-oriented program interface for relational dbms - Google Patents

Abstract

PURPOSE: An object-oriented program interface for a relational database management system(DBMS), is provided to use the relational DBMS, while an application program activates characteristics of an object-oriented program language, by use of a wrapping method. CONSTITUTION: An object-oriented program interface for a relational database management system(DBMS), includes an operation & maintenance subsystem(OMS) and an advanced intelligent processor(AIP). The interface comprises a service switching point(SSP) module application program(23), an UNIX database engine(UDBE)(211), a relational DBMS library(22), a database manager(24), a database tuple(25), and a type conversion integrity check(26). The SSP module application program(23) executes a SSP function. The UDBE(211) searches a database according to a request of the SSP module application program(23). The relational DBMS library(22) executes the UDBE and an interface. The database manager(24) accesses the relational DBMS by use of the library(22), according to the request of the SSP application module program(23). The database tuple(25) is a tuple object shifted tuple contents accessed through the relational DBMS, into a type of an object-oriented concept, which is used in the SSP module application program(23). The type conversion integrity check(26) shifts an attribute type into the object-oriented concept type.

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 relationship 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 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 as described above, the present invention uses a relational DBMS using an effective wrapping technique, an application program using the OOPL object-oriented programming language while maintaining the characteristics of the object-oriented programming language, Its purpose is to enable it.

1 is a block diagram illustrating an exchange associated with an object-oriented program interface for a relational DRAM in accordance with an embodiment of the present invention.

2 is a view for explaining a DBMS interface service package analysis model of the present invention.

FIG. 3 is an exemplary diagram showing trigger processing performed at SSP of AIN in FIG. 2; 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 illustrating an exchanger associated with an object-oriented program interface for a relational device according to an embodiment of the present invention, FIG. 2 is a view for explaining a DBMS interface service package analysis model of the present invention, and FIG. FIG. 2 is an exemplary diagram illustrating trigger processing performed in an SSP of an AIN, and FIG. 4 is a diagram illustrating a DBMS layer of an AIP in FIG. 1.

As shown in FIG. 1, the exchange associated with the operation of the DBMS of the present invention has an OMS (Operation & Maintenance Subsystem) 10, which is a sub-system in charge of operation and maintenance of the exchange, and an AIN (Advanced Intelligent Network) function of the exchange. AIP (Advanced Intelligent Processor) 20, which is a processor that performs (SSP), is included.

The AIP 20 receives a request from an application and retrieves a database (Unix Database Engine; UDBE) 21, and a relational DBMS library 22 provided for interfacing with the UDBE 21. And the SSP module application 23 using the database tuple 25 realized in the middle layer as an application program that performs the SSP function, and the relational DBMS library 22 at the request of the corresponding SSP module application 23. Database manager (24) that accesses a relational DBMS using the database, and the tuple contents of relations accessed through the relational DBMS can be directly used by the corresponding SSP module application (23). If you change the attribute type of the tuple object Database Tuple (25) and the tuple of the relational DBMS into an object-oriented concept It is provided with a Type Conversion Integrity Check (26) to enable the Side Effect (Side Effect) according to the shape change without considering the SSP module interface.

Here, the database exists locally on each processor with the UDBE 21 that controls access to the database, and in the OMS 10 in addition to the local database, the database overlaps with each processor. Responsible for the integrated management of replication type data.

In addition, a schematic configuration of how the DBMS interface service package is related to the rest of the SSP module may be represented as shown in FIG. 2 to explain the DBMS interface service package analysis model.

Each relationship present in a database is held by a database manager object 24, which encapsulates the mechanism for updating or accessing a relational database. In addition, there is a class of objects corresponding to individual tuples of the relationship, and the actual object 23 of the application layer uses a tuple class (ie, a database tuple object 25) corresponding to the application class.

As described in FIG. 2, an object-oriented program interface for a relational DBMS according to an embodiment of the present invention includes three objects, namely, an application object 23 in an OOPL application, a database manager class 24 in an intermediate layer, and an object-oriented program interface. It consists of a database duple class 25 in the middle tier.

First, the application object 23 updates its tuple value using the operation of the DBMS interface service package object, ie an operation provided by the database manager 24 in the middle tier as an application using OOPL. To update their database-related data. In addition, the application object 23 inserts a new tuple into the database based on its tuple value using the DBMS interface service package.

The actual database operation is then summarized within the database manager object 24 using the associated library functions provided by the relational DBMS.

In other words, the application object 23 may maintain its data and reconstruct the data during system operation, the operation of which is generated by the application object 23 based on tuples from one or more relationships. And update. That is, the application object 23 is an application program created using OOPL and maintains its own data using the relational DBMS access function provided by the database manager class 24 generated according to each relationship.

For example, as shown in FIG. 3, trigger processing performed in the SSP of the AIN is shown based on a relationship between a service and SCP groups (Service Control Point Groups).

A service object has some attributes and those attributes are stored in service relationships. The service object is also associated with several SCP groups, which are stored in a separate Service SCP Group Relation.

Loading the corresponding service object into the application object 23 is a process of constructing a service object for each tuple in a service relationship.

Secondly, the database manager class 24 is generated for each relationship from the base database manager class and controls the operation in that relationship, that is, as a class, expressing each relationship on the relational DBMS. Select, Insert, Delete, and Update functions are provided to the application object 23 for each relationship. In addition, the relational DBMS library 22 is used to update the changes made in the middle layer to the relational DBMS according to the request of the application object 23.

Here, the selection function may query a tuple object that meets a specific criterion and return a corresponding result, and the criterion may require the connection of two relationships. The pull function inserts a tuple into a relationship based on the application object 23. The delete function deletes tuples in a relationship that meets the specific criteria. The update function updates specific attributes of tuples in a relationship that meets the specific criteria.

Third, the database duple class 25 provides an intermediate object between the application object 23 and the database and the attributes of the tuples follow the tuples of the database, i.e. the database manager upon initialization of system startup. The object 24 reads the relation necessary for the application object 23 from the relational DBMS and provides a duplex object in an object-oriented format copied to the application object memory area.

Reading or setting each domain of the corresponding tuple object means shape conversion between the application object 23 and the database as well as the actual reading / setting of the corresponding domain and other integrity checks. This type conversion is necessary because the database supports only fixed types, that is, integer or character types.

The objects of the tuple class 25 audit themselves for the relationship, and the audit is used when updating data. The application program using OOPL receives a signal indicating that its data has been updated, and updates the application object 23 based on this. After the update, the updated object is audited against the database to confirm that the same update has been applied to the application object 23 and the relational DBMS, respectively. If the audit fails, an alert will be issued to the failure management package. .

4 shows a database layer in an AIP in which a DBMS service package is used, the configuration of which is a DBMS interface service package 31, a relational DBMS library 32, and a number of message queues 33-1 to 33-3. And a UDBE interface (Unix DBMS Interface) 34, a database engine 35, a shared memory database 36 and a backup log 37, a database backup 38, And an AIP hard disk 39 and an IPC server 40.

In normal operation in the DBMS layer of the AIP, the application object accesses the database that exists locally in the AIP. The library function call uses the Unix message queue 31-1 to communicate database operations to the database engine 35, which in turn has a database 36 in shared memory. Handles the operation in.

Then, the database backup 38 confirms that the update is applied to the database backup, and the backup copy exists on both the AIP and OMS hard disks.

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

Briefly describing the operation of the object-oriented program interface for the relational DBMS of the present invention, each application object loads the necessary relationship from the relational DMBS from the database manager during initialization and stores it as a duple object in the required format. Data stored for use in OOPL can be used directly in various formats during application execution. In addition, the updated contents of the tuple object in the application program are reflected in the relational DBMS using the facilities provided by the database manager.

As described above, the relational DBMS is used in the OOPL environment by allowing an application program using an OOPL object-oriented programming language to use a relational DBMS while utilizing the characteristics of the object-oriented programming language. It also makes it available.

Claims (6)

An OMS in charge of operation and maintenance of the exchange; An object-oriented program interface for a relational DBMS, comprising an AIP that performs an exchange AIN function. The method of claim 1, The AIP is an SSP module application program that performs an SSP function; A UDBE for searching a database according to a request of the SSP module application program; A relational DBMS library that interfaces with the UDBE; A database manager for accessing a relational DBMS using the relational DBMS library at the request of the SSP module application program; A database tuple which is a tuple object changed from a tuple content of a relation accessed through the relational DBMS into an object-oriented concept used in the SSP module application program; An object-oriented program interface for a relational DBMS, characterized in that it comprises a shape conversion integrity detection unit for changing the attribute form of the tuple of the relational DBMS to the object-oriented concept. An application object that updates its tuple value using an operation of the DBMS interface service package object and inserts a new tuple into the database based on its own tuple value using the DBMS interface service package; Represent each relationship on the relational DBMS and provide the application object with the functions of selecting, inserting, deleting, and updating the relation, and using the relational DBMS library to change the middle layer according to the request of the application object. A database manager class for updating the DBMS; And a database duple class for providing a duplex object of an object-oriented type that is an intermediate object between the application object and the database. The method of claim 3, Operation of the database is summarized within the database manager object using the associated library functions provided by the relational DBMS. The method of claim 3, The selection function retrieves a tuple object meeting a specific criterion and returns a corresponding result, and the criterion requires the connection of two relationships, and the retrieval function inserts one tuple into a relationship based on the application object 23. Wherein the delete function deletes tuples in a relationship meeting the specific criteria, and the update function updates specific attributes of tuples in a relationship matching the specific criteria. . The method of claim 3, Reading or setting each domain of the tuple object represents the type conversion between the application object and the database, as well as the actual read / set of that domain and other integrity checks, and objects of the database tuple class self audit the relationship and Auditing is an object-oriented program interface for a relational DBMS, characterized in that for updating data.