WO2024121893A1

WO2024121893A1 - Database management device, database management method, and database management program

Info

Publication number: WO2024121893A1
Application number: PCT/JP2022/044699
Authority: WO
Inventors: 康郎片岡
Original assignee: 日本電信電話株式会社
Priority date: 2022-12-05
Filing date: 2022-12-05
Publication date: 2024-06-13

Abstract

An acquisition unit (15a) acquires data. A separation unit (15b) separates the respective RDB and graph DB regions of a storage unit 14 into a reference system region that allows data to be referenced and an update system region that permits data to be updated. A classification unit (15c) classifies data that is represented by nodes and by a relationship between the nodes, among items of acquired data, into either one of a graph DB reference system (14c) region or a graph DB update system (14d) region, which are separated from one another, within the graph DB region in accordance with attributes of the data, and then stores the classified data in the regions. The classification unit (15c) also classifies data other than that represented by the nodes and the relationship between the nodes, among the items of acquired data, into either one of a RDB reference system (14a) region and a RDB update system (14b) region, which are separated from one another, within the RDB region in accordance with attributes of the data, and then stores the classified data in the regions.

Description

Database management device, database management method and database management program

The present invention relates to a database management device, a database management method, and a database management program.

In the development of information systems, it is necessary to be able to quickly reference databases using applications and to respond to data tampering. In recent years, therefore, in addition to conventional relational databases (RDBs), graph databases (graph DBs), which are capable of outputting and displaying the interconnections between data at higher speeds, have been attracting attention as a data reference source. However, since graph DBs are specialized for displaying graphics and cannot replace RDBs, which are capable of processing functions, statistical processing, and outputting reports, technology has been proposed that uses RDBs and graph DBs side by side (see Patent Document 1 and Non-Patent Document 1).

JP 2014-229276 A

However, with conventional technology, in an integrated environment of an RDB and a graph DB, the schema becomes complicated, which becomes an obstacle to application development. For example, when an RDB and a graph DB are simply placed side by side, the placement of database data becomes chaotic and not necessarily organized in terms of whether the data attributes are reference-only or can be updated. This causes the schema to become complicated, which becomes an obstacle to application development.

The present invention has been made in consideration of the above, and aims to enable the development of applications in an integrated environment of RDB and graph DB, without being hindered by the complexity of the schema.

In order to solve the above problems and achieve the object, the database management device according to the present invention is characterized by having an acquisition unit that acquires data, a separation unit that separates the areas of the relational database and the graph database in the storage unit into an area for referencing data and an area for allowing data updates, and a classification unit that classifies and stores data expressed as nodes and relationships between nodes in one of the separated areas of the graph database according to the attributes of the data, and classifies and stores data other than the data expressed as nodes and relationships between nodes in one of the separated areas of the relational database according to the attributes of the data.

The present invention makes it possible to develop applications in an integrated environment of RDB and graph DB without being hindered by the complexity of the schema.

FIG. 1 is a diagram for explaining an overview of a database management device. FIG. 2 is a schematic diagram illustrating a schematic configuration of a database management device. FIG. 3 is a diagram for explaining the processing of the classification unit. FIG. 4 is a flowchart showing a database management process procedure. FIG. 5 is a diagram illustrating a computer that executes a database management program.

Below, one embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment. In addition, in the drawings, the same parts are denoted by the same reference numerals.

[Database Management Device Overview]
1 is a diagram for explaining an overview of a database management device. As shown in Fig. 1, the database management device of this embodiment separates the areas of each database into a reference system and an update system in an environment in which an RDB and a graph DB are integrated.

Here, the reference system is an area that stores data referenced by an application. The update system is an area that stores data that allows an application to update the data. In the example shown in FIG. 1, the RDB is separated into an RDB reference system 14a and an RDB update system 14b, and the graph DB is separated into a graph DB reference system 14c and a graph DB update system 14d.

