Recording instrument, backup method, and backup program

Abstract

To realize facilitation of introduction of a backup function.SOLUTION: A recording instrument comprises a collecting unit for collecting measurement data, a recording unit for recording the measurement data, and a transmitting unit for transmitting backup data duplicated from the measurement data to another recording instrument connected via a network.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a recorder, a backup method, and a backup program. [Background technology]

[0002] In the industrial measurement field, various measurements are performed using sensors and transducers, such as temperature, pressure, flow rate, level, strain, acceleration, pH, and humidity. Various types of recorders, such as recorders, paperless recorders, and data loggers, are available to record this measurement data.

[0003] Such recorders are provided with a backup function that backs up recorded data in preparation for risks such as power outages, malfunctions, corruption of digital data, etc. For example, the recorder accumulates measurement data collected via input / output, communication, calculation, and other channels to create a data file, and then sends a copy of this data to a server device for backup. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-62298 [Patent Document 2] Japanese Patent Publication No. 2022-125741 Summary of the Invention [Problem to be solved by the invention]

[0005] However, the backup function requires a server device at the back end, which hinders the introduction of the backup function.

[0006] That is, when installing a server device, various settings related to file transfers and the like must be configured on both the server and the client recorder sides, which is costly not only financially but also in terms of time and labor.

[0007] As just one example, if files are transferred using FTP (File Transfer Protocol), the following settings are required on both the FTP server and the FTP client. For example, on the server device side, it is necessary to install FTP server software, register users, set directories, etc. On the other hand, on the client recorder side, it is also necessary to set the destination server, port number, user, password, path, etc.

[0008] An object of the present invention is to facilitate the introduction of a backup function. [Means for solving the problem]

[0009] A recorder according to one aspect includes a collection unit that collects measurement data, a recording unit that records the measurement data, and a transmission unit that transmits backup data, which is a copy of the measurement data, to another recorder connected to the recorder via a network.

[0010] In one aspect of the backup method, a recorder collects measurement data, records the measurement data, and transmits backup data, which is a copy of the measurement data, to another recorder connected to the recorder via a network.

[0011] A backup program according to one aspect causes a recorder to execute processes of collecting measurement data, recording the measurement data, and transmitting backup data in which the measurement data is copied to another recorder connected to the recorder via a network. [Effects of the Invention]

[0012] According to one embodiment, it is possible to easily implement a backup function. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram illustrating an example of a use case of a recorder. [Figure 2] FIG. 2 is a block diagram showing an example of the functional configuration of the recorder. [Figure 3] FIG. 3 is a diagram showing the detailed configuration of each unit related to the backup function. [Figure 4] FIG. 4 is a flowchart showing the procedure of the data recording process. [Figure 5] FIG. 5 is a flowchart showing the procedure of the device identification information transmission process. [Figure 6] FIG. 6 is a flowchart showing the procedure of the device identification information receiving process. [Figure 7] FIG. 7 is a diagram illustrating an example of a schema of a connected device list. [Figure 8] FIG. 8 is a diagram illustrating an example of state transition of the connected device list. [Figure 9] FIG. 9 is a flowchart showing the procedure of the backup data transmission process. [Figure 10] FIG. 10 is a diagram illustrating an example of the schema of the data transmission request table and the transmitted data table. [Figure 11] FIG. 11 is a diagram showing an example of state transitions of the data transmission request table and the transmitted data table. [Figure 12] FIG. 12 is a flowchart showing the procedure of the backup data acquisition process. [Figure 13] FIG. 13 is a flowchart showing the procedure of the write request response process. [Figure 14] FIG. 14 is a flowchart showing the procedure of the read request response process. [Figure 15] FIG. 15 is a diagram illustrating an example of a schema of the other device data table. [Figure 16] FIG. 16 is a schematic diagram illustrating the updating of the file ID. [Figure 17] FIG. 17 illustrates an example of a hardware configuration. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, a description will be given of a mode for carrying out a recorder, a backup method, and a backup program according to the present disclosure (hereinafter referred to as an "embodiment") with reference to the accompanying drawings. Note that this embodiment merely illustrates one example or aspect, and the structure, action, function, properties, characteristics, methods, uses, etc. according to the present disclosure are not limited by such an example.

[0015] <Embodiment 1> <Example of use case> Figure 1 shows an example of a use case for a recorder. For example, Figure 1 shows, as an example only, one segment SEG out of multiple segments into which a network that makes up a data acquisition system is divided.

[0016] As shown in Fig. 1, segment SEG includes three recorders, recorders 10A to 10C. Although Fig. 1 shows three recorders, recorders 10A to 10C, this is merely an example, and any number of recorders greater than or equal to two may be included.

[0017] An example of a connection method for these recorders 10A to 10C is a peer-to-peer method in which the recorders 10A to 10C are connected to one another on an equal footing on the segment SEG. Hereinafter, when there is no need to distinguish between the individual recorders 10A to 10C, the recorders 10A to 10C may be collectively referred to as "recorder 10."

[0018] Recorder 10 is a device that records data measured and collected via multiple channels, such as input / output, communication, and calculation. For example, recorder 10 may be realized as any of a recorder, paperless recorder, or data logger. Furthermore, recorders 10A to 10C may be recorders, paperless recorders, or data loggers of different types and specifications.

[0019] Hereinafter, data measured and collected via multiple channels may be referred to as "scan data."

[0020] <Recording function> First, we will explain the recording function of recorder 10 according to this embodiment. For example, recorder 10 accumulates scan data measured and collected via multiple channels, such as input / output, communication, and calculation, in chronological order in an internal storage area of ​​recorder 10 until a preset timing. After that, when the preset timing has elapsed, recorder 10 creates a data file from the chronological order of the scan data and stores the data file in the internal storage area of ​​recorder 10.

