JP2020166504A - Data provision system and data access method - Google Patents

Abstract

To accurately access data distributed and stored in a plurality of data sources with less workload.SOLUTION: Source definition DB 20 stores, for each combination of history data of data series and storage destination data source, data storage period of the history data stored in the storage destination data source, and a data access device 10 acquires, based on the source definition DB 20 and specified period specified in a data access request from a client terminal CL, history data of specified data series constituting requested history data from the history data and the corresponding storage destination data source and provides it to the client terminal CL.SELECTED DRAWING: Figure 1

Description

The present invention relates to a data access technique for accessing historical data distributed and stored in a plurality of data sources.

Industrial automation systems optimize manufacturing equipment operation by performing analysis using a wide range of long-term data such as equipment operation status and information linkage between one or more manufacturing sites and higher-level management applications. It is being converted. In recent years, in such optimization processing, there is a movement from local optimization to total optimization. In cloud systems, there is also a movement to analyze huge amounts of big data stored in the cloud and use it for business and society. In such a data system, when performing data processing, it is conceivable to access long-term historical data showing the temporal transition of various data series, and the amount of data can be stored in one data source such as a server. The amount of data may be exceeded.

Conventionally, as a technique for handling history data over a period exceeding the amount of data that can be stored on one server, history data that cannot be managed by the server is distributed and stored in multiple external files in advance, and the history data is accessed. In some cases, a technique has been proposed to access the history data of an arbitrary period to be confirmed as a whole by restoring one or more external files having the history data of the period to be confirmed inside the server (for example). , Patent Document 1, etc.). Also, by assigning data for different periods to multiple servers and storing them, and accessing the server that stores the history data for the period you want to check, the history of any period you want to check as a whole Techniques for accessing data have been proposed (see, for example, Patent Document 2).

Japanese Unexamined Patent Publication No. 2001-005516 Japanese Unexamined Patent Publication No. 2008-310634

When accessing historical data over a long period of time in a data system, if the amount of historical data exceeds the amount of data that can be stored in one data source, the operator manually links the above-mentioned conventional access methods. There is a need. Therefore, in the case where the historical data of the period to be confirmed is distributed and stored in multiple data sources, the operator needs to recognize as a combination which period historical data is stored in which data source. .. For this reason, there is a problem that the work efficiency at the time of data access is poor and the work load on the operator increases. Further, if the history data is searched based on the wrong combination, there is a problem that a mistake occurs that the history data of the period to be confirmed cannot be accurately extracted.

The present invention is to solve such a problem, and to provide a data access technique capable of accurately accessing historical data distributed and stored in a plurality of data sources with a small workload. I am aiming.

In order to achieve such an object, the data providing system according to the present invention includes a plurality of data sources that distribute and store historical data indicating the temporal transition of various data series, and the plurality of data sources for each of the historical data. Of the data sources of, the source definition database that stores the storage destination data source that stores the history data in combination, and the request history data related to the specified data series specified in the data access request received from the client terminal are stored in the plurality of cases. The source definition database includes historical data of a data series and a storage destination data source, including a data access device that acquires the request history data from the storage destination data source corresponding to the request history data and provides the data source to the client terminal. For each combination with and, the data storage period of the history data stored in the storage destination data source is stored, and the data access device is set to the source definition database and the specified period specified in the data access request. Based on this, the history data of the designated data series constituting the request history data is acquired from the storage destination data source corresponding to the history data.

Further, in one configuration example of the data providing system according to the present invention, the data access device searches the source definition database based on the designated period to obtain historical data of the designated period related to the designated data series. A source identification unit configured to specify all storage destination data sources to be stored, and a data acquisition unit configured to acquire history data of the specified data series from each of the specified storage destination data sources. It also has a data providing unit configured to generate the requested history data from the acquired history data of the designated data series and provide it to the client terminal.

