Data conversion device, data conversion method, and program

Abstract

A data conversion device (3) comprises: a device communication unit (301); a data conversion unit (303); and a server communication unit (300). The device communication unit (301) acquires, through communication with a device (5) and from the device (5), device data relating to the operation of the device (5). If the acquired device data belongs to a first data group, the data conversion unit (303) converts the device data into data in a first data format indicated by text data that can be read by a person according to a data conversion table (340). If the acquired device data belongs to a second data group different from the first data group, the data conversion unit (303) converts the device data into data in a second data format indicated by text data that cannot be read by a person. The server communication unit (300) transmits the converted device data to a server (2).

Description

Data conversion device, data conversion method and program

[0001] The present disclosure relates to a data conversion device, a data conversion method, and a program.

[0002] In recent years, a system has become well known in which in-home devices are connected to a cloud server via the Internet so that they can communicate with each other, allowing the devices to be remotely controlled and their operating status to be checked using an operating terminal such as a smartphone or tablet (for example, Patent Document 1).

[0003] In addition, there are an increasing number of cases where the above system works in conjunction with other systems, and the other systems analyze data collected from devices by the above cloud server (hereinafter referred to as "device data") and use it for marketing research or feedback on design and development.

[0004] The data format requested by the other systems to the cloud server is generally a data format written in a way that can be read by humans (hereinafter referred to as a "human-readable format"), such as JSON (JavaScript Object Notation), XML (Extensible Markup Language), or YAML. On the other hand, the device data transmitted from the device when the cloud server collects data is generally in binary format. If data conversion from binary format to human-readable format is performed on the cloud server, the cost of using the device data increases, which creates a problem of hindering the active use of the device data by the other systems.

[0005] Therefore, an increasing number of configurations are being implemented in which a device on the device side (more specifically, a communication adapter connected to the device or a communication device installed separately in the home) converts binary format device data sent from the device into human-readable format device data and sends it to a cloud server.

[0006] JP 2016-111564 A

[0007] However, when device data is converted on the device side, the data size of the converted device data is larger than the size of the original device data, which increases the amount of data communication between the device side and the cloud server, raising concerns that this could result in congestion and increased communication costs.

[0008] For this reason, there is a demand for the proposal of a new technology that can suppress an increase in the amount of data communication between the device and the server while suppressing an increase in the data usage costs of the device.

[0009] The present disclosure has been made in consideration of the above-mentioned situation, and aims to provide a data conversion device, a data conversion method, and a program that can suppress an increase in data communication volume with a server while suppressing an increase in costs in using device data.

[0010] In order to achieve the above object, the data conversion device of the present disclosure comprises: a device data acquisition means for acquiring device data related to the operation of the device from the device by communicating with the device; a data conversion means for converting the acquired device data into data in a first data format represented by human-readable text data in accordance with a predetermined conversion rule if the acquired device data belongs to a first data group, and for converting the acquired device data into data in a second data format represented by human-unreadable text data if the acquired device data belongs to a second data group different from the first data group; and a device data transmission means for transmitting the converted device data to a server.

[0011] According to the present disclosure, it is possible to suppress an increase in the amount of data communication in communication with a server while suppressing an increase in the cost of using device data.

[0012] 1 is a diagram showing the overall configuration of a device data collection system according to an embodiment; FIG. 2 is a block diagram showing the hardware configuration of a server according to the embodiment; FIG. 3 is a block diagram showing the hardware configuration of a data conversion device according to the embodiment; FIG. 4 is a block diagram showing the functional configuration of a server and a data conversion device according to the embodiment; FIG. 5 is a diagram showing an example of device correspondence data according to the embodiment; FIG. 6 is a diagram showing an example of a parent table of a data conversion table according to the embodiment; FIG. 7 is a diagram showing an example of a child table (first table) of the data conversion table according to the embodiment; FIG. 8 is a diagram showing an example of a child table (second table) of the data conversion table according to the embodiment;

[0013] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings.

[0014] 1 is a diagram showing the overall configuration of an equipment data collection system 1 according to an embodiment of the present disclosure. The equipment data collection system 1 is a system that collects equipment data relating to the operation, such as the operating state, of equipment 5, and provides services, such as remote operation of the equipment 5, to users of the equipment 5. As shown in FIG. 1, the equipment data collection system 1 includes a server 2, a data conversion device 3, an operation terminal 4, and the equipment 5.

