REMOTE OPERATION SYSTEM, TIME STAMP CORRECTION METHOD, AND TIME STAMP CORRECTION PROGRAM

Abstract

To modify the time series of data in a time series DB that has multiple time stamps according to requirements.SOLUTION: A remote operation system that uses a computer to manage data obtained via a network from an infrastructure base that operates one or more infrastructure devices, includes a time-series DB that accumulates and maintains operational information in which a timestamp of the infrastructure base or the infrastructure device is given to data obtained from the infrastructure device, a time difference detection unit that calculates a difference between a timestamp obtained from the infrastructure base or the infrastructure device and a time stamp of a time synchronization server of an operation base owned by the remote operation system, and a timestamp correction unit that corrects the timestamp of the data in the acquisition range using the difference in accordance with a data acquisition request received from an application, which includes the time series and data acquisition range specified by the data of the infrastructure device used in the application when the timestamp and the difference of the data in the acquisition range acquired from the time series DB meet the predetermined conditions.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a remote operation system, a time stamp correction method, and a time stamp correction program. [Background technology]

[0002] Network virtualization and SDN (Software Defined Networking) have become widespread, and by utilizing them, the IT infrastructure that supports business operations can flexibly and quickly make wide-area and detailed changes to items such as personnel changes and device installations in the workplace. On the other hand, the items to manage IT infrastructure have become bloated and complex, and a great deal of management effort is required not only for installation and initial settings, but also for ongoing operation and operational management. In recent years, there has been an increasing need to outsource non-core operations such as the management of such IT infrastructure, and managed services that not only provide customers with an IT infrastructure environment but also handle ongoing operation and operational management as a whole have been attracting attention.

[0003] In light of this, various companies are developing platforms for providing managed services. As a requirement for managed service providers who provide managed services, they need to centrally manage data in various formats collected from different devices at each location of the client's IT infrastructure and use it for operations in order to centrally manage each client's IT infrastructure. For this reason, the use of time-series DBs, which make it easy to check changes in the situation over time by using timestamps as the primary key and can store data regardless of the type of data other than the timestamp, is attracting attention.

[0004] As a best practice for formatting data acquired from various locations and storing it in a time-series DB, the ELK stack, which combines OSS (Open Source Software) such as Elasticsearch, a time-series DB, Logstash or Beats, a data collection tool, and Kibana, which visualizes data in the time-series DB, is widely used, and data is efficiently collected from multiple locations by distributing the data collection tool and the time-series DB. In addition, the timestamp, which is the primary key of the data to be stored in the time-series DB, is added when the data collection tool formats the data. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2018-190216 A Summary of the Invention [Problem to be solved by the invention]

[0006] When using a time-series DB, the reliability of the timestamps added to the data is important. The prior art shows a method of correcting the timestamps by utilizing the time correction log of the NTP (Network Time Protocol) in order to increase the reliability of the timestamps of the data in the time-series DB built into the control device.

[0007] However, in the case of managed services such as this one, when various data are collected from multiple customers' IT infrastructure sites and managed centrally in a time series DB, the time system of the operation site where the managed service is performed and the time system of the customer's IT infrastructure site are not necessarily the same. Even if the managed service is provided, it is often impossible to align the time system of all the devices at the customer's IT infrastructure site with the operation site, as this is a major change. In addition, IT infrastructure devices that are not time-synchronized may be operated. Assuming that the timestamp is given by the data collection tool and that the data collection tool operates at the customer's IT infrastructure site, the timestamp in the time series DB will be a mixture of the time systems of multiple customers' IT infrastructure sites. In the operation of IT infrastructure, it is not only necessary to adjust the timestamp to the correct time, but also to make corrections according to the operation, such as adjusting the timestamp to match the time of the target of the reconciliation when reconciling the alert time.

[0008] Therefore, an object of one aspect of the present invention is to provide a technique that enables correction of the time system of data in a time-series DB to which timestamps of multiple time systems are assigned according to requirements. [Means for solving the problem]

[0009] A remote operation system according to one aspect of the present invention is a remote operation system that uses a computer to manage data obtained via a network from an infrastructure base that operates one or a plurality of infrastructure devices, and is characterized in that it includes: a time series DB that accumulates and holds operation information in which a timestamp of the infrastructure base or the infrastructure device is added to the data obtained from the infrastructure device; a time difference detection unit that calculates a difference between the timestamp obtained from the infrastructure base or the infrastructure device and a timestamp of a time synchronization server of the operation base possessed by the remote operation system; and a timestamp correction unit that corrects the timestamp of the data in the acquisition range obtained from the time series DB using the difference in accordance with a data acquisition request received from an application, the time system including a time system according to which data of the infrastructure device used in the application complies and a data acquisition range specification, when the difference satisfies a predetermined condition. Effect of the Invention

[0010] According to one aspect of the present invention, the time system of data in a time-series DB to which timestamps of multiple time systems are added can be corrected according to requirements. [Brief description of the drawings]

[0011] [Figure 1] system configuration diagram [Diagram 2] Sequence diagram of time differential recording [Diagram 3] Time difference retention table [Figure 4] Sequence diagram of timestamp correction when acquiring time-series DB data [Diagram 5] Flowchart for timestamp correction when acquiring time-series DB data [Figure 6] Sequence diagram of timestamp correction for individual acquired data [Figure 7] Flowchart for correcting timestamps of individual acquired data [Figure 8]Sequence diagram of timestamp correction information and data storage in time series DB [Figure 9] Flowchart of timestamp correction when acquiring time-series DB data when time-series DB has timestamp correction information [Figure 10] System configuration for creating sub-datasets of a time-series DB [Figure 11A] Sequence diagram for creating a sub-dataset of a time-series DB [Figure 11B] Sequence diagram for creating a sub-dataset of a time-series DB [Figure 12] System configuration diagram for setting requirements for each app [Figure 13] Example of GUI for setting requirements for each application [Figure 14] Computer Schematic DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. The following description and drawings are examples for explaining the present invention, and appropriate omissions and simplifications have been made for clarity of explanation. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural.

[0013] In order to facilitate understanding of the invention, the position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc. Therefore, the present invention is not necessarily limited to the position, size, shape, range, etc. disclosed in the drawings.

[0014] In the following explanation, various information may be described using expressions such as "database," "table," and "list," but the various information may be expressed in other data structures. To indicate independence of data structure, "XX table," "XX list," and the like may be referred to as "XX information." When describing identification information, when expressions such as "identification information," "identifier," "name," "ID," and "number" are used, these are interchangeable.

[0015] When there are multiple components having the same or similar functions, they may be described by using the same reference numerals with different subscripts. However, when there is no need to distinguish between these multiple components, the subscripts may be omitted.

