JP2008033618A - Manager device, control method, and control program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a technology for easily operating devices in cooperation according to a user's preference. <P>SOLUTION: A manager device stores device information including events which are detectable state changes, and action which is executable operation of every device. The manager device outputs events and action of every device to prompt the user to select the event triggering interlocking action, and action to be carried out when the event occurs, and stores a selected combination as interlocking operation information. When the device outputs information for notifying the detected event, the manager device reads the action corresponding to the event indicated in the information, and outputs information for instructing the execution of the action, to the device to carry out the action. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a technique for controlling a device connected to a network.

  Some devices such as air conditioners, bath water heaters, and lighting have a communication function. By having a communication function, it is possible to acquire information, control information, transmit information, and the like via a network.

  Such a device can operate a plurality of devices in conjunction with each other, for example, lighting is triggered by opening a front door. As a technique of such interlocking operation, for example, there is Patent Document 1. In this technology, the control information management server holds information necessary for setting the assumed linked operation in advance, and the linked control device that controls the device in the home from the control information management server, Information for interlocking operation of the device to be controlled is acquired and controlled according to the information.

JP-A-2005-102156

  However, in the above-described prior art, since the combination of devices to be linked is determined in advance, the linkage operation cannot be customized and used according to the user's preference.

  The present invention has been made in view of such circumstances, and an object of the present invention is to provide a technique that enables a plurality of devices to operate in conjunction with each other according to user preferences.

  The present invention has been made to achieve the above object, and is a manager device connected to a plurality of devices having at least one function of state change detection and execution of an instructed operation. Device information storage means for storing each detectable change in state and executable operation information, detectable state change for each device read from the device information storage means, and executable for each device Output means for outputting various operations, input means, accepting means for receiving a state change detected by the device and an operation to be executed by the device when the state change is detected, input from the input means Linked operation information storage means for storing the state change detected by the received device in association with the operation to be performed by the device when the state change is detected, and the state change detected by the device. State change monitoring means for monitoring the state, and when a state change is detected, the operation corresponding to the detected state change is read from the linked operation information storage means, and information for instructing the device to execute the operation And a control means for outputting.

  According to the technology of the present invention, it is possible to operate a plurality of devices in conjunction with each other according to user preferences.

  Hereinafter, an embodiment will be described in detail with reference to the drawings.

