Wireless sensor management device, wireless sensor management system, and wireless sensor management method

Abstract

To allow for centrally managing multiple wireless sensors configured to output data in different formats.SOLUTION: A wireless sensor management device provided herein is for managing multiple wireless sensors configured to output data in different formats, and comprises a reception unit for receiving data output by the wireless sensors, a data conversion unit for converting formats of received data into a common format, and a diagnosis unit configured to diagnose the states of the multiple wireless sensors using the post-conversion data converted to the common format.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a wireless sensor management device, a wireless sensor management system, and a wireless sensor management method for managing the status of a plurality of wireless sensors installed within a predetermined area. [Background technology]

[0002] In order to acquire information necessary for manufacturing steel products, various sensors such as temperature sensors, pressure sensors, position sensors, speed sensors, and acceleration sensors are installed in each facility of a steelworks or the like. The data acquired by each sensor is transmitted to a server via a network and used, for example, to manage the operating status of the facility and each sensor.

[0003] In recent years, in order to strengthen facility maintenance management, the number of sensors installed in facilities has increased, and the amount of data acquired has also increased. If all the data acquired by each sensor were in the same format, this data could be efficiently managed centrally. However, in reality, multiple sensors provided by different vendors are used. Since the format of the data output by the sensors differs depending on the vendor, the format of the data sent from each sensor to the server is not unified, and it is not possible to perform the same processing on all data.

[0004] In relation to such a problem, for example, Patent Document 1 discloses a management device that acquires first device information that is defined in common for multiple devices and second device information that is unique to each device from each device. This makes it possible to acquire and manage device information from multiple vendors in a unified manner using a single device. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2014-157622 Summary of the Invention [Problem to be solved by the invention]

[0006] Here, the multiple devices managed by the management device described in Patent Document 1 are connected to a network via a wire, and device information can be obtained at all times. Therefore, if an abnormality occurs in a device, the device information cannot be obtained, and the status of devices and sensors connected to the network via a wire can be relatively easily determined. From the perspectives of installation flexibility and installation costs, it is expected that wireless sensors will be widely adopted in the future, and it is also required to be able to determine the status of wireless sensors in the same way as devices and sensors connected to the network via a wire.

[0007] However, the formats of data output by wireless sensors are not all the same and usually differ depending on the manufacturer. If the formats of data output from multiple wireless sensors are different, it is not possible to handle all received data in the same way, and data management cannot be performed efficiently. For this reason, it is desirable to be able to efficiently manage all data acquired by multiple wireless sensors in a unified manner, even if the formats of the data are different.

[0008] Therefore, the present invention has been made in consideration of the above problems, and an object of the present invention is to provide a wireless sensor management device, a wireless sensor management system, and a wireless sensor management method that are capable of centrally managing multiple wireless sensors that output data in different formats. [Means for solving the problem]

[0009] In order to solve the above problem, according to one aspect of the present invention, there is provided a wireless sensor management device that manages multiple wireless sensors that output data in different formats, the wireless sensor management device comprising: a receiving unit that receives the data output by the wireless sensors; a data conversion unit that converts the format of the received data into a common format; and a diagnosis unit that diagnoses the status of the multiple wireless sensors using the converted data converted into the common format.

[0010] The data conversion unit can convert binary data included in the received data into text data in a common format.

[0011] The diagnostic unit may calculate the amount of power consumed during the operation of the wireless sensor based on the data transmission period of the wireless sensor identified based on the converted data and the number of data transmitted, and may calculate the remaining battery capacity of the wireless sensor based on the amount of power consumed and the battery capacity of the wireless sensor.

[0012] The diagnostic unit may also obtain the battery voltage of the wireless sensor from the converted data, and calculate the remaining battery capacity of the wireless sensor from the battery voltage based on a relationship between the battery voltage and the remaining battery capacity that has been obtained in advance.

[0013] The wireless sensor management device may further include a control unit that controls the wireless sensors. In this case, the diagnosis unit may calculate the battery life from the calculated remaining battery charge and identify wireless sensors whose battery life will come before the scheduled maintenance date, and the control unit may change the data transmission period of the wireless sensors whose battery life will come before the scheduled maintenance date.

[0014] The diagnosis unit may also calculate a record of data reception from the wireless sensor based on the converted data, and detect an abnormality in the communication state of the wireless sensor based on the record of data reception from the wireless sensor.

[0015] The diagnosis unit may also acquire the receiving sensitivity of the wireless sensor based on the converted data, and detect an abnormality in the communication state of the wireless sensor based on the receiving sensitivity of the wireless sensor.

[0016] The multiple wireless sensors are classified into multiple groups, and the diagnostic unit may identify a group, among the groups to which the wireless sensors that have detected an abnormality in the communication state belong, in which an abnormality in the communication state has been detected in a wireless sensor that is equal to or greater than a reference value, and detect that an abnormality has occurred in the communication state of the wireless sensors on a group-by-group basis.

[0017] The wireless sensor management device may further include an output unit that outputs a diagnosis result from the diagnosis unit to an output device.

[0018] In addition, in order to solve the above-mentioned problems, according to another aspect of the present invention, there is provided a wireless sensor management system in which a plurality of wireless sensors that output data in different formats, a gateway terminal that transmits and receives data to and from the wireless sensors, and a wireless sensor management device that manages the wireless sensors are connected via a network, and the wireless sensor management device includes a receiving unit that receives the data output from the wireless sensors via the gateway terminal, a data conversion unit that converts the format of the received data into a common format, and a diagnosis unit that diagnoses the status of the plurality of wireless sensors using the converted data converted to the common format.

[0019] Furthermore, in order to solve the above-mentioned problems, according to another aspect of the present invention, there is provided a wireless sensor management method for managing a plurality of wireless sensors that output data in different formats, the wireless sensor management method including a receiving step for receiving data output by the wireless sensors, a data conversion step for converting the format of the received data into a common format, and a diagnosis step for diagnosing the status of the plurality of wireless sensors using the converted data converted into the common format. [Effects of the Invention]

[0020] As described above, according to the present invention, by converting the different data formats output by wireless sensors into a common format and diagnosing the status of the wireless sensors using the converted data, it is possible to centrally manage multiple wireless sensors that output data in different formats. [Brief explanation of the drawings]

[0021] [Figure 1] 1 is a block diagram showing an example of the configuration of a wireless sensor management system according to an embodiment of the present invention; [Figure 2] FIG. 2 is an explanatory diagram illustrating an example of data stored in a data storage unit. [Figure 3] FIG. 10 is an explanatory diagram showing an example of the configuration of a converted data DB; [Figure 4] FIG. 10 is an explanatory diagram illustrating an example of a configuration of a data conversion table. [Figure 5] FIG. 10 is an explanatory diagram illustrating an example of the configuration of a sensor table. [Figure 6] FIG. 10 is an explanatory diagram illustrating an example of the configuration of a sensor type table. [Figure 7] FIG. 10 is an explanatory diagram illustrating an example of a configuration of a gateway information table. [Figure 8] FIG. 2 is an explanatory diagram illustrating an example of the configuration of a function table. [Figure 9] FIG. 10 is an explanatory diagram illustrating an example of the configuration of an alarm table. [Figure 10] FIG. 10 is an explanatory diagram illustrating an example of the configuration of a group management table. [Figure 11] FIG. 10 is an explanatory diagram illustrating an example of the configuration of a maintenance management table. [Figure 12] 10 is a flowchart illustrating a wireless sensor management method according to the embodiment. [Figure 13] 10 is a flowchart illustrating a data conversion process according to the embodiment. [Figure 14] FIG. 10 is an explanatory diagram for explaining a data conversion process for converting binary data of individual data into text data. [Figure 15]10 is a flowchart illustrating a method for diagnosing the communication status of a wireless sensor based on the transmission period of the wireless sensor. [Figure 16] 10 is a flowchart illustrating a method for diagnosing the communication status of a wireless sensor based on the reception sensitivity of the wireless sensor. [Figure 17] 10 is a flowchart illustrating an example of a process for diagnosing abnormalities in wireless sensors in units of groups. [Figure 18] 10 is a flowchart illustrating a method for diagnosing the remaining battery charge of a wireless sensor based on the transmission period of the wireless sensor. [Figure 19] 10 is a flowchart illustrating a method for diagnosing the remaining battery capacity of a wireless sensor based on the battery voltage. [Figure 20] 10 is a graph showing an example of a voltage gradient-battery remaining capacity conversion table. [Figure 21] 10 is a flowchart illustrating an example of a process for changing the transmission cycle of a wireless sensor. [Figure 22] FIG. 2 is a block diagram showing an example of a hardware configuration of an information processing device that functions as a wireless sensor management device according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0022] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In this specification and drawings, components having substantially the same functional configurations are designated by the same reference numerals, and redundant explanations will be omitted.