[0016] In addition, in the following description, processing performed by executing a program may be described, but the program is executed by a processor (e.g., a CPU (Central Processing Unit), a GPU (Graphics Processing Unit)) to perform a defined process using storage resources (e.g., a memory) and / or an interface device (e.g., a communication port) as appropriate, so the subject of the processing may be the processor. Similarly, the subject of the processing performed by executing a program may be a controller, device, system, computer, or node having a processor. The subject of the processing performed by executing a program may be a calculation unit, and may include a dedicated circuit that performs specific processing (e.g., an FPGA (Field-Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit)).

[0017] A program may be installed in a device such as a computer from a program source. The program source may be, for example, a program distribution server or a computer-readable storage medium. When the program source is a program distribution server, the program distribution server may include a processor and a storage resource for storing a program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. In the following description, two or more programs may be realized as one program, and one program may be realized as two or more programs.

[0018] In addition, the operational appliance, time adjustment appliance, operational application group, NTP server, etc. described in each of the following embodiments can be realized or stored by a general computer 1600 having, for example, a CPU 1601, memory 1602, an external storage device 1603 such as an HDD (Hard Disk Drive), a reading / writing device 1607 for reading and writing information from a portable storage medium 1608 such as a CD (Compact Disk) or USB memory, input devices 1606 such as a scanner, keyboard, and mouse, output device 1605 such as a display, a communication device 1604 such as a NIC (Network Interface Card) for connecting to a communication network, and an internal communication line (referred to as a system bus) 1609 such as a system bus that connects these together, as shown in Figure 14 (schematic computer diagram).

[0019] Various data (e.g., the time series DB 111 of the operation appliance 110, the time difference recording unit 122 of the time adjustment appliance 120, etc.) stored in or used in the systems and devices shown in the following embodiments can be realized by the CPU 1601 reading them from the memory 1602 or the external storage device 1603 and using them. Also, each functional unit of each system or device (e.g., the base / device time difference detection unit 121 and time stamp correction unit 123 of the time adjustment appliance 120, the operation information acquisition unit 141 and time difference detection unit 142 of the operation agent 140, etc.) can be realized by the CPU 1601 loading a predetermined program stored in the external storage device 1603 into the memory 1602 and executing it.

[0020] The above-mentioned predetermined program may be stored (downloaded) in the external storage device 1603 from the storage medium 1608 via the reading / writing device 1607 or from the network via the communication device 1604, and then loaded onto the memory 1602 and executed by the CPU 1601. Alternatively, the program may be directly loaded onto the memory 1602 from the storage medium 1608 via the reading / writing device 1607 or from the network via the communication device 1604, and executed by the CPU 1601.

[0021] In the following, we will give an example of the case where the appliances, agents, etc. that make up this system are configured on a single computer, but similar functions may be realized by distributing all or part of these functions across one or more computers, such as a cloud, and communicating with each other via a network. EXAMPLES

[0022] In this embodiment, information from each infrastructure device at a remote infrastructure site is collected at the operation site and stored in a time-series DB, and the time difference between the operation site and each infrastructure device at the infrastructure site is obtained and recorded, and when data is obtained from the time-series DB, the timestamp is corrected according to the data usage requirements.

[0023] FIG. 1 is a diagram showing a configuration of the first embodiment.

[0024] The first embodiment has one operation base 101, one or more infrastructure bases 102, and a management network 103 connecting them. As the management network 103, a network that securely connects the bases, such as a VPN (Virtual Private Network) or a dedicated line, may be used.

[0025] An operation appliance 110, a time adjustment appliance 120, an operation application group 130, and an NTP server 124 are operating at the operation base 101. The appliance is a HW (Hardware) device or a server device that virtually operates functions similar to those of a HW device. In this way, the remote operation system including the operation appliance 110 and the time adjustment appliance 120 is connected to the infrastructure base 102 via the management network 103.

[0026] The operation appliance 110 includes a time series DB 111 , a message hub 112 , and an operation dashboard 113 .

[0027] The time adjustment appliance 120 includes a base / device time difference detection unit 121 , a time difference recording unit 122 , and a time stamp correction unit 123 .

[0028] The operational application group 130 includes one or more operational applications. In this embodiment, a NW (Network) usage fee measurement application 131, an alert information collection application 132, and a troubleshooting application 133 are shown as examples.

[0029] An IT infrastructure 150, an operation agent 140, and an NTP server 143 are operating in the infrastructure base 102. As the IT infrastructure 150, a plurality of infrastructure devices 150 are operating.

[0030] The operation agent 140 includes an operation information acquisition unit 141 and a time difference detection unit 142 .

[0031] First, the acquisition of operation information in this example will be described. In the infrastructure base 102, the operation information acquisition unit 141 of the operation agent 140 acquires operation information from the infrastructure devices 150-1, 150-2, ... of the IT infrastructure 150, formats the data, and then transmits the formatted data to the message hub 112 via the management network 103. The operation information acquisition unit 141 uses a data collection tool such as Logstash to acquire event and alert information required for operation from the infrastructure device 150 using protocols such as SNMP (Simple Network Management Protocol), syslog, and telnet. Then, the operation information acquisition unit 141 assigns a time stamp according to the NTP server 143 of the infrastructure base 102, formats the format of the acquired information into a format such as JSON (JavaScript Object Notification) that can be inserted into the time-series DB 111, and transmits the format supported by the message hub, such as REST, AMQP, and Kafka. The message hub 112 receives the data and stores it in the time-series DB 111. The operation dashboard 113 displays operation information based on the contents of the time-series DB 111. In this manner, the operation information includes the above-mentioned event and alert information and time stamps associated with them. Furthermore, the time-series DB 111 is provided with time stamps in a plurality of time systems (for example, the time system of the infrastructure base 102-1 and the time system of the infrastructure base 102-2).

[0032] Next, the acquisition of time difference information in this example will be described. At the infrastructure site 102, the time difference detection unit 142 of the operation agent 140 collects the device setting time from the infrastructure devices 150-1, 150-2, ... of the IT infrastructure 150 and the site time from the NTP server 143, and transmits time information including the device setting time and the site time to the site / apparatus time difference detection unit 121 via the management network 103. The site / apparatus time difference detection unit 121 receives the time information and acquires the time information of the operation site from the NTP server 124. The site / apparatus time difference detection unit 121 calculates the time difference between them and stores it in the time difference recording unit 122 as time difference information.

