JP2014127041A - Apparatus management device, apparatus management method and apparatus management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To simplify an application for management in a configuration for managing a plurality of apparatuses.SOLUTION: An apparatus management device 101 is capable of managing a plurality of apparatuses 161. The apparatus management device 101 comprises: an information processing unit 12 for performing at least one of creation of outgoing information which should be transmitted to the apparatuses 161 and processing of incoming information received from the apparatuses 161; a communication processing unit 11 for performing transmission processing of outgoing information to the apparatuses 161 and reception processing of incoming information from the apparatuses 161; and an apparatus information acquisition unit 11 for acquiring and retaining a correspondence relationship between identifiers added to the apparatuses 161 and addresses of the apparatuses 161 to announce the identifiers to the information processing unit 12. The information processing unit 12 retains the identifiers announced from the apparatus information acquisition unit 11 and performs at least one of creation of outgoing information and processing of incoming information by using the identifiers.

Description

  The present invention relates to a device management apparatus, a device management method, and a device management program, and more particularly to a device management device, a device management method, and a device management program for managing each device by communicating with a plurality of devices.

  Device management systems that manage multiple electrical devices by communicating with various electrical devices in general homes and offices have been developed (for example, “ECHONET Lite standard Ver1.01”, Echonet Consortium, March 2012 Issued on May 5 (see Non-Patent Document 1)).

"ECHONET Lite Standard Ver1.01", Echonet Consortium, issued on March 5, 2012

  In the device management system as described above, the device management apparatus that manages various types of electrical devices manages the electrical devices by designating specific electrical devices and transmitting or receiving information.

  Here, when the transmission medium and the communication protocol with the electric device are different in each electric device, the management application installed in the device management apparatus can be changed according to the difference in the transmission medium and the communication protocol. It is necessary to perform communication processing with a device and creation of a communication message.

  For example, in the technology described in Non-Patent Document 1, in each subnet configuring a domain, an address for realizing layer 2 communication in a transmission medium or an IP address is used as an identifier of a device uniquely identified in the subnet. . This complicates application processing and procedures in the device management apparatus, and increases application development costs.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to provide a device management apparatus and a device management method capable of simplifying a management application in a configuration for managing a plurality of devices. And providing equipment management programs.

  (1) A device management apparatus according to an aspect of the present invention is a device management apparatus capable of managing a plurality of devices, and creates downlink information to be transmitted to the device and processes uplink information received from the device. An information processing unit for performing at least one of the following: a communication processing unit for performing transmission processing of the downlink information to the device and reception processing of the uplink information from the device; and an identifier assigned to the device A device information acquisition unit for acquiring and holding a correspondence relationship with the address of the device and notifying the information processing unit of the identifier, the information processing unit being notified from the device information acquisition unit The identifier is held, and at least one of creation of the downlink information and processing of the uplink information is performed using the identifier.

  With such a configuration, a difference in address system in communication with each device can be absorbed in the communication processing unit. That is, the information processing unit does not need to change the process according to the difference in the address system in communication with the device. Therefore, in the configuration for managing a plurality of devices, it is possible to simplify the management application. Specifically, it is possible to prevent the processing and procedure of the application in the device management apparatus from becoming complicated, and to prevent the development cost of the application from increasing.

  (2) Preferably, the device information acquisition unit acquires and holds a correspondence relationship between the device identifier, the device address, and the device type, and stores the identifier and the corresponding type in the information. The information processing unit holds the identifier and the corresponding type notified from the device information acquisition unit, and creates the downlink information and the uplink using the identifier and the corresponding type. At least one of information processing is performed.

  In this way, the information processing unit can perform processing according to the type of device by the configuration of acquiring the type of device. For example, the information processing unit can appropriately change the content of the downlink information to the device according to the type of the device.

  (3) More preferably, the correspondence relationship includes one address and a plurality of types corresponding to one identifier.

  With such a configuration, for example, by transmitting downlink information with one address as a destination, the downlink information can be notified to a plurality of devices having the address.

  (4) Preferably, the device information acquisition unit acquires and holds a correspondence relationship between the device identifier, the device address, and a communication medium in communication with the device.

  With such a configuration, the communication processing unit can absorb differences in communication media such as transmission media and communication protocols between devices. That is, the information processing unit does not need to change the communication process with the device and the communication message creation process according to differences in transmission media, communication protocols, and the like. Therefore, it is possible to further simplify the application in the device management apparatus.

  (5) More preferably, the information processing unit sends an identifier of the device to which the downlink information is transmitted in addition to the downlink information to the communication processing unit, and the communication processing unit receives the information from the information processing unit. The downlink information is transmitted through the communication medium corresponding to the identifier, with the address corresponding to the identifier as the destination of the downlink information.

  With such a configuration, the information processing unit simply transmits the downlink information to the device without performing processing corresponding to the communication medium in communication with the device, only by notifying the communication processing unit of the device identifier. can do. Therefore, it is possible to further simplify the application in the device management apparatus.

  (6) Preferably, in addition to the downlink information, the information processing unit sends an identifier of the device to which the downlink information is transmitted to the communication processing unit, and the communication processing unit receives the information from the information processing unit. The downlink information is transmitted with the address corresponding to the identifier as a destination.

  With such a configuration, it is possible to easily identify the target device using the identifier of the device between the communication processing unit and the information processing unit, and perform a process of transmitting downlink information to the device.

  (7) Preferably, the communication processing unit sends an identifier of the device that is the transmission source of the uplink information to the information processing unit in addition to the uplink information, and the information processing unit receives the information from the communication processing unit. The uplink information is processed based on the identifier.

  With such a configuration, it is possible to easily identify the target device using the identifier of the device between the communication processing unit and the information processing unit, and perform a process of receiving uplink information from the device.

  (8) A device management method according to an aspect of the present invention is a device management method in a device management apparatus capable of managing a plurality of devices, and the correspondence relationship between an identifier assigned to the device and the address of the device. Acquiring and holding and notifying the identifier; holding the notified identifier; using the identifier to create downlink information to be transmitted to the device and processing uplink information received from the device; Performing at least one of the following.

  With such a configuration, a difference in address system in communication with each device can be absorbed in the communication processing unit. That is, the information processing unit does not need to change the process according to the difference in the address system in communication with the device. Therefore, in the configuration for managing a plurality of devices, it is possible to simplify the management application. Specifically, it is possible to prevent the processing and procedure of the application in the device management apparatus from becoming complicated, and to prevent the development cost of the application from increasing.

  (9) A device management program according to an aspect of the present invention is a device management program used in a device management apparatus capable of managing a plurality of devices, and includes an identifier assigned to the device and an address of the device. A step of notifying and receiving the identifier, creating the downlink information to be transmitted to the device using the identifier, and receiving the identifier from the device. A program for executing at least one of uplink information processing.

  With such a configuration, a difference in address system in communication with each device can be absorbed in the communication processing unit. That is, the information processing unit does not need to change the process according to the difference in the address system in communication with the device. Therefore, in the configuration for managing a plurality of devices, it is possible to simplify the management application. Specifically, it is possible to prevent the processing and procedure of the application in the device management apparatus from becoming complicated, and to prevent the development cost of the application from increasing.

  According to the present invention, it is possible to simplify a management application in a configuration for managing a plurality of devices.