[0023] [1. System Configuration] First, a schematic configuration of a wireless sensor management system 1 according to an embodiment of the present invention will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of the wireless sensor management system 1 according to this embodiment.

[0024] As shown in Fig. 1, the wireless sensor management system 1 includes gateway terminals 70 for a plurality of areas 10 (e.g., areas 10A, 10B, and 10C) and a wireless sensor management device 100, which are connected via a network 5. An area 10 is, for example, a steelworks, a factory or facility within the steelworks, etc., and is an area managed by one gateway terminal 70. Fig. 1 shows the system configuration within only area 10A, but the other areas 10B and 10C are also assumed to be configured in the same way.

[0025] [1-1. Area Composition] A plurality of wireless sensors 30 (wireless sensors 31, 32, ..., 3n) are installed in the area 10 to acquire information within the area. The wireless sensors 30 are, for example, temperature sensors, pressure sensors, position sensors, speed sensors, acceleration sensors, humidity sensors, illuminance sensors, etc. Each wireless sensor 30 transmits acquired data to the gateway terminal 70 via an antenna 50. The format of the data acquired by the wireless sensors 30 and transmitted to the gateway terminal 70 is not particularly limited. The wireless sensors 30 may output data in the same format or in different formats.

[0026] The antenna 50 converts radio waves received from the wireless sensors 30 into electrical signals, and then converts the electrical signals into radio waves and transmits them to the wireless sensors 30. The antenna 50 may be a single antenna capable of communicating with all wireless sensors 30 within the area. Alternatively, multiple antennas may be installed within the area depending on the communication method of each wireless sensor 30.

[0027] The gateway terminal 70 records the data received from each wireless sensor 30 via the antenna 50 in the data storage unit 75. The data storage unit 75 stores the data acquired by each wireless sensor 30 as is.

[0028] FIG. 2 shows an example of data stored in the data storage unit 75. As shown in FIG. 2, the data acquired by the wireless sensor 30 includes a specified data area 75a and a message data area 75b. The specified data area 75a contains predefined data items. For example, as shown in FIG. 2, the specified data area 75a includes a number (No.) indicating the data storage location in the data storage unit 75, the data acquisition date and time, the data update date and time, the device name of the wireless sensor 30, the gateway name of the gateway terminal 70, the measurement time, the radio wave reception strength, the frequency, etc. The message data area 75b includes wireless sensor individual data (hereinafter simply referred to as "individual data"), which is the content of the data itself. In other words, the data measured by the wireless sensor 30 itself is input as binary data in the individual data.

[0029] At a predetermined timing, the gateway terminal 70 outputs the data stored in the data storage unit 75 to the wireless sensor management device 100. In addition, the gateway terminal 70 transmits the data received from the wireless sensor management device 100 via the antenna 50 to the wireless sensor 30 with which it is to communicate.

[0030] [1-2. Wireless sensor management device] The wireless sensor management device 100 is a device that manages wireless sensors 30 installed in an area 10 (e.g., areas 10A, 10B, and 10C) that is to be managed. As shown in Fig. 1, the wireless sensor management device 100 includes a receiving unit 110, a data conversion unit 120, a diagnosis unit 130, a control unit 140, an output unit 150, a converted data DB (database) 160, and a table DB (database) 170.

[0031] The receiving unit 110 receives data acquired by the wireless sensor 30 from the gateway terminal 70 in each area 10 connected via the network 5. The receiving unit 110 requests the gateway terminal 70 to transmit data for a predetermined period stored in the data storage unit 75 at a predetermined timing. The receiving unit 110 may request the gateway terminal 70 to transmit data every 10 minutes, for example. The receiving unit 110 stores the received data in a received data storage table in the table DB 170, which will be described later.

[0032] The data converter 120 converts the format of data stored in the received data storage table of the table DB 170 into a common format. The formats of data output by the wireless sensors 30 installed in the area 10 are determined by the specifications of the wireless sensors 30 and are often different. By using the data converter 120 to convert the formats of data output by multiple wireless sensors 30 into a common format, it becomes possible to efficiently manage data in a centralized manner. Specifically, the data converter 120 converts binary data included in the received data into text data in a common format. The data conversion process by the data converter 120 will be described in detail later. The data converter 120 stores the data converted into the common format (hereinafter also referred to as "converted data") in the converted data DB 160. Here, the common format refers to a format that enables the output data of the wireless sensors 30 to be handled uniformly by converting messages output by multiple wireless sensors 30, which consist of binary data consisting of a sequence of different data items and character string data that has no physical meaning, into text data consisting of a common sequence of data items and significant numerical values ​​that have physical meaning.

[0033] The diagnosing unit 130 diagnoses the status of the multiple wireless sensors 30 using the converted data converted into the common format. The diagnosing unit 130 may diagnose, for example, whether the wireless sensor 30 is in a measurement-disabled state, or may calculate the remaining battery charge of the wireless sensor 30 to diagnose the battery life. By diagnosing the status of the wireless sensor 30 by the diagnosing unit 130, it becomes possible to appropriately determine whether maintenance and inspection of the wireless sensor 30 are required, thereby reducing the inspection load of the wireless sensor 30. The diagnostic process by the diagnosing unit 130 will be described in detail later. The diagnosing unit 130 outputs the diagnosis result to the control unit 140 or the output unit 150.

[0034] The control unit 140 changes the settings of the wireless sensor 30 to control the operating state. When the operating state of the wireless sensor 30 needs to be changed based on the diagnosis result by the diagnosing unit 130, the control unit 140 generates setting change data for changing the settings of the wireless sensor 30. The control unit 140 then transmits the generated setting change data via the network 5 to the gateway terminal 70 in the area 10 where the wireless sensor 30 whose setting is to be changed is installed. The gateway terminal 70 that has received the setting change data transmits the setting change data via the antenna 50 to the wireless sensor 30 whose setting is to be changed. As a result, the settings of the wireless sensor 30 are changed based on the setting change data.

[0035] The output unit 150 is an interface that outputs the diagnosis result by the diagnosing unit 130 to an external device. For example, the output unit 150 outputs the diagnosis result to the output device 200. The output device 200 may be, for example, a display device or the like that can display information, or an audio output device or the like that can output audio, such as a speaker. This allows the diagnosis result by the diagnosing unit 130 of the wireless sensor management device 100 to be notified to an operator or the like.

[0036] The converted data DB 160 is a storage unit that stores data acquired by the wireless sensor 30 that has been converted into a common format by the data conversion unit 120 (i.e., converted data). Fig. 3 shows an example of the configuration of the converted data DB 160. As shown in Fig. 3, the converted data DB 160 that stores the converted data has a specified data storage unit 160a and a message data storage unit 160b, corresponding to the format of the data acquired by the wireless sensor 30 shown in Fig. 2.

[0037] The specified data storage unit 160a is an area in which predefined data items are stored. For example, as shown in Fig. 3, the specified data storage unit 160a stores a number (No.) indicating the data storage location in the converted data DB 160, the data acquisition date and time, the data update date and time, a gateway ID assigned to each gateway terminal 70, a manufacturer ID assigned to each manufacturer of the wireless sensor 30, a model ID assigned to each model of the wireless sensor 30, the device name of the wireless sensor 30, the gateway name, the measurement time, the radio wave reception strength, the frequency, etc. The measurement time has been converted from binary data to text data by the data conversion unit 120.

[0038] The message data storage unit 160b stores the individual data converted into text data. The message data storage unit 160b has storage areas for, for example, individual data 1 to 20, and each storage area stores a value obtained by converting the individual data output from the wireless sensor 30 into text data. For example, each storage area for individual data stores values ​​such as battery voltage, pressure, temperature, and contact signal (for example, the ON / OFF signal of a tank fullness sensor).

[0039] Returning to the explanation of Fig. 1, the table DB 170 is a storage unit that stores various tables required for data processing in the wireless sensor management device 100. The table DB 170 stores, for example, a received data storage table, a data conversion table, a sensor table, a sensor type table, a gateway information table, a function table, an alarm table, a group management table, a maintenance management table, etc. Examples of the configuration of each table are shown in Figs. 4 to 11. Note that the configuration of the received data storage table is the same as the configuration of the data storage unit 75 shown in Fig. 2, so a detailed description will be omitted.

[0040] 4 shows an example of the configuration of data conversion table 1710. Data conversion table 1710 is a table used by data conversion unit 120 in the data conversion process, and stores data conversion information used to convert binary data included in data output by wireless sensor 30 into text data. Data conversion table 1710 stores, for example, a number (No.) representing the data conversion information stored in data conversion table 1710, a manufacturer ID, a model ID, an individual data offset, an offset length, an individual data number, a conversion function ID, a data item name, and a header code (message type).