[0033] Finally, the information reference of the time-series DB 111 from the operational application group 130 in this example will be described. In this example, the operational application group 130 includes a network usage measurement application 131, an alert information collection application 132, and a troubleshooting application 133. All of these applications obtain operation information stored in the time-series DB 111 in order to report operation information or to investigate the cause when a fault occurs. The time stamp correction unit 123 receives a request for information reference from the operational application group 130, refers to information in the time difference recording unit 122, corrects the time stamp according to the requirements of the application, and responds to the request by transmitting data to which the corrected time stamp has been added.

[0034] FIG. 2 is a sequence diagram showing an example of obtaining and recording time difference information.

[0035] First, the time difference detection unit 142 of the infrastructure base 102 triggers the start of a time difference detection sequence. As with NTP time correction, the trigger can be at regular intervals, or when the start time of an application requirement report is reached, or immediately before maintenance when a large number of operational events are expected to occur (201).

[0036] Next, the time difference detection unit 142 acquires the device set time from each of the infrastructure devices 150-1, 150-2, . . . of the IT infrastructure 150 (202).

[0037] Next, the time difference detection unit 142 acquires the time of the infrastructure base 102 from the NTP server 143 (203).

[0038] Next, the time difference detection unit 142 transmits the equipment setting time acquired in step 202 and the time of the infrastructure base 102 acquired in step 203 to the base / equipment time difference detection unit 121 of the operation base 101 as time information of the infrastructure base 102 (204).

[0039] Next, the site / device time difference detection unit 121 acquires the time of the operation site 101 from the NTP server 124 as time information of the operation site (205).

[0040] Finally, the base / device time difference detection unit 121 calculates the time difference 306 between the operation base 101, the infrastructure base 102, and each infrastructure device 150 from the time information acquired in steps 202, 203, and 205, and stores this as time difference information in the time difference recording unit 122 (206).

[0041] Figure 3 is an example of a time difference record.

[0042] The data recorded in the time difference recording unit 122 is managed in a table format, and holds columns of operation site time 301 , infrastructure site 302 , device ID 303 , device setting time 304 , infrastructure site time 305 , and time difference 306 .

[0043] In this example, the base / device time difference detection unit 121 calculates and records the difference between the operation base time 301 and the infrastructure base time 305 as the time difference 306. However, if the infrastructure base time 305 cannot be obtained because NTP is not available, the device setting time 304 is used instead to calculate the time difference 306.

[0044] Each of the rows 311-314... indicates information on the time difference obtained from each infrastructure device 150 of each infrastructure base 102. Rows 311 and 312 indicate an example in which the infrastructure device 150 is synchronized with the NTP server 143 and the time is roughly synchronized. For example, in row 311, the time difference 306 between the operation base time 301 "2021 / 08 / 31 09:00:00.111" and the infrastructure base time 305 "2021 / 08 / 31 09:00:01.500" is "+0.1389", indicating that the two times are roughly synchronized.

[0045] Moreover, lines 313 and 314 show an example in which the infrastructure site 102 does not have an NTP server 143, and the device setting time 304 of the infrastructure device 150 is off by minutes. For example, in line 313, the time difference 306 between the operation site time 301, "2021 / 08 / 31 09:30:00.122", and the device setting time 304, "2021 / 08 / 31 09:40:00.222", is "+10:00.100", indicating that the two times are not synchronized.

[0046] It should be noted that even if the information is about the time difference between the infrastructure devices 150, the time difference is expected to change depending on the calculation timing, so that old information is not immediately deleted but is continuously held.

[0047] FIG. 4 is a sequence diagram showing an example of correcting the timestamp when acquiring time-series DB data.

[0048] First, the operational application group 130 issues a data acquisition query to the time stamp corrector 123 (401).

[0049] Next, the time stamp correction unit 123 obtains data including operational information from the time series DB 111 (402), obtains time difference information including the time difference 306 from the time difference recording unit 122 (403), corrects the time stamp of the data (404), and returns the data with the corrected time stamp attached (405).

[0050] FIG. 5 is an example of a flowchart of the time stamp corrector 123 (step 404) shown in the example of FIG.

[0051] First, the timestamp correction unit 123 receives a data acquisition query for the time-series DB 111 from the operation application group 130. In this example, a REST acquisition query is shown, and the query is conditional on the infrastructure base in the URL path, the device name and time specified in the "query" key, the time system to which the data conforms in the "term" key (in this example, "monitoring_base" representing the operation base 101), the required accuracy (in this example, "0.1 sec"), and the correction method (in this example, "replace" which replaces the timestamp) (501). In step 501, "gt" stands for "Greater than" and "lt" stands for "Less than". Also, "10d" and "9d" stand for "10days" and "9days", respectively, and in this example, this indicates that the query is for acquiring data for one day from 10 days ago to the present.

[0052] Next, the time stamp correction unit 123 acquires data from the time series DB 111 according to the contents of the "query" key of the query received in step 501 (502). For example, the time stamp correction unit 123 acquires {"timestamp":"2021 / 09 / 10 10:10:10.001"} indicating the time stamp included in the operational information stored in the time series DB 111 and "info":{......}} indicating the event or alert information at that time. Such data is acquired for one day from 10 days ago to the present. The data in this example includes, for example, "infrabase_1_equipment_1" representing the infrastructure equipment 150-1 of the infrastructure site 102-1 as the time system according to the data.

[0053] Next, the time stamp correction unit 123 determines whether the query received in step 501 is a query that compiles data for a certain period and returns it, or whether the compilation period is shorter than the accuracy required by the query (503). This is because the time series DB 111 is not necessarily intended to return individual data one by one. For example, for visualization purposes, etc., an overview such as the number of data, average value, or median value may be calculated for data including multiple events or alert information acquired every hour, and the result may be used as the answer to the query. In such a case, if the data is compiles and the compilation period is longer than the required accuracy, it can be determined that there is no need to correct the time stamp.

[0054] In other words, in step 503, if the query received in step 501 requests that the operational appliance 110 return data from the time series DB 111 for a certain period of time (if condition A is satisfied), or if the operational appliance 110 is consolidating data from the time series DB 111 and the period is not shorter than the accuracy requested in the query (if condition B is satisfied), the time stamp correction unit 123 determines that there is no need to correct the time stamp and proceeds to step 506 (503; YES).

[0055] On the other hand, if the query received in step 501 does not satisfy the above condition A or does not satisfy the above condition B, the time stamp correction unit 123 determines that it is necessary to correct the time stamp, and proceeds to step 504 (503; NO). The above conditions A and B are specified in the query, as in steps 501 and 502.

[0056] Next, the time stamp correction unit 123 acquires from the time difference recording unit 122 time difference information including the time difference 306 near the time of the time stamp that satisfies the condition specified in the query from the data acquired in step 502 (504). In this example, the time difference 306 between the operation base 101 and the infrastructure base 102 is acquired according to the query received in step 501. Here, it is shown that the time difference information "{"2021 / 09 / 10AM":{"equipment_1":"+1.1000s"}}" was acquired. If multiple time differences are recorded near the relevant time, the average value or median value is calculated to calculate the most likely time difference. In addition, although the time difference is acquired in JSON format in this example, the data type of the response is not limited to that.