Further, in one configuration example of the data providing system according to the present invention, the source definition database stores event information indicating storage processing of the history data in the storage destination data source for each combination, and specifies the source. Based on the event information of the storage destination data source obtained by searching the source definition database, the unit specifies the data storage period of the historical data stored in the storage destination data source, and stores the data. The storage destination data source is specified by comparing the period with the designated period.

Further, in one configuration example of the data providing system according to the present invention, the event information is a generation event indicating that the storage of the history data of the data series has started in the first storage destination data source, or the above. After the first switching event indicating that the storage destination of the historical data of the data series has been switched from another storage destination data source to the first storage destination data source, and the generation event or the first switching event. The source identification unit includes event information regarding a second switching event indicating that the storage destination of the history data of the data series has been switched from the first storage destination data source to the second storage destination data source. The period from the generation event or the first switching event to the second switching event regarding the history data of the designated data series is specified as the data storage period in the first storage destination data source. It is a thing.

Further, in one configuration example of the data providing system according to the present invention, the event information is a generation event indicating that the storage of the history data of the data series has started in the first storage destination data source, or the above. After the first switching event indicating that the storage destination of the historical data of the data series has been switched from another storage destination data source to the first storage destination data source, and the generation event or the first switching event. The source specifying unit includes the event information related to the deletion event indicating that the storage of the history data of the data series is completed in the first storage destination data source, and the source specifying unit is the generation of the history data of the designated data series. The period from the event or the first switching event to the deletion event is specified as a data storage period in the first storage destination data source.

Further, in one configuration example of the data providing system according to the present invention, the event information includes a deletion event indicating that the storage of the history data of the data series has been completed in the first storage destination data source, and the deletion. After the event, the source identification unit comprises event information relating to a generated event indicating that the storage of historical data of the data series has been resumed in the first storage data source or another storage data source. The period from the deletion event to the generation event of the history data of the designated data series is specified as a missing period of the designated data series.

Further, the data access method according to the present invention is specified by a data access request received from a client terminal by a computer system from a plurality of data sources that distribute and store historical data indicating the temporal transition of various data series. This is a data access method used when acquiring request history data related to a designated data series and providing the request history data to the client terminal. The history data of the plurality of data sources is provided by the computer system for each history data. The storage step stored in the source definition database by combining the storage destination data sources that store the data, and the computer system corresponds the request history data related to the specified data series to the request history data among the plurality of data sources. The storage step includes a data access step that is acquired from the storage destination data source and provided to the client terminal, and the storage step is performed in the storage destination data source for each combination of the history data of the data series and the storage destination data source. The data access step comprises a step of storing the data retention period of the stored history data, and the data access step configures the request history data based on the source definition database and the specified period specified in the data access request. This includes a step of acquiring the history data of the designated data series to be performed from the storage destination data source corresponding to the history data.

Further, in one configuration example of the data access method according to the present invention, the data access step searches the source definition database based on the designated period to obtain historical data of the designated period related to the designated data series. A source specifying step for specifying all storage destination data sources to be stored, a data acquisition step for acquiring history data of the designated data series from each of the specified storage destination data sources, and a history of the acquired designated data series. It includes a data providing step of generating the request history data from the data and providing the request history data to the client terminal.

Further, in one configuration example of the data access method according to the present invention, the storage step includes a step of storing event information indicating a storage process of the history data in the storage destination data source for each combination. The source identification step identifies the data storage period of the historical data stored in the storage destination data source based on the event information of the storage destination data source obtained by searching the source definition database, and the above-mentioned The storage destination data source is included by comparing the data storage period with the designated period.

According to the present invention, the operator simply specifies the specified data series to be accessed and the specified period in the data access request without recognizing which period of data is stored in which data source. Request history data can be acquired and provided from the history data distributed and stored in the data source, and the workload of the operator can be significantly reduced. Further, since the history data is not searched based on the wrong combination, the history data for the specified period can be accurately extracted, and the occurrence of mistakes due to the wrong combination can be suppressed.