[0041] The individual data offset indicates the data start position in the individual data of the data output by the wireless sensor 30. The offset length indicates the data length from the data start position indicated by the individual data offset. The individual data number indicates the location of the storage area in the message data storage unit 160b of the converted data DB 160. For example, data with the individual data number "1" is stored in the storage area of ​​"individual data 1" in the message data storage unit 160b of the converted data DB 160. The conversion function ID indicates the conversion function used to convert binary data to text data. The data item name indicates the item name of the converted data obtained by the data conversion process. The header code (message type) is information for identifying the message structure of the individual data.

[0042] 5 shows an example of the configuration of the sensor table 1720. The sensor table 1720 is a table used by the data conversion unit 120 in the data conversion process, and stores information specific to each wireless sensor 30. The sensor table 1720 stores, for example, a number (No.) indicating the data storage location in the sensor table 1720, a gateway ID, a manufacturer ID, a model ID, a device name, an operation start date, a transmission cycle, a lifespan date and time, a remaining battery level, a predicted remaining battery level date and time, a reference receiving sensitivity, an initial receiving sensitivity, a reference unreceived ratio, a maintenance group No., a location group No., a power supply group No., and a display sensor name.

[0043] The operation start date is the date on which the wireless sensor 30 began to be used. The transmission cycle indicates the data transmission cycle of the wireless sensor 30. The lifespan date and time indicates the most recently calculated date and time when the battery of the wireless sensor 30 will run out. The remaining battery capacity indicates the remaining battery capacity of the wireless sensor 30. The predicted remaining capacity date and time indicates the date and time when the lifespan date and time was calculated. The reference receiving sensitivity indicates the receiving sensitivity that serves as the reference for evaluating the receiving sensitivity of the wireless sensor 30. The initial receiving sensitivity indicates the initial receiving sensitivity of the wireless sensor 30. The reference unreceived ratio is the ratio of unreceived data that serves as the reference when diagnosing an abnormality in the wireless sensor 30. The unreceived ratio is the ratio of unreceived data that was not received by the gateway terminal 70 out of the data transmitted by the wireless sensor 30. The maintenance group number indicates a group of wireless sensors 30 that will undergo maintenance inspection at the same time. The location group number indicates a group of wireless sensors 30 that are grouped according to the installation location of the wireless sensors 30. The power supply group number indicates a group of wireless sensors 30 that use the same power supply. The maintenance group number, location group number, and power group number in the sensor table 1720 indicate the group to which each wireless sensor 30 belongs, using the group number defined in the group management table 1770 described below. The display sensor name indicates the display name of the wireless sensor 30.

[0044] 6 shows an example of the configuration of the sensor type table 1730. The sensor type table 1730 is a table used by the data conversion unit 120 in the data conversion process, and stores information related to the battery specifications of the wireless sensor 30. The sensor type table 1730 stores, for example, a number (No.) indicating the data storage position in the sensor type table 1730, a manufacturer ID, a model ID, a voltage gradient-remaining battery capacity conversion table, battery capacity, current consumption during operation, current consumption during standby, and operating time.

[0045] The voltage gradient-battery remaining capacity conversion table is information showing the relationship between battery voltage and remaining battery capacity. Battery capacity indicates the amount of electricity that the battery will discharge from 100% to 0%. Operating current consumption indicates the current required when the wireless sensor 30 is operating. Standby current consumption indicates the current required when the wireless sensor 30 is in standby. Operating time indicates the time that the wireless sensor 30 is in an operating state.

[0046] 7 shows an example of the configuration of the gateway information table 1740. The gateway information table 1740 is a table used by the receiving unit 110 and stores information related to the gateway terminal 70. The gateway information table 1740 stores, for example, a number (No.) indicating the data storage location within the gateway information table 1740, a gateway ID, an IP address, the last received date and time, and a displayed gateway name. The IP address indicates the IP address of the gateway terminal 70. The last received date and time indicates the date and time when the wireless sensor management device 100 last received data from the data storage unit 75. The displayed gateway name indicates the display name of the gateway terminal 70.

[0047] 8 shows an example of the configuration of the function table 1750. The function table 1750 is a table used by the data conversion unit 120 in the data conversion process, and stores information about the conversion functions used when converting binary data included in the data output by the wireless sensor 30 into text data. The function table 1750 stores, for example, a conversion function ID and a function name. The conversion function ID is unique information assigned to each conversion function. The function name indicates the display name of the conversion function.

[0048] 9 shows an example of the configuration of the alarm table 1760. The alarm table 1760 is a table used by the diagnosing unit 130, and stores alarm information output based on the diagnosis results of the diagnosing unit 130. The alarm table 1760 stores, for example, a number (No.) indicating the data storage location in the alarm table 1760, an alarm link, a sender, an alarm time, an alarm name, a comment, a status, a group No., and a sensor value.

[0049] The alarm link indicates a link to a storage location where detailed information about the issued alarm is stored. The sender indicates the alarm issuing method. The alarm time indicates the time when the alarm was issued. The alarm name indicates the status of the wireless sensor 30 (for example, the details of the abnormality occurring in the wireless sensor 30). The comment is the content notified by the alarm, and stores, for example, the device name of the wireless sensor 30. The status indicates the status of the wireless sensor 30 that caused the alarm to be issued. The group number indicates the number assigned to the group to which the wireless sensor 30 belongs, which is set in the group management table 1770 described below. The sensor value indicates the measurement value of the wireless sensor 30.

[0050] 10 shows an example of the configuration of the group management table 1770. The group management table 1770 is a table used by the diagnosis unit 130, and stores information about groups into which the wireless sensors 30 are classified. The group management table 1770 stores, for example, a number (No.) indicating the data storage location within the group management table 1770, a classification code, and a group No. The classification code is a category indicating the type of group. For example, classification code "1" indicates the maintenance group, classification code "2" indicates the power supply group, and classification code "3" indicates the location group, indicating the type of group. The group No. is a unique number assigned to each set group.

[0051] 11 shows an example of the configuration of the maintenance management table 1780. The maintenance management table 1780 is a table used by the diagnosing unit 130, and stores the maintenance schedule for the wireless sensor 30. The maintenance management table 1780 stores, for example, a number (No.) indicating the data storage location within the maintenance management table 1780, a group No., and a scheduled maintenance date. The scheduled maintenance date indicates the scheduled date for maintenance inspection of the wireless sensor 30.

[0052] The table DB 170 may store tables other than the above-mentioned tables 1710 to 1780.

[0053] The above describes one exemplary configuration of the wireless sensor management system 1 according to the present embodiment. While the wireless sensor management device 100 shown in FIG. 1 includes the receiving unit 110, the data conversion unit 120, the diagnosis unit 130, the control unit 140, the output unit 150, the converted data DB 160, and the table DB 170, the present invention is not limited to this example. One or more of the functional units included in the wireless sensor management device 100 may be included in a separate information processing device. For example, the wireless sensor management device 100 may be configured by an information processing device including the receiving unit 110 and the data conversion unit 120, an information processing device including the diagnosis unit 130, the control unit 140, and the output unit 150, and a server including the converted data DB 160 and the table DB 170.

[0054] [2. Wireless sensor management method] Next, a wireless sensor management method according to this embodiment will be described with reference to Fig. 12. Fig. 12 is a flowchart showing the wireless sensor management method according to this embodiment. In the following description, it is assumed that data acquired by the wireless sensors 30 in each area 10 is transmitted to the gateway terminal 70 at the transmission cycle of each wireless sensor 30 and stored in the data storage unit 75 as needed.

[0055] 12, in the wireless sensor management method according to this embodiment, first, the receiver 110 of the wireless sensor management device 100 receives data stored in the data storage unit 75 of each area 10 at a predetermined timing (S10). Next, the data converter 120 converts the format of the received data into a common format to generate converted data (S20). Then, the diagnostic unit 130 uses the converted data to diagnose the state of the wireless sensor 30 (S30).

[0056] In this way, by converting the formats of data output by multiple wireless sensors 30 into a common format, it becomes possible to efficiently and centrally manage the data. Furthermore, by standardizing the data formats, it becomes possible to efficiently and easily process huge amounts of data. The wireless sensor management method according to this embodiment will be described in detail below.

[0057] [2-1. Data reception process (S10)] The receiver 110 of the wireless sensor management device 100 receives data acquired by the wireless sensors 30 from the gateway terminals 70 in each area 10 connected via the network 5. At a predetermined timing, the receiver 110 requests the gateway terminal 70 to transmit data for a predetermined period stored in the data storage unit 75. The receiver 110 may request the gateway terminal 70 to transmit data every 10 minutes, for example.

[0058] The receiving unit 110 refers to the gateway information table 1740 and checks the last reception date and time when the wireless sensor management device 100 last received data from the data storage unit 75. The receiving unit 110 then requests the gateway terminal 70 to transmit data acquired after the last reception date and time. If the last reception date and time is not recorded in the gateway information table 1740, the receiving unit 110 requests the gateway terminal 70 to transmit all data stored in the data storage unit 75. In response to the request from the receiving unit 110, the gateway terminal 70 transmits the specified data to the wireless sensor management device 100. The receiving unit 110 then stores the received data in the received data storage table (see FIG. 2).