It is a figure which shows the structure of the apparatus management system which concerns on embodiment of this invention. It is a figure which shows the software structure and interface structure of the apparatus management apparatus which concerns on embodiment of this invention. It is the flowchart which defined the operation | movement procedure at the time of the apparatus management apparatus which concerns on embodiment of this invention acquires apparatus information. It is a figure which shows the sequence of the status notification at the time of starting of the apparatus management apparatus which concerns on embodiment of this invention. It is a figure which shows the sequence at the time of the apparatus management apparatus which concerns on embodiment of this invention acquires the information of each apparatus. It is a figure which shows an example of the apparatus management table in the apparatus management apparatus which concerns on embodiment of this invention. It is a figure which shows an example of the apparatus management table in the apparatus management apparatus which concerns on embodiment of this invention. It is a figure which shows an example of the ID table in the apparatus management apparatus which concerns on embodiment of this invention. It is a figure which shows the sequence at the time of the apparatus management apparatus which concerns on embodiment of this invention controls each apparatus. It is a figure which shows the sequence at the time of the apparatus management apparatus which concerns on embodiment of this invention receives the status notification from each apparatus. It is a figure which shows the other example of the sequence at the time of the apparatus management apparatus which concerns on embodiment of this invention receives the status notification from each apparatus. It is a figure which shows the sequence at the time of the apparatus management apparatus which concerns on embodiment of this invention receives the control command from each apparatus. It is a figure which shows the other example of a sequence when the apparatus management apparatus which concerns on embodiment of this invention receives the control command from each apparatus. It is a figure which shows the sequence at the time of the apparatus management apparatus which concerns on embodiment of this invention notifies a state to each apparatus. It is a figure which shows the other example of the apparatus management table in the apparatus management apparatus which concerns on embodiment of this invention.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals and description thereof will not be repeated.