[0015] <Hardware Configuration of Server 2> The server 2 is an example of a server according to the present disclosure. The server 2 is a so-called cloud server, and is connected to a wide area network such as the Internet. As shown in FIG. 2 , the server 2 includes, as its hardware configuration, a communication interface 20, a central processing unit (CPU) 21, a read-only memory (ROM) 22, a random-access memory (RAM) 23, and an auxiliary storage device 24. These components are interconnected via a bus 25. The communication interface 20 is hardware for communicating with the data conversion device 3, the operation terminal 4, the data analysis server 6, and the like via the wide area network. The data analysis server 6 is a server included in a data analysis system that is a separate system from the equipment data collection system 1.

[0016] The CPU 21 is a processor that performs overall control of the server 2. The ROM 22 is a storage device that stores non-rewritable programs such as a basic input / output system (BIOS). The RAM 23 is a storage device used as a work area for the CPU 21. The auxiliary storage device 24 is a storage device that includes a readable / writable non-volatile semiconductor memory, a hard disk drive (HDD), etc. Examples of the readable / writable non-volatile semiconductor memory include an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), and a flash memory.

[0017] The auxiliary storage device 24 stores server programs including a program for collecting equipment data from the equipment 5, a program for realizing remote control services for the equipment 5, and a program for providing the collected equipment data to the data analysis system, as well as data used when the server programs are executed.

[0018] The server 2 can acquire the server program or an update program for updating the server program via communication from another server, terminal, etc. (not shown). These programs can also be stored and distributed on a computer-readable recording medium such as a CD-ROM (Compact Disc Read-Only Memory), a DVD (Digital Versatile Disc), a magneto-optical disk, a USB (Universal Serial Bus) memory, a HDD, an SSD (Solid-State Drive), or a memory card. When such a recording medium is directly or indirectly attached to the server 2, the server 2 can read the server program or update program from the recording medium and install it on itself.

[0019] <Hardware Configuration of Data Conversion Device> The data conversion device 3 is an example of a data conversion device according to the present disclosure. The data conversion device 3 is installed in a user's home, converts request data for the device 5 received from the server 2 into data in a format that the device 5 can handle (in this example, binary format) and transmits the data to the device 5, and also spontaneously transmits request data indicating a request for device data to the device 5 at regular time intervals. Furthermore, the data conversion device 3 converts the device data received from the device 5 into data in a data format that can be read by humans, such as JSON, XML, or YAML (i.e., human-readable format), or data in a data format that cannot be read by humans, such as hexadecimal text data (hereinafter referred to as a "non-human-readable format") and transmits the data to the server 2.

[0020] As shown in FIG. 3 , the data conversion device 3 includes, as its hardware configuration, a communication interface 30, a CPU 31, a ROM 32, a RAM 33, and an auxiliary storage device 34. These components are interconnected via a bus 35. The communication interface 30 is hardware for communicating with the server 2 via a broadband router (not shown) installed in the user's home, and for communicating with devices 5 installed in the user's home. The CPU 31 is a processor that provides overall control of the data conversion device 3. The ROM 32 is a storage device that stores non-rewritable programs such as the BIOS. The RAM 33 is a storage device used as a working area for the CPU 31. The auxiliary storage device 34 is a storage device formed of a readable / writable non-volatile semiconductor memory, a HDD, or the like. The readable / writable non-volatile semiconductor memory may be, for example, an EPROM, an EEPROM, or a flash memory.

[0021] The auxiliary storage device 34 stores a data conversion program for converting request data and device data, as well as data used when executing the data conversion program. The data conversion device 3 can acquire the data conversion program or an update program for updating the data conversion program via communication from the server 2, another server (not shown), a terminal, or the like. These programs can also be stored and distributed on a computer-readable recording medium such as a CD-ROM, DVD, optical magnetic disk, USB memory, HDD, SSD, or memory card. When such a recording medium is directly or indirectly attached to the data conversion device 3, the data conversion device 3 can read the data conversion program or update program from the recording medium and install it on itself.

[0022] <Hardware Configuration of Operation Terminal 4> The operation terminal 4 is a smart device such as a smartphone or tablet terminal that is owned and used by a user. As shown in Fig. 4, the operation terminal 4 includes a display 40, an operation reception unit 41, a communication interface 42, a CPU 43, a ROM 44, a RAM 45, and an auxiliary storage device 46. These components are connected to each other via a bus 47. The display 40 includes a display device such as a liquid crystal display or an organic EL (electroluminescence) display. Under the control of the CPU 43, the display 40 displays various screens and the like in response to user operations.

[0023] The operation reception unit 41 includes one or more input devices such as push buttons, a touch panel, or a touch pad, and receives operation input from a user and outputs a signal related to the received operation to the CPU 43. The communication interface 42 is hardware for communicating with devices such as the server 2 via a wide area network. The CPU 43 is a processor that performs overall control of the operation terminal 4. The ROM 44 is a storage device that stores programs such as the BIOS that do not need to be rewritten. The RAM 45 is a storage device used as a working area for the CPU 43.