[0059] The data reception process is repeatedly executed the same number of times as the number of gateway terminals 70 (ie, areas 10) connected to the wireless sensor management apparatus 100 via the network.

[0060] [2-2. Data conversion process (S20)] Next, the data conversion unit 120 converts the format of the data stored in the received data storage table of the table DB 170 into a common format. The data conversion process will be described in detail below with reference to Fig. 13. Fig. 13 is a flowchart showing the data conversion process according to this embodiment. The data conversion process shown in Fig. 13 is executed for each wireless sensor 30, and data from the same wireless sensor 30 is processed collectively.

[0061] First, the data conversion unit 120 acquires the data acquired by the wireless sensor 30 and stored in the received data storage table in step S10 (S100). To acquire data from the same wireless sensor 30, the data conversion unit 120 selects data for each device name stored in the received data storage table and acquires the data to be processed.

[0062] Next, the data conversion unit 120 acquires the manufacturer ID and model ID of the data selected in step S100 from the sensor table 1720 (S110). The manufacturer ID and model ID can be acquired based on the device name included in the data, and by selecting the sensor table 1720 with the device name, the manufacturer ID and model ID corresponding to the device name can be obtained. For example, for the data shown in FIG. 2, by selecting the data in the sensor table 1720 shown in FIG. 5 with the device name "FEAA5284" of the data, the data No. 3 is found to be relevant, and it can be seen that the manufacturer ID for the device name "FEAA5284" is "5" and the model ID is "2".

[0063] Furthermore, the data conversion unit 120 acquires data conversion information corresponding to the data from the data conversion table 1710 based on the manufacturer ID and model ID acquired in step S110 (S120). The data conversion information is information used to divide the binary data stored in the message data area 75b of the received data storage table into items. As shown in FIG. 4, the data conversion information includes the data conversion information No., manufacturer ID, model ID, individual data offset, offset length, individual data number, conversion function ID, data item name, and header code (message type). The data conversion unit 120 acquires data conversion information that matches the manufacturer ID and model ID acquired in step S110 from the data conversion table 1710.

[0064] The format of the data output by the wireless sensor 30 is determined by the specifications of the wireless sensor 30 and often varies. Furthermore, the individual data is binary data, which is meaningless as is. Therefore, by using the data conversion information to convert the individual data into text data, the data becomes meaningful engineering values, making it easier to handle the data acquired by the wireless sensor 30.

[0065] For example, for the data shown in Fig. 2 above, the manufacturer ID "5" and model ID "2" are obtained in step S110. Therefore, data conversion unit 120 obtains data conversion information with manufacturer ID "5" and model ID "2" from data conversion table 1710. As a result, for example, data conversion information such as that shown in Fig. 4 can be obtained.

[0066] Then, based on the data conversion information acquired in step S120, data conversion unit 120 converts the binary data of the individual data acquired by wireless sensor 30 into text data (S130). Below, with reference to Fig. 14, a flow for converting the binary data of the individual data shown in Fig. 2 into text data will be described.

[0067] As shown in FIG. 14, the data "11000037533a2b4e48" of the individual data acquired by the wireless sensor 30 is binary data. The data conversion unit 120 first acquires data conversion information that matches the header code included in the individual data from the data conversion information acquired in step S120. The header code of the individual data is defined in individual data 1 of the data conversion information for the same manufacturer ID and model ID, and is specified as the first two characters of the individual data. The header code of the individual data shown in FIG. 14 is "11". Therefore, the data conversion unit 120 converts the data using the data conversion information (No. 32 to 36) for the header code "11" from the data conversion table 1710 in FIG. 4.

[0068] Next, the data conversion unit 120 divides the data of the individual data by item based on the individual data offset and offset length of the data conversion information for header code "11." In the example shown in FIG. 14, it can be seen from data conversion information No. 32 that two characters (offset length "2") from the beginning position of the individual data (position of individual data offset "0") correspond to the value stored in the storage area of ​​individual data 1 (individual data number "1"). Similarly, it can be seen from data conversion information No. 33 that four characters (offset length "4") from the third character of the individual data (position of individual data offset "2") correspond to the value stored in the storage area of ​​individual data 2 (individual data number "2"). Similarly, when the data of the individual data is divided based on data conversion information Nos. 34 to 36, it is divided into five parts as shown in FIG. 14.

[0069] Then, data conversion unit 120 converts each piece of the divided individual data from binary data to text data using a conversion function. The conversion function used when converting the binary data is specified by a conversion function ID in data conversion table 1710. Data conversion unit 120 refers to function table 1750, obtains a function name corresponding to the conversion function ID in data conversion table 1710, and converts the binary data into text data using the data conversion method indicated by the function name.

[0070] For example, consider the data conversion of binary data "4e48" with individual data number "5" shown in FIG. 14. This binary data is converted based on data conversion information No. 36. Because the conversion function ID of data conversion information No. 36 is "5," it can be seen from function table 1750 that the binary data should be converted using the half-precision data conversion method represented by the function name "HexToFloat16." As a result, the binary data "4e48" is converted into text data "25.1." Similarly, data conversion unit 120 converts each piece of the divided individual data into text data using a conversion function. Note that specified data storage unit 160a stores information in specified data area 75a of the data output by wireless sensor 30, or information obtained by referencing various tables from the information in specified data area 75a.

[0071] The data conversion unit 120 stores the converted data, obtained by converting binary data into text data in step S130, in the converted data DB 160 (S140). For example, in the example shown in Fig. 14, the individual data "11000037533a2b4e48" of the data acquired by the wireless sensor 30 is converted to "11", "0000", "0.4", "0.7", and "25.1", and these are stored in the storage areas for individual data 1 to 5 in the converted data DB 160, respectively. Note that, according to the data item names of the data conversion information (see Fig. 4), "11" in individual data 1 in Fig. 14 is the header code of the vibration data, "0000" in individual data 2 is the measurement value status, and "0.4" in individual data 3 is the acceleration peak value [m / s 2 ], "0.7" in individual data 4 is the speed RMS value [mm / s], and "25.1" in individual data 5 is the temperature measurement value [℃].

[0072] The data conversion process has been described above. The data conversion process is repeatedly executed in step S10 until all the data acquired by the wireless sensor 30 is exhausted. In this way, the data conversion unit 120 converts the binary data included in the data acquired by the wireless sensor 30 into text data in a common format. This makes it possible to efficiently and centrally manage data acquired by multiple wireless sensors even if the data formats are different. Furthermore, the converted data stored in the converted data DB 160 can be used to diagnose the status of the wireless sensor 30. Because the format of the converted data is standardized, there is no need to change the program that executes the diagnostic process for the status of the wireless sensor 30 to match the format of the data acquired by the wireless sensor 30, and all data can be handled and processed in the same way.

[0073] [2-3. Diagnostic process (S30)] The diagnosing unit 130 calculates the data reception record from the wireless sensor 30 using the converted data converted by the data conversion unit 120, and diagnoses the state of the wireless sensor 30 based on the data reception record from the wireless sensor 30. The diagnosing unit 130 diagnoses, for example, whether the wireless sensor 30 is in a state where it can transmit data and whether the remaining battery charge of the wireless sensor 30 is sufficient, as the state of the wireless sensor. If the diagnosing unit 130 can manage the state of the wireless sensor 30, such as the communication state and the remaining battery charge, the inspection load of the wireless sensor 30 can be reduced. Below, as examples of diagnosing the state of the wireless sensor 30, diagnosing the communication state of the wireless sensor 30 and diagnosing the remaining battery charge of the wireless sensor 30 will be described in detail.

[0074] [2-3-1. Diagnosis of wireless sensor communication status] The communication status of the wireless sensor 30 can be diagnosed based on, for example, the transmission cycle or reception sensitivity of the wireless sensor 30.

[0075] (a. Diagnosis based on the transmission cycle of wireless sensors) First, a method for diagnosing the communication state of the wireless sensor 30 based on the transmission cycle of the wireless sensor 30 will be described with reference to Fig. 15. Fig. 15 is a flowchart showing a method for diagnosing the communication state of the wireless sensor 30 based on the transmission cycle of the wireless sensor 30.

[0076] The diagnosis unit 130 acquires the data transmission period of the wireless sensor 30 to be diagnosed from the sensor table 1720 (S201a). For example, based on the device name of the converted data, the diagnosis unit 130 acquires the transmission period having the same device name from the sensor table 1720.

[0077] Next, the diagnosis unit 130 calculates the proportion of unreceived data transmitted from the wireless sensor 30 being diagnosed as a data reception record from the most recent n pieces of converted data of the wireless sensor 30 in question (S203a). The diagnosis unit 130 acquires the most recent n pieces of converted data of the wireless sensor 30 being diagnosed from the converted data DB 160. Note that pieces received at the same time are counted as one piece. The proportion of unreceived data can be calculated from the number N of data received in the period from the current time to n × transmission cycle [sec] ago using the following formula (1):