[0057] Next, the timestamp correction unit 123 checks whether the timestamp included in the data acquired in step 502 has been corrected by determining whether the time system of the timestamp included in the data acquired in step 502 (in this example, infrastructure device 150-1 at infrastructure site 102-1) is different from the time system presented in the query in step 501 (in this example, operation site 101) and whether the time difference is greater than the required accuracy (505).

[0058] For example, when the operation agent 140 follows the NTP server 124 of the operation base 101 via the management network 103, the time stamp correction unit 123 may have been given a time stamp of the time system of the operation base 101 from the beginning. For example, the time stamp correction unit 123 reads information such as "infrabase_1" (identification information of the infrastructure base 102) related to the time system to be followed, which is recorded in the data acquired in step 502. The time stamp correction unit 123 judges whether the read information related to the time system to be followed differs from the information related to the time system to be followed specified in the query received in step 501 (for example, "monitoring_base" representing the operation base 101), and if it is judged that the two differ, it further confirms that the difference between the time stamp of the data acquired in step 502 and the time of the NTP server 124 of the operation base 101, i.e., the time difference 306 between the operation base 101 and the infrastructure base 102, is greater than the required accuracy specified in the query received in step 501. In the above example, since the two do not match, the process proceeds to step 507.

[0059] That is, in step 505, if the condition that the information on the time system to be followed is different from the information on the time system to be followed specified in the query received in step 501 is satisfied (if condition C is satisfied), and if condition C is satisfied and further the condition that the time difference 306 between the operation base 101 and the infrastructure base 102 is greater than the required accuracy specified in the query received in step 501 is satisfied (if condition D is satisfied), the time stamp correction unit 123 proceeds to step 507 (505; YES). On the other hand, if neither condition C nor condition D is satisfied in step 505, the time stamp correction unit 123 determines that it is not necessary to correct the time stamp, and proceeds to step 506 (505; NO).

[0060] Next, if the timestamp correction unit 123 determines in step 505 that the timestamp needs to be corrected, it corrects the timestamp according to the correction method specified in the query received in step 501, and returns the data with the corrected timestamp to the operational application group 130 (507).

[0061] In this example, since the modification method specified in the query received in step 501 is "replace", the time stamp modification unit 123 calculates a modified time stamp {"timestamp": "2021 / 09 / 10 10:10:11.101"} by adding {"2021 / 09 / 10AM":{"equipment_1":"+1.1000s"}}" indicating the time difference 306 between the operation site 101 and the infrastructure site 102 obtained in step 504 to {"timestamp":"2021 / 09 / 10 10:10:10.001"} indicating the time stamp of the data obtained in step 502. Then, the time stamp modification unit 123 transmits the data having the modified time stamp obtained by the above calculation to the operation application group 130.

[0062] In this example, the timestamp is replaced, but other possible methods of modification include listing the pre-modification and post-modification timestamps side by side using different key names, or adding an offset using a different key.

[0063] If it is determined that there is no need to modify the timestamp, the timestamp corrector 123 returns the data acquired in step 502 to the operational application group 130 as is (506). EXAMPLES

[0064] In this embodiment, not only the data in the time-series DB 111 but also the time stamps of information such as logs acquired by the operational applications group 130 individually from the infrastructure devices 150 of the infrastructure bases 102 are corrected to a different time system.

[0065] FIG. 6 is a sequence diagram of an example of correcting the timestamp of individually acquired data.

[0066] First, the operational application group 130 individually acquires information such as a log with a time stamp from the infrastructure device 150 (601). In this example, the operational application group 130 acquires, for example, "2021 / 09 / 11 20:20:10.002 "info..."" from the infrastructure device 150 as the information such as the log.

[0067] The reason why the operation application group 130 directly acquires information such as logs from the infrastructure device 150 is as follows. That is, the information to be stored in the time-series DB 111 is acquired by the operation information acquisition unit 141 of the operation agent 140. The operation information acquisition unit 141 does not send all information in consideration of the load on the infrastructure device 150 and the capacity of the time-series DB 111, but basically transmits only information with a high priority in operation. However, when responding to a failure or maintenance, other detailed information is also required, so the operation information acquisition unit 141 acquires information individually according to the situation.

[0068] Next, the operational application group 130 sends a timestamp correction request to the timestamp correction unit 123 (602). The timestamp of the information acquired in step 601 is given with the device setting time of the infrastructure device 150. However, for example, when comparing with log information acquired from other infrastructure devices 150-n or verifying the order relationship with nearby events at the operational base 101, it becomes necessary to correct the time system. For this reason, the operational application group 130 sends the above correction request to the timestamp correction unit 123.

[0069] Next, the time stamp correction unit 123 obtains the time difference information from the time difference recording unit 122 (603), corrects the time stamp (604), and returns the corrected time stamp by, for example, sending data with the corrected time stamp attached (605).

[0070] FIG. 7 is an example of a flowchart of the time stamp corrector 123 (step 602) shown in the example of FIG.

[0071] First, the timestamp correction unit 123 receives a timestamp correction request from the operation application group 130 (701). In this example, a correction request in REST is indicated, and the URL path indicates the timestamp correction request, the "term" key indicates the original time system (the time system of the information acquired in step 601; in this example, "equipment_1_1"), the time system to be followed after correction (in this example, "monitoring_base" representing the operation base 101), and the requested accuracy (in this example, "0.1 sec"). In addition, the "timestamp" key specifies the timestamp to be corrected. In this example, the timestamp correction unit 123 receives the timestamp correction request including, for example, "2021 / 09 / 11 20:20:10.002" indicating the timestamp included in the information such as the log acquired in step 601.

[0072] Next, similar to step 504, the time stamp correction unit 123 acquires from the time difference recording unit 122 time difference information including the time difference 306 near the time of the timestamp for which the correction request was received in step 701 (702). In this example, in accordance with the time stamp correction request received in step 701, the time difference 306 corresponding to a time within a predetermined range (e.g., 5 minutes) including the time indicated by the timestamp included in the log or other information is acquired from the time difference recording unit 122. This example shows that the time stamp correction unit 123 acquired "{"2021 / 09 / 11PM":{"equipment_1":"+2.1000s"}}" as the time difference 306.