FIG. 1 is a block diagram showing a configuration of a data providing system. FIG. 2 is an explanatory diagram showing a configuration example of the source definition database. FIG. 3 is a sequence diagram showing a data access operation. FIG. 4 is an explanatory diagram showing a data storage period of the storage destination data source. FIG. 5 is an explanatory diagram showing another data storage period (switching-switching) of the storage destination data source. FIG. 6 is an explanatory diagram showing another data storage period (generation-deletion) of the storage destination data source. FIG. 7 is an explanatory diagram showing duplication of data storage.

Next, an embodiment of the present invention will be described with reference to the drawings.
[Data provision system]
First, the data providing system 1 according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing a configuration of a data providing system.
This data providing system 1 distributes and stores historical data indicating the temporal transition of various data series. Request history related to a designated data series specified by a data access request received from a client terminal CL from a plurality of data sources 30. This is a system that acquires data and provides it to the client terminal CL.

As shown in FIG. 1, the data providing system 1 is composed of a computer system including a plurality of nodes such as a server device, a database, and a storage source as a whole.
The data providing system 1 includes a data access device 10, a source definition database (hereinafter referred to as a source definition DB), and a plurality of data sources 30 as main nodes. The configuration of the data providing system 1 is not limited to the configuration example of FIG. 1, and may be arbitrarily changed. For example, the source definition DB 20 may be housed inside the data access device 10, or a part or all of the data source 30 may be housed inside the data access device 10.

The data access device 10 is composed of an information processing device such as a server device as a whole, is connected to the communication network NW via the communication line L1, and is a request regarding a designated data series specified by a data access request received from the client terminal CL. It has a function of acquiring history data from a storage destination data source corresponding to the request history data among a plurality of data sources 30 and providing the history data to the client terminal CL.

The source definition DB 20 is composed of a storage device such as a hard disk or a semiconductor memory as a whole, and is connected to the data access device 10 via a communication line L2 so as to exchange data. The source definition DB 20 has a function of combining and storing a storage destination data source that stores the history data among a plurality of data sources for each history data, and a combination of the history data of the data series and the storage destination data source. Each has a function of storing the data storage period of the history data stored in the storage destination data source.
Specifically, the source definition DB 20 has a function of storing event information indicating the storage process of the history data in the storage destination data source for each combination of the history data of the data series and the storage destination data source. There is.

FIG. 2 is an explanatory diagram showing a configuration example of the source definition database. The source definition DB 20 identifies a data series ID consisting of a data series name or the like for identifying individual data series, and a storage destination data source for storing historical data of the data series corresponding to the data series ID among the data sources 30. For each combination with the data source ID for identifying the item ID for identifying a series of history data (items) in the data series ID and the corresponding data series, and the storage process of the history data in the storage destination data source. Event information indicating that is registered.

The event information includes the event type and the event valid date and time. The event type is a type for identifying the specific content of the event related to the storage process, and the event valid date and time indicates the date and time when the event of the event type is valid.
The main event types of event information are generate event, switch event, and delete event. The generation event is an event indicating that the storage of the history data of the data series has started in the storage destination data source. The switching event is an event indicating that the storage destination of the history data of the data series has been switched from another storage destination data source to the storage destination data source. The delete event is an event indicating that the storage of the history data of the data series has been completed in the storage destination data source.

In the example of FIG. 2, a plurality of events are registered. It is assumed that the registered contents in FIG. 2 indicate the present of "2019/04/01 00:00:00".
Of these, the event type "generated event" and the event valid date and time "2016/01/01 00:00:00" are registered as the events of the data source HA1 related to the data series "device A temperature". Therefore, this event indicates that the storage resource of the history data of the data series "device A temperature" was newly generated in the data source HA1 at the event valid date and time "2016/01/01 00:00:00". ing.