[0021] <Backup function> Next, a description will be given of the backup function of the recorder 10 according to this embodiment. Each of the recorders 10A to 10C connected to the network in the same segment SEG periodically exchanges device information (such as device identification information for recognizing the device) with the other recorders.

[0022] Through such alive monitoring, each of the recorders 10A to 10C recognizes other recorders 10 that are connectable to the network among the recorders 10A to 10C connected to the same segment SEG, and sets them as candidates for the backup destination.

[0023] For example, backup destination candidates can be determined according to a predetermined rule from among other recorders 10 that can be connected to the same segment SEG. The following rules (1) to (4) are merely examples of such rules. (1) The destination device is changed each time a transmission is made, in the order in which the network connection is recognized by alive monitoring. (2) Prioritize other devices that are first recognized as connected to the network by alive monitoring (3) Prioritize other devices with IP addresses close to your own. (4) Prioritize other devices with a low load, determined from parameters such as free memory space and the number of other devices currently being backed up (this can be achieved by including information on memory capacity in the device information, etc.)

[0024] For ease of explanation, the following description will be given taking as an example a case where recorder 10A and recorder 10B mutually serve as backup destinations. Furthermore, recorder 10A, which is the focus of attention among recorders 10, will be referred to as the "own device," and recorder 10B and recorder 10C other than the own device will be referred to as the "other device." Furthermore, it is assumed that the device identification information of recorder 10A, recorder 10B, and recorder 10C included in the same segment SEG are "AAAAA," "BBBBB," and "CCCCC," respectively.

[0025] In one aspect, recorder 10A transmits the scan data accumulated in its internal storage area or the data files stored in its internal storage area to recorder 10B for backup according to specified conditions, such as thresholds for data volume or time. Recorder 10A can then retrieve the backup data stored in recorder 10B at any time as needed, for example, in the event of an abnormality in its own storage area.

[0026] In another aspect, recorder 10A receives and backs up scan data or data files of recorder 10B from recorder 10B, and then transmits the backup data to recorder 10B in response to a data retrieval request from recorder 10B.

[0027] In this way, the backup function according to this embodiment can be realized self-contained by the recorder 10 included in the same segment SEG. This eliminates the need for a server device as infrastructure dedicated to backup. This also reduces the work of configuring various settings related to file transfers, etc. on both the server and client recorder 10 sides. In addition, the introduction of this backup function does not require the addition of any hardware other than the server device.

[0028] Therefore, the backup function according to this embodiment can be easily implemented.

[0029] <Recorder 10 Functional Configuration> Fig. 2 is a block diagram showing an example of the functional configuration of recorder 10. As shown in Fig. 2, recorder 10 has a measurement / collection unit 100, a data recording unit 200, a storage unit 300, a NW (Network) connected device management unit 400, a self-device data processing unit 500, a other-device data processing unit 600, a communication unit 700, and a UI (User Interface) unit 800.

[0030] Of these functional units, in order to realize the backup function according to this embodiment, the functional units indicated by hatching in FIGS. 2 and 3, namely, the NW-connected device management unit 400, the local device data processing unit 500, and the other device data processing unit 600, have been added, and other device record data has also been added as backup data.

[0031] Fig. 3 is a diagram showing the detailed configuration of each unit related to the backup function. For example, Fig. 3 shows the detailed functional configuration of each functional unit of the NW-connected device management unit 400, the local device data processing unit 500, and the other device data processing unit 600 that realize the backup function according to this embodiment, as well as related functional units.

[0032] Each of the functional units of the recorder 10 shown in FIG. 2 will be described below with reference to the detailed functional configuration of each functional unit shown in FIG.

[0033] <Measurement and collection unit 100> The measurement and collection unit 100 is a functional unit that acquires channel measurement data in units of channels such as input / output, communication, and calculation, and collects measurement data for N channels.

[0034] In one aspect, the measurement and collection unit 100 can obtain input / output data as channel measurement data by processing input / output signals of input / output channels. In another aspect, the measurement and collection unit 100 can obtain communication input data as channel measurement data by acquiring data input via communication channels. In a further aspect, the measurement and collection unit 100 can obtain calculation data as channel measurement data by performing calculation processing on data input via calculation channels. In addition, the measurement and collection unit 100 can obtain calculation data as channel measurement data via calculation channels by performing calculation processing on input / output data and communication input data.

[0035] The measurement data for N channels of the input / output data, communication input data, and calculation data may be input as scan data to the data recording unit 200. It goes without saying that any data can be acquired as the input / output data, communication input data, and calculation data depending on the operating environment of the recorder 10.

[0036] <Data recording unit 200> The data recording unit 200 is a functional unit that executes processes related to the recording of various types of data. As shown in Fig. 3, the data recording unit 200 has a recording unit 201 that records data recorded in the device itself, and a reading unit 202 that reads the data recorded in the device itself.

[0037] <Recording Unit 201> 3, the recording unit 201 stores the scan data collected by the measurement processing (input / output signal processing, communication data processing, and arithmetic processing) by the measurement / collection unit 100 in the internal storage area 301 of the storage unit 300 (step S101).

[0038] Then, the recording unit 201 determines whether the amount of scan data stored in the internal storage area 301 satisfies a predetermined backup condition, for example, a condition in which the data amount or cycle is a threshold value (step S102).

[0039] Such "backup conditions" may be arbitrarily set through system definition by the developer of the recorder 10 or user definition by the user of the recorder 10. As just one example, when implementing high-frequency backups, it is possible to execute backups at intervals corresponding to the measurement interval, such as 10 milliseconds.

[0040] At this time, if the above backup conditions are met (step S102 Yes), the recording unit 201 registers information identifying the data to be transmitted (hereinafter referred to as data identification information) in the data transmission request table (step S103), so that the scan data accumulated in the internal storage area 301 can be transmitted as backup data to the backup data transmission unit 501 of the local device data processing unit 500, which will be described later. Note that if the above backup conditions are not met (step S102 No), the processing of step S103 is skipped.