[0073] Next, the time stamp correction unit 123 judges whether or not the time difference acquired in step 702 is greater than the required accuracy of the correction request received in step 701, thereby determining whether or not the time stamp needs to be corrected (703). That is, if the time stamp correction unit 123 determines that the time difference acquired in step 702 is greater than the required accuracy of the correction request received in step 701, it determines that the required accuracy is not met and therefore correction is necessary, and proceeds to step 704 (703; YES). On the other hand, if the time stamp correction unit 123 determines that the time difference acquired in step 702 is not greater than the required accuracy of the correction request received in step 701, it determines that the required accuracy is met and therefore correction is unnecessary, and proceeds to step 705 (703; NO).

[0074] Next, if the timestamp correction unit 123 determines that the timestamp needs to be corrected, it corrects the timestamp to satisfy the correction request received in step 701, and returns the data with the corrected timestamp to the operational application group 130 (704).

[0075] In this example, the time stamp correction unit 123 adds the time difference "{"2021 / 09 / 11PM":{"equipment_1":"+2.1000s"}}" acquired in step 702 to the time stamp ""2021 / 09 / 11 20:20:10.002"" included in the correction request received in step 701, and calculates the corrected time stamp ""2021 / 09 / 11 20:20:12.102". Then, the time stamp correction unit 123 transmits data having the corrected time stamp obtained by the above calculation to the operational application group 130. Note that in this example, only the corrected time stamp is returned, but it is also possible to simplify handling by listing the time stamps before and after correction side by side or adding information such as the number of lines.

[0076] On the other hand, if it is determined that the time stamp needs not to be modified, the time stamp corrector 123 notifies the operational application group 130 accordingly (705). EXAMPLES

[0077] In this embodiment, when the operation information acquisition unit 141 creates data of operation information to be stored in the time-series DB 111, the operation information acquisition unit 141 stores the data in the time-series DB 111 with a time stamp of the operation base so that the time difference can be traced later. This embodiment assumes that the data acquisition tool of the operation information acquisition unit 141 can be modified. In addition, if the time stamp of the operation base is added to all data stored in the time-series DB 111 and there is no large blank time of a predetermined threshold or more for the data, the time stamp shown in the first and second embodiments can be corrected based on the data of the time-series DB 111. However, access to the time-series DB 111 does not necessarily acquire all data for each item. In addition, access to acquire data summarized in the time direction is mainstream, and if many data acquisitions for each item are operated in parallel every time the time stamp is corrected, the access load to the time-series DB 111 may double. For this reason, when correcting the time stamp, a determination is made as to whether to use the time difference recording unit 122 or the data of the time-series DB 111 according to the requirements.

[0078] FIG. 8 is a sequence diagram showing an example in which the operation information acquiring unit 141 stores data in the time-series DB 111 together with a time stamp of the operation base.

[0079] First, the operation information acquisition unit 141 collects (801) operation information from the infrastructure device 150. The method of acquiring this information is the same as in the first embodiment.

[0080] Next, the operation information acquisition unit 141 acquires the time information of the operation base 101 via the time difference detection unit 142 (802).

[0081] Next, the operation information acquisition unit 141 performs data reformatting in the same manner as in the first embodiment, and at that time also writes down the time information of the operation base 101 acquired in step 802 (803), and transmits the data to the time series DB 111 via the message hub 112 (804). Here, the operation information acquisition unit 141 acquires data 804a in which the time stamp of the operation site 101, "monitorzone_timestamp": "2021 / 09 / 20 15:01:10.001", "info":{......}}", included in the operation information acquired from the infrastructure device 150 of the infrastructure site 102, is added to the data 804a in which the time stamp of the operation site 101, "monitorzone_timestamp": "2021 / 09 / 20 15:01:09.501", included in the time information acquired from the NTP server 124 of the operation site 101, is added to "{"timestamp": "2021 / 09 / 20 15:11:11.111", "info":{......}}", 15:01:10.611"}" is added to data 804b. In this example, the timestamps for multiple infrastructure locations and infrastructure devices, including infrastructure devices at infrastructure locations 102-1 and 102-2, are included as infrastructure devices 150 at infrastructure location 102.

[0082] It should be noted that "info":{......}" is event or alert information of the infrastructure base, as in the case of the embodiment 1. In this embodiment, since the time information of the operation base 101 is associated with each event or alert information of the infrastructure base, the time difference can be grasped for each event or alert.

[0083] 9 is an example of a flowchart for correcting the timestamp of data in the time-series DB 111 in accordance with application requirements when the data stored in the time-series DB 111 includes not only the timestamp of the infrastructure site 102 but also the timestamp of the operation site 101. This process is performed by the timestamp correction unit 123, but many parts are similar to those in FIG. 5 of the first embodiment, so the following description will focus on the differences.

[0084] Steps 901 to 903 are partially similar to steps 501 to 503 in FIG.

[0085] That is, the time stamp corrector 123 receives a data acquisition query for the time-series DB 111 from the operational application group 130 (901). This example shows a REST acquisition query, and the query is based on the infrastructure site in the URL path, the device name and time specification in the "query" key (in this example, "infrabase_1_equipment_1" indicating the infrastructure equipment at infrastructure site 102-1 and the time from the present to 10 days ago {"gt":"now-10d", "lt":"now"}, and the time system to which the data follows in the "term" key (in this example, the infrastructure equipment at infrastructure site 102-2, "infrabase_2_equipment_2"), the requested accuracy (in this example, "0.001 sec"), and the correction method (in this example, "replace" indicating replacement of the timestamp). In other words, this shows that the query received in step 901 is a query requesting to replace the timestamps of the infrastructure equipment at infrastructure site 102-1 from the present to 10 days ago with the timestamps of the infrastructure equipment at infrastructure site 102-2 with an accuracy of 0.001 seconds.

[0086] Next, the time stamp correction unit 123 acquires data from the time-series DB 111 according to the contents of the "query" key of the query received in step 901 (902). For example, the time stamp correction unit 123 acquires the time stamp "2021 / 09 / 20 15:01:09.501" of the operation base 101 and the time stamp "timestamp": "2021 / 09 / 20 15:01:10.001" of the infrastructure base 102-1 "infrabase_1_equipment_1" contained in the operation information transmitted in step 804 of Fig. 8 and stored in the time-series DB 111, and "info": {......}} indicating the event and alert information at the relevant time point.

[0087] Then, the time stamp corrector 123 receives the data acquisition query of the time-series DB 111, and similarly to the first embodiment, if the query received in step 901 requests that the operational appliance 110 return data of the time-series DB 111 in a certain period (if condition A is satisfied), or if the operational appliance 110 has summarized the data of the time-series DB 111 and the period is not shorter than the accuracy required by the query (if condition B is satisfied), the time stamp corrector 123 determines that it is not necessary to correct the time stamp, and proceeds to step 909 (903; YES). On the other hand, if the query received in step 901 does not satisfy the above condition A or does not satisfy the above condition B, the time stamp corrector 123 determines that it is necessary to correct the time stamp, and proceeds to step 904 (903; NO).