In this way, multiple layers of reference and update systems are configured inside the database. Data is then stored in each area according to the data attributes. For example, in a database related to telecommunications equipment, master data that is not updated is stored in the RDB reference system, and report system data such as equipment attribute data used for statistics and reports is stored in the RDB reference system.

The graph DB reference system stores data that is not updated, such as nodes and links, among data that is expressed by the relationships between nodes. For example, coordinates of point equipment and span lengths are stored. The graph DB update system stores equipment attributes that are updated frequently. For example, attribute values such as the material and construction year of the actual equipment, and services that use the actual equipment are stored.

In this way, data placement is optimized according to data attributes such as data reference/data update, allowing application developers to easily understand the internal structure of the database, improving development efficiency and shortening development time.

In addition, by storing data in the graph DB reference system and the graph DB update system, it becomes possible to speed up processing specialized for graphic display.

In addition, NoSQL databases, including graph DBs, generally have insufficient transaction management implementations due to the emphasis on performance, but the transaction management of the graph DB is complemented by the transaction management of the parallel RDB, strengthening the reliability of the data.

In addition, by backing up the configured database only for the update system, it is possible to shorten backup and recovery times.

[Configuration of database management device]
2 is a schematic diagram illustrating an example of a general configuration of a database management device. As illustrated in Fig. 2, a database management device 10 is realized by a general-purpose computer such as a personal computer, and includes an input unit 11, an output unit 12, a communication control unit 13, a storage unit 14, and a control unit 15.

The input unit 11 is realized using input devices such as a keyboard and a mouse, and inputs various instruction information such as a command to start processing to the control unit 15 in response to input operations by an operator. The output unit 12 is realized by a display device such as a liquid crystal display, a printing device such as a printer, etc.

The communication control unit 13 is realized by a NIC (Network Interface Card) or the like, and controls communication between the control unit 15 and external devices such as a server via a network. For example, the communication control unit 13 controls communication between the control unit 15 and a database device of another system that manages data used in the database management process described below, a user terminal on which an application is installed, etc.

The storage unit 14 is realized by a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. The storage unit 14 stores in advance the processing programs that operate the database management device 10 and data used during the execution of the processing programs, or stores them temporarily each time processing is performed. The storage unit 14 may be configured to communicate with the control unit 15 via the communication control unit 13.

In this embodiment, the storage unit 14 stores an RDB reference system 14a, an RDB update system 14b, a graph DB reference system 14c, and a graph DB update system 14d that are generated in the database management process described below, and are used by the application as a database.

The control unit 15 is realized using a CPU (Central Processing Unit) or the like, and executes a processing program stored in memory. As a result, the control unit 15 functions as an acquisition unit 15a, a separation unit 15b, and a classification unit 15c, as exemplified in FIG. 2. Note that each or some of these functional units may be implemented in different hardware. For example, the separation unit 15b may be implemented in a device separate from the other functional units. The control unit 15 may also include other functional units.

The acquisition unit 15a acquires data. For example, the acquisition unit 15a acquires data used in the database management process described below from the database of another system via the input unit 11 or the communication control unit 13. Specifically, the acquisition unit 15a replicates the database of the other system by snapshot. The acquisition unit 15a may also store the acquired data in the storage unit 14 as master data or initial data. The acquisition unit 15a may also transfer this data to the classification unit 15c described below without storing it in the storage unit 14.

The separation unit 15b separates the RDB and graph DB areas of the storage unit 14 into a reference system area that references data and an update system area that allows data to be updated. Specifically, the separation unit 15b creates areas in the storage unit 14 for an RDB reference system 14a, an RDB update system 14b, a graph DB reference system 14c, and a graph DB update system 14d.

The classification unit 15c classifies and stores the acquired data in separate areas according to the attributes of the data. Here, the attributes of the data include, for example, whether the data is to be referenced or updated. The classification unit 15c then stores the acquired data in one of the RDB reference system 14a, the RDB update system 14b, the graph DB reference system 14c, and the graph DB update system 14d according to the attributes of each data.