[0078] Unreceived rate [%] = (1-N / n) × 100 (1)

[0079] Then, the diagnosis unit 130 compares the data unreceived ratio calculated in step S203a with a reference value to diagnose the state of the wireless sensor 30 (S205a). The reference value is the value (upper limit) of the data unreceived ratio at which the communication state of the wireless sensor 30 can be determined to be normal, and the reference unreceived ratio in the sensor table 1720 is used.

[0080] If the unreceived ratio exceeds the reference value (S205a: YES), the diagnosis unit 130 diagnoses that the communication status of the wireless sensor 30 has deteriorated and that an abnormality has occurred in the wireless sensor 30 (S207a).The diagnosis unit 130 then records alarm information in the alarm table 1760 to notify that an abnormality has occurred in the wireless sensor 30.

[0081] The alarm information recorded in the alarm table 1760 is output by the output unit 150. When the output unit 150 records alarm information in the alarm table 1760, it outputs the alarm information to the output device 200. Based on the alarm information, the output device 200 notifies an operator that an abnormality has occurred in a wireless sensor 30 by displaying the alarm information on a display or outputting from a speaker that there is a wireless sensor 30 in which an abnormality has occurred. Based on the notification, the operator can take action to quickly resolve the abnormal state of the wireless sensor 30 by requesting a maintenance worker to inspect the wireless sensor 30.

[0082] On the other hand, if the unreceived data ratio is equal to or less than the reference value (S205a: NO), the diagnosis unit 130 diagnoses that the communication status of the wireless sensor 30 is normal (S209a) and ends the processing in Fig. 15. In this way, the diagnosis unit 130 detects an abnormality in the communication status of the wireless sensor 30 based on the unreceived data ratio, which is the data reception record from the wireless sensor 30. The processing in Fig. 15 is executed for each wireless sensor 30.

[0083] (b. Diagnosis based on wireless sensor reception sensitivity) Next, a method for diagnosing the communication state of the wireless sensor 30 based on the reception sensitivity of the wireless sensor 30 will be described with reference to Fig. 16. Fig. 16 is a flowchart showing the method for diagnosing the communication state of the wireless sensor 30 based on the reception sensitivity of the wireless sensor 30.

[0084] The diagnosis unit 130 acquires the initial receiving sensitivity of the data of the wireless sensor 30 to be diagnosed from the sensor table 1720 (S201b). The diagnosis unit 130 acquires the initial receiving sensitivity from the sensor table 1720 based on, for example, the device name of the converted data. If the initial receiving sensitivity is not recorded in the sensor table 1720, the diagnosis unit 130 may acquire it by calculating the average of the receiving sensitivity of the initial n pieces of data, and record it in the sensor table 1720 as the initial receiving sensitivity.

[0085] Next, the diagnosis unit 130 calculates the average receiving sensitivity of the wireless sensor 30 to be diagnosed from the most recent n pieces of converted data of the wireless sensor 30 (S203b). The diagnosis unit 130 obtains the most recent n pieces of converted data of the wireless sensor 30 to be diagnosed from the converted data DB 160, and calculates the average value of the radio wave receiving strength of the received n pieces of converted data as the average receiving sensitivity.

[0086] The diagnosis unit 130 then compares the average receiving sensitivity calculated in step S203b with a reference value to diagnose the state of the wireless sensor 30 (S205b). The reference value is the receiving sensitivity (lower limit) at which the communication state of the wireless sensor 30 can be determined to be normal, and the reference receiving sensitivity in the sensor table 1720 is used. The reference receiving sensitivity can be set arbitrarily, and may be set to a value that is, for example, about 80% of the initial receiving sensitivity. Since the receiving sensitivity varies depending on the installation location of the wireless sensor 30, the reference receiving sensitivity may be set taking into account the installation location of the wireless sensor 30.

[0087] If the average receiving sensitivity is below the reference value (S205b: YES), the diagnosis unit 130 diagnoses that the communication state of the wireless sensor 30 has deteriorated and that an abnormality has occurred in the wireless sensor 30 (S207b).The diagnosis unit 130 then records alarm information in the alarm table 1760 to notify that an abnormality has occurred in the wireless sensor 30.

[0088] The alarm information recorded in the alarm table 1760 is output by the output unit 150. When alarm information is recorded in the alarm table 1760, as in the case of Fig. 15 , the output unit 150 outputs the alarm information to the output device 200, and the output device 200 notifies an operator, based on the alarm information, that an abnormality has occurred in the wireless sensor 30. Based on the notification, the operator can take action to quickly resolve the abnormal state of the wireless sensor 30 by requesting a maintenance worker to inspect the wireless sensor 30.

[0089] On the other hand, if the unreceived ratio is equal to or less than the reference value (S205b: NO), the diagnosis unit 130 diagnoses that the communication status of the wireless sensor 30 is normal (S209b), and ends the processing in Fig. 16. In this way, the diagnosis unit 130 detects an abnormality in the communication status of the wireless sensor 30 based on the reception sensitivity of the wireless sensor 30. The processing in Fig. 16 is executed for each wireless sensor 30.

[0090] (c. Group diagnosis) 15 and 16, the diagnosis of the communication state of the wireless sensor 30 diagnoses whether or not an abnormality has occurred for each wireless sensor 30. Here, for example, if many of the wireless sensors 30 with deteriorating communication states are installed in the same area, it is possible that an abnormality has not occurred in the wireless sensor 30 itself, but rather in the area in which the wireless sensor 30 is installed. Therefore, based on the information of a wireless sensor 30 diagnosed as having an abnormality, the diagnosis unit 130 may further diagnose whether or not an abnormality has occurred in the group to which the wireless sensor 30 belongs. This makes it possible to find the cause of the abnormality in the wireless sensor 30 from a different perspective.

[0091] 17 shows an example of a process for diagnosing whether or not an abnormality has occurred in the wireless sensor 30 on a group basis. Here, it is assumed that a plurality of wireless sensors 30 installed in the area 10 are classified into a plurality of groups. Information about the groups into which the wireless sensors 30 have been classified is recorded in a group management table 1770. For example, the wireless sensors 30 can be classified into a maintenance group in which maintenance inspections are performed at the same time, a power supply group in which the wireless sensors 30 use the same power source, a location group in which the wireless sensors 30 are installed in the same area, and so on. As shown in FIG. 10, the group management table 1770 records a classification code indicating the type of group and a group number. The diagnosing unit 130 can identify the group to which the wireless sensor 30 belongs because the group number defined in the group management table 1770 is set in the sensor table 1720.

[0092] First, the diagnosis unit 130 refers to the alarm table 1760 and counts, for each group, the number of wireless sensors 30 that have been diagnosed as having an abnormality within a predetermined period of time (S211). The predetermined period can be set arbitrarily, and may be set to, for example, the past 24 hours. The diagnosis unit 130 counts the number of wireless sensors 30 with the same group number from each piece of alarm information stored in the alarm table 1760.

[0093] Next, the diagnosis unit 130 compares the count number for each group obtained in step S211 with a reference value (S213). The reference value is the number (lower limit) of wireless sensors 30 for which an abnormality is suspected on a group-by-group basis, and is set in advance. If the count number is equal to or greater than the reference value (S213: YES), the diagnosis unit 130 diagnoses that an abnormality has occurred in the wireless sensors 30 concentrated in a specific group (S215). Then, the diagnosis unit 130 newly records alarm information in the alarm table 1760 to notify that an abnormality has occurred in that group.

[0094] The alarm information recorded in the alarm table 1760 is output by the output unit 150. When the alarm information is recorded in the alarm table 1760, the output unit 150 outputs the alarm information to the output device 200, as in the cases of FIGS. 15 and 16 . Based on the alarm information, the output device 200 notifies an operator that an abnormality has occurred in the group. Based on the notification, the operator can take action to quickly resolve the abnormal state of the wireless sensors 30 by requesting a maintenance worker to inspect the wireless sensors 30 in the notified group.

[0095] On the other hand, if the count number is less than the reference value (S213: NO), the diagnosing unit 130 diagnoses that no abnormality has occurred in the wireless sensors 30 on a group-by-group basis (S217). After completing the process of step S215 or step S217, the diagnosing unit 130 checks whether the diagnosis has been performed on all groups included in the alarm information recorded in the alarm table 1760 (S219). If there are any groups that have not been diagnosed (S219: NO), the diagnosing unit 130 repeats the process from step S213. If the diagnosis has been completed on all groups (S219: YES), the diagnosing unit ends the process of FIG. 17.