[0088] Next, the timestamp correction unit 123 acquires from the time series DB 111 event data that is relatively close to the timestamp of the data acquired in step 902, and includes the timestamp of the infrastructure equipment at infrastructure site 102-2, which is the time system specified for correction (e.g., “infrabase_2_equipment_2”, “timestamp”: “2021 / 09 / 20 14:30:05.000”) and the timestamp of the operation site's time system (e.g., “monitorzone_timestamp”: “2021 / 09 / 20 14:30:07.001”) (904).

[0089] Furthermore, the time stamp corrector 123 determines whether or not there is a certain amount of time difference between the time stamp of the data acquired in step 902 and the data acquired in step 904 (905). In this example, the time stamp corrector 123 determines whether or not there is a certain amount of time difference between the time stamp of the infrastructure equipment "infrabase_1_equipment_1" of the infrastructure base 102-1 acquired in step 902 and the time stamp of the infrastructure equipment "infrabase_2_equipment_2" of the infrastructure base 102-2 acquired in step 904.

[0090] If time stamp correction unit 123 determines that the time stamp of the data acquired in step 902 and the data acquired in step 904 are not different by a certain amount (905; YES), it determines that time stamps can be corrected between infrastructure locations and between infrastructure devices. Then, in accordance with the request of the query received in step 901, time stamp correction unit 123 corrects the time stamp of the infrastructure device of infrastructure location 102-1 acquired in step 902 to the time stamp of the infrastructure device of infrastructure location 102-2 acquired in step 904, and responds to the request by transmitting data with the corrected time stamp attached (906).

[0091] On the other hand, if the time stamp correction unit 123 determines that the time stamp of the data acquired in step 902 and the data acquired in step 904 are different by a certain amount or more (905; NO), it determines that time stamp correction between infrastructure bases and between infrastructure devices is not possible. Then, the time stamp correction unit 123 acquires from the time difference recording unit 122 the time difference between the time stamp of the infrastructure device infrastructure_2_equipment_2 of the infrastructure base 102-2, which is the time system specified to be corrected in the query received in step 901, and the time stamp of the time system of the operation base acquired in step 902. For example, the time stamp correction unit 123 acquires {"2021 / 09 / 20 PM":{"equipment_1":"-2.000s"}} calculated by the time difference recording unit 122 (907).

[0092] Then, the timestamp correction unit 123 considers the timestamp obtained by adding the difference obtained in step 907 to the timestamp of the infrastructure equipment at infrastructure site 102-1 obtained in step 902 to be the timestamp of the infrastructure equipment at infrastructure site 102-2, and responds to the above request by, for example, sending data to which the considered timestamp has been attached (908).

[0093] If the time stamp corrector 123 determines that it is not necessary to correct the time stamp (903; YES), it returns the data acquired in step 902 to the operational application group 130 as is (909), as in the first embodiment.

[0094] This sequence makes it possible to correct the timestamp while reducing the load of accessing the time-series DB 111 by obtaining reference data only when necessary, without obtaining reference data from the time-series DB 111 every time the timestamp is corrected. EXAMPLES

[0095] In the first to third embodiments, the timestamp is corrected when data is acquired from the time-series DB 111. However, in terms of data management, it is effective for load balancing to separate frequently accessed data, perform necessary corrections in advance, and create sub-datasets, rather than always accessing a DB that centrally manages all data. An ETL (Extract, Transfer, Load) tool is often used as a tool for creating sub-datasets, and in this embodiment, it is assumed that the timestamp required for conversion to a sub-dataset is also changed. In addition, in data management, a component that centrally manages all data, such as the time-series DB 111, is sometimes called a "data lake," and a component that is separated and formatted to be easy to refer to, such as a sub-dataset, is sometimes called a "data warehouse" or "data mart."

[0096] Fig. 10 is a system configuration diagram for creating a sub data set from a time series DB 111. The difference from the system configuration diagram of the first embodiment shown in Fig. 1 is that the operation appliance additionally includes a sub data time series DB 1001 and a sub data set forming unit 1002. The time adjustment appliance 120 may be provided with a base / device time difference detection unit 121.

[0097] 11A and 11B are sequence diagrams of an example of creating a sub-dataset from the time-series DB 111. FIG.

[0098] 11A, the sub data set forming unit 1002 triggers the start of adding a sub data set (1101). As the trigger, various conditions are assumed, such as every certain time or after a certain number of data are added to the time-series DB 111.

[0099] Next, the sub-dataset forming unit 1002 acquires (1102) original data for the sub-dataset from the time-series DB 111. This acquisition method is similar to the procedure of step 502 in FIG.

[0100] Next, the sub data set forming unit 1002 acquires time difference information near the timestamp of the sub data set to be added from the time difference recording unit 122 in order to correct the timestamp (1103). This acquisition method is similar to, for example, the procedure of step 504 in FIG. 5 in the first embodiment.

[0101] Next, the sub data set forming unit 1002 shapes the sub data set (1104). This shaping is similar to the shaping method in step 507 of FIG. 5 in the first embodiment, for example, and adds or replaces data according to expected application requirements. After that, the sub data set forming unit 1002 adds the sub data set to the sub data time series DB 1101. In this example, the data is edited as the sub data set by adding the timestamp of the operation base (1105).

[0102] FIG. 11A illustrates a case where data is stored in the time-series DB 111 without the timestamp of the operation base being written thereto, as in the case of the first and second embodiments. However, the same can be considered for a case where data with the timestamp of the operation base written thereto is stored in the time-series DB 111, as in the case of the third embodiment shown in FIG. 11B.

[0103] 11B, the sub data set forming unit 1002 triggers the start of adding a sub data set (1101). As in the case of FIG. 11A, the trigger can be any of a variety of conditions, such as every certain time or after a certain number of data items are added to the time-series DB 111.

[0104] Next, the sub-dataset forming unit 1002 acquires original data for the sub-dataset from the time-series DB 111 (1102b). This acquisition method is similar to the procedure of step 902 in FIG. 9 in the third embodiment, for example. In FIG. 11B, unlike FIG. 11A, in step 1102b, for example, the timestamp “2021 / 09 / 20 15:01:09.501” of the operation base 101 and the timestamp “timestamp”: “2021 / 09 / 20 15:01:10.001” of the infrastructure base 102-1 “infrabase_1_equipment_1” included in the operation information stored in the time-series DB 111, and “info”: {......}} indicating the event and alert information at the time are acquired.