Specifically, the classification unit 15c classifies and stores, among the acquired data, data represented by relationships between nodes into either the area of the separated graph DB reference system 14c in the graph DB area or the area of the graph DB update system 14d in accordance with the attributes of the data. In addition, the classification unit 15c classifies and stores, among the acquired data, data other than data represented by relationships between nodes into either the area of the separated RDB reference system 14a in the RDB area or the area of the separated RDB update system 14b in accordance with the attributes of the data.

Here, FIG. 3 is a diagram for explaining the processing of the classification unit. As shown in FIG. 3, the classification unit 15c classifies and stores data acquired from DBs of other systems into an RDB reference system 14a, an RDB update system 14b, a graph DB reference system 14c, and a graph DB update system 14d according to the attributes of each data.

Specifically, the classification unit 15c stores the data acquired by the acquisition unit 15a from the other system DB in the RDB reference system 14a. Next, the classification unit 15c moves independently managed data such as key values to be updated from the RDB reference system 14a to the RDB update system 14b (FIG. 3 (1)), excluding master data that does not need to be updated and is stored in the RDB reference system 14a, and data that is stored in the graph DB, such as data represented by the relationships between nodes. For example, this is report-related data such as equipment attribute data used in statistics and reports.

The classification unit 15c also classifies data stored in the graph DB, such as data expressed as relationships between nodes, into either the graph DB reference system 14c or the graph DB update system 14d. Data expressed as relationships between nodes is data that can be illustrated in a line diagram or network form, such as the coordinates of point facilities such as manholes and utility poles, and the span lengths between point facilities such as tunnels, conduits, and cables.

Specifically, the classification unit 15c first moves the data to be referenced from the RDB reference system 14a to the graph DB reference system 14c (Figure 3 (2)). For example, attribute values such as coordinate data of point equipment and span lengths (path lengths) are stored in the graph DB reference system 14c. This makes it possible to synchronize data to realize graph display.

In addition, if there is a key value to be updated among the data in the graph DB reference system 14c, the classification unit 15c moves it from the graph DB reference system 14c to the graph DB update system 14d (Figure 3 (3)).

The classification unit 15c also moves data to be updated from the RDB reference system 14a to the graph DB update system 14d (FIG. 3(4)). For example, the graph DB update system 14d stores attribute values, materials, construction years, etc. for a portion of the actual equipment.

In addition, if there is an attribute value to be updated that is represented as a relationship between nodes among the data in the RDB update system 14b, the classification unit 15c moves it from the RDB update system 14b to the graph DB update system 14d (FIG. 3 (5)). For example, the graph DB update system 14d stores some attribute values of core line information and services, usage status, service quality, etc.

In this way, a multi-layer of reference and update systems is configured inside the RDB and graph DB, respectively (see Figures 3 (1) and (3)). This improves the efficiency of application development. Also, by separating data from the RDB and storing it in the graph DB reference system 14c and graph DB update system 14d (see Figures 3 (2), (4), and (5)), it becomes possible to speed up processing specialized for graphic display.

Furthermore, with the storage unit 14 configured in this way as a database, for example, an application that displays graphs can access the graph DB reference system 14c and the graph DB update system 14d (FIG. 3 (6) and (8)). Also, an application that displays data can access the RDB reference system 14a and the RDB update system 14b (FIG. 3 (7) and (9)).

As described above, the storage unit 14 of this embodiment stores, for example, data related to communication facilities as a database in which the RDB and the graph DB are integrated. Specifically, the RDB stores equipment information such as data used for statistics and data used for reports, and the graph DB stores information such as coordinates for point equipment, connection information using lengths for spans, attribute values of associated actual equipment, and services.