[0041] Next, the recording unit 201 determines whether the amount of scan data stored in the internal storage area 301 satisfies a predetermined filing condition (step S104). Such a "filing condition" may be set by the system or the user at a cycle suitable for management such as periodic reports or monitoring, or for analysis such as prediction of abnormal signs, such as 10 minutes or 1 day.

[0042] If the predetermined filing conditions are met (Yes in step S104), the recording unit 201 creates a data file from the time series of the scan data accumulated in the internal storage area 301 and stores the data file in the internal storage area 301 (step S105).

[0043] Furthermore, the recording unit 201 registers the data identification information in the data transmission request table in order to cause the backup data transmission unit 501, which will be described later, to transmit the backup data (step S106).

[0044] If the predetermined file creation conditions are not met (No in step S104), skip the above steps S105 and S106 and end the process.

[0045] <Reading unit 202> When the reading unit 202 receives a data reading request from the backup data transmission unit 501 described later, it reads out the device recording data (duplicate data) corresponding to the data identification information specified in the data reading request from the internal storage area 301.

[0046] <Storage unit 300> The storage unit 300 is a functional unit that stores various types of data. As shown in FIG. 3, the storage unit 300 may include an internal storage area 301 stored inside the recorder 10 and an external storage area 302 stored outside the recorder 10.

[0047] <Internal storage area 301> The internal storage area 301 may be realized by various auxiliary storage devices such as a non-volatile memory or an SD (Secure Digital) memory card. For example, the internal storage area 301 can store the scan data of the device itself, store the data files of the device itself, or store the backup data of other devices. Note that since the scan data becomes unnecessary due to duplication if a data file is created from the scan data, the storage area for the scan data is used for overwriting after the data file is created.

[0048] <External storage area 302> The external storage area 302 may be realized by a removable medium such as an SD memory card or a USB memory. For example, the external storage area 302 stores the backup data of the device itself saved in other devices after being acquired by the backup data acquisition unit 502 described later, or stores the other device recording data read by the reading unit 602 described later in response to a request to retrieve other device recording data.

[0049] <NW connection device management unit 400> The NW connected device management unit 400 is a functional unit that manages a list of recorders 10 connected to the network of the same segment SEG as a connected device list. Such a connected device list may be realized by alive monitoring (communication confirmation) that checks whether communication of device identification information via broadcast communication is possible.

[0050] 5 is a flowchart showing the procedure for transmitting device identification information. This process may be initiated at a predetermined interval, for example, every second. As shown in FIG. 3, the NW connected device management unit 400 requests the broadcast communication unit 701 to transmit the device identification information of its own device (step S201).

[0051] 6 is a flowchart showing the procedure of the device identification information receiving process. As shown in FIG. 3, the NW connected device management unit 400 receives the device identification information of other devices via the broadcast communication unit 701 (described later) (step S301).

[0052] At this time, if the device identification information received in step S301 is a device that is not registered in the connected device list (Yes in step S302), the NW connected device management unit 400 additionally registers the device identification information received in step S301 in the connected device list (step S303), and terminates the processing.

[0053] On the other hand, if the device identification information received in step S301 is not a device that is not registered in the connected device list (No in step S302), the NW connected device management unit 400 updates the unreceived counter corresponding to the device identification information received in step S301 among the device identification information included in the connected device list to "0" and updates the device status to "GOOD" (step S304), and terminates the process.

[0054] The connected device list managed in this manner is monitored by a timer. For example, the NW connected device management unit 400 counts up a non-received counter for each piece of device identification information included in the connected device list according to the timer. Thereafter, the NW connected device management unit 400 considers another device from which it has not been able to receive device identification information for a certain period of time to be abnormal, and updates the device status corresponding to the device identification information of that other device to "BAD." Another device whose device status has been updated to "BAD" in this manner is excluded from backup candidates, i.e., from destinations for backup data. The above device status can be output as information via display, communication, etc.

[0055] Fig. 7 is a diagram showing an example of a schema of a connected device list. As shown in Fig. 7, the connected device list may include items such as "information necessary for communication," "device identification information," "unreceived counter," and "device status."

[0056] For example, "information necessary for communication" may include address information such as an IP address or MAC address. Furthermore, "device identification information" is information that can identify and specify the recorder 10, such as the type of recorder 10 or the product serial number assigned to each individual recorder 10. Furthermore, the "unreceived counter" may be a counter that measures the period during which device identification information has not been received. For example, when device identification information is received, the value is cleared to 0, while if device identification information continues to be unreceived, the counter is incremented over time. Furthermore, "device status" refers to the status of the network connection of the recorder 10, and may take two or more values, such as "GOOD," which indicates that the recorder 10 is a candidate for a backup data destination, and "BAD," which indicates that the recorder 10 is excluded from the list of candidate backup data destinations.

[0057] Fig. 8 is a diagram showing an example of the state transition of the connected device list. Fig. 8 shows, as an example, a connected device list managed by recorder 10A as its own device. Fig. 8 also shows an example in which a record with device identification information "BBBBB" corresponding to recorder 10B and a record with device identification information "CCCCC" corresponding to recorder 10C have already been registered. Note that Fig. 8 shows an example in which the threshold value of the unreceived counter for updating the device status from "GOOD" to "BAD" is "50."

[0058] 8, at time t1, the device status corresponding to the device identification information "BBBBB" and the device status corresponding to the device identification information "CCCCC" are both "GOOD," so both recorder 10B and recorder 10C are designated as backup candidates. Thereafter, at time t2, the unreceived counter corresponding to the device identification information "CCCCC" counts up to "50," so the device status is updated to "BAD." Therefore, at time t2, recorder 10B is designated as a candidate destination for backup data, while recorder 10C is excluded from the candidate destinations for backup data.