[0096] In this way, the diagnosis unit 130 identifies a group in which a communication abnormality has been detected in a wireless sensor 30 that is equal to or greater than the reference value, among groups to which the wireless sensor 30 that detected the communication abnormality belongs, and detects that an abnormality has occurred in the communication state of the wireless sensor 30 on a group-by-group basis. If an abnormality is confirmed in multiple wireless sensors 30 in the same group, the diagnosis unit 130 can also notify the operator that an abnormality may have occurred on a group-by-group basis.

[0097] [2-3-2. Wireless sensor battery level diagnosis] The remaining battery level of the wireless sensor 30 can be diagnosed based on, for example, the transmission cycle or battery voltage of the wireless sensor 30 .

[0098] (a. Diagnosis based on the transmission cycle of wireless sensors) First, a method for diagnosing the remaining battery charge of the wireless sensor 30 based on the transmission cycle of the wireless sensor 30 will be described with reference to Fig. 18. Fig. 18 is a flowchart showing a method for diagnosing the remaining battery charge of the wireless sensor 30 based on the transmission cycle of the wireless sensor 30.

[0099] The diagnosis unit 130 acquires the battery capacity, operation start date, and data transmission cycle of the wireless sensor 30 to be diagnosed (S301a). The battery capacity can be acquired from the sensor type table 1730, for example, based on the model ID of the converted data. The battery capacity stored in the sensor type table 1730 may be a manufacturer-guaranteed value provided by the manufacturer of the wireless sensor 30, or an actually measured value. The operation start date and data transmission cycle can be acquired from the sensor table 1720, for example, based on the device name of the converted data.

[0100] Next, the diagnosis unit 130 calculates the remaining battery capacity of the wireless sensor 30 to be diagnosed from the most recent converted data of the wireless sensor 30 (S302a). The remaining battery capacity can be calculated using the following formula (2).

[0101] Battery remaining capacity [mAh] = (battery capacity [mAh]) - (power consumption [mAh]) (2)

[0102] Here, the power consumption is calculated using the following formula (3). Because the wireless sensor 30 alternates between standby and operation at each transmission cycle, the power consumption can be calculated from the current consumption and time for each. The number of receptions can be calculated from the number of data from the wireless sensor 30 recorded in the converted data DB 160 (i.e., the number of data transmitted by the wireless sensor 30), but receptions within the same operation time are counted as one reception. The operation time of the wireless sensor 30 is the time from the operation start date to the current date and time.

[0103] Power consumption [mAh] = (current consumption during operation [mA] x actual operating time [h]) + (Standby current consumption [mA] × Actual standby time [h]) (3) where: Actual operating time [h] = operating time [h] x number of receptions Actual standby time [h] = operation time [h] - actual operation time [h]

[0104] In this way, the diagnostic unit 130 calculates the power consumption during the operation period of the wireless sensor 30 using the above formula (3) based on the data transmission cycle of the wireless sensor 30 and the number of transmitted data items identified based on the converted data.The diagnostic unit 130 then calculates the remaining battery power of the wireless sensor 30 using the above formula (2) based on the calculated power consumption and the battery capacity of the wireless sensor 30.

[0105] The diagnostic unit 130 records the calculated remaining battery capacity and the estimated remaining capacity date and time when the calculation process was performed in the sensor table 1720. Then, the diagnostic unit 130 calculates the battery life date and time of the wireless sensor 30 based on the remaining battery capacity calculated in step S302a and the transmission cycle (S303a). The battery life date and time can be calculated using the following formula (4). Note that the operating time is the operating state time within one cycle of standby and operation per transmission cycle, and is considered to be a fixed time that does not fluctuate.

[0106] Lifespan date and time = current date and time + battery life [h] ···(4) where: Battery life [h] = Remaining battery capacity [mAh] / Power consumption per cycle [mAh] x Transmission cycle [h] Power consumption per cycle [mAh] = (current consumption during operation [mA] x operating time [h]) + {Standby current consumption [mA] × (transmission cycle [h] - operating time [h])}

[0107] The diagnostic unit 130 records the calculated end of life date and time in the sensor table 1720. The diagnostic unit 130 compares the end of life date and time calculated in step S303a with the scheduled maintenance date of the wireless sensor 30 (S304a). The diagnostic unit 130 can obtain the scheduled maintenance date of the wireless sensor 30 by referencing the maintenance management table 1780 from the group number of the wireless sensor 30. For example, if "022BF" is stored as the power group number in the sensor table 1720, referencing the maintenance management table 1780 reveals that the scheduled maintenance date for group number "022BF" is May 23, 2021.

[0108] If the battery life end date and time of the wireless sensor 30 is before the scheduled maintenance date (S304a: YES), the diagnosis unit 130 identifies the wireless sensor 30 as a wireless sensor 30 with insufficient battery power (S305a). Then, the diagnosis unit 130 records alarm information in the alarm table 1760 to notify that the battery power of the wireless sensor 30 is insufficient. The alarm information recorded in the alarm table 1760 is output by the output unit 150.

[0109] When alarm information is recorded in the alarm table 1760, the output unit 150 outputs the alarm information to the output device 200. Based on the alarm information, the output device 200 notifies an operator that the wireless sensor 30 has a low battery by displaying the alarm information on a display or outputting from a speaker that there is a wireless sensor 30 with a low battery. Based on the notification, the operator can take action to quickly resolve the low battery of the wireless sensor 30 by requesting a maintenance worker to inspect the wireless sensor 30.

[0110] On the other hand, if the battery life date and time of the wireless sensor 30 is after the scheduled maintenance date (S304a: NO), the wireless sensor 30 is diagnosed as having sufficient battery power (S306a), and the processing in Fig. 18 is terminated. The processing in Fig. 18 is executed for each wireless sensor 30. Note that the next time the processing in Fig. 18 is executed for the same wireless sensor 30, the amount of calculation can be reduced by calculating the difference from the value calculated in the previous processing.

[0111] (b. Battery voltage based diagnosis) Next, a method for diagnosing the remaining battery charge of the wireless sensor 30 based on the battery voltage will be described with reference to Fig. 19. Fig. 19 is a flowchart showing the method for diagnosing the remaining battery charge of the wireless sensor 30 based on the battery voltage.

[0112] First, the diagnosis unit 130 calculates the average battery voltage of the wireless sensor 30 to be diagnosed from the most recent n pieces of converted data of the wireless sensor 30 (S301b). The diagnosis unit 130 acquires the most recent n pieces of converted data of the wireless sensor 30 to be diagnosed from the converted data DB 160, and calculates the average value of the battery voltages of the received n pieces of converted data as the average battery voltage. The battery voltage is stored in the storage area for individual data of the converted data.

[0113] Next, the diagnosis unit 130 calculates the remaining battery capacity from the average battery voltage calculated in step S301b (S302b). The remaining battery capacity can be calculated using a voltage gradient-to-battery capacity conversion table recorded in the sensor type table 1730. FIG. 20 shows an example of the voltage gradient-to-battery capacity conversion table. The voltage gradient-to-battery capacity conversion table is information indicating the relationship between the battery voltage and the remaining battery capacity. The capacity corresponding to the average battery voltage Vave calculated in step S301b is the remaining battery capacity Qr.

[0114] That is, the diagnosis unit 130 acquires the battery voltage of the wireless sensor 30 from the converted data, and calculates the remaining battery capacity Qr of the wireless sensor 30 from the acquired battery voltage based on the relationship between the battery voltage and the remaining battery capacity acquired in advance (voltage gradient-remaining battery capacity conversion table).

[0115] Diagnosis unit 130 then calculates the battery life end date and time of wireless sensor 30 based on the remaining battery power Qr calculated in step S302b and the transmission period (S303b). The battery life end date and time of wireless sensor 30 can be calculated in the same manner as the processing in step S303a in Fig. 18, and can be calculated using equation (4) above. In step S303a, the remaining battery power was calculated using equation (2) above, but here the remaining battery power Qr calculated in step S302b is used.

[0116] If the battery life end date and time of the wireless sensor 30 is before the scheduled maintenance date (S304b: YES), the diagnosis unit 130 identifies the wireless sensor 30 as a wireless sensor 30 with insufficient battery power (S305b). The diagnosis unit 130 then records alarm information in the alarm table 1760 to notify the wireless sensor 30 that the battery power is insufficient. The alarm information recorded in the alarm table 1760 is output by the output unit 150.

[0117] 18 , when alarm information is recorded in the alarm table 1760, the output unit 150 outputs the alarm information to the output device 200, and the output device 200 notifies the operator based on the alarm information that the remaining battery power of the wireless sensor 30 is low. Based on the notification, the operator can take measures to quickly resolve the remaining battery power shortage of the wireless sensor 30 by requesting a maintenance worker to inspect the wireless sensor 30.

[0118] On the other hand, if the battery life date and time of the wireless sensor 30 is after the scheduled maintenance date (S304b: NO), the wireless sensor 30 is diagnosed as having sufficient remaining battery power (S306b), and the processing in Fig. 19 is terminated. The processing in Fig. 19 is executed for each wireless sensor 30.