[0024] The auxiliary storage device 46 is configured with a readable / writable nonvolatile semiconductor memory. Examples of the readable / writable nonvolatile semiconductor memory include an EPROM, an EEPROM, a flash memory, etc. The auxiliary storage device 46 stores various programs including a device operation app, which is an application program for operating the device 5, and data used when these programs are executed.

[0025] The operation terminal 4 can acquire the device operation app or an update program for updating the device operation app via communication from the server 2, another server or terminal (not shown), or the like, and store the program in the auxiliary storage device 46. These programs can also be stored and distributed on a computer-readable recording medium such as a CD-ROM, DVD, optical magnetic disk, USB memory, HDD, SSD, or memory card. When such a recording medium is directly or indirectly attached to the operation terminal 4, the operation terminal 4 can read the device operation app or the update program from the recording medium and store the program in the auxiliary storage device 46.

[0026] <Device 5> Device 5 is an example of a device according to the present disclosure. Device 5 is a home appliance known as an IoT device, an information appliance, a network appliance, a smart appliance, or the like, such as an air conditioner, a television, or a water heater.

[0027] 5, the server 2 functionally includes a terminal communication unit 200, a data conversion device communication unit 201, and a device data providing unit 202. These functional units are realized by the CPU 21 of the server 2 executing the above-mentioned server program stored in the auxiliary storage device 24.

[0028] The data conversion device 3 functionally comprises a server communication unit 300, a device communication unit 301, a device data request unit 302, and a data conversion unit 303. These functional units are realized by the CPU 31 of the data conversion device 3 executing the above-mentioned data conversion program stored in the auxiliary storage device 34.

[0029] In the server 2, the device communication unit 200 transmits and receives communication messages to and from the operation terminal 4 in accordance with a communication format (hereinafter referred to as "communication format A") previously determined between the operation terminal 4 and the operation terminal 4. For example, when a user of the device 5 receives an operation request for the device 5, such as a request to turn on the power of the device 5 or a request to change the operation mode, via the device operation app, the operation terminal 4 transmits a request message storing request data indicating the operation request to the server 2. Alternatively, when a user of the device 5 receives a data acquisition request, which is a request to acquire data indicating the operation status of the device 5 (for example, operation ON / OFF, power consumption, operation mode, set temperature, etc.), via the device operation app, the operation terminal 4 transmits a request message storing request data indicating the data acquisition request to the server 2.

[0030] The terminal communication unit 200 receives the request message sent from the operation terminal 4 in accordance with communication format A, and notifies the data conversion device communication unit 201 that it has received the request message from the operation terminal 4. The terminal communication unit 200 also converts the response message from the data conversion device 3 received by the data conversion device communication unit 201 into a response message in accordance with communication format A and sends it to the operation terminal 4.

[0031] The data conversion device communication unit 201 transmits and receives communication messages to and from the data conversion device 3 in accordance with a communication format (hereinafter referred to as "communication format B") previously determined between the data conversion device 3. For example, the data conversion device communication unit 201 converts a request message from the operation terminal 4 received by the terminal communication unit 200 into a request message conforming to communication format B and transmits it to the data conversion device 3. The data conversion device communication unit 201 also receives a response message transmitted from the data conversion device 3 in accordance with communication format B.

[0032] When the data conversion device communication unit 201 receives the response message, it notifies the terminal communication unit 200 of the receipt, and extracts and stores the device data included in the response message in the device data storage unit 240. As will be described in detail below, the device data is stored in the response message in a human-readable format or a non-human-readable format. The human-readable format is an example of a first data format according to the present disclosure, and the non-human-readable format is an example of a second data format according to the present disclosure. The device data storage unit 240 is a memory area provided by the auxiliary storage device 24 of the server 2. The device data collected from each device 5 in each user's home is sorted and stored in the device data storage unit 240 according to predetermined rules.

[0033] The equipment data providing unit 202 provides equipment data to the data analysis system. Specifically, when the equipment data providing unit 202 receives an equipment data acquisition request from the data analysis server 6, it reads out equipment data that meets the conditions included in the acquisition request from the equipment data storage unit 240 and transmits the read equipment data to the data analysis server 6. The data analysis server 6 is a computer that analyzes the equipment data provided by the server 2 to utilize it for, for example, marketing research or feedback to design and development.