<First Embodiment>
First, the first embodiment will be described.

  A system configuration example of the first embodiment will be described with reference to FIG.

  In FIG. 1, the system according to the present embodiment includes a manager apparatus 101, a client terminal 102, a plurality of devices 103, and the like. The manager device 101, the client terminal 102, the device 103, and the like are connected via a communication network 104.

  The device 103 is a device having a communication function, such as a clock, an interphone, a sensor, a camera, lighting, a television, a recording device, a list monitor, and the like. Hereinafter, when the devices 103 are specifically distinguished and described, for example, “device 103a” is given a reference numeral. In the example of FIG. 1, each of the devices 103a to 103g is a clock, an interphone, a brightness sensor, a photographing camera, a lighting, a recording device, and a list monitor. Here, the wrist monitor is for attaching to the wrist of the user, and vibrates when a predetermined signal is input.

  The client terminal 102 is an information processing apparatus such as a PC (Personal Computer), a PDA (Personal Digital Assistant), or an STB (Set Top Box). The user uses the client terminal 102 to select the device 103 to be operated in conjunction.

  The manager apparatus 101 is an information processing apparatus for controlling each device 103 according to settings by the user.

  The communication network 104 is an arbitrary network such as a LAN (Local Area Network).

  Here, the outline of the system will be briefly described.

  Each device 103 has at least one of a notification function that detects and notifies a change in state, and an execution function that changes its own state in accordance with the notified command. Here, the state change is, for example, that a predetermined date and time has been reached if the device 103 is a clock, a visitor pressed a button or the like if the device 103 is an interphone, and a device that is a brightness sensor. For example, the brightness is equal to or higher than a predetermined threshold. In addition, changing the state of itself means, for example, starting or ending shooting if the device 103 is a camera, turning on or off if the device 103 is illumination, and turning on or off if the device 103 is a television. On / off, recording is started or ended if the device 103 is a recording device, and vibration is performed if the device 103 is a list monitor.

  Here, the detected state change as described above is called an event, and changing its own state is called an action.

  The manager apparatus 101 stores events that can be detected by each device 103, actions that can be instructed to each device 103, and the like in a storage device, and transmits them to the client terminal 102. The client terminal 102 outputs an event that can be detected by each device 103, an executable action, and the like to an output device such as a display.

  The user checks the event that can be detected by each device 103 and the executable action that are output to the output device of the client terminal 102, and among the output events and actions, the event and the event have occurred. Specify the action to be executed. The client terminal 102 transmits the specified event and action to the manager device 101. The manager device 101 stores the received event, action, and the like in the storage device in association with each other.

  The manager apparatus 101 monitors notification information output from each device 103 to notify the occurrence of an event. When detecting the notification information, the manager device 101 selects a combination including the detected event from the combination of the event and the action transmitted from the client terminal 102 by the above operation from the storage device, and executes the action of the selected combination. The instruction information to be instructed is output to the device 103 that should execute the action.

  The device 103 to which the instruction information is input executes an action according to the instruction.

  As described above, the system according to the present embodiment stores “events” that can be detected and “actions” that can be executed in advance for each device, and executes “events” that are triggers to the user and the triggers thereof. "Action" to be selected. As a result, it is possible to customize the interlocking operation according to the user's preference, and it is possible to flexibly cope with the introduction of new devices and system expansion.

  In addition, the “event” and “action” parts that are difficult to predict in advance in the settings for linking devices are replaced with “events” and “actions”, and the “event” is given to the user. And “Action” are selected, it becomes easy to set the linked operation.

  Note that the type of the device 103 is not particularly limited, and has only to have a communication function and at least one of an event detection function and an action execution function.

  In the system of the present embodiment, the number of client terminals 102 and devices 103 is not limited to that shown in FIG. Also, a plurality of devices may have the functions of the manager device 101 described in detail below.

  Hereinafter, the system of this embodiment will be described in detail.

  First, a configuration example of each device will be described.

  A configuration example of the manager device 101 will be described with reference to FIG.

  2, the manager device 101 includes a CPU (Central Processing Unit) 201, a boot ROM (Read Only Memory) 202, a peripheral controller 203, a network interface 204, a volatile storage device 205, a nonvolatile storage device 206, and the like.

  The nonvolatile storage device 206 includes a device information table 261, a linked operation information table 262, a device property manager program (“PG” in the drawing, the same applies hereinafter) 263, an event packet monitor program 264, and the like. The device information table 261 stores identification information of each device 103, detectable events, executable actions, and the like. The linked operation information table 262 includes, among the devices 103 in the device information table 261, the device 103 that detects the occurrence of an event, the action that is performed when the event occurrence is detected by the device 103, and the device 103 that executes the action. And so on. Details of these tables will be described later. The device property manager program 263 is for realizing an interlock setting client 211 described later. The event packet monitor program 264 is for realizing the event action manager 212 described later.

  The CPU 201 executes the device property manager program 263 and the event packet monitor program 264, thereby realizing the linkage setting client 211, the event action manager 212, and the like.

  The link setting client 211 includes a setting receiving unit 221, a device information table setting unit 222, a link operation information table setting unit 223, and the like. The setting reception unit 221 receives an update of information in the device information table 261 and the interlocking operation information table 262, and the like. The device information table setting unit 222 updates information in the device information table 261 and the like. The interlocking operation information table setting unit 223 stores the device 103 specified by the user in association with the event detecting device 103 and the device 103 that performs an action when the event is detected by the device 103 in the interlocking operation information table 262. To do.

  The event action manager 212 includes an event monitoring unit 231 and an action instruction unit 232. The event monitoring unit 231 monitors notification information that notifies the occurrence of an event output from the device 103. When the action instruction unit 232 detects notification information for notifying the occurrence of an event, the action instruction unit 232 reads an action corresponding to the event that has occurred from the linked operation information table 262 and outputs instruction information for executing the read action to the device 103.

  Next, an example of the device information table 261 and the linked operation information table 262 will be described.

  First, an example of the device information table 261 will be described with reference to FIG.

  3, the device information table 261 includes a device name 301, an address 302, an event name 303, an event packet 304, an action name 305, an action packet 306, and the like. The device name 301, address 302, event name 303, event packet 304, action name 305, action packet 306, etc. in each row are associated with each other.

  The device name 301 is the name of a device that detects the occurrence of an event or a device that executes an action. The address 302 is a network address assigned to the device with the corresponding device name 301. The event name 303 is the name of an event detected by the device 103 with the corresponding device name 301. The event packet 304 is the content of a packet that is output when the device 103 with the corresponding device name 301 detects the occurrence of the event with the corresponding event name 303. In FIG. 3, “?” Included in “888000 ?? 00 ???? B07341”, for example, of the event packet 304 means a portion that changes for each packet. Become. The action name 305 is an action name that can be instructed to the corresponding device name 301 via the network. The action packet 306 is the content of a packet for instructing execution of the action with the corresponding action name 305.

  Specifically, for example, in the example of FIG. 3, when the device 103 with the device name 301 “illuminance sensor” having the address 302 “192.168.0.XXX” detects the event name 303 “bright”, the event This means that the packet 304 “888000 ?? 00 ???? B07341” is output. Also, for example, in the example of FIG. 3, when the action packet 306 “/ right? Power = 01” is input to the device 103 with the device name 301 “lighting” having the address 302 “192.168.0.Y1” , Action name 305 “power ON” is executed.

  In FIG. 3, the event name 303 and the event packet 304 with “-” indicate that the corresponding device name 301 and device with the address 302 do not have an event detection function. In addition, when the action name 305 and the action packet 306 are “−”, the corresponding device name 301 and device with the address 302 do not have an action execution function. In FIG. 3, an address 302 of “−” indicates that a network address is not set for the device 103 of the corresponding device name 301.

  In the example of FIG. 3, each device has only one of the event detection function and the action execution function. However, the device is not limited to this, and one device has Both the event detection function and the action execution function may be provided. Specifically, for example, the device 103d that is a camera may have an illuminance sensor function that is an event detection function as well as a shooting function that is an action execution function.

  Here, it is assumed that the device name table 301, the event name 303, the event packet 304, the action name 305, the action packet 306, and the like are stored in advance in the device information table 261 at the time of shipment of the manager device 101. Thus, the address 302 of each device 103 is stored, but the user himself stores, changes, deletes, etc. the device name 301, event name 303, event packet 304, action name 305, action packet 306, etc. Also good.

  Further, when the event packet 304, the action packet 306, and the like are different even in the device 103 having the same device name 301 depending on the manufacturer of the device 103, the manufacturer name and model number of each device 103 are further associated with the device information table 261. It may be stored.

  Next, an example of the interlocking operation information table 262 will be described with reference to FIG.

  In FIG. 4, the linked operation information table 262 includes a detection device name 401, an event name 402, an event detection address 403, an event packet 404, an execution device 405, an action name 406, an action execution address 407, an action packet 408, and the like. The detection device name 401, the event name 402, the event detection address 403, the event packet 404, the execution device 405, the action name 406, the action execution address 407, the action packet 408, etc. in each row are associated with each other.

  The detection device name 401 is a name of a device that detects occurrence of an event. The event name 402 is an event name detected by the device having the corresponding detection device name 401. The event detection address 403 describes the network address of the device with the corresponding detection device name 401. The event packet 404 is the content of a packet that is output when the device with the corresponding detection device name 401 detects an event. Here, in the example of FIG. 4, for example, “?” Such as the event packet 404 “888000 ?? 00 ???? B07341” indicates a portion that changes for each packet, and is treated as a don't care when compared. The execution device 405 is the device name of the device 103 that instructs execution of an action when the occurrence of the event with the corresponding event name 402 is detected by the corresponding detection device name 401. The action name 406 is an action name to be executed by the corresponding execution device 405 when an event with the corresponding event name 402 occurs in the corresponding detection device name 401. The action execution address 407 is a network address of the corresponding execution device 405. The action packet 408 is the content of a packet for causing the corresponding execution device 405 to execute an action.

  Specifically, in the example of FIG. 4, for example, the detection device name 401 “illuminance sensor” of the event detection address 403 “192.168.0.XXX” detects the event with the event name 402 “bright”. When the event packet 404 “888000 ?? 00 ???? B07341” is output, the action name 406 “Power ON” is assigned to the execution device 405 “lighting” of the action execution address 407 “192.168.0.Y1”. The action packet 408 “/ right? Power = 01” for executing “” is output.

  In the example of FIG. 4, only the device whose detection device name 401 is “illuminance sensor” is shown, but the device 103 with which the operation is associated in the linked operation information table 262 is not limited to this. For example, when the detection device name 401 “interphone” detects the event name 402 “visitor”, the execution device name 405 “list monitor” may execute the action name 406 “power ON”.

  Moreover, although the example of FIG. 4 shows an example in which one action is executed for one event occurrence detection, the present invention is not limited to this. For example, a plurality of actions may be executed for one event occurrence detection, or one or a plurality of actions may be executed for a plurality of event occurrence detections. Here, when an action is executed with a plurality of event occurrences as triggers, the detection conditions for the plurality of event occurrences may be arbitrary. For example, even if another event occurs within a predetermined time from the first event occurrence. Good.

  Next, a configuration example of the device 103 having an event detection function will be described with reference to FIG. FIG. 5 shows an example in which the device 103 is an illuminance sensor (device 103c). Since the device 103c is the same as the network-compatible sensor of the prior art, only functions related to the system of this embodiment will be described here, and other descriptions will be omitted.

  In FIG. 5, the device 103c includes a sensor circuit unit 501, a battery 502, and the like. The sensor circuit unit 501 includes a network interface 511, a sensor unit 512, a microcomputer 513, and the like.

  The network interface 511 is connected to the microcomputer 513. The sensor unit 512 is connected to the microcomputer 513. The battery 502 is connected to the sensor circuit unit 501.

  The network interface 511 is connected to the communication network 104.

  The microcomputer 513 determines “bright” or “dark” from the value read from the sensor unit 512, and outputs notification information for notifying the determination result via the network interface 511. The destination of the notification information may be the manager device 101 or may be output by broadcast or the like. In order to determine “bright”, “dark”, or the like, the microcomputer 513 determines, for example, whether or not the value read from the sensor unit 512 is equal to or greater than a predetermined threshold. Further, the microcomputer 513 may not only notify the occurrence of an event spontaneously, but also may transmit a value read from the sensor unit 512 when receiving an access from another device such as the manager device 101 or the client terminal 102. . The protocol of the signal to be transmitted here is not particularly limited, and may be a known common format such as ECHONET.

  A function of detecting an event occurrence corresponding to the sensor unit 512, the microcomputer 513, and the like and a function of outputting information notifying the occurrence of an event applicable to the microcomputer 513 of each device 103 are included in one device. A plurality of different devices may be dispersed.

  Next, a configuration example of the device 103 having an action execution function will be described with reference to FIG. FIG. 6 shows an example in which the device 103 is illumination (device 103e). Since the device 103e is the same as the network-compatible lighting in the prior art, only functions related to the system of this embodiment will be described here, and other descriptions will be omitted.

  In FIG. 6, the device 103e includes a network interface 601, a specific device 602, a control unit 603, and the like.

  The network interface 601 is connected to the communication network 104. The unique device 602 is a dedicated device included in each of the devices 103. Specifically, for example, the unique device 602 when the device 103 is illumination is a light bulb or the like. Further, the unique device 602 in the case where the device 103 is a recording device is a device that writes data to a medium, a power source, and the like.

  The control unit 603 includes a CPU 611, a RAM (Random Access Memory) 612, a ROM 613, a peripheral controller 614, and the like. The CPU 611 realizes a function of instructing the specific device 602 to execute an action indicated by the received instruction information by executing a program (not shown).

  The protocol for causing the specific device 602 to execute an action is not particularly limited, and may be any protocol such as HTTP (Hypertext Transfer Protocol), DLNA (Digital Living Network Alliance) guidelines, and the like.

  Each device 103 may include a function for instructing the specific device 602 to execute an action according to the received instruction information, and a specific device 602 for executing an action according to the instruction. A plurality of different devices may be dispersed.

  Next, an operation example will be described.

  First, an example of an operation for registering information necessary for the linked operation in the device information table 261 and the linked operation information table 262 will be described with reference to FIG.

  As described above, here, the information in the device information table 261 includes the device name 301, the event name 303, the event packet 304, the action name 305, the action packet 306, and the like in advance when the manager device 101 is shipped. It is assumed that the address 302 of each device 103 is stored by an operation described later. In the example of FIG. 7, an operation example in which the user registers an address or the like in the device information table 261 after shipment or the like will be described. In the example of FIG. 7, an operation example in which information in the interlocking operation information table 262 is stored by the user will be described.

  When the user wants to update information in the device information table 261 or the linked operation information table 262, the user instructs information registration using an input device (not shown) such as the client terminal 102. The client terminal 102 transmits an information registration start request to the manager device 101.

  When the information registration start request is received, the setting reception unit 221 of the manager device 101 is activated. The setting reception unit 221 receives an instruction as to whether to update the device information table 261 or to update the interlocking operation information table 262 (S701). For this purpose, the setting reception unit 221 transmits information for receiving specification of the table to be updated to the client terminal 102. The client terminal 102 outputs the information to an output device such as a display by a browser or the like, and accepts input of information specifying a table to be updated. The user uses the input device of the client terminal 102 to instruct whether to update the device information table 261 or update the interlocking operation information table 262. The client terminal 102 transmits the instructed information to the manager device 101.

  The setting reception unit 221 determines whether the instruction received in S701 is an update of the device information table 261 or the like (S702).

  If the received instruction is an update of the device information table 261 or the like as a result of the determination in S702, the setting reception unit 221 activates the device information table setting unit 222.

  The device information table setting unit 222 receives information for updating information in the device information table 261 (S703), and updates the device information table 261 according to the received information (S704). Therefore, for example, the device information table setting unit 222 transmits request reception information for receiving input of information stored in the device information table 261 to the client terminal 102. The client terminal 102 outputs the received request acceptance information to an output device (not shown) and accepts input of information from the user.

  Here, FIG. 8 shows an example of a screen output to a display or the like in order to accept input of information for updating the device information table 261 or the like. In FIG. 8, a screen 801 is for accepting input of information stored in the device information table 261. A screen 801 includes a region 811, a region 812, a region 813, a region 814, a region 815, a region 816, a region 821, a region 822, a region 823, a region 824, and the like.

  Areas 811 to 816 are areas for changing device information already stored in the device information table 261. An area 821 to an area 824 are areas for deleting device information already stored in the device information table 261.

  An area 811 is used to detect the occurrence of an event or specify the name of a device that executes an action. An area 812 is for designating a network address assigned to the device designated in the area 811. An area 813 is used to specify the name of an event that can be detected by the device specified in the area 811. The area 814 is for designating the contents of a packet that is output when the device designated in the area 811 detects the event designated in the area 813. An area 815 is used to specify the name of an action that can be executed by the device specified in the area 811. An area 816 is for designating the content of a packet for instructing execution of the action designated in the area 815.

  An area 821 is an area for displaying information on events already stored in the device information table 261. The area 823 displays a check box for instructing deletion of information related to the event displayed in the area 821. An area 822 is for displaying information on actions already stored in the linked operation information table 262. The area 824 is for displaying a check box for instructing deletion of information related to the action displayed in the area 822.

  The device name displayed in the area 811 is the device name of each row when the device name 301 is already stored in the device information table 261. The event names displayed in the area 813 are action names and action packets when the device information table 261 already stores executable actions of the device specified in the area 811.

  For example, when a new address of each device is registered in the device information table 261, the device information table setting unit 222 is already stored in the device information table 261 in each of the area 811, the area 813, and the area 815 of the screen 801. Each of the device name, event name, and action name may be selected by pull-down or the like. Here, the device name, event name, and action name that can be selected by pull-down or the like are those read by the device information table setting unit 222 from the device name 301, event name 303, and action name 305 rows of the device information table 261. is there. The user sets an address by specifying at least one of a device name, an event name, and an action name by pulling down at least one of the region 811, the region 813, and the region 815 using an input device. Identify the device. Further, the user uses the input device of the client terminal 102 to input an address in the area 812 and presses a button 831 to instruct registration. The client terminal 102 transmits information for specifying a device such as a device name, an event name, and an action name and an address input in the area 812 to the manager apparatus 101 as update information of the device information table 261. The device information table setting unit 222 selects a device name 301, an event name 303, and an action name 304 in each row of the device information table 261 that match the received device name, event name, action name, etc., and selects the selected row. The received address is stored in the address 302.

  When deleting information related to an event already stored in the device information table 261, the device information table setting unit 222 reads the event name 303, the event packet 304, and the like of each row of the device information table 261, and sends them to the client terminal 102. Information for displaying the read event name 303, event packet 304, etc. in the area 821 is transmitted. The user uses the input device of the client terminal 102 to check a check box of information related to an event to be deleted in the area 823 and then presses a button 832 to instruct deletion. The client terminal 102 transmits a deletion request including an event name, event packet, and the like instructed to be deleted to the manager device 101. The device information table setting unit 222 selects the event name 303, event packet 304, etc. of each row of the device information table 261 that matches the event name, event packet, etc. included in the received information deletion request, and selects the selected row. Is deleted.

  As described above, the information in the device information table 261 is stored in advance at the time of shipment. When an operator or the like registers information in the device information table 261 before shipment or the like, input may be received on the screen as shown in FIG. 8 as an example. In this case, the device name, event name, event packet, action name, action packet, and the like in the areas 811 and 813 to 816 of the screen 801 may be input by free description. When a general user updates the device information table 261, etc., as in the case of the worker described above, the device name, event name, event packet, action name in the areas 811 and 813 to 816 on the screen 801 are displayed. The action packet or the like may be input by free description. The device information table setting unit 222 converts the information input in the area 811, the area 812, the area 813, the area 814, and the area 815 into device names 301, addresses 302, event names 303, event packets corresponding to each other in the device information table 261. 304, an action name 305, an action packet 306, and the like are additionally stored.

  Further, as described above, even when the device name is the same, the event packet 304, the action packet 306, and the like differ depending on the manufacturer, and the device information table 261 is further associated with the manufacturer name, the model number, and the like. The manufacturer name, model number, and the like may be further included in a screen 801 showing an example.

  In FIG. 7, the device information table setting unit 222 performs the same operation as described above on information related to a device when an update or the like for another device is instructed.

  On the other hand, if the received instruction is not an update of the device information table 261 or the like as a result of the determination in S702, the setting reception unit 221 determines whether or not the instruction received in S701 is an update of the interlocking operation information table 262 or the like ( S705).

  If the received instruction is not an update of the interlocking operation information table 262 or the like as a result of the determination in S705, the setting reception unit 221 performs an error process (S706) and ends the process.

  As a result of the determination in S <b> 705, when the received instruction is an update of the linked operation information table 262 or the like, the setting receiving unit 221 activates the linked operation information table setting unit 223.

  The linked operation information table setting unit 223 reads the device information table 261 from the nonvolatile storage device 206 (S707), and transmits request acceptance information including the read device information table 261 and the like to the client terminal 102 that has transmitted the update instruction. (S708). The client terminal 102 outputs the received request acceptance information to the output device.

  Here, FIG. 9 shows an example of a screen when request acceptance information is output to the display. In FIG. 9, a screen 901 has areas 911 to 916, an area 931, and the like.

  Areas 911 to 916 are for instructing linked operation information to be added to the linked operation information table 262. An area 931 is for instructing deletion of the linked operation information already stored in the linked operation information table 262.

  First, the region 911 to the region 916 will be described.

  Areas 911 to 913 are for receiving designation of an event and a device that detects the event. Specifically, the area 911 receives a device name, the area 912 receives an address, and the area 913 receives an event designation.

  An area 911 is for accepting designation of a device name for detecting an event. For example, the linked operation information table setting unit 223 reads the device name 301 whose corresponding event name 303 is not “−” from the device information table 261, and sets information for enabling selection of the read device name by, for example, pull-down. Output in request reception information. Here, when an address has already been specified in the area 912 at the time of pulling down the area 911, the linked operation information table setting unit 223 reads the address that matches the specified address from the device information table 261. The device name 301 associated with 302 may be read, and information for displaying the read device name 301 may be included in the request acceptance information and output. Also, when an event name is already specified in the area 913 at the time of pulling down the area 911, the linked operation information table setting unit 223 reads the event name that matches the specified event name from the device information table 261. The device name 301 associated with 303 may be read out, and information for enabling selection of the read device name 301 by, for example, pull-down may be included in the request reception information and output.

  An area 912 is for receiving designation of an address of a device that detects an event. The linked operation information table setting unit 223 reads the address 302 in which the corresponding event name 303 is not “−” from the device information table 261, and uses information for enabling selection of the read address by pull-down or the like as request reception information. Including the output. Here, when the device name is already specified in the area 911 at the time of pulling down the area 912, the linked operation information table setting unit 223 matches the specified device name from the device information table 261. The address 302 associated with the device name 301 to be read may be read, and information for displaying the read address 302 may be included in the request acceptance information and output. Also, when an event name has already been specified in the area 913 at the time of pulling down the area 912, the linked operation information table setting unit 223 reads the event name that matches the specified event name from the device information table 261. The address 302 associated with 303 may be read, and information for enabling selection of the read address 302 by pull-down or the like may be included in the request acceptance information and output.

  An area 913 is for receiving designation of an event that can be detected by the device. The linked operation information table setting unit 223 reads an event name 303 that is not “−” from the device information table 261, and outputs information for enabling selection of the read event name by, for example, pull-down or the like. . Here, when the device name is already specified in the area 911 at the time of pulling down the area 913, the linked operation information table setting unit 223 matches the specified device name from the device information table 261. The event name 303 associated with the device name 301 to be read may be read, and information for displaying the read event name 303 may be included in the request reception information and output. Further, when an address is already specified in the area 912 at the time of pulling down the area 913, the linked operation information table setting unit 223 corresponds to the address 302 that matches the specified address from the device information table 261. The attached event name 303 may be read, and information for enabling selection of the read event name by pull-down or the like may be included in the request reception information and output.

  The areas 914 to 916 are used to receive an action to be executed and a designation of a device or the like that executes the action when the event specified by the device specified in the areas 911 to 913 is detected. Specifically, the area 914 is a device, the area 915 is an address, and the area 916 is an area for receiving an action designation.

  An area 914 is for accepting designation of a device name for executing an action. For example, the linked operation information table setting unit 223 reads out the device name 301 whose corresponding action name 305 is not “−” from the device information table 261, and sets information for enabling the read device name to be selected by, for example, pull-down. Output in request reception information. Here, when an address is already specified in the area 915 at the time of pulling down the area 914 or the like, the linked operation information table setting unit 223 reads an address that matches the specified address from the device information table 261. The device name 301 associated with 302 may be read, and information for displaying the read device name 301 may be included in the request acceptance information and output. Also, when an action name has already been specified in the area 916 at the time of pulling down the area 914, the linked operation information table setting unit 223 reads the action name that matches the specified action name from the device information table 261. The device name 301 associated with 305 may be read out, and information for enabling selection of the read device name 301 by, for example, pull-down may be included in the request reception information and output.

  An area 915 is for receiving designation of an address of a device that executes an action. The linked operation information table setting unit 223 reads the address 302 whose corresponding action name 305 is not “−” from the device information table 261, and uses the information for enabling selection of the read address by pull-down or the like as request acceptance information. Including the output. Here, when the device name is already specified in the area 914 at the time of pulling down the area 915, the linked operation information table setting unit 223 matches the specified device name from the device information table 261. The address 302 associated with the device name 301 to be read may be read, and information for displaying the read address 302 may be included in the request acceptance information and output. Also, when an action name has already been specified in the area 916 at the time of pulling down the area 915, the linked operation information table setting unit 223 reads the action name that matches the specified action name from the device information table 261. Address 302 associated with 305 may be read, and information for enabling selection of read address 302 by pull-down or the like may be included in the request reception information and output.

  An area 916 is for accepting designation of an action to be executed by the device. The interlocking operation information table setting unit 223 reads the action name 305 that is not “−” from the device information table 261, and outputs information for enabling selection of the read action name by, for example, pull-down or the like. . Here, when a device name has already been specified in the area 914 at the time of pulling down the area 916, the linked operation information table setting unit 223 matches the specified device name from the device information table 261. The action name 305 associated with the device name 301 to be read may be read, and information for displaying the read action name 305 may be included in the request reception information and output. Further, when an address is already specified in the area 915 at the time of pulling down the area 916, the linked operation information table setting unit 223 corresponds to the address 302 that matches the specified address from the device information table 261. The attached action name 305 may be read, and information for enabling selection of the read action name by pull-down or the like may be included in the request reception information and output.

  Next, the region 931 will be described.

  The area 931 includes rows including an event occurrence detection device 932, an event 933, an action execution device 934, an action 935, a deletion 936, and the like as fields for indicating linked operation information. The linked operation information table setting unit 223 stores the detection device name 401 and the event occurrence address 402, the event name 403, the execution device 405, the action execution address 407, and the action name 406 of each row read from the linked operation information table 262 in the area 931. Information to be output as the event occurrence detection device 932, the event 933, the action execution device 934, and the action 935 is included in the request reception information and output. The deletion 936 is for the user to instruct deletion of the linked operation information indicated by the event occurrence detection device 932, the event 933, the action execution device 934, and the action 935 in the same row.

  The user designates each of the area 911 to the area 916 using the input device and then presses the button 921 to instruct registration in the interlocking operation information table 262. The client terminal 102 transmits information specified in each of the areas 911 to 916 to the manager apparatus 101 together with a registration request.

  Further, the user turns on the check box of the deletion 936 of the line to be deleted among the interlocking operation information of each line displayed in the area 931 by using the input device, and presses the button 941, etc. An instruction to update the interlocking operation information table 262 is given. The client terminal 102 transmits the event occurrence detection device 932, the event 933, the action execution device 934, the action 935, and the like in the row where the check box of the deletion 936 is ON to the manager apparatus 101 together with the deletion request.

  When the interlocking operation information table setting unit 223 of the manager device 101 receives a request from the client terminal 102 (S709), it determines whether the request is a registration request (S710).

  If the result of determination in S710 is a registration request, the linked operation information table setting unit 223 stores the information received together with the registration request in the linked operation information table 262 (S711). Specifically, for example, the linked operation information table setting unit 223 uses the information input in the areas 911 to 916 as the detection device name 401, the event name 402, and the event detection address of the new line in the linked operation information table 262. 403, execution device 405, action name 406, and action execution address 407 are stored. Further, the linked operation information table setting unit 223 selects a device name 301, an address 302, and an event name 303 in each row of the device information table 261 that matches the information input in the area 911, the area 912, and the area 913. Then, the event packet 304 of the selected row is read and stored in the event packet 404 of the row in which the above information is previously stored in the interlocking operation information table 262. Further, the linked operation information table setting unit 223 selects a device name 301, an address 302, and an action name 305 in each row of the device information table 261 that matches the information input in the area 914, the area 915, and the area 916. Then, the action packet 306 of the selected row is read and stored in the action packet 408 of the row in which the above information is previously stored in the interlocking operation information table 262.

  On the other hand, if the result of determination in S <b> 710 is not a registration request, the received request is a delete request, and therefore the interlocking operation information table setting unit 223 deletes the interlocking operation information received together with the delete request from the interlocking operation information table 262. (S712). Specifically, for example, the linked operation information table setting unit 223 includes the detection device name 401 and the event detection address 403, the event name 402, the execution device 405, the action execution address 407, and the action name 406 of each row of the linked operation information table 262. Among them, the event occurrence detection device 932, the event 933, the action execution device 934, and the action 935 that are received together with the deletion request are selected, and the selected row is deleted.

  Next, an operation example of the event action manager 212 of the manager device 101 will be described with reference to FIG.

  The event monitoring unit 231 of the event action manager 212 is activated when the manager device 101 is turned on, and starts the following operation.

  The event monitoring unit 231 reads the linked operation information table 262 from the nonvolatile storage device 206 (S1001), monitors a packet sent to the communication network 104, and enters an information reception waiting state (S1002). When the event monitoring unit 231 receives any information, the event monitoring unit 231 performs a process of S1003 described later.

  On the other hand, when the device 103 having the event detection function detects an event, it outputs notification information for notifying the occurrence of the detected event. This information includes information indicating the event that has occurred, its own address, and the like. This operation example is the same as in the prior art.

  When the information is received, the device 103 determines whether or not the received information is information for notifying the occurrence of an event, and the generated event is an event set in the linked operation information of the linked operation information table 262. (S1003). Therefore, the event monitoring unit 231 determines whether the received information includes information indicating the event that has occurred, an address, and the like. As a result of the determination, if the received information includes information indicating an event and an address, the event monitoring unit 231 extracts the information indicating the event, the address, and the like, and operates the linked operation information table. It is determined whether or not the event packet 404 and the event detection address 403 in each row 262 match.

  As a result of the determination in S1003, when the event that has occurred is an event set in the linked operation information in the linked operation information table 262, the action instruction unit 232 instructs execution of the action set in the linked operation information. (S1004). For this purpose, the action instruction unit 232 selects, from each row of the linked operation information table 262, the event packet 404 and the event detection address 403 that match the information indicating the event extracted from the received information, the address, and the like. The action execution address 406 and the action packet 408 in the line thus read are read out. Next, the action instruction unit 232 transmits an action execution request including the read action packet 408 with the read action execution address 406 as a destination. Thereafter, the process returns to the above-described processing of S1002.

  The device 103 that has received the action execution request performs its own operation in accordance with the information included in the received request. This operation example is the same as in the prior art.

  On the other hand, as a result of the determination in S1003, if the event that has occurred does not indicate that the event is not set in the linked operation information in the linked operation information table 262, the event monitoring unit 231 determines that the received information is the above-described S709. In step S1005, it is determined whether the request is an update request or a delete request received in step S1005.

  As a result of the determination in S1005, when the received information is an update request or a deletion request, the event monitoring unit 231 reads the interlocking operation information table 262 from the nonvolatile storage device 206 again, and returns to the above-described processing of S1002.

  As a result of the determination in S1005, when the received information is neither an update request nor a deletion request, the event monitoring unit 231 performs error processing and returns to the above-described processing of S1002.

  Next, a specific sequence example based on an operation example of the manager apparatus 101 alone will be described with reference to FIG. In the following, an example in which the device 103c, which is an illuminance sensor, detects the event “dark” will be described.

  In FIG. 11, first, the user instructs registration of device information using the client terminal 102. The client terminal 102 transmits the instructed device information to the manager device 101 (S1101).

  The device information table setting unit 222 of the manager apparatus 101 stores the received device information in the device information table 261 (S1102). This operation example is the same as S704 described above.

  Next, the user selects an event and an action to be interlocked and instructs to update or delete the interlocking operation information. In accordance with this instruction, the client terminal 102 transmits an update request or deletion request to the manager device 101 (S1103).

  The interlocking operation information table setting unit 223 of the manager device 101 updates the interlocking operation information table 262 in accordance with the received update request or deletion request (S1104). This operation example is the same as S711 and S712 described above.

  Hereinafter, it is assumed that the device information table 261 shown in FIG. 3 and the linked operation information table 262 shown in FIG. 4 are stored in the nonvolatile storage device 206 of the manager apparatus 101 according to the above-described operation example.

  The microcomputer 513 of the device 103c obtains a measurement value or the like from the sensor unit 512 every predetermined time or the like, and monitors the occurrence of an event “bright” or “dark” depending on whether or not the measurement value is equal to or less than the predetermined value. To do. Here, it is assumed that the device 103c detects the occurrence of an event “dark”. The microcomputer 513 transmits notification information including its own address “192.168.0.XXX” and information “888000 ?? 00 ???? B07340” for notifying the event that has occurred by broadcast or the like (S1105). ).

  The event monitoring unit 231 of the manager device 101 determines whether or not the received information is notification information, and the generated event is an event set in the linked operation information in the linked operation information table 262 (S1106). ). This operation example corresponds to S1003 described above. Here, as described above, the received information is notification information. The event monitoring unit 231 refers to the event detection address 403, the event packet 404, and the like in each row of the linked operation information table 262, and notifies the address “192.168.0.XXX” extracted from the notification information and the event that has occurred. It is determined whether or not there is a combination that matches the information “888000 ?? 00 ???? B07340” or the like. Here, the linked operation information table 262 shown in FIG. 4 includes an event detection address 403 “192.168.0.XXX” and an event packet 404 “888000 ?? 00 ???? B07340” corresponding to each other. Therefore, the event monitoring unit 231 determines that the generated event is an event set in the linked operation information in the linked operation information table 262.

  The action instruction unit 232 of the manager device 101 transmits an action execution request to the device 103 set to execute an action in accordance with the interlocking operation information in the interlocking operation information table 262 (S1107). Specifically, for example, the action instruction unit 232 reads the event detection address 403 “192.168.0.XXX” and the event packet 404 “888000 ?? 00 ??” from the linked operation information table 262 shown in FIG. The action execution address 407 “192.168.0.Y1” associated with “? B07340” and the action packet 408 “/ right? Power = 01” are read out. Next, the action instruction unit 232 receives an action execution request including the read action packet 408 “/ right? Power = 01” as an execution command, with the read action execution address 407 “192.168.0.Y1” as the destination. Send.