Further, as the event of the data source HA2 related to the data series "device A temperature", the event type "switching event" and the event valid date and time "2017/02/01 00:00:00" are registered. Therefore, this event indicates that the storage resource of the history data of the data series "device A temperature" has been switched to the data source HA2 at the event valid date and time "2017/02/01 00:00:00". ..

Further, as the event of the data source HA2 related to the data series "device A temperature", the event type "deletion event" and the event valid date and time "2018/03/01 00:00:00" are registered. Therefore, this event indicates that the storage resource of the history data of the data series "device A temperature" has been terminated at the data source HA2 at the event valid date and time "2018/03/01 00:00:00". ..

Further, as the event of the data source HAX-A related to the data series "device A temperature", the event type "generation event" and the event valid date and time "2019/05/01 00:00:00" are registered. Therefore, since the event valid date and time "2019/05/01 00:00:00" indicates a future date and time for this event, the storage resource of the history data of the data series "device A temperature" is the event valid date and time. At "2018/03/01 00:00:00", it is shown that it is scheduled to be generated by the data source HAX-A. As a result, the plan for storing the history data can be registered as an event.

The data source 30 is composed of a storage device such as a hard disk or a semiconductor memory, or a server device such as a data server equipped with these storage devices, and is connected to the data access device 10 via a communication line L3 so as to exchange data. ing. The data source 30 has a function of distributing and storing historical data indicating the temporal transition of various data series based on the item ID.

[Data access device]
Next, the data access device 10 according to the present embodiment will be described in detail with reference to FIG.
The data access device 10 is composed of an information processing device such as a server device as a whole, and mainly includes a communication I / F circuit 11, an operation input device 12, a display device 13, a storage device 14, and an arithmetic processing device 15. ing.

The communication I / F circuit 11 has a function of transmitting and receiving various data such as data access requests and request history data by performing data communication with the client terminal CL via the communication line L1 and the communication network NW. ing.
The operation input device 12 includes an operation input device such as a keyboard, a mouse, and a touch panel, and has a function of detecting an operator's operation and outputting the operation to the arithmetic processing unit 15.
The display device 13 is composed of a screen display device such as an LCD, and has a function of displaying various screen data such as a menu screen, a setting screen, and a management screen output from the arithmetic processing unit 15 on the screen.

The storage device 14 is composed of a storage device such as a hard disk or a semiconductor memory, and has a function of storing various processing data and programs used in the data access processing executed by the arithmetic processing unit 15.
The program is a program that realizes various processing units that constitute data access processing by cooperating with the CPU of the arithmetic processing unit 15, and is an external device or recording medium connected to the data access device 10 via a communication line. Is read in advance and stored in the storage device 14.

The arithmetic processing unit 15 has a CPU and its peripheral circuits, and has a function of realizing various processing units constituting data access processing by coordinating the CPU and the program of the storage device 14.
The main processing units realized by the arithmetic processing unit 15 include a source specifying unit 15A, a data acquisition unit 15B, and a data providing unit 15C.

The source specifying unit 15A is a source via the communication line L2 based on the specified period specified in the data access request received from the client terminal CL via the communication network NW, the communication line L1, and the communication I / F circuit 11. By searching the definition DB 20, the function of specifying all the storage destination data sources for storing the history data of the specified data series for the specified period from the data sources 30, and the storage obtained by searching the source definition DB 20. Based on the event information of the destination data source, specify the data storage period of the history data stored in the storage destination data source, and specify the storage destination data source by comparing the data storage period with the specified period. It has a function.

Specifically, the source identification unit 15A indicates that the history data of the specified data series has been switched from the storage destination data source to another storage destination data source from the generation event indicating the start of storage at the storage destination data source. The function to specify the period until the switching event shown as the data storage period in the storage destination data source, and the generation event related to the history data of the specified data series, or the storage destination of the history data of the data series is other storage destination data. It has a function to specify the period from the switching event indicating that the source has been switched to the storage destination data source to the deletion event as the data storage period in the storage destination data source.