[0034] In the data conversion device 3, the server communication unit 300 transmits and receives communication messages to and from the server 2 in accordance with communication format B. For example, the server communication unit 300 receives a request message transmitted from the server 2 in accordance with communication format B. The server communication unit 300 notifies the data conversion unit 303 that it has received the request message from the server 2. The server communication unit 300 also generates a response message in accordance with communication format B that stores the device data converted by the data conversion unit 303, and transmits the generated response message to the server 2. The server communication unit 300 is an example of device data transmission means and an example of request message reception means according to the present disclosure.

[0035] The device communication unit 301 transmits and receives communication messages to and from the device 5 in accordance with a communication format (hereinafter referred to as "communication format C") previously determined between the device 5 and the device 5. For example, the device communication unit 301 generates a request message in accordance with the communication format C, storing the request data converted by the data conversion unit 303, and transmits the generated request message to the device 5. The device communication unit 301 also generates a request message in accordance with the communication format C, storing the request data generated by the device data request unit 302, and transmits the generated request message to the device 5. The device communication unit 301 also receives a response message transmitted from the device 5 in accordance with the communication format C. The device communication unit 301 notifies the data conversion unit 303 that the response message has been received from the device 5. The device communication unit 301 is an example of a device data acquisition means according to the present disclosure.

[0036] The device data request unit 302 generates request data at regular intervals to request device data for periodic acquisition from the device 5. The request data generated by the device data request unit 302 is data in a binary format that can be handled by the device 5.

[0037] The data conversion unit 303 is an example of a data conversion means according to the present disclosure. The data conversion unit 303 converts request data included in a request message received from the server 2 into binary data that can be handled by the device 5. The data conversion unit 303 also converts device data included in a response message received from the device 5 into a human-readable format or a non-human-readable format. Hereinafter, the request data that can be handled by the device 5 and the device data transmitted from the device 5 are collectively referred to as device-compatible data. As shown in FIG. 6 , the device-compatible data is composed of a communication data identifier (ID) and device data properties. The communication data ID is information for identifying the device-compatible data and is composed of a service type and a device data type.

[0038] The service type is set with information indicating the type of request or response. For example, in the case of request data, information indicating the type of request, such as an operation request or a data acquisition request (e.g., "01" for an operation request, "03" for a data acquisition request, etc.) is set as the service type. Also, in the case of device data, information indicating the type of response, such as an operation request response or a data acquisition request response (e.g., "02" for an operation request response, "04" for a data acquisition request response, etc.) is set as the service type. Fig. 6 shows an example of device correspondence data (i.e., device data) when the device 5 is an air conditioner and the service type is a data acquisition response.

[0039] The device data type is set with information identifying a set of properties (e.g., operation ON / OFF state, power consumption, operation mode, and set temperature) included in the device data property of the device correspondence data. Note that only one property may correspond to one device data type. The device data property is set with the value of each property corresponding to the device data type.

[0040] In this embodiment, the request data stored in the request message received from the server 2 corresponds to device-compatible data converted into hexadecimal text. Therefore, the data conversion unit 303 converts the request data included in the request message received from the server 2 into binary format, thereby generating request data that can be handled by the device 5.

[0041] Next, the conversion of the device data acquired from the device 5 will be described in detail. First, the data conversion unit 303 determines the group type of the device data acquired from the device 5. In this embodiment, the device data belongs to either a first data group or a second data group. For example, the first data group includes device data that is frequently used by the data analysis system, such as device data acquired periodically, and the second data group includes device data that is less frequently used by the data analysis system.

[0042] In this embodiment, the data conversion unit 303 determines the group type of the device data based on the device data type in the communication data ID of the device data. A table linking device data types with group types (hereinafter referred to as the "group type determination table") is stored in advance in the auxiliary storage device 34 of the data conversion device 3. The data conversion unit 303 converts device data belonging to the first data group into data in a human-readable format (JSON format in this embodiment) using the data conversion table 340. On the other hand, the data conversion unit 303 converts device data belonging to the second data group into data in a non-human-readable format (hexadecimal text data in this embodiment).

[0043] The data conversion table 340 is a data table that defines rules for converting each property in device data into a human-readable format, and is stored in the auxiliary storage device 34. The data conversion table 340 is composed of a parent table prepared for each device data type and multiple child tables (first table, second table, ...). As shown in FIG. 7 , the parent table is composed of fields such as "property start position," "property size," "key name," "data type," and "reference table." The "property start position" stores the start position of each property value in the device data property of the device data, assuming that the first value is "1." The "property size" stores the size (in bytes) of each property value. The "key name" stores the key name in the human-readable format, and the "data type" stores the data type of the key name in the human-readable format.

