JP2015201060A - sensor data collection system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system that converts or processes sensor data by a gateway device according to a rule, and that prevents a processing operation on the gateway device from being not fast enough when computational complexity on the gateway device increases as sensors increase in number or as the processing operation becomes complex.SOLUTION: A sensor data collection system is provided with means of dividing a processing process for data obtained from a sensor into a plurality and relating the divided processing processes to devices to execute the processing processes, provided with means of connecting and displaying the plurality of divided processing processes, and provided with means of setting to which device a displayed processing process is divided and related, and distributing the divided processing processes to the related devices. Further, the sensor data collection system is provided with a function of setting which device the processing process is divided and related to while displaying margin amounts of computation resources of the respective devices.

Description

  The present invention relates to a sensor data collection system including a sensor, a gateway device, and a data collection server.

  In various industrial fields, in order to realize automatic control and failure sign detection of equipment, there is an increasing need to collect and analyze data from sensors attached to equipment and infrastructure. For example, there is a need to collect data from a temperature sensor or a load sensor attached to a vehicle engine and to predict the replacement time of the component by analyzing the component load in the vehicle.

In order to analyze the sensor data and establish a data utilization method such as failure sign detection, in order to reduce the load on the M2M server that collects data from a large number of sensors and the data communication fee, A gateway device that is located in the middle and performs data filtering, processing, and compression is required.
Also, in order to improve the accuracy of data analysis, hypotheses are made about the data to be collected and how to use them, data is collected, statistical analysis and verification are performed, and hypotheses are reassembled based on the verification results and data is collected again. Such a hypothesis verification cycle is necessary, and it is necessary to dynamically update the data filtering and processing method on the gateway device.

  In Patent Document 1 below, one or a plurality of sensors, a gateway device that collects, converts, processes, thresholds, and connects data from the sensors, and can transmit to the M2M server at any time, and a sensor from the gateway device It consists of an M2M server that collects data, and the M2M server has a means to compress sensor data conversion / processing / threshold judgment / compression / transmission timing settings into binary and send it to the gateway, and the gateway device is compressed into binary In accordance with the various settings, the data collected from the sensor is subjected to conversion, processing, threshold judgment, and connection, and has a means for transmitting the sensor data to the data collection server at the transmission timing.

Japanese Patent Application No. 2013-158495 “Sensor Data Collection System”

  However, in Patent Document 1, although the processing operation on the gateway device can be changed only by distributing rules, the amount of calculation on the gateway device increases due to an increase in the number of sensors and the complexity of the processing operation. When there is a large number, there is a problem that processing operations in the gateway device are not in time. In particular, unlike a server, a gateway device is limited in CPU and memory resources, so there is a high possibility that operations will not be in time.

  The first object of the present invention is to provide a sensor data collection system that can divide a process for performing sensor data processing based on rules such as Patent Document 1 into a plurality of computer resources, and further, The second object of the present invention is to provide a sensor data collection system capable of supporting rule setting across a plurality of computers.

In order to achieve the first object, the present invention is characterized in that there is provided means for dividing a processing process into a plurality of parts and associating the divided processing process with a device to be processed. In other words, a rule that sets the conversion and processing of sensor data and the gateway device that performs conversion and processing on the data collected from the sensor according to the rule definition for setting the conversion and processing of sensor data and sends it to the intermediate server at the base A data collection server that performs conversion and processing on the data collected from the intermediate server according to the definition;
The data collection server includes means for managing the association between rules for data conversion / processing and devices for executing the processing, and distributing the rules to the gateway device and the intermediate server associated with the rules based on the association. It is characterized by.
Also, in order to achieve the second purpose, a means for connecting and displaying the plurality of divided processing processes is provided, the displayed processing process is divided, and the device to be associated is set and associated. Means are provided for distributing the divided processing to the device. Further, the present invention is characterized in that there is provided means for dividing the processing process and setting which device is associated with the display while displaying a surplus amount of calculation resources of each device. That is, the data collection server edits the conversion / processing process while displaying the calculation capacity of the gateway apparatus and the intermediate server, and uses the edited result as a rule for new data conversion / processing process. The apparatus further comprises means for distributing to the server.

According to the present invention, processing operations based on rules can be processed in cooperation with a plurality of devices such as a base server and a vehicle, and rules can be edited collectively across a plurality of devices. . Also, by displaying the calculation power, for example, if the remaining calculation power of vehicle A decreases as a result of continuing to add processing rules to vehicle A, the rule is deleted from vehicle A, and the deleted rule is By adding to the server A, it is possible to determine that the processing is distributed.