The data acquisition unit 15B has a function of acquiring the history data of the designated data series from each of the storage destination data sources specified by the source identification unit 15A among the data sources 30 via the communication line L3.
The data providing unit 15C generates request history data from the history data of the designated data series acquired by the data acquisition unit 15B, and provides the request history data to the client terminal CL via the communication I / F circuit 11, the communication line L1, and the communication network NW. Has the function of

[Operation of the present embodiment]
Next, the data access operation of the data providing system 1 according to the present embodiment will be described with reference to FIG. FIG. 3 is a sequence diagram showing a data access operation.
The data providing system 1 executes the data access operation shown in FIG. 3 in response to the data access request from the client terminal CL. It is assumed that three data sources 30, the data sources HA1, HA2, and HAX-A, are connected to the data access device 10 as the data source 30 via the communication line L3. Further, it is assumed that the data as shown in FIG. 2 is registered in the source definition DB 20 prior to the execution of the data access operation.

First, according to the operator operation on the client terminal CL (step S100), the designated data series "device A temperature" to be accessed and the designated period "2016/04/01 00:00:00" to "2017/08" It is assumed that the data access request including "/ 31 23:59:59" has been transmitted (step S101).

The arithmetic processing unit 15 of the data access device 10 receives a data access request from the client terminal CL via the communication network NW and the communication I / F circuit 11.
The source specifying unit 15A searches the source definition DB 20 based on the specified period specified in the data access request received from the client terminal CL, and thereby stores all the historical data of the specified period related to the specified data series. The destination data source is specified (step S102). Details of specifying the storage destination data source will be described later.

Here, when the data sources HA1 and HA2 are specified as the storage destination data source, the data acquisition unit 15B requests the data including the item ID indicating the history data of the designated data series registered in the source definition DB 20. It is transmitted to the data source HA1 which is one of the storage destination data sources (step S103), and the data response returned from the data source HA1 is received accordingly, and the history data of the specified data series included in the data response is acquired. (Step S104).

Similarly, the data acquisition unit 15B sends a data request including an item ID indicating the history data of the designated data series registered in the source definition DB 20 to the data source HA2 which is one of the storage destination data sources. It transmits (step S105), receives the data response returned from the data source HA2 in response to this, and acquires the history data of the designated data series included in the data response (step S106).

After that, the data providing unit 15C uses the history data of the designated data series acquired from the data sources HA1 and HA2 by the data acquisition unit 15B to specify the designated period "2016/04/01 00:00:00" specified in the data access request. ”To“ 2017/08/31 23:59:59 ”are extracted and concatenated to generate request history data (step S107), communication I / F circuit 11, communication line. It is provided to the client terminal CL by a data response via L1 and the communication network NW (step S108), and a series of data access operations is terminated.

[Identify the storage destination data source]
Next, with reference to FIG. 4, the operation of specifying the storage destination data source in the data providing system 1 according to the present embodiment will be described. FIG. 4 is an explanatory diagram showing a data storage period of the storage destination data source.

FIG. 4 shows the data storage period of the data sources HA1, HA2, HAX-A relating to the data series “device A temperature” based on the registration example of the source definition DB 20 of FIG. First, based on the "generation event" of the data source HA1 and the "switching event" of the data source HA2, the data source HA1 is subjected to the event valid date and time "2016/01/01 00:00:00" of the "generation event". , It can be seen that the history data in the data storage period up to immediately before the event valid date and time "2017/02/01 00:00:00" of the "switching event" is registered.

In addition, based on the "switching event" and "deletion event" of the data source HA2, the data source HA2 is given a "deletion event" from the event valid date and time "2017/02/01 00: 00: 00" of the "switching event". It can be seen that the history data in the data storage period up to immediately before the event valid date and time "2018/03/01 00:00:00" of "" is registered.