[0044] The "reference table" stores information indicating the child table to be referenced. The child tables (first table, second table, ...) are data tables that link property values ​​in the device data (raw data) acquired from the device 5 with text data. Examples of the first to fourth tables are shown in Figures 8 to 11. The data conversion unit 303 first selects a parent table corresponding to the device data type of the device data to be converted. Then, it references the "property start position" and "property size" from the first record of the selected parent table, reads the value of the property to be converted from the device data, and converts the value of the property into text data using the corresponding child table.

[0045] Then, the data conversion unit 303 generates human-readable text corresponding to the property based on the key name and data type stored in the "key name" and "data type" of the record and the property value converted into text. The data conversion unit 303 converts the device data into human-readable data by repeating the same process sequentially for the second and subsequent records in the selected parent table. As a result, for example, the device data shown in FIG. 6 is converted into human-readable data as shown in FIG. 12.

[0046] <Processing of Server 2> FIG. 13 is a flowchart showing the procedure of processing executed by the server 2.

[0047] (Step S100) The server 2 determines whether or not a request message has been received from the operation terminal 4. If a request message has been received from the operation terminal 4 (Step S100; YES), the processing of the server 2 proceeds to Step S101. If a request message has not been received from the operation terminal 4 (Step S100; NO), the processing of the server 2 proceeds to Step S103.

[0048] (Step S101) The server 2 converts the received request message into a communication format (i.e., communication format B) for communication with the data conversion device 3. After that, the process of the server 2 proceeds to step S102.

[0049] (Step S102) The server 2 transmits the converted request message to the data conversion device 3. After that, the process of the server 2 returns to step S100.

[0050] (Step S103) The server 2 determines whether or not a response message has been received from the data conversion device 3. If a response message has been received from the data conversion device 3 (Step S103; YES), the processing of the server 2 proceeds to Step S104. If a response message has not been received from the data conversion device 3 (Step S103; NO), the processing of the server 2 returns to Step S100.

[0051] (Step S104) The server 2 stores the device data extracted from the received response message in the device data storage unit 240. After that, the process of the server 2 proceeds to step S105.

[0052] (Step S105) The server 2 determines whether the received response message is in response to the request message from the operation terminal 4. For example, if the received response message is based on device data periodically acquired from the device 5 by the data conversion device 3, the server 2 determines that the received response message is not in response to the request message from the operation terminal 4. If the received response message is in response to the request message from the operation terminal 4 (Step S105; YES), the processing of the server 2 proceeds to Step S106. If the received response message is not in response to the request message from the operation terminal 4 (Step S105; NO), the processing of the server 2 returns to Step S100.

[0053] (Step S106) The server 2 converts the received response message into a response message that complies with the communication format (i.e., communication format A) used when communicating with the operation terminal 4. After that, the process of the server 2 proceeds to step S107.

[0054] (Step S107) The server 2 transmits the converted response message to the operation terminal 4. After that, the process of the server 2 returns to step S100.

[0055] <Processing of Data Conversion Device 3> FIG. 14 is a flowchart showing the procedure of processing executed by the data conversion device 3.

[0056] (Step S200) The data conversion device 3 determines whether or not a request message has been received from the server 2. If a request message has been received from the server 2 (Step S200; YES), the processing of the data conversion device 3 proceeds to Step S201. If a request message has not been received from the server 2 (Step S200; NO), the processing of the data conversion device 3 proceeds to Step S203.

[0057] (Step S201) The data conversion device 3 converts the request data included in the received request message into request data in a format that can be handled by the device 5. As described above, the request data stored in the request message received from the server 2 corresponds to the device correspondence data (see FIG. 6) converted into hexadecimal text. Therefore, the data conversion device 3 converts the request data included in the received request message into request data in binary format. After that, the process of the data conversion device 3 proceeds to step S202.

[0058] (Step S202) The data conversion device 3 generates a request message that stores the converted request data and conforms to the communication format (i.e., communication format C) for communicating with the device 5, and transmits the request message to the device 5. Thereafter, the processing of the data conversion device 3 returns to step S200.

[0059] (Step S203) The data conversion device 3 determines whether the time has come for periodic acquisition of equipment data. As described above, the data conversion device 3 autonomously acquires equipment data from the equipment 5 at regular time intervals. At this time, the data conversion device 3 acquires equipment data of a predetermined equipment data type. If the time has come for periodic acquisition of equipment data, that is, if a certain amount of time has passed since the previous periodic acquisition (Step S203; YES), the processing of the data conversion device 3 proceeds to Step S204. If the time has not come for periodic acquisition of equipment data (Step S203; NO), the processing of the data conversion device 3 proceeds to Step S206.

[0060] (Step S204) The data conversion device 3 generates request data for requesting device data of a device data type corresponding to periodic acquisition from the device 5. At this time, the data conversion device 3 generates request data in a format that can be handled by the device 5. Thereafter, the process of the data conversion device 3 proceeds to step S205.