This action execution request is received by the device 103e. The device 103e extracts an execution command from the received action execution request, and operates according to the extracted execution command (S1108). Here, the CPU 611 of the device 103e turns on the lighting by turning on the power to the light bulb of the unique device 602.
<Second Embodiment>
Next, a second embodiment will be described.

  In the first embodiment described above, the manager apparatus 101 and the device 103 are connected via one communication network 104. In the second embodiment described below, the manager apparatus 101 and a part of the device 103 are connected via a communication network 104, and the manager apparatus 101 and another device 103 are connected via another communication network. It is what is done.

  Hereinafter, the same reference numerals are given to the same configurations as those of the above-described embodiment, and detailed description thereof is omitted.

  First, a configuration example of the second embodiment will be described with reference to FIG.

  In FIG. 12, the system of the present embodiment further includes a communication network 1201. The communication network 1201 is a network that conforms to regulations different from the communication network 104. For example, when the communication network 104 is a home LAN or the like, the communication network 1201 is a specific power-saving radio or the like.

  A part of the device 103 is connected to the communication network 1201. Here, the device 103 connected to the communication network 1201 is assumed to have an event detection function. However, the present invention is not limited to this, and a device 103 having only an action execution function may be connected.

  The manager device 101 is connected to both the communication network 104 and the communication network 1201.

  Next, a configuration example of the manager device 101 will be described with reference to FIG.

  In FIG. 13, the manager device 101 further includes a network interface 1301. As described above, the network interface 204 is for connecting to the communication network 104. The network interface 1301 is for connecting to the communication network 1201. Specifically, for example, when the communication network 104 is a LAN and the communication network 1201 is a specific power-saving radio, the network interface 204 is a device such as a PHY (physical layer) or RJ45, and the network interface 1301 is a specific A power-saving wireless modem.

  As described above, according to the above-described system, it is possible to perform the linked setting only by selecting the “event” and the “action”. Therefore, it is easy to set the linked operation according to the user's preference. . In addition, even when a new device is introduced, it is possible to flexibly change the interlock setting, and it is not necessary to change the operation of the existing network compatible device significantly.

  The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes design changes and the like without departing from the gist of the present invention. .

  For example, the control access destination (device 103) is not limited to the home, but is effective for devices outside the home. For example, when an event occurrence is detected, the action may be a report to a mobile phone registered in advance, a report to a data center or a security company, and the like.

  In the above embodiment, the user inputs the address of the device that detects the event and the address of the device that executes the action. However, the present invention is not limited to this. For example, the manager device performs polling by broadcasting or the like at startup or every predetermined time, and acquires information such as the device name and address, event name, event packet, action name, action packet name, etc. of each device by the polling Then, information such as an address in the device information table may be updated with the acquired information.