Further, based on the event valid date and time "2019/05/01 00:00:00" of the "generated event" of the data source HAX-A, the data source HAX-A is set to "2019/05/01 00:00:00: It can be seen that the storage of history data after "00" is scheduled to be resumed. As a result, the registered contents of the source definition DB 20 can be used for future schedule management related to the operating device / equipment.

Further, based on the "deletion event" of the data source HA2 and the "generation event" of the data source HAX-A, the "generation event" is started from the event valid date and time "2018/03/01 00:00:00" of the "deletion event". It can be seen that the history data in the period up to immediately before the event valid date and time "2019/05/01 00:00:00" is missing. As a result, when displaying the history data of an arbitrary data series on the screen, the missing period is "expressed by a horizontal line showing the same value because the history data has not changed" and "there is an item that is the target of the history data". Since I didn't do it, I can decide which one to use, "express the loss of historical data without drawing a line during that time."

Therefore, comparing the data storage period of these data sources HA1, HA2, HAX-A with the specified period specified in the data access request received from the client terminal CL, among the historical data of the data series "device A temperature" , The history data from the beginning of the specified period "2016/04/01 00: 00: 00" to just before the event valid date "2017/02/01 00: 00: 00" of the "switching event" is sent to the data source HA1. You can see that it is stored.

In addition, in the history data of the data series "device A temperature", from the event valid date and time "2017/02/01 00:00:00" of the "switching event", the end of the designated period "2017/08/31 23:59" It can be seen that the history data up to: 59 ”is stored in the data source HA2.
Thereby, among the history data of the data series "device A temperature", the storage destination data sources of the history data corresponding to the designated period are specified to be the data source HA1 and the data source HA2. Therefore, from the history data acquired from these data sources HA1 and HA2, the history data from the designated period "2016/04/01 00:00:00" to "2017/08/31 23:59:59" is extracted. After that, the request history data will be generated by being linked to one.

FIG. 5 is an explanatory diagram showing another data storage period (switching-switching) of the storage destination data source. In FIG. 4, a case has been described as an example in which a generation event in the data source HA1 and a subsequent switching event in the data source HA2 are specified as a data storage period in the data source HA1 regarding the data series “device A temperature”. However, it is possible that a new switching event will continue after the switching event. For example, as shown in FIG. 5, when the switching event at the data source HA2 at the date and time t2 is followed by the switching event at the data source HAX-A at the date and time t3 regarding the data series “device A temperature”, these 2 The interval between the two switching events may be specified as the data storage period in the data source HA2.

FIG. 6 is an explanatory diagram showing another data storage period (generation-deletion) of the storage destination data source. In FIG. 4, a case where the data series “device A temperature” from the switching event in the data source HA2 to the subsequent deletion event is specified as the data storage period in the data source HA2 has been described as an example, but the generation event After that, it is possible that the deletion event continues. For example, as shown in FIG. 6, when the generation event at the data source HA1 at the date / time t1 is followed by the deletion event at the data source HA1 at the date / time t4 regarding the data series “device A temperature”, from these generation events The period until the deletion event may be specified as the data storage period in the data source HA1.

FIG. 7 is an explanatory diagram showing duplication of data storage. Regarding the storage of history data in the data source 30, it is possible to accurately switch to a different data source before and after the event valid date and time of the "switching event", but as shown in FIG. 7, the event valid date and time of the "switching event" There may be overlapping periods before and after. In such a case, the request history data does not have to be switched at the event valid date and time of the "switching event" as long as it is within the overlapping period. Therefore, at what point within the overlapping period the history data is switched may be set in advance.

[Effect of this embodiment]
As described above, in the present embodiment, the source definition DB 20 stores the data storage period of the history data stored in the storage destination data source for each combination of the history data of the data series and the storage destination data source. Then, the data access device 10 corresponds the history data of the designated data series constituting the request history data with the history data based on the source definition DB 20 and the designated period specified by the data access request from the client terminal CL. It is acquired from the storage destination data source to be provided and provided to the client terminal CL.