1 is an overall configuration diagram showing an embodiment of a sensor data collection system according to the present invention. It is the figure which showed the software structure of the gateway apparatus. It is the figure which showed the software configuration of the base server. It is the figure which showed the software structure of the M2M server. It is the figure which showed the structural example of the conversion and process rule on a gateway apparatus. It is the figure which showed the example of a structure of the conversion and processing rule on a base server. It is the figure which showed the structure of the device management table. It is the figure which showed the structure of the sensor data table. It is the figure which showed the example of the rule management table. It is the figure which showed the example of the process calculation / calculation resource table. It is the figure which showed a series of processes of data acquisition, processing, and accumulation. It is a figure showing a rule edit / distribution function.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
In this embodiment, an example will be described in which data collection from a large number of sensors installed in an industrial vehicle such as a construction machine is distributed with base servers set at a construction site or the like.
FIG. 1 is a diagram showing the configuration of the entire system.
A plurality of vehicles 110 are operating inside a site such as a construction site. In the present embodiment, it is assumed that three vehicles A, B, and C are operating. A base server 130 is installed inside the base and is connected to the vehicle 110 via the WiFi network 120.
A sensor group 111 is attached to the vehicle 110 so that data such as the coolant temperature and the engine speed can be acquired.

  Data acquired by the sensor group 111 is collected by the gateway device 113 (gateway device) through the CAN network 112. The configuration of the gateway device 113 will be described later with reference to FIG. The gateway device 113 converts and processes the aggregated data according to the conversion / processing rules that are installed in advance, and transmits the data to the base server 130 through the WiFi 120.

  The base server 130 converts and processes the data received from the vehicle 110 according to the conversion / processing rules that are mounted in advance, and sends the data to the M2M server 150 through the Internet 140. The M2M server 150 has a function of editing and distributing the conversion / processing rules installed in the gateway device 113 and the base server 130 and a function of storing data transmitted from the gateway device 113. A detailed configuration is shown in FIG. The business system 170 provides a business support function such as using the data stored in the M2M server 130 to visualize the data by overlaying it with a map, for example.

FIG. 2 is a diagram showing the configuration of the gateway device 113.
The hardware of the gateway device consists of a permanent storage such as a CPU, RAM, flash ROM, etc., and an interface device for communicating with the CAN network 112 and the WiFi 120, and further includes an operating system such as Linux (registered trademark). On top of that, software and data as shown in FIG. 2 exist.

The data acquisition unit 210 acquires sensor data from the sensor group 111 through the CAN network 112. Here, the sensor data is broadcast from the sensor group 111 to the CAN network 112 at an arbitrary timing. The data format is a concatenation of CAN ID and sensor data binary data. The data acquisition unit 210 receives all broadcast data.
The conversion / processing unit 220 converts / processes the sensor data acquired by the data acquisition unit 211 in accordance with the conversion / processing rule described in the rule 250.
The data up unit 230 transmits the data converted and processed by the conversion / processing unit 220 to the base server 130 through the WiFi 120.
The rule acquisition unit 240 acquires / updates the conversion / processing rules stored in the rule 250 from the M2M server 130.
The rule 250 is a conversion / processing rule used in the conversion / processing unit 220, and a detailed configuration will be described with reference to FIG. 4 using an example. In the device information 260, a device ID for identifying the device and a type representing the hardware of the device are stored in advance.

FIG. 3 is a diagram illustrating the configuration of the base server 130.
The base server hardware includes a persistent storage such as a CPU, RAM, and flash ROM, and an interface device for communicating with the WiFi 120 and the Internet 130, and further includes an operating system such as Linux (registered trademark). On top of that, software and data as shown in FIG. 3 exist.
The data acquisition unit 310 acquires data transmitted from the vehicle 110 through the WiFi 120.
The conversion / processing unit 320 converts / processes the sensor data acquired by the data acquisition unit 310 according to the conversion / processing rule described in the rule 350.
The data-up means 330 transmits the data converted / processed by the conversion / processing means 330 to the M2M server 150 via the Internet 140.
The rule acquisition unit 340 acquires / updates the conversion / processing rules stored in the rule 350 from the M2M server 150.
A rule 350 is a conversion / processing rule used in the conversion / processing unit 220, and a detailed configuration will be described with reference to FIG. In the device information 360, a device ID for identifying the device and a type representing the hardware of the device are stored in advance.

FIG. 4 is a diagram showing the configuration of the M2M server 150. The hardware of the M2M server is composed of an interface device for communicating with the CPU, RAM, HDD, in-house network 160, and Internet 140, and is further equipped with an operating system such as Linux (registered trademark). 4 includes software and data as shown in FIG.
The data collection unit 410 receives data transmitted from the base server 130 and stores it in the sensor data table 440. The configuration of the sensor data table 440 will be described with reference to FIG. The device management unit 420 manages the parent-child relationship between the base server 130 and the vehicle 110. Data used in this function is managed in the device management table 450. The configuration of the device management table will be described with reference to FIG.
The rule editing / distribution means 430 registers the conversion / processing rules managed by the rule management table 460 from the outside through the in-house network 160. The configuration of the rule management table 460 will be described with reference to FIG.
The processing / calculation resource table 470 is a table used by the rule editing / distribution means 430, and the configuration will be described with reference to FIG.

  As described above, how the gateway device 113, the base server 130, and the M2M server 140 shown in FIGS. 2, 3, and 4 are actually used is described in FIG. 11 using a series of processing examples. . The data structure will be described with reference to FIGS.