The system configuration example of 1st Embodiment. The structural example of the manager apparatus of the embodiment. An example of a device information table of the embodiment. An example of the interlocking operation information table of the embodiment. The example of a structure of the device of the embodiment. The example of a structure of the device of the embodiment. The operation example of the manager apparatus of the embodiment. The example of a screen of the embodiment. The example of a screen of the embodiment. The operation example of the manager apparatus of the embodiment. The sequence example of the same embodiment. The system configuration example of 2nd Embodiment. The structural example of the manager apparatus of the embodiment.

Explanation of symbols

101: Manager terminal, 102: Client terminal, 103: Device, 104: Communication network, 201: CPU, 211: Linked setting client, 221: Setting receiving unit, 222: Device information table setting unit, 223: Linked operation information table, 212: Event action manager, 231: Event monitoring unit, 232: Action instruction unit, 202: Boot ROM, 203: Peripheral controller, 204: Network interface, 205: Existence storage device, 206: Non-execution storage device, 261: Device information table, 262: interlocking operation information table, 263: device property manager program, 264: event packet monitor program, 501: sensor circuit unit, 511: network interface, 5 2: sensor unit, 513: microcomputer, 502: battery, 601: network interface, 602: device-specific, 603: control unit, 611: CPU, 612: RAM, 613: ROM, 614: Peripheral Controller