[0061] (Step S205) The data conversion device 3 generates a request message in accordance with the communication format (i.e., communication format C) for communicating with the device 5, in which the generated request data is stored, and transmits the request message to the device 5. Thereafter, the processing of the data conversion device 3 returns to step S200.

[0062] (Step S206) The data conversion device 3 determines whether or not a response message has been received from the device 5. If a response message has been received from the device 5 (step S206; YES), the processing of the data conversion device 3 proceeds to step S207. If a response message has not been received from the device 5 (step S206; NO), the processing of the data conversion device 3 returns to step S200.

[0063] (Step S207) The data conversion device 3 executes a data conversion process to convert the device data included in the received response message into a human-readable format or a non-human-readable format. The details of the data conversion process will be described later. After that, the process of the data conversion device 3 proceeds to step S208.

[0064] (Step S208) The data conversion device 3 generates a response message in accordance with the communication format (i.e., communication format B) for communicating with the server 2, in which the converted device data is stored, and transmits the response message to the server 2. Thereafter, the processing of the data conversion device 3 returns to step S200.

[0065] <Data Conversion Processing> FIG. 15 is a flowchart showing the procedure of the data conversion processing executed by the data conversion device 3.

[0066] (Step S300) The data conversion device 3 acquires the device data type from the communication data ID of the device data received from the device 5. After that, the process of the data conversion device 3 proceeds to step S301.

[0067] (Step S301) The data conversion device 3 determines whether the group type of the device data is the first data group. Specifically, the data conversion device 3 determines the group type of the device data based on the acquired device data type and the above-mentioned group type determination table pre-stored in the auxiliary storage device 34. If the group type of the device data is the first data group (Step S301; YES), the processing of the data conversion device 3 proceeds to Step S302. If the group type of the device data is not the first data group, i.e., if it is the second data group (Step S301; NO), the processing of the data conversion device 3 proceeds to Step S303.

[0068] (Step S302) The data conversion device 3 converts the device data received from the device 5 into device data in a human-readable format based on the data conversion table 340 (see FIGS. 7 to 11). After that, the data conversion device 3 ends the data conversion process.

[0069] (Step S303) The data conversion device 3 converts the device data received from the device 5 into device data in a non-human-readable format. Specifically, the data conversion device 3 converts the device data received from the device 5 into device data represented as hexadecimal text data. Thereafter, the data conversion device 3 ends the data conversion process.

[0070] As described above, in the device data collection system 1 according to the present embodiment, when device data included in a response message received from a device 5 belongs to the first data group, the data conversion device 3 converts the device data into human-readable data based on the data conversion table 340 and transmits the converted device data to the server 2. This allows the data conversion device 3 to convert highly useful and significant device data into a human-readable format by pre-setting the group type discrimination table so that, for example, device data that is frequently used by the data analysis system, such as periodically acquired device data, belongs to the first data group. As a result, the server 2 can store highly useful and significant device data in a human-readable format without performing data conversion, thereby minimizing increases in the cost of using device data.

[0071] Furthermore, the data conversion device 3 converts device data that does not belong to the first data group, i.e., belongs to the second data group, into data in a non-human-readable format represented by hexadecimal text data and transmits it to the server 2. Because the data size of the non-human-readable format data is smaller than the data size of the human-readable format data, it is possible to suppress an increase in the amount of data communication in communication with the server 2.

[0072] (Variation 1) There is no limit to the number of devices 5 installed in each user's home. When multiple devices 5 are installed in a user's home, the devices 5 may be of the same model (product type, such as an air conditioner, television, or water heater), or different models may be included.

[0073] (Modification 2) The server 2 may voluntarily transmit to the data conversion device 3 a request message that stores request data such as an operation request or a data acquisition request.

[0074] (Modification 3) Data in a non-human-readable format is not limited to hexadecimal text data. For example, encoding methods such as Base64 may also be used for conversion to a non-human-readable format.

[0075] (Variation 4) A single request message transmitted from the operation terminal 4 may include multiple pieces of request data. In this case, the device data types indicated by the communication data IDs of the request data are different, but the service type is the same. When such a request message is received, the data conversion device 3 converts the request data so that it can be handled by the device 5 and sequentially transmits it to the device 5. The data conversion device 3 then sequentially receives device data corresponding to each piece of request data from the device 5 and converts it into a human-readable format or a non-human-readable format. The data conversion device 3 generates a response message that collectively stores the converted device data and transmits it to the server 2.