[0059] <Own device data processing unit 500> The local device data processing unit 500 is a processing unit that processes data recorded in the local device. As shown in Fig. 3, the local device data processing unit 500 has a backup data transmission unit 501 that transmits backup data of the data recorded in the local device to other devices, and a backup data acquisition unit 502 that acquires backup data of the local device stored in other devices.

[0060] <Backup data transmission unit 501> 9 is a flowchart showing the procedure for the backup data transmission process. As shown in FIG. 9, if a record exists in the data transmission request table, that is, if there is data recorded in the own device for which backup has not been completed (Yes in step S401), the backup data transmission unit 501 executes the following process.

[0061] That is, the backup data transmission unit 501 determines, from among the other devices whose device identification information is registered in the connected device list, the other device, such as the recorder 10B, to which the data recorded by the own device will be sent in accordance with a predetermined rule, such as rules (1) to (4) above (step S402).

[0062] Next, the backup data transmission unit 501 causes the reading unit 202 to read out from the internal storage area 301 the data recorded in its own device that corresponds to the data identification information registered in the data transmission request table, and creates transmission data (step S403).

[0063] Then, the backup data transmission unit 501 sets the device identification information (destination) value in the data transmission request table to the device identification information determined as the destination in step S402, and sets the transmission result value in the data transmission request table to "NG" (step S404).

[0064] Thereafter, the backup data transmission unit 501 causes the unicast communication unit 702, described later, to transmit the write request for the transmission data generated in step S403 to the recorder 10B determined as the transmission destination in step S402 (step S405).

[0065] Such a write request may include the "device identification information," "data identification information," and "backup data" of recorder 10A that is the sender of the backup data.

[0066] Meanwhile, the other device request responding unit 601 of the recorder 10B receives the write request transmitted from the backup data transmitting unit 501 of the recorder 10A in step S405 (step S406).

[0067] In response to this write request, the other device request responding unit 601 of the recorder 10B stores the backup data received in step S406 in the storage unit 300 of the recorder 10B (step S407).

[0068] Thereafter, the other device request response unit 601 of the recorder 10B returns the result of the success or failure of the write request received in step S406 to the recorder 10A as response data (step S408).

[0069] Meanwhile, backup data transmission unit 501 of recorder 10A, which is the own device, receives the response data returned in step S408 (step S409).

[0070] Here, if the result included in the response data received in step S409 is successful (step S410 Yes), the backup data transmission unit 501 deletes the record from the data transmission request table, sets the transmission result value of the record to "OK", and registers it in the transmitted data table (step S411), and proceeds to step S401.

[0071] If the result included in the response data received in step S409 is a failure (step S410 No), step S411 is skipped and the process proceeds to step S401.

[0072] A specific example of the data transmission request table and the transmitted data table used in such a backup data transmission process will be described below.

[0073] The data transmission request table is a table used to execute a request to write backup data to other devices. For example, if a record exists in the data transmission request table at the branch in step S401, transmission of the backup data of the own device to the other device is started.

[0074] On the other hand, the transmitted data table is a table used to manage backup data of the device itself that has been backed up by another device. For example, when acquiring backup data of the device itself that has been backed up by another device, the backup data and the other device that is the backup destination are identified, and the backup data of the device itself is acquired from the backup destination.

[0075] 10 is a diagram showing an example of the schema of the data transmission request table and the transmitted data table. As shown in FIG. 10, the data transmission request table and the transmitted data table may have a common schema. These two tables may include items such as "data identification information," "device identification information (transmission destination)," and "transmission result."

[0076] "Data identification information" refers to information that can identify and specify data, and may be, for example, a data-specific ID or a file name. "Device identification information (destination)" refers to the device identification information of the destination (backup destination) of the backup data. "Transmission result" refers to the success or failure of writing the backup data at the destination, and may be expressed by two or more values, for example, success (OK) or failure (NG).

[0077] 11 is a diagram showing an example of state transitions of the data transmission request table and the transmitted data table, which are managed by recorder 10A as its own device.

[0078] For example, Fig. 11 shows the data transmission request table at time t11 when step S103 or step S106 of the data recording process shown in Fig. 4 is executed. At time t11, as the data recorded in the device itself is recorded in the internal storage area 301 in step S103 or step S106, a new record including the data identification information "ddddd" of the data recorded in the device itself is created in the data transmission request table.

[0079] 11 shows the data transmission request table at time t12 when step S404 of the backup data transmission process shown in FIG. 9 is executed. At time t12, the device identification information "BBBBB" of recorder 10B, which has been determined as the destination of the backup data and is identified by the data identification information "ddddd," is set in the data transmission request table. Furthermore, the backup data transmission result "NG" is set in the data transmission request table until a success response is returned in response to the write request.

[0080] 11 shows the data transmission request table and the transmitted data table at time t13, when step S411 of the backup data transmission process shown in Fig. 9 was executed. At time t13, response data of "success (OK)" is returned to recorder 10A from recorder 10B, which is the destination of the backup data. Therefore, the record of data identification information "ddddd" to which the response data of "success (OK)" was returned is deleted from the data transmission request table, and a record in which the transmission result value of that record has been updated to "OK" is registered in the transmitted data table.

[0081] Naturally, if response data indicating "failure (NG)" is returned to recorder 10A, or if no response data is returned, the transmission result value for the record with data identification information "ddddd" remains "NG" in the data transmission request table. In this case, the process proceeds to "Yes" at the branch in step S401 from the next time onwards, and the transmission of backup data is repeated until response data indicating "success (OK)" is obtained in the processing from step S402 onwards.