As a database, the storage unit 14 optimizes data placement according to data attributes such as data reference/data update, and clarifies the area to be processed by applications that access the database. This makes application development easier and shortens the development period. In addition, by limiting backup operations during operation as a database to only the update system, it is possible to shorten the time required for backup and restoration operations.

Alternatively, the storage unit 14 of this embodiment can be applied to a system that displays graph DB data as a line diagram, such as a GIS (Geographic Information System), as a database that integrates an RDB and a graph DB.

[Database management process]
Next, a database management process by the database management device 10 according to the present embodiment will be described with reference to Fig. 4. Fig. 4 is a flowchart showing a procedure of the database management process. The flowchart in Fig. 4 is started, for example, when an operational input is made to instruct the start of the database management process.

First, the acquisition unit 15a acquires the data to be processed from a database of another system (step S1).

Next, the separation unit 15b separates each of the RDB and graph DB areas in the storage unit 14 into a reference system area that allows data to be referenced and an update system area that allows data to be updated (step S2). Specifically, the separation unit 15b generates areas in the storage unit 14 for the RDB reference system 14a, the RDB update system 14b, the graph DB reference system 14c, and the graph DB update system 14d.

Then, the classification unit 15c classifies and stores the acquired data into one of the RDB reference system 14a, the RDB update system 14b, the graph DB reference system 14c, and the graph DB update system 14d according to the attributes of each data (step S3).

Specifically, the classification unit 15c classifies and stores, among the acquired data, data represented by relationships between nodes into either the area of the separated graph DB reference system 14c or the area of the separated graph DB update system 14d in the graph DB area, depending on the attributes of the data. In addition, the classification unit 15c classifies and stores, among the acquired data, data other than data represented by relationships between nodes into either the area of the separated RDB reference system 14a or the area of the separated RDB update system 14b in the RDB area, depending on the attributes of the data. This completes the series of database management processes.

[effect]
As described above, in the database management device 10, the acquisition unit 15a acquires data. The separation unit 15b separates the RDB and graph DB areas of the storage unit 14 into a reference system area that refers to data and an update system area that allows data to be updated. The classification unit 15c classifies and stores data represented by a relationship between nodes into either the graph DB reference system 14c area or the graph DB update system 14d area of the graph DB area according to the attributes of the data. In addition, the classification unit 15c classifies and stores data other than data represented by a relationship between nodes into either the RDB reference system 14a area or the RDB update system 14b area of the RDB area according to the attributes of the data.

This allows the database management device 10 to configure multiple layers of reference/update systems within each of the RDB and graph DB. Therefore, data placement is optimized according to data attributes such as data reference/data update, and application developers can easily grasp the internal structure of the database, improving development efficiency and shortening development time.

In addition, by separating the data from the RDB and storing it in the graph DB reference system 14c and graph DB update system 14d, it becomes possible to speed up processing specialized for graphic display. Furthermore, while NoSQL databases that include graph DBs generally have insufficient transaction management implementation due to the emphasis on performance, the transaction management of the graph DB is complemented by the transaction management of the coexisting RDB, strengthening the reliability of the data.

In this way, an integrated environment of RDB and graph DB makes it possible to develop applications that are not hindered by complex schemas.

Specifically, the storage unit 14 stores data related to communication equipment. This makes the development of applications related to communication equipment more efficient. It also makes it possible to display graphs related to communication equipment more quickly.

[program]
A program in which the processing executed by the database management device 10 according to the above embodiment is written in a language executable by a computer can also be created. As an embodiment, the database management device 10 can be implemented by installing a database management program that executes the above database management processing as package software or online software on a desired computer. For example, by executing the above database management program on an information processing device, the information processing device can function as the database management device 10. In addition, the information processing device also includes mobile communication terminals such as smartphones, mobile phones, and PHS (Personal Handyphone System), and even slate terminals such as PDAs (Personal Digital Assistants). The functions of the database management device 10 may be implemented on a cloud server.