Claims (5)

A manager device connected to a plurality of devices having at least one function of detecting a state change and executing an instructed operation,
Device information storage means for storing a detectable state change and executable operation information for each device;
An output means for outputting a detectable state change for each device read from the device information storage means, and an executable operation for each device;
Input means;
A receiving unit that receives a state change detected by the device and an operation to be performed by the device when the state change is detected, input from the input unit;
Interlocking operation information storage means for storing a state change detected by the received device and an operation to be performed by the device when the state change is detected;
State change monitoring means for monitoring the state change detected by the device;
When a state change is detected, a control unit that reads out an operation corresponding to the detected state change from the linked operation information storage unit and outputs information instructing the operation to a device that executes the operation;
A manager device comprising: A manager device connected to a plurality of devices having at least one of a function of outputting a detected state change and its identification information, and an execution function of an instructed operation;
Device information storage means for storing the identification information for each device, a detectable state change, and executable operation information in association with each other;
An output means for outputting the identification information of each device read from the device information storage means, a detectable state change of each device, and an executable operation of each device;
Input means;
Input from the input means,
A receiving means for receiving device identification information, a state change detected by the device, an operation to be executed when the state change is detected, and identification information of the device executing the operation;
Interlocking operation for storing the received device identification information, the state change detected by the device, the operation to be executed when the state change is detected, and the identification information of the device executing the operation in association with each other Information storage means;
State change monitoring means for monitoring state changes and identification information output from each device;
When the state change is detected, the operation corresponding to the detected state change and the identification information of the device that has detected the state change is read from the interlocking operation information storage unit, and the device that executes the operation is read by the device. Control means for outputting information instructing operation;
A manager device comprising: A manager connected via a first communication network to a first device group that detects and notifies a change in state, and is connected via a second communication network to a second device group that executes the instructed operation. A device,
Device information storage means for storing a detectable state change for each first device and an executable operation for each second device;
Output means for outputting a detectable state change for each first device read from the device information storage means and an executable operation for each second device;
Input means;
Receiving means for receiving a state change detected by the first device group and an operation to be executed by the second device group when the state change is detected, input from the input means;
Linked operation information storage means for storing the received state change detected by the first device group and the operation to be executed by the second device group when the state change is detected;
State change monitoring means for monitoring the state change detected by the one device group;
When the state change is detected, the control unit reads out the operation corresponding to the detected state change from the interlocking operation information storage unit and outputs information instructing the operation to the second device for executing the operation When,
A manager device comprising: A control method by a manager device connected to a plurality of devices having at least one function of detection of a state change and execution of an instructed operation,
For each device, device information storage means for storing a detectable state change and executable operation information;
Interlocking operation information storage means;
Output means;
The manager device having input means,
An output step of outputting to the output means the change in state that can be detected for each device read from the device information storage means, and the executable operation for each device;
A reception step for receiving a state change detected by the device and an operation to be performed by the device when the state change is detected, input from the input unit;
A registration step of storing the received state change and an operation to be performed by a device when the state change is detected in association with the interlocking operation information storage unit;
A state change monitoring step for monitoring a state change detected by the device;
When a state change is detected, a control step of reading out an operation corresponding to the detected state change from the interlocking operation information storage means, and outputting information instructing the operation to a device that executes the operation;
A control method characterized by comprising: A control program executed by a manager device connected to a plurality of devices having at least one function of detecting a state change and executing an instructed operation,
For each device, device information storage means for storing a detectable state change and executable operation information;
Interlocking operation information storage means;
Output means;
The manager device having input means;
An output step of outputting to the output means the change in state that can be detected for each device read from the device information storage means, and the executable operation for each device;
A reception step for receiving a state change detected by the device and an operation to be performed by the device when the state change is detected, input from the input unit;
A registration step of storing the received state change and an operation to be performed by a device when the state change is detected in association with the interlocking operation information storage unit;
A state change monitoring step for monitoring a state change detected by the device;
When a state change is detected, a control step of reading out an operation corresponding to the detected state change from the interlocking operation information storage means, and outputting information instructing the operation to a device that executes the operation;
A control program characterized by causing

Images