[0076] Furthermore, when periodically acquiring device data from the device 5, the data conversion device 3 may sequentially acquire multiple pieces of device data of different device data types from the device 5. In this case, as in the above, the data conversion device 3 converts each piece of acquired device data into a human-readable format or a non-human-readable format, and transmits a response message storing all of the converted device data together to the server 2.

[0077] (Variation 5) When the device data acquired from the device 5 belongs to the first data group, the data conversion device 3 may convert the device data into device data in a human-readable format and into device data in a non-human-readable format. In this case, the data conversion device 3 transmits a response message storing the converted device data to the server 2. FIG. 16 shows an example of both sets of device data included in the response message in this case. In the data conversion table 340, conversion rules for each property are defined for each device data type, but conversion rules are not necessarily defined for all properties. In other words, there may be properties that cannot be converted into a human-readable format. In this variation, the server 2 can manage the values ​​of all properties in each device data, thereby preventing data loss during data analysis, etc.

[0078] Instead of converting the entire device data to a non-human-readable format, the data conversion device 3 may convert only the properties that have not been converted to a human-readable format to a non-human-readable format. For example, if the data length of the device data property is 14 bytes and the first 6 consecutive bytes of the device data property are converted to a human-readable format according to the data conversion table 340, the 7th to 14th bytes (a total of 8 bytes) from the beginning of the device data property will be the value of the property that has not been converted to a human-readable format. In this case, the data conversion device 3 converts the value of those 8 bytes of the property to a non-human-readable format. This reduces the data size of the response message sent to the server 2 compared to the above case.

[0079] (Variation 6) In a request message transmitted from the operation terminal 4, the request data corresponding to the device data of the first data group may be written in a human-readable format. Fig. 17 shows an example of a case where the request message includes request data in a human-readable format indicating an operation request. In this case, the data conversion device 3 uses the data conversion table 340 to convert the request data into request data that can be handled by the device 5.

[0080] (Variation 7) In the above embodiment, the data conversion device 3 determines the group type of the device data (i.e., the first data group or the second data group) based on the device data type, but information on the group type may be included in the request message sent from the server 2. In this case, the data conversion device 3 regards the device data periodically acquired from the device 5 as belonging to the first data group and converts it into a human-readable format.