FIG. 5 is a diagram showing an example of a computer that executes a database management program. The computer 1000 has, for example, a memory 1010, a CPU 1020, a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These components are connected by a bus 1080.

The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM 1012. The ROM 1011 stores a boot program such as a BIOS (Basic Input Output System). The hard disk drive interface 1030 is connected to a hard disk drive 1031. The disk drive interface 1040 is connected to a disk drive 1041. A removable storage medium such as a magnetic disk or optical disk is inserted into the disk drive 1041. The serial port interface 1050 is connected to a mouse 1051 and a keyboard 1052, for example. The video adapter 1060 is connected to a display 1061, for example.

Here, the hard disk drive 1031 stores, for example, an OS (Operating System) 1091, an application program 1092, a program module 1093, and program data 1094. Each piece of information described in the above embodiment is stored, for example, in the hard disk drive 1031 or memory 1010.

The database management program is stored in the hard disk drive 1031, for example, as a program module 1093 in which instructions to be executed by the computer 1000 are written. Specifically, the program module 1093 in which each process executed by the database management device 10 described in the above embodiment is written is stored in the hard disk drive 1031.

In addition, data used for information processing by the database management program is stored as program data 1094, for example, in the hard disk drive 1031. Then, the CPU 1020 reads the program module 1093 and program data 1094 stored in the hard disk drive 1031 into the RAM 1012 as necessary, and executes each of the procedures described above.

The program module 1093 and program data 1094 related to the database management program are not limited to being stored in the hard disk drive 1031, but may be stored in a removable storage medium, for example, and read by the CPU 1020 via the disk drive 1041 or the like. Alternatively, the program module 1093 and program data 1094 related to the database management program may be stored in another computer connected via a network such as a LAN (Local Area Network) or a WAN (Wide Area Network), and read by the CPU 1020 via the network interface 1070.

The above describes an embodiment of the invention made by the inventor, but the present invention is not limited to the descriptions and drawings that form part of the disclosure of the present invention according to this embodiment. In other words, other embodiments, examples, operational techniques, etc. made by those skilled in the art based on this embodiment are all included in the scope of the present invention.

REFERENCE SIGNS LIST 10 Database management device 11 Input unit 12 Output unit 13 Communication control unit 14 Storage unit 14a RDB reference system 14b RDB update system 14c Graph DB reference system 14d Graph DB update system 15 Control unit 15a Acquisition unit 15b Separation unit 15c Classification unit

Claims

An acquisition unit for acquiring data;
a separation unit that separates each of the areas of the relational database and the graph database in the storage unit into an area for referencing data and an area for allowing data updates;
a classification unit that classifies and stores data represented by relationships between nodes among the acquired data into any one of the separated areas of the graph database according to an attribute of the data, and classifies and stores data other than data represented by relationships between nodes among the acquired data into any one of the separated areas of the relational database according to an attribute of the data;
A database management device comprising:
The database management device according to claim 1, characterized in that the storage unit stores data related to communication facilities.
A database management method executed by a database management device having a storage unit, comprising:
An acquisition step of acquiring data;
A separation step of separating each of the areas of the relational database and the graph database in the storage unit into an area for referencing data and an area for allowing data updates;
a classification step of classifying and storing data represented by relationships between nodes among the acquired data into any one of the separated areas of the graph database according to an attribute of the data, and classifying and storing data other than data represented by relationships between nodes among the acquired data into any one of the separated areas of the relational database according to an attribute of the data;
A database management method comprising:
an acquisition step for acquiring data;
A separation step of separating each of the areas of the relational database and the graph database in the storage unit into an area for referencing data and an area for allowing data updates;
a classification step of classifying and storing data represented by relationships between nodes among the acquired data into any one of the separated areas of the graph database according to an attribute of the data, and classifying and storing data other than data represented by relationships between nodes among the acquired data into any one of the separated areas of the relational database according to an attribute of the data;
A database management program for executing the above on a computer.