[0105] Next, the sub data set forming unit 1002 acquires time difference information near the timestamp of the sub data set to be added from the time difference recording unit 122 in order to correct the timestamp (1103b). This acquisition method is similar to the procedure of, for example, step 907 in FIG. 9 in the third embodiment.

[0106] Next, the sub data set forming unit 1002 shapes the sub data set (1104b). This shaping is, for example, similar to the shaping method in step 908 of FIG. 9 in the third embodiment, and data is added or replaced according to expected application requirements. After that, the sub data set forming unit 1002 adds the sub data set to the sub data time series DB 1101. In this example, the data is edited as the sub data set by adding a time stamp for the infrastructure site 102-2 in addition to the time stamp for the operation site (1105b).

[0107] Sub-datasets are created as described above. Of course, there is not only one sub-dataset, and individual sub-datasets may be created according to the requirements of the application. In addition, it is expected that the method of using data will change depending on the purpose, such as a data set that consolidates necessary parts of data from multiple infrastructure devices 150 and multiple infrastructure sites 102, unifies timestamps, and centrally visualizes the main chronological order. EXAMPLES

[0108] In the first to fourth embodiments, the time adjustment appliance 120 operates as a black box function, but it is also assumed that the time adjustment appliance 120 is separated from the operation appliance 110 so that it can operate in combination with the operation appliance 110 and the operation application group 130. In this embodiment, a setting GUI for the time adjustment appliance 120 is used to set the requirements for timestamp adjustment for each application in advance, enabling flexible cooperation with the applications.

[0109] 12 is a system configuration diagram for setting requirements for time stamp adjustment for each application in a time adjustment appliance. As a difference from the first embodiment, the time adjustment appliance 120 includes a per-application requirement setting unit 1202 and a per-application requirement recording unit 1203. Furthermore, the time adjustment appliance 120 includes a setting GUI 1201 for setting the per-application requirement setting unit 1202.

[0110] FIG. 13 shows an example of a GUI for setting requirements for timestamp adjustment for each application in a time adjustment appliance.

[0111] For example, the application requirement setting unit 1202 holds this data in a table format including, as rows, an application name 1301, application specifications 1302, a time system to be matched 1303, a required accuracy 1304, a correction method 1305, and other items 1306. After accepting an operation from a user via an input device 1606 to set items in each row, the application requirement setting unit 1202 accepts pressing of a decision button 1321 to reflect the setting of each of the above items and displays the information on an output device 1605. The application requirement setting unit 1202 records the set items as they are in the application requirement recording unit 1203 (a table such as a database). As described in step 501, step 901, etc., when the time stamp correction unit 123 receives a data acquisition query for the time-series DB 111 from the operational application group 130, the time stamp correction unit 123 selects an application by referring to the application name 1301 and application specifications 1302 included in the query, and generates time stamp correction requirements similar to those in the first embodiment by referring to the time system 1303 to be matched, the required accuracy 1304, and the correction method 1305.

[0112] As described above, according to the present system, for example, in the case of managing operation information using an IT infrastructure remote operation system that connects and operates remote IT infrastructures via a management network such as a VPN, and a time-series DB (Database), the time difference between each infrastructure base or device and the operation base is recorded, and when outputting data, the recorded time difference information is used to correct the data, thereby making it possible to smoothly refer to data according to the purpose of data use in a time-series DB where timestamps in multiple time systems are mixed.