[0082] <Backup data acquisition unit 502> 12 is a flowchart showing the procedure of the backup data acquisition process. This process may be started when a backup data acquisition request is received via the UI unit 800, which will be described later, as an example.

[0083] As shown in FIG. 12, if a record exists in the transmitted data table, that is, if the data recorded in the own device has been backed up in another device (Yes in step S501), the backup data acquisition unit 502 executes the following process.

[0084] That is, the backup data acquisition unit 502 identifies the device identification information included in the transmitted data table as another device that is the destination of the backup data request, and also identifies the data identification information included in the transmitted data table as the backup data to be acquired (step S502).

[0085] Then, the backup data acquisition unit 502 creates transmission data including the "device identification information" of the other device that is the backup data request destination and the "data identification information" of the backup data to be acquired (step S503).

[0086] Thereafter, the backup data acquisition unit 502 causes the unicast communication unit 702 described below to transmit a read request for the transmission data generated in step S503 to the recorder 10B identified in step S502 as the other device requesting the backup data (step S504).

[0087] Meanwhile, the other device request responding unit 601 of the recorder 10B receives the read request transmitted from the backup data acquiring unit 502 of the recorder 10A in step S504 (step S505).

[0088] In response to this read request, the reading unit 602 of the recorder 10B reads, from the storage unit 300 of the recorder 10B, the backup data corresponding to the device identification information and data identification information specified in the read request (step S506).

[0089] Thereafter, the reading unit 602 of the recorder 10B returns the backup data read in step S506 to the recorder 10A as read data (step S507).

[0090] Meanwhile, backup data acquisition unit 502 of recorder 10A receives the read data returned in step S507, stores the read data in external storage area 302 of storage unit 300 (step S508), and ends the process.

[0091] <Other device data processing unit 600> The other-device data processing unit 600 is a functional unit that processes other-device recorded data. As shown in Fig. 3, the other-device data processing unit 600 has an other-device request response unit 601 that executes processing to respond to write and read requests for backup data from other devices, and a read unit 602 that reads other-device recorded data from the storage unit 300 in accordance with a request to retrieve other-device recorded data received via the UI unit 800 of its own device.

[0092] <Other device request response unit 601> 13 is a flowchart showing the procedure of the write request response process. As shown in FIG. 3, the backup data transmission unit 501 of the other device transmits a write request for backup data, with the recorder 10A, which is the own device, determined as the transmission destination (step S601).

[0093] On the other hand, the other device request response unit 601 of the own device accepts a request to write backup data via the unicast communication unit 702 (described later) (step S602).

[0094] Then, the other device request response unit 601 of the own device stores the backup data in the internal storage area 301 of the storage unit 300 in accordance with the write request received in step S602 (step S603). Note that although an example in which the backup data is stored in the internal storage area 301 has been given here, it is also possible for the backup data to be stored in the external storage area 302.

[0095] Next, the other device request response unit 601 of the own device adds and registers a new record in the other device data table, including the device identification information and data identification information specified in the write request accepted in step S602 and the memory unit access information stored in the memory unit 300 in step S603 (step S604).

[0096] Then, the other device request response unit 601 of the own device returns the result of the write process in step S603, for example, success (OK) or failure (NG), as response data to the backup data transmission unit 501 of the other device via the unicast communication unit 702 described below (step S605), and ends the process. Note that the backup data transmission unit 501 of the other device receives the response data returned in step S605 (step S606).

[0097] 14 is a flowchart showing the procedure of the read request response process. As shown in FIG. 3, the backup data acquisition unit 502 of the other device transmits a read request for the backup data of the other device, with the recorder 10A being the own device, being determined as the destination (step S701).

[0098] Meanwhile, the other device request response unit 601 of the own device accepts a read request for backup data of another device via the unicast communication unit 702 (described later) (step S702).

[0099] Then, the other device request response unit 601 of the own device acquires the memory access information included in the other device data table that corresponds to the pair of device identification information and data identification information specified in the read request received in step S702 (step S703).

[0100] Next, the other device request response unit 601 of the own device reads the other device recorded data stored as backup data of the other device in the storage unit 300 in accordance with the storage unit access information acquired in step S703 (step S704).

[0101] Then, the other device request response unit 601 of the own device returns the backup data of the other device read in step S704 to the backup data acquisition unit 502 of the other device via the unicast communication unit 702 (described later) (step S705), and ends the process. Note that the backup data acquisition unit 502 of the other device receives the backup data of the other device returned in step S705 (step S706).

[0102] <Reading unit 602> The reading unit 602 receives a request to retrieve data recorded in another device via the UI unit 800 of its own device. For example, it can receive designation of device identification information of the other device to be retrieved and data identification information of the backup data to be retrieved. The reading unit 602 then reads the data recorded in the other device from the storage unit 300 in accordance with the storage unit access information corresponding to the device identification information and data identification information designated in the retrieval request. The reading unit 602 then saves the data recorded in the other device read from the storage unit 300 in the external storage area 302.

[0103] The other device data table used in the other device data processing unit 600 will now be described. Fig. 15 is a diagram showing an example of the schema of the other device data table. As shown in Fig. 15, the other device data table may include items such as "data identification information," "device identification information (data source)," and "storage unit access information."

[0104] The "data identification information" is the same information as the data identification information described above, but differs in its use in that it is used to read or extract data recorded in other devices. The "device identification information (data source)" is also the same information as the device identification information described above, but differs in its use in that it is used to read or extract data recorded in other devices. The "storage unit access information" is information for accessing data recorded in other devices specified in a read request or extract request, and may be, for example, address information or a file name where the desired information is stored in the internal storage area 301, the external storage area 302, etc.