[Configuration and basic operation]
FIG. 1 is a diagram showing a configuration of a device management system according to an embodiment of the present invention.

  With reference to FIG. 1, the device management system 201 includes a device management apparatus 101 and a plurality of devices 161.

  The device management apparatus 101 is a device provided in a home, an office, or the like, and is, for example, a general-purpose home device for connecting a home gateway or a home gateway and a home electric appliance, that is, an end user device.

  The device management apparatus 101 can manage a plurality of devices 161. Here, it is assumed that a plurality of devices 161 are connected to the device management apparatus 101 by wire or wireless. For example, the device management apparatus 101 can install and execute a power monitoring software module for comprehensively monitoring the power consumption of the plurality of devices 161. Note that the device management apparatus 101 may be used to manage one device 161.

  Specifically, the device management apparatus 101 executes a software module for power monitoring, and from the device 161 such as a home television receiver, an air conditioner, or a PC (Personal Computer) via a sensor or the like, the device 161 Receive information about the amount of power used. In addition, the device management apparatus 101 executes a power monitoring software module, and thereby, from a device 161 such as a solar cell in the home via a sensor or the like, information on the power generation amount of the device 161 and a sensor or the like. Information on the amount of electricity stored in the device 161 is received from the device 161 such as a storage battery in the home. Then, the device management apparatus 101 creates management information based on the received information, and controls the operation of each device 161 based on the created management information, for example.

  Further, the device management apparatus 101 executes management software module 161 for managing information and the like so that the user can view the amount of power used or the amount of power generation or statistical information thereof by executing the power monitoring software module. It is also possible to send to.

  In addition, the device management apparatus 101 can include not only a power monitoring software module but also a plurality of software modules for providing other services to the user.

  For example, the device management apparatus 101 includes a software module for providing a user with a home security function such as specifying a user who uses the device 161 or limiting an access range by the device 161.

  The device management apparatus 101 downloads and installs such software modules from an external network or the like as necessary, and deletes unnecessary software modules, thereby flexibly changing functions.

  Here, a software plug-in that enables operation of the same software module even when the hardware manufacturer or type is different, and enables addition or replacement of the software module without restarting the device. As a mechanism, there is OSGi (Open Services Gateway initiative) which is an execution environment of software modules using Java (registered trademark).

  In this OSGi, a Java VM (virtual machine) is executed as a process on the OS (Operating System), OSGi FW (Framework), which is middleware described in the Java language, operates on the process, and further on the OSGi FW One or a plurality of software modules (hereinafter also referred to as bundles) are installed and executed.

  FIG. 2 is a diagram showing a software configuration and an interface configuration of the device management apparatus according to the embodiment of the present invention.

  Referring to FIG. 2, the device management apparatus 101 includes a WAN (Wide Area Network) interface unit 31, a wireless LAN interface unit 32, a ZigBee interface unit 33, a wired LAN interface unit 34, a serial interface unit 35, And a PLC (Power Line Communications) interface unit 36.

  Hereinafter, each of the WAN interface unit 31, the wireless LAN interface unit 32, the ZigBee interface unit 33, the wired LAN interface unit 34, the serial interface unit 35, and the PLC interface unit 36 may be simply referred to as an “interface unit”. In addition, each of the wireless LAN interface unit 32, the ZigBee interface unit 33, the wired LAN interface unit 34, the serial interface unit 35, and the PLC interface unit 36 may be referred to as a “device interface unit”.

  The software of the device management apparatus 101 includes an OS (Operating System) 21, a Java virtual machine (Java VM) 22, an OSGi FW (Open Service Gateway initiative Framework) 23, and a bundle group 24. The bundle group 24 includes a message generation / analysis process and transmission / reception process bundle (communication processing unit and device information acquisition unit) 11 and an application (information processing unit) 12. The application 12 is, for example, a power monitoring bundle or a home security bundle.

  The device management apparatus 101 operates according to a plurality of hierarchized layers. More specifically, the OS 21 layer is the lowest layer (first layer), the upper layer is the Java virtual machine 22 layer, the upper layer is the OSGi FW 23 layer, and the upper layer is This is a layer (second layer) of the bundle group 24.

  OSGi FW23 is a standardized technology by the OSGi Alliance, and is a software platform that provides an execution environment for software components created based on open software componentization technology based on the Java (registered trademark) language as described above. is there.

  The device management apparatus 101 can execute each bundle of the bundle group 24 alone or in cooperation on the OSGi FW 23. In FIG. 2, one application is shown as a bundle included in the bundle group 24, but the bundle group 24 may include a plurality of bundles.

  The software platform for executing each bundle is not limited to the Java virtual machine 22 and the OSGi FW 23, and may be another application execution environment.

  Each bundle included in the bundle group 24 operates on the OSGi FW 23 using a function provided from the OSGi FW 23.

  The application 12 creates downlink information to be transmitted to the device 161 and processes the uplink information received from the device 161 on the OSGi FW 23.

  The telegram generation / analysis process and transmission / reception process bundle 11 performs a process of transmitting downlink information to the device 161 and a process of receiving uplink information from the device 161.

  Specifically, the message generation / analysis processing and transmission / reception processing bundle 11 communicates with the device 161 on the OSGi FW 23 via each interface unit, the OS 21, and the Java virtual machine 22.

  The OS 21 transmits / receives communication signals to / from a plurality of devices 161 that are wired or wirelessly connected to its own device management apparatus 101 via the device interface unit.

  Each device interface unit including a communication circuit and a communication medium used when the OS 21 transmits / receives a communication signal to / from the device 161 include physical lines such as copper wires, coaxial cables, telephone wires, optical fiber cables, radio waves, and infrared rays. And a logical medium such as a communication protocol.

  Specifically, the wireless LAN interface unit 32 and the OS 21 have a wireless transmission medium and use a communication medium of a communication protocol in accordance with the IEEE 802.11 standard.

  The ZigBee interface unit 33 and the OS 21 have a wireless transmission medium and use a communication medium of a communication protocol according to the ZigBee standard.

  In the wired LAN interface unit 34 and the OS 21, the transmission medium is a LAN cable, and for example, a communication medium of a communication protocol according to the Ethernet (registered trademark) standard is used.

  In the serial interface unit 35 and the OS 21, the transmission medium is a serial cable, and for example, a communication medium of a communication protocol according to the RS-232C standard is used.

  In the PLC interface unit 36 and the OS 21, the transmission medium is a power line, and for example, a communication medium of a communication protocol according to the HD-PLC (registered trademark) standard is used.

  The device interface unit receives uplink information from the device 161 via, for example, a USB (Universal Serial Bus) interface, and outputs the uplink information to the message generation / analysis processing and transmission / reception processing bundle 11.

  In addition, the device interface unit acquires downlink information from the message generation / analysis process and transmission / reception processing bundle 11 to the device 161, and transmits the acquired downlink information to the device 161. The device interface unit can also transmit and receive information to and from the device 161 via a measuring instrument such as a watt hour meter.

  For example, the application 12 which is a home security software module provides a user with a home security function by transmitting and receiving information to and from the device 161 via the message generation / analysis processing and transmission / reception processing bundle 11 and the device interface unit.

  Further, for example, the application 12 that is a power monitoring software module acquires uplink information indicating the amount of power used by the device 161 via the message generation / analysis processing and transmission / reception processing bundle 11 and the device interface unit, and acquires the acquired uplink information. For example, the amount of power used in a plurality of devices 161 in the home is comprehensively managed, such as creating statistical information based on.

  Further, the application 12 creates downlink information related to the temperature setting of the device 161 that is an air conditioner, for example, and sends it to the message generation / analysis process and transmission / reception process bundle 11 together with the ID (identifier) of the air conditioner.

  The message generation / analysis processing and transmission / reception processing bundle 11 creates a frame including downlink information received from the application 12 in a frame format corresponding to the ID received from the application 12, and transmits the frame to the device 161 via the device interface unit. .