[0119] (c. Changes to maintenance work plans) The diagnosis of the remaining battery charge of the wireless sensor 30 shown in FIGS. 18 and 19 diagnoses whether the remaining battery charge of the wireless sensor 30 is sufficient until the scheduled maintenance date of the wireless sensor 30. If it is determined that the battery will run out before the scheduled maintenance date, maintenance work must be performed before the battery runs out, and the scheduled maintenance date must be revised. Therefore, to support the operator in planning maintenance work, the diagnosis unit 130 may create a list of wireless sensors 30 whose batteries are predicted to run out before the scheduled maintenance date for each maintenance group of the wireless sensors 30, based on the battery life date and time calculated by the processing shown in FIG. 18 or 19 and the current scheduled maintenance date. The list created by the diagnosis unit 130 is presented to the operator from the output device 200 via the output unit 150. The output device 200 displays a list of, for example, the device names, battery life date and time, current scheduled maintenance date, maintenance group number, etc. of the wireless sensors 30 whose batteries are predicted to run out before the scheduled maintenance date.

[0120] Based on the list displayed on the output device 200, the operator can change the scheduled maintenance date for the wireless sensor 30 or change the maintenance group to which the wireless sensor 30 belongs. This allows the operator to take action such as replacing the battery before it runs out. The change in the maintenance work plan may be made by the operator or by machine learning.

[0121] (d. Changing the settings of the wireless sensor) If it is diagnosed that the battery will run out before the scheduled maintenance date, the scheduled maintenance date can be changed as described above to prevent the wireless sensor 30 from stopping operation due to a lack of battery. However, for example, if the maintenance worker's schedule does not match or if the battery replacement work for the wireless sensor 30 cannot be incorporated into the maintenance work of another maintenance group, it is possible to extend the battery life by reducing the power consumption of the wireless sensor 30. For example, the power consumption of the wireless sensor 30 can be reduced by lengthening the data transmission cycle of the wireless sensor 30.

[0122] 21 shows an example of the process for changing the transmission cycle of the wireless sensor 30. When the diagnosis unit 130 determines that the battery of the wireless sensor 30 will run out before the scheduled maintenance date, the control unit 140 first changes the transmission cycle of data from the wireless sensor 30 based on the current remaining battery charge and the number of days remaining until the scheduled maintenance date (S311). For example, the control unit 140 changes the transmission cycle by lengthening the current transmission cycle by a predetermined unit time within the settable cycle range determined by the specifications of the wireless sensor 30. The unit time can be set arbitrarily and may be, for example, one second.

[0123] When the control unit 140 changes the data transmission cycle, it calculates the battery end of life date and time based on the current remaining battery power and the changed transmission cycle (S313). Then, the control unit 140 determines whether the end of life date and time calculated in step S313 is later than the current scheduled maintenance date (S315). If the end of life date and time of the battery of the wireless sensor 30 is still earlier than the scheduled maintenance date (S315: NO), the control unit 140 executes the process again from step S311 because the remaining battery power of the wireless sensor 30 is still insufficient for the transmission cycle set in step S311. The processes of steps S311 to S315 are repeatedly executed until the end of life date and time of the battery of the wireless sensor 30 is later than the scheduled maintenance date.

[0124] Then, when the battery life date and time of the wireless sensor 30 is later than the scheduled maintenance date (S315: YES), the control unit 140 sets the changed data transmission cycle set in step S311 to the wireless sensor 30 (S317). The transmission cycle of the wireless sensor 30 is changed by transmitting setting change instruction data from the wireless sensor management device 100 to the wireless sensor 30 to be changed via the network 5 and the gateway terminal 70.

[0125] The format of the setting change instruction data is determined by the specifications of the gateway terminal 70, and similar to the format of the data acquired from the wireless sensor 30 shown in FIG. 2, the setting change instruction data includes a specified data area and a message data area. The message data area stores the changed data transmission period. The message data area stores binary data in a format determined for each wireless sensor 30. For this reason, the control unit 140 converts the changed data transmission period, which is text data, into binary data, using, for example, a data reverse conversion table (not shown) similar to the data conversion table 1710, and stores the binary data in the message data area of ​​the setting change instruction data. The control unit 140 then transmits the generated setting change instruction data to the wireless sensor 30 to be changed via the network 5 and the gateway terminal 70. The wireless sensor 30 that has received the setting change instruction data changes the data transmission period based on the binary data representing the changed data transmission period stored in the message data area.

[0126] In this way, by changing the transmission period of the wireless sensor 30 whose battery life is approaching the scheduled maintenance date, the control unit 140 can reduce the power consumption of the wireless sensor 30 and extend the battery life.

[0127] The wireless sensor 30 operates on an onboard battery, and may not be able to acquire data properly if the remaining battery power is low. Therefore, unlike a wired sensor, when data acquired by the wireless sensor 30 cannot be received, it is difficult to identify the cause: whether an abnormality has occurred in the wireless sensor 30 itself that is preventing the data from being acquired, or whether the data cannot be acquired due to insufficient battery power. For this reason, the wireless sensor 30 requires regular inspection to prevent the battery power from running low. According to this embodiment, the status of the wireless sensor 30, such as the remaining battery power, can be managed based on the data acquired by the wireless sensor 30, thereby reducing the inspection burden of the wireless sensor 30.

[0128] The configuration of the wireless sensor management system 1 according to this embodiment and the wireless sensor management method using the wireless sensor management device 100 have been described above. According to this embodiment, the receiving unit 110 of the wireless sensor management device 100 receives data stored in the data storage unit 75 of each area 10 at a predetermined timing. Next, the data conversion unit 120 converts the format of the received data into a common format to generate converted data. The diagnosing unit 130 then uses the converted data to diagnose the state of the wireless sensor 30.

[0129] In this way, data can be efficiently and centrally managed by converting the formats of data output by multiple wireless sensors 30 into a common format. Furthermore, by standardizing the data format, it becomes possible to process large amounts of data efficiently and easily.

[0130] [3. Hardware configuration] The hardware configuration of the wireless sensor management apparatus 100 according to this embodiment will be described with reference to Fig. 22. Fig. 22 is a block diagram showing an example of the hardware configuration of an information processing apparatus 900 that functions as the wireless sensor management apparatus 100 according to this embodiment.

[0131] The information processing device 900 includes a processor (CPU 901 in FIG. 22), a ROM 903, and a RAM 905. The information processing device 900 also includes a bus 907, an input I / F 909, an output I / F 911, a storage device 913, a drive 915, a connection port 917, and a communication device 919.

[0132] The CPU 901 functions as an arithmetic processing device and a control device. The CPU 901 controls all or part of the operations within the information processing device 900 in accordance with various programs recorded in the ROM 903, the RAM 905, the storage device 913, or the removable recording medium 925. The ROM 903 stores programs used by the CPU 901, arithmetic parameters, etc. The RAM 905 temporarily stores programs used by the CPU 901, or parameters that change as appropriate during program execution. These are interconnected by a bus 907 constituted by an internal bus such as a CPU bus.

[0133] The bus 907 is connected to an external bus such as a PCI (Peripheral Component Interconnect / Interface) bus or PCI Express (registered trademark) via a bridge.

[0134] The input I / F 909 is an interface that accepts input from an input device 921, which is an operating means operated by a user, such as a mouse, keyboard, touch panel, button, switch, or lever. The input I / F 909 is configured, for example, as an input control circuit that generates an input signal based on information input by the user using the input device 921 and outputs the signal to the CPU 901. The input device 921 may be, for example, a remote control device that uses infrared or other radio waves, or an external device 927 such as a PDA that supports operation of the information processing device 900. A user of the information processing device 900 can operate the input device 921 to input various data to the information processing device 900 and instruct the information processing device 900 to perform processing operations.

[0135] The output I / F 911 is an interface that outputs input information to an output device 923 that can notify the user visually or audibly. The output device 923 may be, for example, a display device such as a CRT display device, a liquid crystal display device, a plasma display device, an EL display device, or a lamp. Alternatively, the output device 923 may be an audio output device such as a speaker or headphones, a printer, a mobile communication terminal, or a facsimile machine. The output I / F 911 instructs the output device 923 to output, for example, processing results obtained from various processes executed by the information processing device 900. Specifically, the output I / F 911 instructs the display device to display the processing results of the information processing device 900 as text or images. The output I / F 911 also instructs the audio output device to convert audio signals, such as audio data instructed to be played, into analog signals and output them.

[0136] The storage device 913 is one of the storage units of the information processing device 900 and is a device for storing data. The storage device 913 is configured, for example, by a magnetic storage device such as a hard disk drive (HDD), a semiconductor storage device such as a solid state drive (SSD), an optical storage device, a magneto-optical storage device, etc. The storage device 913 stores programs executed by the CPU 901, various data generated by the execution of the programs, various data acquired from the outside, etc.