[0105] <Communication unit 700> The communication unit 700 is a functional unit that executes communications with other devices. As shown in Fig. 3, the communication unit 700 includes a broadcast communication unit 701 that executes broadcast communications addressed to all recorders 10 participating in the same network, and a unicast communication unit 702 that executes unicast communications addressed to a single device corresponding to a specified address among the recorders 10 participating in the same network.

[0106] <Broadcast communication unit 701> In one aspect, the broadcast communication unit 701 broadcasts the device identification information of its own device in accordance with an instruction from the NW connected device management unit 400 in step S201 of the device identification information transmission process shown in Fig. 5. In another aspect, the broadcast communication unit 701 receives the device identification information of another device broadcast from the other device in step S301 of the device identification information reception process shown in Fig. 6, and outputs the device identification information of the other device to the NW connected device management unit 400. Note that although the case where broadcast communication is performed has been exemplified here, multicast communication may also be performed.

[0107] <Unicast communication unit 702> On one side, the unicast communication unit 702 receives communication input data from another device in step S101 of the data recording process shown in FIG. 4, and outputs the communication input data to the measurement / collection unit 100. On another side, the unicast communication unit 702 receives a write request received in step S602 of the write request response process shown in FIG. 13, or a read request received in step S702 of the read request response process shown in FIG. 14, and outputs the write request or the read request to the other device request response unit 601. As a further aspect, the unicast communication unit 702 transmits a write request in accordance with an instruction from the backup data transmission unit 501 in step S405 of the backup data transmission process shown in FIG. 9, and then outputs the response data received in step S409 to the backup data transmission unit 501. On another side, the unicast communication unit 702 transmits a write request in accordance with an instruction from the backup data acquisition unit 502 in step S504 of the backup data acquisition process shown in FIG. 12, and then outputs the backup data returned in step S508 to the backup data acquisition unit 502.

[0108] <UI unit 800> The UI unit 800 is a functional unit that accepts various user operations. On one side, the UI unit 800 accepts an operation to acquire backup data. On another side, the UI unit 800 accepts an operation to extract other device recording data.

[0109] <One aspect of the effects of Embodiment 1> As described above, the recording meter 10 according to the present embodiment transmits scan data accumulated in the internal storage area 301 of its own device or a data file stored in the internal storage area 301 of its own device to another device for backup.

[0110] As a result, the recorder 10 included in the same segment SEG can achieve the backup function self-containedly. This eliminates the need for a server device as infrastructure dedicated to backup. For example, it also reduces the work of configuring various settings related to file transfers, etc. on both the server and client recorder 10 sides. In addition, the introduction of this backup function does not require the addition of any hardware other than the server device.

[0111] Therefore, the recorder 10 according to this embodiment can easily implement a backup function.

[0112] <Other embodiments> Although the embodiments of the present disclosure have been described above, various applications are possible, and the present disclosure may be implemented in various different forms other than the above-described embodiments.

[0113] <Duplicate data removal> An application example of deleting duplicate data from the above scan data and data files will be described. That is, once a data file is created, the scan data stored in the internal storage area 301 becomes unnecessary because the scan data is included in the data file. Furthermore, if the data file is backed up to another device, the scan data backed up to the other device also becomes unnecessary. By deleting unnecessary scan data from the internal storage area 301 in this way, memory resources can be used effectively.

[0114] In order to achieve this kind of duplicate data deletion, the data item "data identification information" in the data transmission request table and the transmitted data table described using Figures 10 and 11 can include "data type" and "file ID", etc.

[0115] "Data type" refers to the type of scan data or data file. "File ID" refers to identification information that identifies a data file; for example, each data file is assigned an ID that can uniquely identify that data file.

[0116] For example, the recording unit 201 of the data recording unit 200 updates the file ID every time a data file is created in step S105 of the data recording process shown in Fig. 4. By updating the file ID in this way, a common file ID can be assigned to the time series of scan data collected by the measurement and collection unit 100 during the period from the creation of a data file until the creation of the next data file, and to the data files created from this scan data.

[0117] Fig. 16 is a schematic diagram for explaining file ID updates. In Fig. 16, the timing at which scan data is accumulated is plotted in chronological order with white triangular marks, and the timing at which data files are created is plotted in chronological order with black triangular marks.

[0118] Here, in steps S101 and S105 of the data recording process shown in FIG. 4, the recording unit 201 assigns the same file ID to the scan data and data file shown in the dashed frame in FIG. 16, sets the file ID as the value of the data identification information, and registers it in the data transmission request table.

[0119] This makes it possible to delete duplicate data for which a data file has been created from the scan data stored in the device itself, and also makes it possible to delete duplicate data for which a data file has been created from the scan data of the device itself that has been backed up to another device.

[0120] In one aspect, the other device request response unit 601 stores backup data specified in a write request from another device in the internal storage area 301 of the storage unit 300 in a process of responding to the write request from the other device, and then determines whether the data type of the backup data written to the internal storage area 301 is a data file. If the data type is a data file, the other device request response unit 601 deletes from the internal storage area 301 scan data of the other device that has a file ID that is the same as or smaller than the file ID value of the data file among the other device record data stored in the internal storage area 301. Note that the backup data transmission unit 501 can also instruct the deletion of scan data that has a file ID other than the file ID value of the data file when transmitting a write request corresponding to the data file.

[0121] In this way, in order to collectively delete not only the backup data (data file) written to the internal storage area 301 but also scan data whose data file was created before the backup data, it is sufficient to establish a magnitude relationship between the file IDs in the chronological order in which the file IDs are assigned. For example, in the process of transmitting own device data to another device, the data is processed in the order in which it is registered in the data transmission request table. Therefore, even if the scan data of another device that has been backed up is no longer needed due to the selection of the backup destination, it may remain in the internal storage area 301. In this case, it is still possible to delete duplicate data.