Specifically, in the data access device 10, the source specifying unit 15A searches the source definition database based on the specified period to search all the storage destination data sources for storing the history data of the specified period related to the specified data series. The specified data acquisition unit 15B acquires the history data of the specified data series from each of the specified storage destination data sources, and the data providing unit 15C generates the request history data from the acquired history data of the specified data series. It is provided to the client terminal CL.

As a result, the operator simply specifies the designated data series to be accessed and the designated period in the data access request without recognizing which period of data is stored in which data source 30, and a plurality of data sources. It is possible to acquire and provide the requested history data from the history data distributed and stored in 30, and it is possible to significantly reduce the work load of the operator. Further, since the history data is not searched based on the wrong combination, the history data for the specified period can be accurately extracted, and the occurrence of mistakes due to the wrong combination can be suppressed.

Further, in the present embodiment, the source definition DB 20 stores event information indicating the storage process of the history data in the storage destination data source for each combination, and the source identification unit 15A searches the source definition DB 20. Based on the event information of the obtained storage destination data source, the data storage period of the history data stored in the storage destination data source is specified, and the storage destination data is compared between the data storage period and the specified period. It is intended to identify the source.

Specifically, the event information includes a generated event indicating that the storage of the history data of the data series has started in the storage destination data source, and the storage destination of the history data of the data series is the storage destination from another storage destination data source. From the generation event indicating the start of storage in the storage destination data source regarding the history data of the specified data series, the source identification unit 15A contains event information regarding the switching event indicating that the data source has been switched to, from the storage destination data source. The period until the switching event indicating that the data source has been switched to another storage destination data source is specified as the data storage period in the storage destination data source.

Further, the event information includes event information regarding a deletion event indicating that the storage of the history data of the data series has been completed in the storage destination data source, and the source specifying unit 15A includes a generation event regarding the history data of the specified data series. Alternatively, the period from the switching event indicating that the storage destination of the history data of the data series has been switched from another storage destination data source to the storage destination data source to the deletion event is set as the data storage period in the storage destination data source. It is intended to be specified.

As a result, when an event related to the history data storage process occurs for each storage destination data source, the storage period of the history data stored in each data source 30 can be set by simply registering the event in the source definition DB 20. Can be identified. Therefore, it is not necessary to register the storage period of the history data stored in each data source 30 in detail, and the processing load required for managing the storage period of the history data can be significantly reduced.

[Extension of Embodiment]
Although the present invention has been described above with reference to the embodiments, the present invention is not limited to the above embodiments. Various changes that can be understood by those skilled in the art can be made to the structure and details of the present invention within the scope of the present invention.

1 ... Data providing system, 10 ... Data access device, 11 ... Communication I / F circuit, 12 ... Operation input device, 13 ... Display device, 14 ... Storage device, 15 ... Arithmetic processing device, 20 ... Source definition DB, 30, HA1, HA2, HAX-A ... Data source, CL ... Client terminal, NW ... Communication network, L1, L2, L3 ... Communication line.

Claims (9)