[0137] The drive 915 is a reader / writer for a recording medium, and is built into or externally attached to the information processing device 900. The drive 915 reads information recorded on the attached removable recording medium 925 and outputs it to the RAM 905. The drive 915 can also write information to the attached removable recording medium 925. The removable recording medium 925 is, for example, a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory. Specifically, the removable recording medium 925 may be a CD medium, a DVD medium, a Blu-ray (registered trademark) medium, a CompactFlash (registered trademark) (CF), a flash memory, an SD memory card (Secure Digital memory card), or the like. The removable recording medium 925 may also be, for example, an IC card (Integrated Circuit card) equipped with a contactless IC chip, an electronic device, or the like.

[0138] The connection port 917 is a port for directly connecting a device to the information processing device 900. The connection port 917 is, for example, a Universal Serial Bus (USB) port, an external Serial Advanced Technology Attachment (eSATA), or a Serial Attached Small Computer System Interface (SAS) port. The information processing device 900 can directly acquire various data from an external device 927 connected to the connection port 917, or provide various data to the external device 927. For example, an alarm notification device such as PATLITE (registered trademark) for notifying alarm information may be connected via the connection port 917. Furthermore, a network attached storage (NAS) may be connected as the external device 927 and used as a storage device.

[0139] The communication device 919 is, for example, a communication interface configured with a communication device or the like for connecting to a communication network 929. The communication device 919 is, for example, a communication card for a wired or wireless LAN (Local Area Network), Bluetooth (registered trademark), or WUSB (Wireless USB). The communication device 919 may also be a router for optical communication, a router for ADSL (Asymmetric Digital Subscriber Line), or a modem for various types of communication. The communication device 919 can transmit and receive signals, for example, between the Internet and other communication devices in accordance with a predetermined protocol such as TCP / IP. For example, a computer for operating the information processing device 900 can be connected via the communication device 919. The communication network 929 connected to the communication device 919 is configured with a network connected by wire or wirelessly. For example, the communication network 929 is the Internet, a home LAN, infrared communication, radio wave communication, satellite communication, or the like.

[0140] The above describes an example of the hardware configuration of the information processing device 900. Each of the above-described components may be configured using general-purpose components, or may be configured using hardware specialized for the function of each component. The hardware configuration of the information processing device 900 can be changed as appropriate depending on the technical level at the time of implementing this embodiment.

[0141] Although the preferred embodiments of the present invention have been described in detail above with reference to the accompanying drawings, the present invention is not limited to these examples. It is clear that a person skilled in the art to which the present invention pertains can conceive of various modifications and alterations within the scope of the technical ideas set forth in the claims, and it is understood that these also naturally fall within the technical scope of the present invention. [Explanation of symbols]

[0142] 1. Wireless Sensor Management System 5. Network 10 (10A, 10B, 10C) Area 30(31, 32, . . . , 3n) Wireless Sensor 50 Antennas 70 Gateway terminal 75 Data storage unit 75a Regulation Data Area 75b Message Data Area 100 Wireless sensor management device 110 Receiving unit 120 Data Conversion Unit 130 Diagnostic Department 140 Control Unit 150 Output section 160 converted data DB 160a Specification data storage section 160b Message data storage section 170 Table DB 200 Output Device 900 Information Processing Equipment 1710 Data Conversion Table 1720 Sensor Table 1730 Sensor type table 1740 Gateway Information Table 1750 Function Table 1760 Alarm Table 1770 Group Management Table 1780 Maintenance Management Table

Claims

1. A wireless sensor management device that manages a plurality of wireless sensors that output data in different formats, a receiving unit that receives the data output by the wireless sensor; a data conversion unit that converts the format of the received data into a common format using data conversion information that is information for dividing the received data into items; a diagnosis unit that diagnoses states of the plurality of wireless sensors using the converted data into the common format; Equipped with The diagnostic unit calculating the amount of power consumption during an operation period of the wireless sensor based on the data transmission period of the wireless sensor and the number of transmitted data items identified based on the converted data; Calculating the remaining battery capacity of the wireless sensor based on the power consumption amount and the battery capacity of the wireless sensor; or obtaining a battery voltage of the wireless sensor from the converted data; A wireless sensor management device that calculates the remaining battery capacity of the wireless sensor from the battery voltage based on a relationship between the battery voltage and the remaining battery capacity that has been acquired in advance.

2. A wireless sensor management device that manages multiple wireless sensors that output data in different formats, comprising: a receiving unit that receives the data output by the wireless sensor; a data conversion unit that converts the format of the received data into a common format using data conversion information that is information for dividing the received data into items; a diagnosis unit that diagnoses states of the plurality of wireless sensors using the converted data into the common format; Equipped with The diagnostic unit acquiring the receiving sensitivity of the wireless sensor based on the converted data; A wireless sensor management device that detects an abnormality in the communication state of the wireless sensor based on the reception sensitivity of the wireless sensor.

3. The wireless sensor management device according to claim 1 , wherein the data conversion unit converts binary data included in the received data into text data in the common format.

4. a control unit for controlling the wireless sensor; The diagnostic unit Calculating the battery life from the calculated remaining battery capacity, Identifying a wireless sensor whose battery life is approaching its scheduled maintenance date; The wireless sensor management device according to claim 1 , wherein the control unit changes the data transmission period of a wireless sensor whose battery life is approaching a scheduled maintenance date.

5. the plurality of wireless sensors are classified into a plurality of groups, The diagnostic unit The wireless sensor management device according to claim 2, further comprising: a group to which the wireless sensor that has detected an abnormality in the communication state belongs, the group being identified as having a wireless sensor with a communication state abnormality equal to or greater than a reference value; and a wireless sensor on a group-by-group basis being identified as having an abnormality in the communication state.

6. 1. A wireless sensor management system, comprising: a plurality of wireless sensors that output data in different formats; a gateway terminal that transmits and receives data to and from the wireless sensor; a wireless sensor management device that manages the wireless sensors; are connected via a network, the wireless sensor management device, a receiving unit that receives the data output from the wireless sensor via the gateway terminal; a data conversion unit that converts the format of the received data into a common format using data conversion information that is information for dividing the received data into items; a diagnosis unit that diagnoses states of the plurality of wireless sensors using the converted data into the common format; Equipped with The diagnostic unit calculating the amount of power consumption during an operation period of the wireless sensor based on the data transmission period of the wireless sensor and the number of transmitted data items identified based on the converted data; Calculating the remaining battery capacity of the wireless sensor based on the power consumption amount and the battery capacity of the wireless sensor; or obtaining a battery voltage of the wireless sensor from the converted data; A wireless sensor management system that calculates the remaining battery capacity of the wireless sensor from the battery voltage based on a relationship between the battery voltage and the remaining battery capacity that has been acquired in advance.

7. A wireless sensor management system, a plurality of wireless sensors that output data in different formats; a gateway terminal that transmits and receives data to and from the wireless sensor; a wireless sensor management device that manages the wireless sensors; are connected via a network, the wireless sensor management device, a receiving unit that receives the data output from the wireless sensor via the gateway terminal; a data conversion unit that converts the format of the received data into a common format using data conversion information that is information for dividing the received data into items; a diagnosis unit that diagnoses states of the plurality of wireless sensors using the converted data into the common format; Equipped with The diagnostic unit acquiring the receiving sensitivity of the wireless sensor based on the converted data; A wireless sensor management system that detects an abnormality in the communication state of the wireless sensor based on the receiving sensitivity of the wireless sensor.

8. A wireless sensor management method for managing a plurality of wireless sensors that output data in different formats, comprising: a receiving step of receiving the data output by the wireless sensor; a data conversion step of converting the format of the received data into a common format using data conversion information that is information for dividing the received data into items; a diagnosis step of diagnosing states of the plurality of wireless sensors using the converted data into the common format; Including, The diagnostic step includes: calculating the amount of power consumption during an operation period of the wireless sensor based on the data transmission period of the wireless sensor and the number of transmitted data items identified based on the converted data; Calculating the remaining battery capacity of the wireless sensor based on the power consumption amount and the battery capacity of the wireless sensor; or obtaining a battery voltage of the wireless sensor from the converted data; A wireless sensor management method, comprising: calculating a remaining battery capacity of the wireless sensor from the battery voltage based on a relationship between the battery voltage and the remaining battery capacity obtained in advance.

9. A wireless sensor management method for managing a plurality of wireless sensors that output data in different formats, comprising: a receiving step of receiving the data output by the wireless sensor; a data conversion step of converting the format of the received data into a common format using data conversion information that is information for dividing the received data into items; a diagnosis step of diagnosing states of the plurality of wireless sensors using the converted data into the common format; Including, The diagnostic step includes: acquiring the receiving sensitivity of the wireless sensor based on the converted data; A wireless sensor management method for detecting an abnormality in the communication state of the wireless sensor based on the receiving sensitivity of the wireless sensor.

Images