[0122] Another aspect is that the storage of scan data in the device itself is achieved by using the internal storage area 301 as a buffer. Therefore, by emptying the buffer every time a data file is created, only the scan data before the data file was created is stored in the internal storage area 301. In other words, every time a data file is created, unnecessary scan data is deleted from the internal storage area 301.

[0123] As a further aspect, if scan data and a data file with the same file ID are registered in the data transmission request table, the scan data does not need to be transmitted. Therefore, the backup data transmission unit 501 can make the above-mentioned determination in step S401 shown in Fig. 9 and delete scan data that does not need to be transmitted from the data transmission request table.

[0124] <Multiplexing according to importance> In the above-mentioned first embodiment, the example of the backup in which the scan data and data files are duplicated is given, but the backup in which the data files are duplicated in triplicate or more can be performed.

[0125] For example, the importance can be set by system definition or user definition for each channel or group of channels in the recorder 10. Based on this channel importance setting, the backup data transmission unit 501 increases the number of recorders to which backup data for scan data or data files is sent as the importance set for a channel increases, while decreasing the number of recorders to which backup data for scan data or data files is sent as the importance set for a channel decreases. This allows the degree of backup multiplexing to be controlled according to the importance of the channel.

[0126] <Data tracking application example 1> The recorder 10 according to this embodiment may further include a display control unit that displays on an arbitrary display unit which other devices the backup data of the recorder 10 itself has been backed up to.

[0127] For example, when the display control unit receives a request for tracking data of the recorder itself via the UI unit 800 or the like, it causes the records stored in the transmitted data table shown in Fig. 11 to be displayed on the display unit (not shown) of the recorder 10. As an example, such a display unit may be realized by a liquid crystal display or a 7-segment LED that is installed on or connected to the recorder 10. In this case, the display control unit can extract and display only records for which the transmission result is "success (OK)," or extract and display a predetermined number of records that were registered most recently from all the records.

[0128] Such a table display includes data identification information that can identify the backup data of the device itself, as well as device identification information that can identify other devices that record the backup data of the device itself.

[0129] For example, if some abnormality occurs in the storage unit 300 of the device itself, such as a breakdown, loss of data due to FIFO (First-In First-Out), or operation without media, the backup destination of the backup data of the device itself can be confirmed.

[0130] Furthermore, by receiving a backup data acquisition request via the UI unit 800, the backup data acquisition process shown in Fig. 12 can be executed. At this time, the backup data acquisition unit 502 can acquire all of the backup data of the device corresponding to all records in the transmitted data table, or it can acquire one or more backup data of the device corresponding to one or more records in the transmitted data table.

[0131] <Data tracking application example 2> The recorder 10 according to this embodiment may further include a display control unit that displays on an arbitrary display unit which other devices' backup data is backed up in the recorder 10 itself.

[0132] For example, when the display control unit receives a request for tracking data from another device via the UI unit 800 or the like, it causes the display unit of the recorder 10 to display the records stored in the other device data table shown in FIG.

[0133] The display of such a table includes data identification information that can identify the backup data of other devices recorded in the own device, as well as device identification information that can identify the other devices whose backup data has been recorded in the own device.

[0134] This allows data tracking of other devices. For example, if the remaining capacity of the external media of the device is low, the backup data of other devices can be selected and operated (acquired / deleted). In addition, if a device breaks down and cannot be started, this can also function as a means to find out where to retrieve the backup data of other devices.

[0135] Furthermore, by receiving a request to retrieve other device recorded data via the UI unit 800, the reading unit 602 can be made to retrieve the other device recorded data from the storage unit 300. At this time, the reading unit 602 can be made to obtain all backup data of other devices corresponding to all records in the other device data table, or can be made to obtain one or more backup data of other devices corresponding to one or more records in the other device data table.

[0136] <Exercise creative ability> The matters described in the above embodiment, such as the number of recorders 10 constituting the segment SEG, the backup conditions, the filing conditions, and other specific examples, are merely examples and may be changed. Furthermore, the processing order of the flowcharts described in the above embodiment may be changed within a consistent range.

[0137] <System> The information, including the processing procedures, control procedures, specific names, various data, and parameters shown in the above documents and drawings, can be changed as desired unless otherwise specified. For example, one or more of the functional units among the measurement and collection unit 100, data recording unit 200, NW connection device management unit 400, local device data processing unit 500, other device data processing unit 600, communication unit 700, and UI unit 800 may be configured as separate devices.

[0138] Furthermore, the components of each device shown in the figure are functional concepts and do not necessarily have to be physically configured as shown. In other words, the specific form of distribution and integration of each device is not limited to that shown. In other words, all or part of them can be functionally or physically distributed and integrated in any unit depending on various loads, usage conditions, etc. Note that each configuration may also be a physical configuration.

[0139] Furthermore, each processing function performed by each device can be realized, in whole or in part, by a CPU (Central Processing Unit) and a program analyzed and executed by the CPU, or can be realized as hardware using wired logic.

[0140] <Hardware> Next, an example of the hardware configuration of the computer described in the above embodiment will be described. Fig. 17 is a diagram showing an example of the hardware configuration. As shown in Fig. 17, the recorder 10 has a communication device 10a, a storage device 10b, a memory 10c, and a processor 10d. Note that the components shown in Fig. 17 may be connected to each other via a bus or the like.

[0141] The communication device 10a is a network interface card, etc. The storage device 10b is a storage device such as a hard disk drive (HDD) or a solid state drive (SSD). For example, the storage device 10b stores programs and databases that operate the functions shown in FIGS. 2 and 3.

[0142] The processor 10d reads a program that executes processing similar to that of the processing units shown in Figures 2 and 3 from the storage device 10b, etc., and expands it in the memory 10c, thereby operating a process that executes the functions described in Figures 2 and 3.