[Operation]
Next, the operation of the device management system according to the embodiment of the present invention will be described with reference to the drawings. The device management apparatus 101 reads out and executes a program including the following flowchart and sequence steps from a memory (not shown). This program can be installed externally.

  FIG. 3 is a flowchart defining an operation procedure when the device management apparatus according to the embodiment of the present invention acquires device information.

  Referring to FIG. 3, first, when device management apparatus 101 is activated (step S <b> 1), its own information, for example, device management apparatus 101, is activated for each device 161 in its own management target network. The activation message including the information and the identification information of the device management apparatus 101 is notified via the device interface unit (step S2).

  Next, in the device management apparatus 101, the application 12 requests the message generation / analysis processing and transmission / reception processing bundle 11 for the ID (identifier) of the device 161 and device information such as the type of the device 161 (step S3).

  Next, in response to the request from the application 12, the message generation / analysis process / transmission / reception process bundle 11 notifies the device 161 in the management target network of a device information request message (step S4).

  Next, the message generation / analysis processing and transmission / reception processing bundle 11 receives a response message from each device 161 in response to the device information request message, creates a device management table based on the response message of each device 161, and holds it. (Step S5).

  Next, the message generation / analysis processing and transmission / reception processing bundle 11 notifies the application 12 of the ID of each device 161 and the corresponding device information from the created device management table (step S6).

  Next, the application 12 holds the ID of each device 161 notified from the message generation / analysis processing and transmission / reception processing bundle 11 and the corresponding device information (step S7).

  Note that the message generation / analysis processing and transmission / reception processing bundle 11 is not limited to the time when the device management apparatus 101 is started. The information request message may be notified and the device management table may be updated.

  In addition, a newly activated device 161 in the management target network can spontaneously transmit its own information to the device management apparatus 101.

  In addition, the message generation / analysis processing and transmission / reception processing bundle 11 and the application 12 may be already installed when the device management apparatus 101 is activated, or may be newly downloaded and installed from an external network or the like after activation. Good.

  FIG. 4 is a diagram showing a state notification sequence when the device management apparatus according to the embodiment of the present invention is activated.

  Referring to FIG. 4, first, when device management apparatus 101 is activated, application 12 outputs a status notification command to message generation / analysis processing bundle 11. This status notification command includes, for example, information indicating the operation start of the device management apparatus 101 (step S11).

  Next, the message generation / analysis processing bundle 11 receives a status notification command from the application 12, and is a message, that is, a message including the content of the status notification command, in accordance with each protocol registered in advance in the device management apparatus 101. A message is created (step S12) and output to the transmission / reception processing bundle 11 (step S13). This message corresponds to the activation message in FIG.

  Next, the transmission / reception processing bundle 11 multicasts the message received from the message generation / analysis processing bundle 11 to each device via each communication medium. Here, a communication medium that can be used by the device management apparatus 101 is registered in advance in the device management apparatus 101, and the transmission / reception processing bundle 11 acquires a multicast address for each communication medium based on the registered contents. (Steps S14 and S15).

  FIG. 5 is a diagram showing a sequence when the device management apparatus according to the embodiment of the present invention acquires information on each device.

  The message generation / analysis processing and transmission / reception processing bundle 11 acquires and holds the correspondence between the ID assigned to the device 161 and the address of the device 161, and notifies the application 12 of the ID.

  The application 12 holds the ID notified from the telegram generation / analysis process and the transmission / reception process bundle 11, and creates downlink information and processes uplink information using the ID.

  More specifically, for example, the message generation / analysis processing and transmission / reception processing bundle 11 acquires and holds the correspondence relationship between the ID of the device 161, the address of the device 161, and the type of the device 161. The type is notified to the application 12.

  Further, for example, the message generation / analysis process and the transmission / reception process bundle 11 acquires and holds the correspondence relationship between the ID of the device 161, the address of the device 161, and the communication medium in communication with the device 161.

  Specifically, referring to FIG. 5, first, the application 12 outputs a device type code acquisition command to the message generation / analysis processing bundle 11 (step S21).

  Next, in response to the device type code acquisition command from the application 12, the message generation / analysis processing bundle 11 creates a message or message for each protocol registered in advance in the device management apparatus 101 (step S22). The data is output to the processing bundle 11 (step S23). This message corresponds to the device information request message in FIG.

  Next, the transmission / reception processing bundle 11 multicasts the message received from the message generation / analysis processing bundle 11 to each device via each communication medium. Here, a communication medium that can be used by the device management apparatus 101 is registered in advance in the device management apparatus 101, and the transmission / reception processing bundle 11 acquires a multicast address for each communication medium based on the registered contents. (Steps S24 and S25).

  Next, the transmission / reception processing bundle 11 receives a response message from each device (step S26), and creates a device management table based on the response message (step S27).

  FIG. 6 is a diagram showing an example of a device management table in the device management apparatus according to the embodiment of the present invention.

  Referring to FIG. 6, this device management table is a table created by transmission / reception processing bundle 11 in step S27 of the flowchart shown in FIG. 5, and shows the correspondence between IDs, transmission media, and addresses.

  Specifically, in the device management table, the transmission medium corresponding to the device 161 with ID 1 is Ethernet, and the address is an IP address according to IPv6 (Internet Protocol Version 6), specifically 2001 :: ff5f: 7535. The transmission medium corresponding to the device 161 of ID2 is PLC, and the address is an IP address according to IPv4 (Internet Protocol Version 4), specifically, 192.168.2.10. The transmission medium corresponding to the device 161 of ID3 is serial and the address is USB1. The transmission medium corresponding to the device 161 with ID4 is ZigBee and the address is 0x0012.

  Referring to FIG. 5 again, next, the transmission / reception processing bundle 11 outputs the received response message and the ID in the created device management table to the message generation / analysis processing bundle 11 (step S28).

  Next, the message generation / analysis processing bundle 11 analyzes the response message received from the transmission / reception processing bundle 11, and adds the device type code and protocol type of the device 161 of each ID to the device management table (step S29).

  FIG. 7 is a diagram showing an example of a device management table in the device management apparatus according to the embodiment of the present invention.

  Referring to FIG. 7, this device management table is a table to which information is added by message generation / analysis processing bundle 11 in step S29 of the flowchart shown in FIG. 5, and includes ID, device type code, transmission medium, address, and protocol. The correspondence relationship is shown.

  Specifically, in the device management table, the device type code of the device 161 with ID1 is A indicating air conditioner, and the device management protocol is Echonet Lite described in Non-Patent Document 1. The device type code of the device 161 with ID2 is B indicating television, and the device management protocol is SEP (Smart Energy Profile) 2.0. The device type code of the device 161 of ID3 is C indicating a storage battery, and the device management protocol is KNX. The device type code of the device 161 of ID4 is D indicating a solar cell, and the device management protocol is Echonet Lite described in Non-Patent Document 1.

  The contents of items other than the device type code and device management protocol in the device management table shown in FIG. 7 are the same as those in the device management table shown in FIG.

  Referring to FIG. 5 again, next, the message generation / analysis processing bundle 11 outputs the ID table in which the ID and the device type code are extracted from the created device management table to the application 12 (step S30).

  FIG. 8 is a diagram showing an example of an ID table in the device management apparatus according to the embodiment of the present invention.

  Referring to FIG. 8, this ID table is a table that is output to application 12 by message generation / analysis processing bundle 11 in step S30 of the flowchart shown in FIG. 5, and shows the correspondence between IDs and device type codes.

  Specifically, in the ID table, the device type code of the device 161 of ID1 is A, the device type code of the device 161 of ID2 is B, the device type code of the device 161 of ID3 is C, and the ID4 The device type code of the device 161 is D.

  FIG. 9 is a diagram illustrating a sequence when the device management apparatus according to the embodiment of the present invention controls each device.

  The application 12 holds the ID notified from the message generation / analysis processing and transmission / reception processing bundle 11 and the type of the corresponding device 161, and creates the downlink information and processes the uplink information using the ID and the type of the corresponding device 161. To do.

  In addition, for example, the application 12 sends the ID of the device 161 that is the transmission destination of the downlink information to the message generation / analysis processing and transmission / reception processing bundle 11 in addition to the downlink information.

  The telegram generation / analysis process and transmission / reception process bundle 11 uses the address corresponding to the ID received from the application 12 as the destination of the downlink information, and performs the transmission process of the downlink information via the communication medium corresponding to the ID.

  Specifically, referring to FIG. 9, first, the application 12 outputs a device control command to the message generation / analysis processing bundle 11. This device control command includes an ID and control content. Here, the device control command includes an operation start for the device 161 with the device type code A of ID1 (step S41).

  Next, the message generation / analysis processing bundle 11 receives a device control command from the application 12, refers to the device management table, and checks the device management protocol of the device 161 to be controlled from the ID indicated by the device control command. Then, a message for the device management protocol including the control content indicated by the device control command is created (step S42).

  Next, the message generation / analysis processing bundle 11 outputs the created message and ID to the transmission / reception processing bundle 11 (step S43).

  Next, the transmission / reception processing bundle 11 receives the message and ID from the message generation / analysis processing bundle 11, refers to the device management table, and confirms the communication medium and address of the device 161 to be controlled from the ID (step S44). ).

  Next, the transmission / reception processing bundle 11 sets the transmission destination of the message received from the message generation / analysis processing bundle 11 as the confirmed address, and transmits it to the control target device 161 via the confirmed communication medium (step S45).