Multiple data sources that distribute and store historical data showing the temporal transition of various data series,
For each of the history data, a source definition database that stores a combination of storage destination data sources that store the history data among the plurality of data sources, and a source definition database.
The request history data related to the specified data series specified in the data access request received from the client terminal is acquired from the storage destination data source corresponding to the request history data among the plurality of data sources and provided to the client terminal. Equipped with a data access device
The source definition database stores the data storage period of the history data stored in the storage destination data source for each combination of the history data of the data series and the storage destination data source.
Based on the source definition database and the designated period specified in the data access request, the data access device stores the history data of the designated data series constituting the request history data as a storage destination corresponding to the history data. A data delivery system characterized by obtaining from a data source. In the data providing system according to claim 1,
The data access device is
A source identification unit configured to specify all storage destination data sources for storing the history data of the specified period for the specified data series by searching the source definition database based on the specified period.
A data acquisition unit configured to acquire the history data of the specified data series from each of the specified storage destination data sources, and
A data providing system including a data providing unit configured to generate the requested history data from the acquired history data of the designated data series and provide the requested history data to the client terminal. In the data providing system according to claim 2,
The source definition database stores event information indicating the storage process of the history data in the storage destination data source for each of the combinations.
The source specifying unit specifies the data storage period of the historical data stored in the storage destination data source based on the event information of the storage destination data source obtained by searching the source definition database. A data providing system characterized in that the storage destination data source is specified by comparing the data storage period with the designated period. In the data providing system according to claim 3,
The event information is a generation event indicating that the storage of the history data of the data series has started in the first storage destination data source, or the storage destination of the history data of the data series is from another storage destination data source. After the first switching event indicating that the data source has been switched to the first storage destination data source and the generation event or the first switching event, the storage destination of the history data of the data series is the first storage destination. Includes event information about a second switch event that indicates that the data source has been switched to a second destination data source.
The source specifying unit sets the period from the generation event or the first switching event to the second switching event regarding the history data of the designated data series as the data storage period in the first storage destination data source. A data provision system characterized by identification. In the data providing system according to claim 3,
The event information is a generation event indicating that the storage of the history data of the data series has started in the first storage destination data source, or the storage destination of the history data of the data series is from another storage destination data source. After the first switching event indicating that the data source has been switched to the first storage destination data source and the generation event or the first switching event, the history data of the data series in the first storage destination data source Contains event information about the delete event and the delete event that indicates the end of storage
The source specifying unit specifies the period from the generation event or the first switching event to the deletion event regarding the history data of the designated data series as the data storage period in the first storage destination data source. A data provision system featuring. In the data providing system according to claim 3,
The event information includes a deletion event indicating that the storage of historical data of the data series has been completed in the first storage destination data source, and after the deletion event, the first storage destination data source or other storage. Includes event information about a generated event that indicates that the storage of historical data for the data series has been resumed in the destination data source.
The source specifying unit is a data providing system characterized in that the period from the deletion event to the generation event of the history data of the designated data series is specified as a missing period of the designated data series. The computer system acquires the request history data related to the specified data series specified in the data access request received from the client terminal from multiple data sources that distribute and store the history data showing the temporal transition of various data series. , A data access method used when providing to the client terminal.
A storage step in which the computer system combines the storage destination data sources that store the history data among the plurality of data sources for each history data and stores them in the source definition database.
The computer system includes a data access step of acquiring request history data related to a designated data series from a storage destination data source corresponding to the request history data among the plurality of data sources and providing the request history data to the client terminal.
The storage step includes a step of storing the data storage period of the history data stored in the storage destination data source for each combination of the history data of the data series and the storage destination data source.
In the data access step, the history data of the designated data series constituting the request history data is stored in the storage destination corresponding to the history data based on the source definition database and the designated period specified in the data access request. A data access method that involves retrieving from a data source. In the data access method according to claim 7.
The data access step
A source identification step for identifying all storage destination data sources for storing the history data of the specified period for the specified data series by searching the source definition database based on the specified period.
A data acquisition step of acquiring the history data of the specified data series from each of the specified storage destination data sources, and
A data access method including a data provision step of generating the request history data from the acquired history data of the designated data series and providing the request history data to the client terminal. In the data access method according to claim 8,
The storage step includes, for each of the combinations, a step of storing event information indicating the storage process of the history data in the storage destination data source.
The source identification step identifies the data retention period of the history data stored in the storage destination data source based on the event information of the storage destination data source obtained by searching the source definition database. A data access method comprising the storage destination data source by comparing the data storage period with the designated period.

Images