[0143] Such a process realizes the same functions as the processing units of the recorder 10. For example, the processor 10d reads from the storage device 10b or the like a program having the same functions as the data recording unit 200, the NW-connected device management unit 400, the local device data processing unit 500, the other device data processing unit 600, etc. Then, the processor 10d executes a process that executes the same processing as the data recording unit 200, the NW-connected device management unit 400, the local device data processing unit 500, the other device data processing unit 600, etc.

[0144] In this way, the recorder 10 operates as an information processing device that executes a backup method by reading and executing a program. The recorder 10 can also implement the same functions as the above-described embodiment by reading the program from a recording medium using a media reader and executing the read program. Note that the program in these other embodiments is not limited to being executed by the recorder 10. For example, the present invention can also be applied to cases where another computer or server executes the program, or where these execute the program in cooperation with each other.

[0145] The above program can be distributed via a network such as the Internet. The above program can also be recorded on any recording medium and executed by a computer by reading it from the recording medium. For example, the recording medium can be a hard disk, an SSD, a flexible disk (FD), a CD-ROM, a magneto-optical disk (MO), a digital versatile disk (DVD), or the like.

[0146] <Other> Some examples of combinations of the disclosed technical features are set out below.

[0147] (1) A recorder, a collection unit that collects measurement data; a recording unit that records the measurement data; a transmission unit that transmits backup data obtained by duplicating the measurement data to another recorder connected to the recorder via a network; A recorder comprising:

[0148] (2) the recording unit records a data file created from the time series of the measurement data; The recorder according to (1), wherein the transmission unit transmits backup data in which the data file is copied to the other recorder.

[0149] (3) The recorder according to (2), wherein the transmitting unit instructs deletion of backup data corresponding to the measurement data used to create the data file when transmitting the backup data into which the data file has been copied.

[0150] (4) further comprising a communication confirmation unit that confirms whether the other recorder is connected to the network; The recorder according to any one of (1) to (3), wherein the transmission unit transmits backup data to the other recorders for which the communication has been confirmed among the other recorders.

[0151] (5) the collecting unit collects measurement data for each channel; The recorder according to any one of (1) to (4), wherein the transmission unit changes the number of recorders to which the backup is to be sent depending on the importance set for the channel.

[0152] (6) The recorder according to (5), wherein the transmission unit increases the number of recorders to which the backup data is to be sent as the importance set for the channel increases.

[0153] (7) The recorder described in any one of (1) to (6), further comprising a display control unit that causes a display unit to display which of the other recorders connected via the network the backup data is backed up to.

[0154] (8) A recorder, a collection unit that collects measurement data; a storage unit for recording the measurement data; an other device data processing unit that acquires backup data that is a copy of measurement data recorded in another recorder connected via a network, The storage unit stores the backup data. A recorder characterized by:

[0155] (9) The recorder according to (8), further comprising a display control unit that causes a display unit to display which of the other recorders connected via the network has measurement data backed up in the memory unit of the recorder.

[0156] (10) The recorder Collect measurement data, Recording the measurement data; transmitting the backup data, which is a copy of the measurement data, to another recorder connected to the recorder via a network; A backup method comprising:

[0157] (11) On the recorder, Collect measurement data, Recording the measurement data; transmitting the backup data, which is a copy of the measurement data, to another recorder connected to the recorder via a network; A backup program characterized by executing a process. [Explanation of symbols]

[0158] 10 Recorder 100 Measurement and Collection Unit 200 Data recording unit 201 Recording Department 202 Readout section 300 Storage section 301 Internal storage area 302 External storage area 400 Network Connection Device Management Department 500 Self-device data processing unit 501 Backup data transmission unit 502 Backup data acquisition unit 600 Other equipment data processing section 601 Other device request response part 602 Readout unit 700 Communications Department 701 Broadcast Communications Department 702 Unicast Communication Department 800 UI section

Claims

1. A recorder, a collection unit that collects measurement data; a recording unit that records the measurement data; a transmission unit that transmits backup data obtained by duplicating the measurement data to another recorder connected to the recorder via a network; A recorder comprising:

2. the recording unit records a data file created from the time series of the measurement data, 2. The recorder according to claim 1, wherein the transmission unit transmits backup data, which is a copy of the data file, to the other recorder.

3. 3. The recorder according to claim 2, wherein the transmission unit instructs deletion of backup data corresponding to the measurement data used to create the data file when transmitting the backup data obtained by duplicating the data file.

4. a communication confirmation unit that confirms whether the other recorder is connected to the network; The recorder according to claim 1 , wherein the transmission unit transmits the backup data to the other recorders for which the communication has been confirmed among the other recorders.

5. the collecting unit collects measurement data for each channel; 2. The recorder according to claim 1, wherein the transmission unit changes the number of recorders to which the backup is to be sent depending on the importance level set for the channel.

6. 6. The recorder according to claim 5, wherein the transmission unit increases the number of recorders to which the backup data is to be transmitted as the importance set for the channel increases.

7. The recorder according to any one of claims 1 to 6, further comprising a display control unit that causes a display unit to display to which of the other recorders connected via the network the backup data has been backed up.

8. A recorder, a collection unit that collects measurement data; a storage unit for recording the measurement data; an other device data processing unit that acquires backup data that is a copy of measurement data recorded in another recorder connected via a network, The storage unit stores the backup data. A recorder characterized by:

9. 9. The recorder according to claim 8, further comprising a display control unit that causes a display unit to display which of the other recorders connected via the network has measurement data backed up in the memory unit of the recorder.

10. The recorder, Collect measurement data, Recording the measurement data; transmitting the backup data, which is a copy of the measurement data, to another recorder connected to the recorder via a network; A backup method comprising:

11. On the recorder, Collect measurement data, Recording the measurement data; transmitting the backup data, which is a copy of the measurement data, to another recorder connected to the recorder via a network; A backup program characterized by executing a process.

Images