Next, the transmission / reception processing bundle 11 receives the response message from the device 161 (step S46), refers to the device management table, and searches for the corresponding ID from the communication medium and the transmission source address of the response message (step S46). S47).
Next, the transmission / reception processing bundle 11 outputs the received response message and the retrieved ID to the message generation / analysis processing bundle 11 (step S48).

  Next, the message generation / analysis processing bundle 11 receives the response message and the ID from the transmission / reception processing bundle 11, confirms the device management protocol from the ID, analyzes the response message based on the confirmed device management protocol, The control result of the device 161 to be controlled is acquired (step S49).

  Next, the message generation / analysis processing bundle 11 outputs the ID and the control result to the application 12. Here, the application 12 receives information indicating that the “operation start” of the device 161 with the device type code A of ID1 has been completed (step S50).

  FIG. 10 is a diagram showing a sequence when the device management apparatus according to the embodiment of the present invention receives a status notification from each device.

  With reference to FIG. 10, first, the transmission / reception processing bundle 11 receives a voluntary status notification message from the device 161 (step S71), refers to the device management table, and transmits the communication medium and transmission of the status notification message. The corresponding ID is searched from the original address (step S72).

  Next, when the corresponding ID is found, the transmission / reception processing bundle 11 outputs the received status notification message and the searched ID to the message generation / analysis processing bundle 11 (step S73).

  Next, the message generation / analysis processing bundle 11 receives the status notification message and the ID from the transmission / reception processing bundle 11, confirms the device management protocol from the ID, and analyzes the status notification message based on the confirmed device management protocol. Then, the notification content of the device 161 is acquired (step S74).

  Next, the message generation / analysis processing bundle 11 outputs the ID and the notification content to the application 12. Here, the application 12 receives information indicating that an abnormality has occurred in the device 161 with the device type code A of ID1 (step S75).

  FIG. 11 is a diagram showing another example of a sequence when the device management apparatus according to the embodiment of the present invention receives a status notification from each device.

  Referring to FIG. 11, first, the transmission / reception processing bundle 11 receives a voluntary status notification message from the device 161 (step S61), refers to the device management table, and transmits the communication medium and transmission of the status notification message. A corresponding ID is searched from the original address (step S62).

  Next, when the corresponding ID is not found, the transmission / reception processing bundle 11 updates the device management table by associating the communication medium and the transmission source address of the state notification message with the new ID (step S63).

  Next, the transmission / reception processing bundle 11 outputs the received status notification message and the new ID to the message generation / analysis processing bundle 11 (step S64).

  Next, the message generation / analysis processing bundle 11 receives the status notification message and ID from the transmission / reception processing bundle 11, analyzes the status notification message received from the transmission / reception processing bundle 11, and stores the device with the new ID in the device management table. The device type code 161 and the protocol type of 161 are added, and the notification content of the device 161 is acquired (step S65).

  Next, the message generation / analysis processing bundle 11 outputs the ID, device type code, and notification content to the application 12. Here, the application 12 receives information indicating that the device 161 having the device type code A of ID1 has started operation. Then, the application 12 updates the ID table (Step S66).

  FIG. 12 is a diagram showing a sequence when the device management apparatus according to the embodiment of the present invention receives a control command from each device.

  The message generation / analysis processing and transmission / reception processing bundle 11 sends the ID of the device 161 that is the source of the uplink information to the application 12 in addition to the uplink information.

  The application 12 processes the uplink information based on the ID received from the message generation / analysis process and the transmission / reception process bundle 11.

  Specifically, referring to FIG. 12, first, the transmission / reception processing bundle 11 receives a control message from the device 161 (step S81), refers to the device management table, and refers to the communication medium and transmission source of the control message. The corresponding ID is searched from the address (step S82).

  Next, when the corresponding ID is found, the transmission / reception processing bundle 11 outputs the received control message and the searched ID to the message generation / analysis processing bundle 11 (step S83).

  Next, the message generation / analysis processing bundle 11 receives the control message and the ID from the transmission / reception processing bundle 11, confirms the device management protocol from the ID, analyzes the control message based on the confirmed device management protocol, The control content commanded by the device 161 is acquired (step S84).

  Next, the message generation / analysis processing bundle 11 outputs the ID and the control content to the application 12. Here, the application 12 receives a “status notification request” from the device 161 with the device type code A of ID1 (step S85).

  Next, the application 12 outputs the ID of the device 161 that has issued the control command and the control result for the control command to the message generation / analysis processing bundle 11. Here, the application 12 outputs information indicating that the device management apparatus 101 is in the “normal state” to the device 161 with the device type code A of ID1 (step S86).

  Next, the message generation / analysis processing bundle 11 confirms the device management protocol of the instruction source device 161 from the ID received from the application 12, and creates a response message for the device management protocol including the control result (step S87). ).

  Next, the message generation / analysis processing bundle 11 outputs the created response message and ID to the transmission / reception processing bundle 11 (step S88).

  Next, the transmission / reception processing bundle 11 receives the response message and ID from the message generation / analysis processing bundle 11, refers to the device management table, and confirms the communication medium and address of the instruction source device 161 from the ID (step). S89).

  Next, the transmission / reception processing bundle 11 sets the destination of the response message received from the message generation / analysis processing bundle 11 as the confirmed address, and transmits it to the instruction source device 161 via the confirmed communication medium (step S90). .

  FIG. 13 is a diagram showing another example of a sequence when the device management apparatus according to the embodiment of the present invention receives a control command from each device.

  Referring to FIG. 13, first, the transmission / reception processing bundle 11 receives a control message from the device 161 (step S101), refers to the device management table, and responds from the communication medium and the transmission source address of the control message. The ID is searched (step S102).

  Next, when the corresponding ID is not found, the transmission / reception processing bundle 11 updates the device management table by associating the communication medium and the transmission source address of the status notification message with the new ID (step S103).

  Next, the transmission / reception processing bundle 11 outputs the received control message and the new ID to the message generation / analysis processing bundle 11 (step S104).

  Next, the message generation / analysis processing bundle 11 receives the control message and ID from the transmission / reception processing bundle 11, analyzes the control message received from the transmission / reception processing bundle 11, and stores the device 161 of the new ID in the device management table. The device type code and the protocol type are added, and the control message is analyzed based on the device management protocol obtained by the analysis, and the control content commanded by the device 161 is acquired (step S105).

  Next, the message generation / analysis processing bundle 11 outputs the ID, the device type code, and the control content to the application 12. Here, the application 12 receives a “status notification request” from the device 161 with the device type code A of ID1. Then, the application 12 updates the ID table (Step S106).

  Next, the application 12 outputs the ID of the device 161 that has issued the control command and the control result for the control command to the message generation / analysis processing bundle 11. Here, the application 12 outputs information indicating that the device management apparatus 101 is in “normal state” to the device 161 with the device type code A of ID1 (step S107).

  Next, the message generation / analysis processing bundle 11 confirms the device management protocol of the instruction source device 161 from the ID received from the application 12, and creates a response message for the device management protocol including the control result (step S108). ).

  Next, the message generation / analysis processing bundle 11 outputs the created response message and ID to the transmission / reception processing bundle 11 (step S109).

  Next, the transmission / reception processing bundle 11 receives the response message and ID from the message generation / analysis processing bundle 11, refers to the device management table, and confirms the communication medium and address of the instruction source device 161 from the ID (step). S110).

  Next, the transmission / reception processing bundle 11 sets the destination of the response message received from the message generation / analysis processing bundle 11 as the confirmed address, and transmits it to the instruction source device 161 via the confirmed communication medium (step S111). .

  FIG. 14 is a diagram showing a sequence when the device management apparatus according to the embodiment of the present invention sends a status notification to each device.

  Referring to FIG. 14, first, the application 12 outputs a status notification command to the message generation / analysis processing bundle 11. This state notification command includes, for example, that the device management apparatus 101 is in “abnormal state” (step S91).

  Next, the message generation / analysis processing bundle 11 receives a status notification command from the application 12, refers to the device management table, and is a message or message including the content of the status notification command, and is registered in the device management table. A message conforming to each protocol is created (step S92) and output to the transmission / reception processing bundle 11 (step S93).

  Next, the transmission / reception processing bundle 11 refers to the device management table, and multicasts the message received from the message generation / analysis processing bundle 11 to each device via each communication medium registered in the device management table (step). S94 and S95).

  Note that the device management table is not limited to a configuration including an ID, a device type code, a transmission medium, an address, and a device management protocol as shown in FIG. The configuration may not include any one or two of the code, the transmission medium, and the device management protocol.

  However, the configuration using the device management table including the device management protocol can absorb the difference in the device management protocol of each device 161 in the message generation / analysis processing and transmission / reception processing bundle 11. That is, the application 12 does not need to change the communication processing with the device 161 and the communication message creation processing according to the difference in the device management protocol.

  In addition, the device management apparatus 101 may be configured to store or acquire information of IDs set in advance in each device 161 by a user or the like, or may be configured to give an ID to each device 161 by itself. Also good.

  FIG. 15 is a diagram showing another example of the device management table in the device management apparatus according to the embodiment of the present invention. The contents of ID2 to ID4 shown in FIG. 15 are the same as those in the device management table shown in FIG.

  In the device management system 201, a plurality of devices 161 may have a common address. In other words, the correspondence relationship held by the message generation / analysis process and the transmission / reception process bundle 11, that is, the device management table includes one address and a plurality of types corresponding to one ID.

  Specifically, referring to FIG. 15, in the device management table, the device type code of the device 161 of ID1 is A indicating air conditioner and E indicating refrigerator, the transmission medium is Ethernet, and the address is IP according to IPv6. The address, specifically 2001 :: ff5f: 7535, and the device management protocol is Echonet Lite described in Non-Patent Document 1.

  That is, the transmission media, addresses, and device management protocols of the two devices 161 of ID1 are the same.

  In this case, in the operations shown in FIGS. 9, 10, and 12, the device type code is further input / output between the transmission / reception processing bundle 11 and the application 12, so that the transmission / reception processing bundle 11 and the application 12 Differences in types can be recognized.

  As described above, the device management apparatus 101 operates according to a plurality of hierarchized layers and manages a plurality of devices 161.

  More specifically, in the device management apparatus 101, the OS 21 transmits / receives a signal to / from the device 161 according to the first layer as a signal transmission / reception unit.

  The application 12 creates downlink information to be transmitted to the device 161 and processes uplink information received from the device 161 in accordance with the second layer higher than the first layer.

  The telegram generating / analyzing process and transmission / reception process bundle 11 performs transmission processing of downlink information to the device 161 and reception processing of uplink information from the device 161 via the OS 21 according to the second layer. In addition, the message generation / analysis processing and transmission / reception processing bundle 11 acquires and holds the correspondence between the ID assigned to the device 161 and the address of the device 161 according to the second layer, and notifies the application 12 of the ID. To do.

  The application 12 holds the ID notified from the telegram generation / analysis process and the transmission / reception process bundle 11, and creates downlink information and processes uplink information using the ID.

  By the way, in a device management system that manages a plurality of electrical devices by communicating with various electrical devices, when the transmission medium and communication protocol between the electrical devices differ for each electrical device, it is implemented in the device management apparatus. The management application needs to perform communication processing with an electrical device and create a communication message according to differences in transmission media and communication protocols. For example, in the technology described in Non-Patent Document 1, in each subnet configuring a domain, an address for realizing layer 2 communication in a transmission medium or an IP address is used as an identifier of a device uniquely identified in the subnet. . This complicates application processing and procedures in the device management apparatus, and increases application development costs.

  On the other hand, in the device management apparatus according to the embodiment of the present invention, the application 12 creates downlink information to be transmitted to the device 161 and processes the uplink information received from the device 161. The telegram generation / analysis process and transmission / reception process bundle 11 performs a process of transmitting downlink information to the device 161 and a process of receiving uplink information from the device 161. The message generation / analysis processing and transmission / reception processing bundle 11 acquires and holds the correspondence between the ID assigned to the device 161 and the address of the device 161, and notifies the application 12 of the ID. Then, the application 12 holds the ID notified from the message generation / analysis processing / transmission / reception processing bundle 11, and creates downlink information and processes uplink information using the ID.

  With such a configuration, a difference in address system in communication with each device 161 can be absorbed in the message generation / analysis process and the transmission / reception process bundle 11. That is, the application 12 does not need to change processing according to the difference in the address system in communication with the device 161. Therefore, in the device management apparatus according to the embodiment of the present invention, it is possible to simplify the management application in a configuration for managing a plurality of devices. Specifically, it is possible to prevent application processing and procedures in the device management apparatus 101 from becoming complicated, and to prevent an application development cost from increasing.

  In the device management apparatus according to the embodiment of the present invention, the message generation / analysis processing and transmission / reception processing bundle 11 acquires the correspondence relationship between the ID of the device 161, the address of the device 161, and the type of the device 161. The ID and the corresponding type are notified to the application 12. The application 12 holds the ID notified from the telegram generation / analysis process and the transmission / reception process bundle 11 and the corresponding type, and uses at least the ID and the corresponding type to generate downlink information and process uplink information. Do one.

  Thus, the application 12 can perform processing according to the type of the device 161 by the configuration in which the type of the device 161 is acquired. For example, the application 12 can appropriately change the content of the downlink information to the device 161 according to the type of the device 161.

  In the device management apparatus according to the embodiment of the present invention, the correspondence relationship includes one address and a plurality of types corresponding to one ID.

  With such a configuration, for example, by transmitting downlink information with one address as a destination, the downlink information can be notified to a plurality of devices 161 having the address.

  In the device management apparatus according to the embodiment of the present invention, the message generation / analysis processing and transmission / reception processing bundle 11 corresponds to the ID of the device 161, the address of the device 161, and the communication medium in communication with the device 161. Obtain and maintain relationships.

  With such a configuration, differences in communication media such as transmission media and communication protocols between the devices 161 can be absorbed in the message generation / analysis processing and transmission / reception processing bundle 11. That is, the application 12 does not need to change the communication processing with the device 161 and the communication message creation processing according to differences in transmission media and communication protocols. Therefore, it is possible to further simplify the application in the device management apparatus 101.

  In the device management apparatus according to the embodiment of the present invention, the application 12 sends the ID of the device 161 that is the transmission destination of the downlink information to the message generation / analysis processing and transmission / reception processing bundle 11 in addition to the downlink information. Then, the telegram generation / analysis process and the transmission / reception process bundle 11 performs the downlink information transmission process via the communication medium corresponding to the ID, with the address corresponding to the ID received from the application 12 as the destination of the downlink information.

  With such a configuration, the application 12 only notifies the identifier of the device 161 to the message generation / analysis processing / transmission / reception processing bundle 11 without performing processing corresponding to the communication medium in communication with the device 161. Downlink information can be transmitted to the device 161. Therefore, it is possible to further simplify the application in the device management apparatus 101.

  In the device management apparatus according to the embodiment of the present invention, the application 12 sends the ID of the device 161 that is the transmission destination of the downlink information to the message generation / analysis processing and transmission / reception processing bundle 11 in addition to the downlink information. Then, the message generation / analysis processing and transmission / reception processing bundle 11 performs the transmission processing of the downlink information with the address corresponding to the ID received from the application 12 as the destination.

  With such a configuration, the message generation / analysis processing and transmission / reception processing bundle 11 and the application 12 can easily identify the target device 161 using the identifier of the device 161 and transmit the downlink information to the device 161. Can be performed.

  Further, in the device management apparatus according to the embodiment of the present invention, the message generation / analysis processing and transmission / reception processing bundle 11 sends the ID of the device 161 that is the transmission source of uplink information to the application 12 in addition to the uplink information. Then, the application 12 processes the uplink information based on the ID received from the message generation / analysis process and the transmission / reception process bundle 11.

  With such a configuration, the telegram generation / analysis processing and transmission / reception processing bundle 11 and the application 12 can easily identify the target device 161 using the identifier of the device 161 and receive the uplink information from the device 161. Can be performed.

  In the device management apparatus according to the embodiment of the present invention, the application 12 is configured to perform transmission of downlink information to the device 161 and processing of uplink information received from the device 161. However, the present invention is limited to this. It is not a thing. The application 12 may be configured to perform one of transmission of downlink information and processing of uplink information.

  The above embodiment should be considered as illustrative in all points and not restrictive. The scope of the present invention is defined by the terms of the claims, rather than the description above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims.