[0081] (Variation 8) All or part of the functional units of the server 2 (see FIG. 5) may be realized by dedicated hardware, and all or part of the functional units of the data conversion device 3 (see FIG. 5) may be realized by dedicated hardware. The dedicated hardware may be, for example, a single circuit, a composite circuit, a programmed processor, an ASIC (Application-Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a combination thereof.

[0082] The technical ideas according to the above-described modifications may be realized independently or in appropriate combination.

[0083] The present disclosure allows various embodiments and modifications without departing from the broad spirit and scope. Furthermore, the above-described embodiments are intended to explain the present disclosure and do not limit the scope of the present disclosure. In other words, the scope of the present disclosure is defined by the claims, not the embodiments. Various modifications made within the scope of the claims and within the meaning of the disclosure equivalent thereto are considered to be within the scope of the present disclosure.

[0084] The present disclosure can be suitably adopted in a system for collecting equipment data of equipment.

[0085] 1 Equipment data collection system, 2 Server, 3 Data conversion device, 4 Operation terminal, 5 Equipment, 6 Data analysis server, 20, 30, 42 Communication interface, 21, 31, 43 CPU, 22, 32, 44 ROM, 23, 33, 45 RAM, 24, 34, 46 Auxiliary storage device, 25, 35, 47 Bus, 40 Display, 41 Operation acceptance unit, 200 Terminal communication unit, 201 Data conversion device communication unit, 202 Equipment data provision unit, 240 Equipment data storage unit, 300 Server communication unit, 301 Equipment communication unit, 302 Equipment data request unit, 303 Data conversion unit, 340 Data conversion table

Claims

1. A means for acquiring device data that acquires device data relating to the operation of the device from the device through communication with the device, If the acquired device data belongs to a first data group, the data conversion means converts the device data into a first data format represented as human-readable text data according to predetermined conversion rules, and if the acquired device data belongs to a second data group different from the first data group, the data conversion means converts the device data into a second data format represented as human-readable text data. The system includes a device data transmission means for transmitting the converted device data to a server, The data conversion means, when the acquired device data belongs to the first data group, converts the device data into data in the first data format and also into data in the second data format according to the conversion rules. Data conversion device.

2. A device data acquisition means that acquires device data relating to the operation of the device from the device by communication with the device, If the acquired device data belongs to a first data group, the data conversion means converts the device data into a first data format represented as human-readable text data according to predetermined conversion rules, and if the acquired device data belongs to a second data group different from the first data group, the data conversion means converts the device data into a second data format represented as human-readable text data. The system includes a device data transmission means for transmitting the converted device data to a server, The data conversion means, when the acquired device data belongs to the first data group, converts the device data into data in the first data format according to the conversion rules, and converts any properties included in the device data that have not been converted into data in the first data format into data in the second data format. Data conversion device.

3. The data conversion means determines, based on the information contained in the acquired device data, whether the device data belongs to the first data group or the second data group. A data conversion device according to claim 1 or 2.

4. A request message receiving means that receives a request message from a server indicating a request to a device, When the aforementioned request message is received, a device data acquisition means obtains device data relating to the operation of the device from the device through communication with the device, If the acquired device data belongs to a first data group, the data conversion means converts the device data into a first data format represented as human-readable text data according to predetermined conversion rules, and if the acquired device data belongs to a second data group different from the first data group, the data conversion means converts the device data into a second data format represented as human-readable text data. The system includes a device data transmission means for transmitting the converted device data to the server, The data conversion means determines, based on the information contained in the request message, whether the device data belongs to the first data group or the second data group. Data conversion device.

5. The device data acquisition means acquires device data relating to the operation of the device from the device through communication with the device. If the acquired device data belongs to a first data group, the data conversion means converts the device data into data in a first data format represented as human-readable text data according to predetermined conversion rules; if the acquired device data belongs to a second data group different from the first data group, the data conversion means converts the device data into data in a second data format represented as human-readable text data. A data conversion method comprising a device data transmission means that transmits the converted device data to a server, The data conversion means, when the acquired device data belongs to the first data group, converts the device data into data in the first data format and also into data in the second data format according to the conversion rules. Data conversion method.

6. The device data acquisition means acquires device data relating to the operation of the device from the device by communication with the device, If the acquired device data belongs to a first data group, the data conversion means converts the device data into data in a first data format represented as human-readable text data according to predetermined conversion rules; if the acquired device data belongs to a second data group different from the first data group, the data conversion means converts the device data into data in a second data format represented as human-readable text data. A data conversion method comprising a device data transmission means that transmits the converted device data to a server, The data conversion means, when the acquired device data belongs to the first data group, converts the device data into data in the first data format according to the conversion rules, and converts any properties included in the device data that have not been converted into data in the first data format into data in the second data format. Data conversion method.

7. The request message receiving means receives a request message from the server indicating a request to the device, When the request message is received, the device data acquisition means acquires device data relating to the operation of the device from the device through communication with the device. If the acquired device data belongs to a first data group, the data conversion means converts the device data into data in a first data format represented as human-readable text data according to predetermined conversion rules; if the acquired device data belongs to a second data group different from the first data group, the data conversion means converts the device data into data in a second data format represented as human-readable text data. A data conversion method comprising: a device data transmission means that transmits the converted device data to the server, The data conversion means determines, based on the information contained in the request message, whether the device data belongs to the first data group or the second data group. Data conversion method.

8. Computers, Device data acquisition means that acquires device data relating to the operation of the device from the device through communication with the device, If the acquired device data belongs to a first data group, the data conversion means converts the device data into a first data format represented as human-readable text data according to predetermined conversion rules; if the acquired device data belongs to a second data group different from the first data group, the data conversion means converts the device data into a second data format represented as human-readable text data. It functions as a device data transmission means that transmits the converted device data to a server. The data conversion means, when the acquired device data belongs to the first data group, converts the device data into data in the first data format and also into data in the second data format according to the conversion rules. program.

9. A computer, Device data acquisition means that acquires device data relating to the operation of the device from the device through communication with the device, If the acquired device data belongs to a first data group, the data conversion means converts the device data into a first data format represented as human-readable text data according to predetermined conversion rules; if the acquired device data belongs to a second data group different from the first data group, the data conversion means converts the device data into a second data format represented as human-readable text data. It functions as a device data transmission means that transmits the converted device data to a server. The data conversion means, when the acquired device data belongs to the first data group, converts the device data into data in the first data format according to the conversion rules, and converts any properties included in the device data that have not been converted into data in the first data format into data in the second data format. program.

10. A computer, Request message receiving means for receiving a request message from a server indicating a request to a device. When the aforementioned request message is received, a device data acquisition means obtains device data relating to the operation of the device from the device through communication with the device. If the acquired device data belongs to a first data group, the data conversion means converts the device data into a first data format represented as human-readable text data according to predetermined conversion rules; if the acquired device data belongs to a second data group different from the first data group, the data conversion means converts the device data into a second data format represented as human-readable text data. It functions as a device data transmission means that transmits the converted device data to the server, The data conversion means determines, based on the information contained in the request message, whether the device data belongs to the first data group or the second data group. program.