FIG. 5 shows an example of the rules 250 used by the conversion / processing means 220 on the gateway device 113. In this embodiment, it is assumed that the same rules as those in this figure are stored in all the gateway devices of vehicle A, vehicle B, and vehicle C. Tables indicated by 511 to 525 represent conversion rules.
Reference numeral 511 denotes a CAN ID flowing through the CAN network 112. 512 indicates the corresponding data type, 513 indicates the byte order, 514 and 515 indicate the data position, and 516 indicates the data type to be converted. For example, 521 matches when the CAN ID of the data flowing through the CAN network is “AAA”, and the data from the 0th byte to the 8th byte is identified as “engine coolant temperature” and is arranged in little endian. The rule is to convert data to int16 type.
The example of 522 matches when the CAN ID of the data flowing through the CAN network 112 is “AAA”, and the data from the 8th byte to the 16th byte is identified as “engine speed” and is arranged in little endian. The rule is to convert the data to uint16 type.

Reference numerals 541 and 544 denote processing rules for processing data identified and converted according to the conversion rules. For example, reference numeral 541 denotes a processing rule for data identified and converted as “engine coolant temperature” by the conversion rule. This means that the “maximum value” of “600 seconds” of the corresponding data is acquired, stored with a data length of “1 byte”, and identified by the processed data ID “D01”. In an example of complicated processing, there is also processing for acquiring a histogram as in 543. 543 shows a processing rule for data identified and converted as “engine coolant temperature” by the conversion rule. This means that a “histogram” of “temperature 0 to 20 degrees width, number of sections 5” is created, stored in the “15 bytes” area, and identified as the data ID “D03”.
544 represents data to be processed by the base server 130, and means that the data identified as “engine speed” is transferred to the base server 130 as it is.

FIG. 6 is an example of the rule 350 in the base server 130.
A part having a configuration different from the processing rule of FIG. 5 is a device ID in the column 616. This is intended to process only data transmitted from the vehicle with the corresponding device ID.

FIG. 7 is a diagram showing the configuration of the device management table 450.
The device ID 711 is based on information managed by the device information 260 and the device information 360. The parent device 713 manages the parent-child relationship of devices. The parent-child relationship in the example of FIG. 7 is based on the relationship shown in FIG. 1 in which the base server 130 is connected under the M2M server 150 and the vehicles A, B, and C are connected thereunder. Yes. The calculation resource 714 is a numerical value obtained by quantifying the calculation power calculated from the CPU frequency, the RAM capacity, and the like.

  FIG. 8 shows the configuration of the sensor data table 440. Data transmitted from the gateway device 113 via the base server 130 is stored as a set of time, device ID, processing data ID, and data. How the data is specifically stored will be described in a series of processes in FIG.

  FIG. 9 shows the configuration of the rule management table 460. Reference numerals 911 to 922 store device IDs and conversion / processing rules stored in the corresponding gateway device or base server 130. In 912, conversion / processing rules as exemplified in FIGS. 5 and 6 are stored in a text expression such as XML.

  FIG. 10 is a configuration example of the machining calculation / calculation resource table 470. As shown in FIG. 5 and FIG. 6, an index quantified based on a measure such as CPU time and consumed memory is managed as to how much processing resources the processing operation requires. Column 1011 shows the processing operation type, and column 1012 shows the calculation resource amount.

FIG. 11 is a diagram for explaining a flow of a series of processes until sensor data is collected, converted and processed by the gateway device (gateway device apparatus) 113 and the base server 130 and accumulated in the M2M server 150.
<Step 1110>
The gateway device 113 uses the data acquisition unit 210 to acquire data from the sensor group that flows through the CAN network 112.
<Step 1120>
Data acquired according to the conversion rule of rule 250 is processed. For example, if data called CAN ID AAA is received, processing that matches the rules of the rows 421 and 422 is performed. That is, 0-8 bits of received data are converted to int16 type as little endian, stored in RAM in pairs with an identifier indicating "engine coolant temperature", and uint16 type is received with 8-16 bits of received data as little endian. And stored in the RAM in pairs with an identifier indicating “engine speed”.
<Step 1130>
The data on the RAM stored in step 1120 is processed according to the processing rule of rule 250. For example, for the data identified by “engine coolant temperature”, the processing shown in rows 541 and 543 is performed. In other words, the maximum value of data over 600 seconds is acquired. The data length is 1 byte, stored in RAM as a pair with an ID of D01, and the histogram is acquired for 100 hours, and then stored in the RAM as a pair with an ID of D03. To do. Here, it is assumed that logic necessary for processing such as logic for obtaining a maximum value and logic for taking a histogram is built in the conversion / processing means 220 in advance.
Note that data of a data type (in this embodiment, data identified by “engine speed” in this embodiment) that matches the line where the machining data ID is “through” as in the line 544 is left as is in step 1140. To pass.
<Step 1140>
The device ID stored in the device information 260 and the transmission time are added to the data on the RAM stored in step 1130 and transmitted to the base server 130. That is, the device ID, transmission time, processed data ID, and processed data are transmitted.
In step 1130, data of a data type that matches a line whose processing data ID is “through” is transmitted to the base server 130 with a device ID, a transmission time, and a data type.