31 WAN Interface Unit 32 Wireless LAN Interface Unit 33 ZigBee Interface Unit 34 Wired LAN Interface Unit 35 Serial Interface Unit 36 PLC Interface Unit 101 Device Management Device 161 Device 201 Device Management System

Claims (9)

A device management apparatus capable of managing a plurality of devices,
An information processing unit for performing at least one of creation of downlink information to be transmitted to the device and processing of uplink information received from the device;
A communication processing unit for performing transmission processing of the downlink information to the device and reception processing of the uplink information from the device;
A device information acquisition unit for acquiring and holding a correspondence relationship between the identifier assigned to the device and the address of the device, and notifying the information processing unit of the identifier,
The information processing unit holds the identifier notified from the device information acquisition unit, and performs at least one of creation of the downlink information and processing of the uplink information using the identifier. The device information acquisition unit acquires and holds a correspondence relationship between the device identifier, the device address, and the device type, and notifies the information processing unit of the identifier and the corresponding type,
The information processing unit holds the identifier and the corresponding type notified from the device information acquisition unit, and uses at least one of the creation of the downlink information and the processing of the uplink information using the identifier and the corresponding type The device management apparatus according to claim 1, wherein:   The device management apparatus according to claim 2, wherein the correspondence relationship includes one address and a plurality of the types corresponding to one identifier.   4. The device information acquisition unit according to claim 1, wherein the device information acquisition unit acquires and holds a correspondence relationship between the device identifier, the device address, and a communication medium in communication with the device. 5. The device management apparatus described in 1. The information processing unit sends an identifier of the device to which the downlink information is transmitted in addition to the downlink information to the communication processing unit,
The communication processing unit performs transmission processing of the downlink information via the communication medium corresponding to the identifier, with the address corresponding to the identifier received from the information processing unit as a destination of the downlink information. 4. The device management apparatus according to 4. The information processing unit sends an identifier of the device to which the downlink information is transmitted in addition to the downlink information to the communication processing unit,
The device management apparatus according to any one of claims 1 to 5, wherein the communication processing unit performs the downlink information transmission process with the address corresponding to the identifier received from the information processing unit as a destination. . The communication processing unit sends an identifier of the device that is the transmission source of the uplink information to the information processing unit in addition to the uplink information,
The device management apparatus according to claim 1, wherein the information processing unit processes the uplink information based on the identifier received from the communication processing unit. A device management method in a device management apparatus capable of managing a plurality of devices,
Acquiring and holding a correspondence relationship between the identifier assigned to the device and the address of the device, and notifying the identifier;
A device management method comprising: holding the notified identifier and performing at least one of creation of downlink information to be transmitted to the device and processing of uplink information received from the device using the identifier. A device management program used in a device management apparatus capable of managing a plurality of devices,
Acquiring and holding a correspondence relationship between the identifier assigned to the device and the address of the device, and notifying the identifier;
A device for holding the notified identifier and performing at least one of creation of downlink information to be transmitted to the device and processing of uplink information received from the device using the identifier Management program.

Images