[0113] For example, as described in the first embodiment, in the present system, in a remote operation system that manages data obtained via a network from an infrastructure base (e.g., infrastructure base 102) that operates one or more infrastructure devices (e.g., infrastructure devices 150-1 and 150-2) by a computer, a time-series DB (e.g., a DB that stores data in the format described in step 502 of FIG. 5) that accumulates and stores operation information in which the data (e.g., event and alert information) obtained from the infrastructure device is time-stamped with the infrastructure base or the infrastructure device, and a time-series DB that stores and stores operation information in which the data (e.g., event and alert information) obtained from the infrastructure device is time-stamped with the timestamp of ... a time difference detection unit (e.g., the base / device time difference detection unit 121) that calculates the difference between a timestamp acquired from the application (e.g., the NW usage fee measurement application 131, the alert information collection application 132, the troubleshooting application 133) and a time system (e.g., “monitoring_base” specified in step 501 of FIG. 5) to which the data of the infrastructure device used in the application (e.g., the NW usage fee measurement application 131, the alert information collection application 132, the troubleshooting application 133) conforms and a data acquisition range (e.g., “timestamp”:{“gt”:”now-10d”, and a timestamp correction unit (e.g., the timestamp correction unit 123) that corrects the timestamp of the data in the acquisition range by using the difference when the timestamp of the data in the acquisition range acquired from the time-series DB in accordance with a data acquisition request (e.g., the data acquisition query in step 501) including a specification of {{timestamp ":"now"}} satisfies a predetermined condition (e.g., condition C and condition D shown in step 505 of FIG. 5). Thus, the time system of the data in the time-series DB to which timestamps of multiple time systems are assigned can be corrected according to requirements required by an application or the like.

[0114] As described in the second embodiment, the infrastructure device outputs the data with a time stamp (for example, the log information shown in step 601 in FIG. 6), and the time stamp correction unit acquires the data with the time stamp from the infrastructure device, and corrects the time stamp included in the acquired data by using the difference. Therefore, the operation application group 130 can correct the time stamp to another time system by using information such as a log acquired individually from the infrastructure device 150 of each infrastructure base 102, without using data of a time-series DB.

[0115] As described in the third embodiment, the timestamp correction unit receives the data acquisition request including an infrastructure device that outputs a timestamp (e.g., the timestamp of "infrabase_2_equipment_2" shown in step 901 of FIG. 9) that is a reference for correcting the timestamp of the infrastructure device used in the application (e.g., the timestamp of "infrabase_1_equipment_1" shown in step 901 of FIG. 9), and if the predetermined condition is satisfied, acquires data including the timestamp of the infrastructure device that outputs the reference timestamp and the timestamp of the time synchronization server from the time-series DB, and corrects the timestamp of the infrastructure device used in the application to the reference timestamp as described in step 906 of FIG. 9 if there is no difference between the two timestamps by a certain time or more (e.g., YES in step 905 of FIG. 9). Therefore, it is possible to correct timestamps between infrastructure bases and between infrastructure devices while maintaining a certain degree of accuracy.

[0116] Furthermore, if there is a gap of a certain time or more between the two timestamps (for example, NO in step 905 of FIG. 9), the timestamp correction unit corrects the timestamp of the infrastructure device used in the application using the difference between the reference timestamp and the timestamp of the time synchronization server at the operation base (for example, the time difference calculated in step 907). Therefore, even if timestamp correction between infrastructure bases and infrastructure devices is not possible, it is possible to correct the timestamp using the time synchronization server at the operation base while maintaining a certain level of accuracy.

[0117] Moreover, the infrastructure base has an operation information acquisition unit (e.g., operation information acquisition unit 141) that writes data in which the timestamp of the infrastructure device used in the application is associated with the timestamp of the time synchronization server (e.g., data 804a in step 804 shown in FIG. 8) and data in which the timestamp of the infrastructure device that outputs the reference timestamp is associated with the timestamp of the time synchronization server (e.g., data 804b in step 804 shown in FIG. 8) into the time-series DB. Therefore, it becomes possible to grasp the time difference in units of events or alerts.

[0118] The present invention is not limited to the above-described embodiments as they are, and in the implementation stage, the components can be modified and embodied within the scope of the gist of the present invention, or multiple components disclosed in the above-described embodiments can be appropriately combined. [Explanation of symbols]

[0119] 101 Operational bases 102 Infrastructure base 103 Management Network 110 Operational Appliances 111 Time Series DB 112 Message Hub 113 Operational Dashboard 120 Time Adjustment Appliance 121 Base / device time difference detection unit 122 Time differential recording section 123 Timestamp correction section 124 NTP servers 130 Operational Applications 131 Network usage fee measurement app 132 Alert information collection app 133 Troubleshooting App 140 Operational Agent 141 Operational Information Acquisition Department 142 Time difference detection unit 143 NTP Server 150 IT Infrastructure 150-1, 150-2 Infrastructure equipment

Claims

1. A remote operation system that manages data obtained via a network from an infrastructure site that operates one or more infrastructure devices using a computer, a time-series DB that accumulates and holds operation information in which a timestamp obtained from the infrastructure site is added to data obtained from the infrastructure device; a time difference detection unit that calculates a difference between a time stamp acquired from the infrastructure site or the infrastructure device and a time stamp of a time synchronization server of the operation site of the remote operation system; a timestamp correction unit that corrects a timestamp of data in an acquisition range acquired from the time-series DB according to a data acquisition request received from an application, the timestamp including a time system according to which data of the infrastructure device used in the application conforms and a designation of a data acquisition range, when a timestamp of the data in the acquisition range acquired from the time-series DB and the difference satisfy a predetermined condition; A remote operation system comprising:

2. 2. The remote operation system according to claim 1, The infrastructure device outputs the data with a time stamp attached thereto; the time stamp correction unit acquires the data to which the time stamp is attached from the infrastructure device, and corrects the time stamp included in the acquired data by using the difference. A remote operation system comprising:

3. 2. The remote operation system according to claim 1, the timestamp correction unit receives the data acquisition request including an infrastructure device that outputs a reference timestamp for correcting the timestamp of the infrastructure device used in the application, and if the predetermined condition is satisfied, acquires from the time-series DB the reference timestamp and the timestamp of the infrastructure device used in the application, and if there is no difference of a certain time or more between the two timestamps, corrects the timestamp of the infrastructure device used in the application to the reference timestamp. A remote operation system comprising:

4. 4. The remote operation system according to claim 3, the time stamp correction unit corrects the time stamp of the infrastructure device used in the application by using a difference between the reference time stamp and a time stamp of the time synchronization server at the operation site when there is a difference of a certain time or more between the two time stamps. A remote operation system comprising:

5. 4. The remote operation system according to claim 3, an operation information acquisition unit that writes data in which a timestamp of the infrastructure device used in the application is associated with a timestamp of the time synchronization server, and data in which a timestamp of an infrastructure device that outputs the reference timestamp is associated with a timestamp of the time synchronization server, into the time-series DB; A remote operation system comprising:

6. A time stamp correction method performed by a computer in a remote operation system that manages data obtained via a network from an infrastructure site that operates one or more infrastructure devices, comprising: a time difference detection unit calculates a difference between a time stamp acquired from the infrastructure site or the infrastructure device and a time stamp of a time synchronization server at the operation site of the remote operation system; a time stamp correction unit, in accordance with a data acquisition request received from an application, including a time system according to which data of the infrastructure device used in the application conforms and a designation of a data acquisition range, corrects the time stamp of the data in the acquisition range using the difference when a predetermined condition is satisfied between the time stamp of the data in the acquisition range acquired from a time-series DB that accumulates and holds operation information to which a time stamp of the infrastructure site or the infrastructure device is added, and the difference.

2. A method for correcting a time stamp comprising:

7. 7. A method for correcting a time stamp according to claim 6, comprising the steps of: The infrastructure device outputs the data with a time stamp; the time stamp correction unit acquires the data to which the time stamp is attached from the infrastructure device, and corrects the time stamp included in the acquired data by using the difference; 2. A method for correcting a time stamp comprising:

8. 7. A method for correcting a time stamp according to claim 6, comprising the steps of: the timestamp correction unit receives the data acquisition request including an infrastructure device that outputs a reference timestamp for correcting the timestamp of the infrastructure device used in the application, and if the predetermined condition is satisfied, acquires from the time-series DB the reference timestamp and the timestamp of the infrastructure device used in the application, and if there is no difference of a certain time or more between the two timestamps, corrects the timestamp of the infrastructure device used in the application to the reference timestamp.

2. A method for correcting a time stamp comprising:

9. 9. A method for correcting a time stamp according to claim 8, comprising the steps of: the time stamp correction unit corrects the time stamp of the infrastructure device used in the application using a difference between the reference time stamp and a time stamp of the time synchronization server at the operation site when there is a difference of a certain time or more between the two time stamps; 2. A method for correcting a time stamp comprising:

10. 9. A method for correcting a time stamp according to claim 8, comprising the steps of: an operation information acquisition unit of the infrastructure base writes data in which a timestamp of the infrastructure device used in the application is associated with a timestamp of the time synchronization server, and data in which a timestamp of the infrastructure device that outputs the reference timestamp is associated with a timestamp of the time synchronization server, into the time-series DB; 2. A method for correcting a time stamp comprising:

11. On the computer, A process of calculating a difference between a timestamp acquired from an infrastructure site that operates one or more infrastructure devices or from the infrastructure devices and a timestamp of a time synchronization server of an operation site that a remote operation system has, which manages data acquired via a network from the infrastructure site that operates one or more infrastructure devices; a process of correcting a timestamp of data in the acquisition range obtained from a time-series DB that accumulates and holds operation information to which a timestamp of the infrastructure site or the infrastructure device is added, in accordance with a data acquisition request received from an application and including a designation of a time system to which data of the infrastructure device used in the application conforms and a data acquisition range, when the difference satisfies a predetermined condition; A time stamp correction program for causing the program to execute the steps described above.

Images