<Step 1150>
This is a process for receiving the data transmitted in step 1140. The data transmitted in step 1140 as a combination of the device ID, transmission time, processed data ID, and processed data is transmitted to the M2M server 150 as it is.
In step 1140, the data transmitted with the device ID, transmission time, data type, and data set is passed to the processing in step 1160.
<Step 1160>
Processing is performed according to the processing rule of rule 350 illustrated in FIG. In this example, for each device ID specified in column 616, data identified by “engine speed” is continuously accumulated for 600 seconds, and a fast Fourier transform operation is performed at a frequency of 0 to 10,000 hz and a section width of 100 hz. , D04, the processing data ID, the device ID that became the transmission source in step 1140, and the time after the completion of the calculation are stored in the RAM as a pair.
<Step 1170>
In step 1160, the device ID, time, processed data ID, and processed data stored in the RAM are transmitted to the M2M server 150.
<Step 1180>
The M2M server 150 receives the data transmitted in steps 1150 and 1170 and stores it in the sensor data table 440 as shown in FIG. The business system 170 uses the sensor data accumulated in this way.

FIG. 12 is a diagram showing the main functions of the rule editing / distribution means 430 in the M2M server 150. A tree is displayed based on the parent-child relationship shown in the device management table 450 of FIG. 7, and the remaining calculation power is displayed based on the processing calculation calculation resource table 470. When the rule editor looks at this remaining calculation power, it is possible to roughly know the calculation capacity of the device, which can be used as a reference for editing.
An example of the calculation method of the remaining calculation power is described below.
The remaining computing power of the vehicle A of 1220 is obtained by “the computing resource of the device management table—the sum of the computing resources in the rule”. The computing resource of the device management table is 500 according to FIG. Referring to FIG. 9, the sum of the calculation powers in the rule is 50, 100, and 200, respectively, as shown in FIG. 9, so the sum is 350, and the calculation power described in 1220 is “ 500-350 "is marked as" 150 ". The remaining computing power of the base server A 1210 is “the computing resource of the device management table—the sum of the computing power in the rule”. This also becomes “5000-1500 = 3500”. When 1210, 1220, 1230, and 1240 are selected, an addition / deletion operation can be performed on the tables as shown in FIGS. The edited result is stored as a text expression in the rule management table of FIG. 9, and after editing, the data stored in the rule management table of FIG. 9 is distributed to the device with the corresponding device ID, and the corresponding rule 250 and rule 350 are stored. Saved.

As described above, according to the above-described embodiment, the processing operation based on the rule can be divided and processed by the plurality of devices such as the base server and the vehicle, and the editing and setting of the rule can also be performed on the plurality of devices. It can be performed in a lump across. And by displaying the calculation power as shown in FIG. 12, for example, when the remaining calculation power of the vehicle A is reduced as a result of continuously adding the processing rule to the vehicle A, the rule is deleted from the vehicle A By adding the deleted rule to the base server A, it is possible to determine that the processing is distributed.

110 Vehicle 111 Sensor group 112 CAN network 113 Gateway device (gateway device)
120 WiFi
130 Base server 140 Internet 150 M2M server 160 Internal network 170 Business system

Claims (2)

According to the rule definition that sets the conversion and processing of sensor data, the gateway device that executes the conversion and processing on the data collected from the sensor according to the rule definition that sets the conversion and processing of sensor data, and the rule definition that sets the conversion and processing of sensor data A data collection server that performs conversion and processing on the data collected from the intermediate server,
The data collection server includes means for managing the association between rules for data conversion / processing and devices for executing the processing, and distributing the rules to the gateway device and the intermediate server associated with the rules based on the association. Sensor data collection system characterized by   The data collection server edits the conversion / processing process while displaying the calculation capacity of the gateway apparatus and the intermediate server, and the editing result is transferred to the gateway apparatus and the intermediate server as a new data conversion / processing rule. The sensor data collection system according to claim 1, further comprising means for distributing.

Images