JP2019012887A - Apparatus management device, terminal unit, management support device, apparatus management system, apparatus management method, display processing method, apparatus management program, and display processing program - Google Patents

Abstract

To provide an apparatus management device, a terminal unit, a management support device, an apparatus management system, an apparatus management method, a display processing method, an apparatus management program, and a display processing program, capable of automatically avoiding a communication connection of an unexpected combination with a slave unit.SOLUTION: An apparatus management device includes: a communication unit capable of communicating with one or more slave units and receiving, from other device, identification information of a target slave unit that is the one or more slave units, the target slave unit being allowed a communication connection with the apparatus management device itself; and a processing unit selectively allowing a connection request from the target slave unit to perform processing for establishing a communication connection with the target slave unit, on the basis of the identification information received by the communication unit.SELECTED DRAWING: Figure 2

Description

  The present invention relates to a device management device, a terminal device, a management support device, a device management system, a device management method, a display processing method, a device management program, and a display processing program.

  Conventionally, a management system for managing a plurality of devices by communicating with various devices in general homes and offices has been developed (for example, see International Publication No. 2014/103341 (Patent Document 1)). Patent Document 1 discloses a method for controlling opening and closing of a door based on a plurality of bright line patterns included in an image obtained by photographing a subject with a predetermined exposure time.

  In addition, in order to manage the device by the management device, a communication connection is established in advance between the management device and the device (for example, “ZIGBEE SPECIFICATION”, ZigBee Alliance Board of Directors, issued on January 17, 2008) (Refer nonpatent literature 1). Non-Patent Document 1 discloses a procedure for establishing a communication connection between a device that is a child device and a management device that is a parent device. Specifically, the slave unit detects a master unit that satisfies a predetermined condition, and requests communication connection to the detected master unit. Then, when the parent device permits a connection request from a child device that conforms to the same communication standard as the self device, a communication connection between the parent device and the child device is established.

International Publication No. 2014/103341

"ZIGBEE SPECIFICATION", ZigBee Alliance Board of Directors, published on January 17, 2008

  However, in the management system as described above, an unexpected combination of communication connections may be performed between the parent device and the child device. For example, there is a possibility that a child device that is not a management target is connected to the parent device by communication, or the child device is connected to a parent device different from the parent device that manages the child device.

  In addition, in order to avoid an unexpected combination of communication connections, it may be possible for the user to register the identification information of the slave unit to be managed in the master unit in advance. Cost.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to provide an apparatus management apparatus, a terminal apparatus, and a management apparatus that can automatically avoid an unexpected combination of communication connections with a slave unit. It is to provide a support device, a device management system, a device management method, a display processing method, a device management program, and a display processing program.

  (1) In order to solve the above-described problem, a device management apparatus according to an aspect of the present invention can communicate with one or a plurality of slave units, and communication connection with the device management apparatus is permitted. A communication unit that receives the identification information of the target slave unit that is the slave unit from another device, and selectively permits a connection request from the target slave unit based on the identification information received by the communication unit. And a processing unit that performs processing for establishing a communication connection with the target slave unit.

  (3) In order to solve the above-described problem, a terminal device according to an aspect of the present invention receives identification information of a target child device that is a child device permitted to communicate with the device management device from another device. And a display processing unit that performs processing for displaying the identification information received by the communication unit on a screen.

  (5) In order to solve the above-described problem, the management support apparatus according to an aspect of the present invention acquires first correspondence information indicating a correspondence relationship between the identification information of the device management apparatus and the identification information of the slave unit. And a processing unit that acquires identification information of the target device management apparatus and transmits a command to establish a communication connection with the slave unit to the target device management apparatus, and the processing unit includes the acquisition unit The instruction including the identification information of the slave unit corresponding to the identification information of the target device management apparatus is transmitted based on the first correspondence information acquired by the above.

  (7) In order to solve the above-described problem, a device management system according to an aspect of the present invention provides a device management apparatus capable of communicating with one or a plurality of slave units and a command for establishing a communication connection with the slave units. A management support device for transmitting to the device management device, the management support device based on first correspondence information indicating a correspondence relationship between the identification information of the device management device and the identification information of the slave unit, The instruction including the identification information of the slave corresponding to the identification information of the device management apparatus is transmitted to the target device management apparatus.

  (8) In order to solve the above-described problem, an apparatus management method according to an aspect of the present invention is an apparatus management method in an apparatus management apparatus, which is a slave unit that is permitted to communicate with the apparatus management apparatus. A step of receiving identification information of a certain target slave unit from another device, and establishing a communication connection with the target slave unit by selectively permitting a connection request from the target slave unit based on the received identification information Performing a process to perform.

  (9) In order to solve the above-described problem, a display processing method according to an aspect of the present invention is a display processing method in a terminal device, and is an object that is a slave unit that is permitted to communicate with a device management device Receiving the identification information of the slave unit from another device, and performing a process of displaying the received identification information on a screen.

  (10) In order to solve the above-described problem, an apparatus management method according to another aspect of the present invention is an apparatus management method in a management support apparatus that transmits a command for establishing a communication connection with a slave unit to an apparatus management apparatus. Acquiring the first correspondence information indicating the correspondence between the identification information of the device management apparatus and the identification information of the slave unit, and the identification information of the target device management apparatus, and the acquired first correspondence information And, based on the identification information of the target device management apparatus, transmitting the command including the identification information of the slave unit corresponding to the identification information of the target device management apparatus to the target device management apparatus. Including.

  (11) In order to solve the above-described problem, a device management program according to an aspect of the present invention is a device management program used in a device management apparatus, and can communicate a computer with one or a plurality of slave units. Based on the identification information received by the communication unit, the communication unit that receives the identification information of the target child device that is the child device that is permitted to communicate with the device management device of itself A program for causing a function to function as a processing unit that selectively permits a connection request from the target slave unit and establishes a communication connection with the target slave unit.

  (12) In order to solve the above problems, a display processing program according to an aspect of the present invention is a display processing program used in a terminal device, and the computer is allowed to communicate with the device management apparatus. A program for functioning as a communication unit that receives identification information of a target child device that is a child device from another device, and a display processing unit that performs processing for displaying the identification information received by the communication unit on a screen. is there.

  (13) In order to solve the above-described problem, a device management program according to another aspect of the present invention is a device management program used in a management support device, and includes a computer, identification information of the device management device, and a slave unit. An acquisition unit that acquires first correspondence information indicating a correspondence relationship with identification information, and an instruction for acquiring identification information of the target device management apparatus and establishing a communication connection with the slave unit. The processing unit is a program for causing a function to be transmitted to the processing unit, and the processing unit corresponds to the identification information of the target device management apparatus based on the first correspondence information acquired by the acquisition unit. The command including the machine identification information is transmitted.

  The present invention can be realized not only as a device management apparatus including such a characteristic processing unit, but also as a semiconductor integrated circuit that realizes part or all of the device management apparatus, or includes a device management apparatus. It can be realized as a device management system.

  In addition, the present invention can be realized not only as a terminal device including such a characteristic processing unit, but also as a semiconductor integrated circuit that realizes part or all of the terminal device, or a device including the terminal device. Or as a management system.

  In addition, the present invention can be realized not only as a management support apparatus including such a characteristic processing unit, but also as a semiconductor integrated circuit that realizes part or all of the management support apparatus. Can be realized as a device management system comprising

  According to the present invention, an unexpected combination of communication connections between the device management apparatus and the slave unit can be automatically avoided.

FIG. 1 is a diagram showing a configuration of a device management system according to the first embodiment of the present invention. FIG. 2 is a diagram showing a configuration of the device management apparatus according to the first embodiment of the present invention. FIG. 3 is a diagram showing a configuration of the server according to the first embodiment of the present invention. FIG. 4 is a diagram showing an example of corresponding device information stored in the storage device according to the first embodiment of the present invention. FIG. 5 is a diagram illustrating an example of corresponding sensor information stored in the storage device according to the first embodiment of the present invention. FIG. 6 is a diagram illustrating a configuration of the terminal device according to the first embodiment of the present invention. FIG. 7 is a diagram illustrating an example (part 1) of a connection state screen displayed by the terminal device according to the first embodiment of the present invention. FIG. 8 is a diagram showing an example (part 2) of the connection state screen displayed by the terminal device according to the first embodiment of the present invention. FIG. 9 is a diagram showing an example (part 3) of the connection status screen displayed by the terminal device according to the first embodiment of the present invention. FIG. 10 is a diagram showing an example of a sequence defining a procedure for establishing a communication connection in the device management system according to the first embodiment of the present invention. FIG. 11 is a diagram showing a configuration of a device management system according to the second embodiment of the present invention. FIG. 12 is a diagram showing a configuration of a device management apparatus according to the second embodiment of the present invention. FIG. 13 is a diagram showing an example of a sequence defining a procedure for establishing a communication connection in the device management system according to the second embodiment of the present invention.

  First, the contents of the embodiment of the present invention will be listed and described.

  (1) The device management apparatus according to the embodiment of the present invention is an object child that is capable of communicating with one or a plurality of child devices and is a child device that is permitted to communicate with the device management device. A communication unit that receives the identification information of the machine from another device; and based on the identification information received by the communication unit, selectively permits a connection request from the target slave unit and And a processing unit that performs processing for establishing a communication connection.

  With such a configuration, the connection request from the target slave unit is selectively permitted without the user registering the identification information of the target slave unit in advance. Therefore, an unexpected combination of communication connections between the device management apparatus and the slave unit can be automatically avoided.

  (2) Preferably, the processing unit rejects a connection request from a non-target child device that is the child device that is not permitted to communicate with the device management apparatus, or the non-target child device. A connection refusal notification indicating that a process for refusing a connection request or a process for severing a communication connection has been performed is transmitted to another device via the communication unit.

  With such a configuration, it is possible to more reliably avoid the establishment of a communication connection between the device management apparatus and the non-target child device. In addition, the device management apparatus can notify the user that establishment of a communication connection between the device management apparatus and the non-target slave unit is avoided, for example, by transmitting a connection rejection notification to another apparatus.

  (3) A terminal device according to an embodiment of the present invention includes a communication unit that receives, from another device, identification information of a target child device that is a child device that is permitted to communicate with a device management device, and the communication A display processing unit that performs a process of displaying the identification information received by the unit on a screen.

  With such a configuration, the user can easily grasp the target slave unit by checking the contents of the screen. Therefore, the user can perform an operation for connecting a slave unit that is not the target slave unit to the device management apparatus. Can be avoided. Therefore, an unexpected combination of communication connections between the device management apparatus and the slave unit can be automatically avoided.

  (4) Preferably, the display processing unit indicates that a connection request from a non-target child device that is a child device that is not permitted to communicate with the device management device is rejected, or the device management device and the device Processing to further display that the communication connection with the non-target slave unit has been disconnected is performed.

  With such a configuration, it is possible to easily grasp that establishment of communication connection between the device management apparatus and the non-target child device is avoided by the user confirming the contents of the screen. In addition, since it is displayed that the connection request from the slave unit has been rejected or the communication connection between the device management apparatus and the slave unit has been disconnected, for example, the user establishes a communication connection with the device management apparatus. When the operation for the slave unit is performed, it can be easily confirmed whether or not the communication connection between the device management apparatus and the slave unit has been established.

  (5) A management support apparatus according to an embodiment of the present invention includes an acquisition unit that acquires first correspondence information indicating a correspondence relationship between identification information of a device management apparatus and identification information of a slave unit, and the target device management A processing unit that acquires device identification information and transmits a command to establish a communication connection with the slave unit to the target device management device, wherein the processing unit is the first acquired by the acquiring unit. Based on the correspondence information, the instruction including the identification information of the slave unit corresponding to the identification information of the target device management apparatus is transmitted.

  With such a configuration, the device management apparatus can selectively permit a connection request from a slave unit that is permitted to communicate with itself based on a command from the management support apparatus. Therefore, an unexpected combination of communication connections between the device management apparatus and the slave unit can be automatically avoided.

  (6) Preferably, the acquisition unit further acquires second correspondence information indicating a correspondence relationship between the identification information of the user and the identification information of the device management apparatus, and the processing unit obtains the identification information of the target user. Further, based on the second correspondence information acquired by the acquisition unit, the identification information of the device management apparatus corresponding to the identification information of the target user is acquired as the identification information of the target device management apparatus. To do.

  With this configuration, when the user inputs his / her identification information, the user instructs the establishment of a communication connection between the device management apparatus corresponding to the user's identification information and the slave unit managed by the device management apparatus. be able to. For this reason, it is not necessary for the user to grasp the identification information of the device management apparatus.

  (7) The device management system according to the embodiment of the present invention transmits to the device management device a device management device capable of communicating with one or more slave devices and a command for establishing a communication connection with the slave device. A management support device, wherein the management support device is based on first correspondence information indicating a correspondence relationship between the identification information of the device management device and the identification information of the slave unit, and the identification information of the target device management device The instruction including the identification information of the slave unit corresponding to is transmitted to the target device management apparatus.

  With such a configuration, the device management apparatus can selectively permit a connection request from a slave unit that is permitted to communicate with itself based on a command from the management support apparatus. Therefore, an unexpected combination of communication connections between the device management apparatus and the slave unit can be automatically avoided.

  (8) A device management method according to an embodiment of the present invention is a device management method in a device management apparatus, and identification information of a target child device that is a child device that is permitted to communicate with the device management device. And a step of selectively allowing a connection request from the target slave unit and establishing a communication connection with the target slave unit based on the received identification information. Including.

  By such a method, the connection request from the target slave unit is selectively permitted without the user registering the identification information of the target slave unit in advance. Therefore, an unexpected combination of communication connections between the device management apparatus and the slave unit can be automatically avoided.

  (9) A display processing method according to an embodiment of the present invention is a display processing method in a terminal device, and includes other identification information of a target child device that is a child device permitted to communicate with the device management device. And a step of performing a process of displaying the received identification information on a screen.

  With this method, the user can easily grasp the target slave unit by checking the contents of the screen. Therefore, the user can perform an operation to connect the slave unit that is not the target slave unit to the device management apparatus. Can be avoided. Therefore, an unexpected combination of communication connections between the device management apparatus and the slave unit can be automatically avoided.

  (10) A device management method according to an embodiment of the present invention is a device management method in a management support device that transmits a command for establishing a communication connection with a child device to a device management device, and identifies the device management device First correspondence information indicating a correspondence relationship between the information and the identification information of the slave unit, and identification information of the target device management device; and the acquired first correspondence information and the target device management device Transmitting the command including the identification information of the slave unit corresponding to the identification information of the target device management apparatus to the target device management apparatus based on the identification information.

  By such a method, the device management apparatus can selectively permit a connection request from a slave unit that is permitted to communicate with itself based on a command from the management support apparatus. Therefore, an unexpected combination of communication connections between the device management apparatus and the slave unit can be automatically avoided.

  (11) A device management program according to an embodiment of the present invention is a device management program used in a device management apparatus, and is capable of communicating a computer with one or a plurality of slave units. From the target slave unit based on the identification information received by the communication unit, and a communication unit that receives the identification information of the target slave unit that is the slave unit permitted to communicate with Is a program for functioning as a processing unit that performs processing for selectively permitting a connection request and establishing communication connection with the target slave unit.

  With such a configuration, a connection request from a slave unit that is permitted to communicate with the device management device without the user registering in advance the identification information of the slave device managed by the device management device. Is selectively allowed. Therefore, an unexpected combination of communication connections between the device management apparatus and the slave unit can be automatically avoided.

  (12) A display processing program according to an embodiment of the present invention is a display processing program used in a terminal device, and is a target child device that is a child device that is permitted to communicate with a device management device. Is a program for functioning as a communication unit that receives the identification information from another device and a display processing unit that performs a process of displaying the identification information received by the communication unit on a screen.

  With such a configuration, the user can easily grasp the target slave unit by checking the contents of the screen. Therefore, the user can perform an operation for connecting a slave unit that is not the target slave unit to the device management apparatus. Can be avoided. Therefore, an unexpected combination of communication connections between the device management apparatus and the slave unit can be automatically avoided.

  (13) A device management program according to an embodiment of the present invention is a device management program used in a management support apparatus, and shows a correspondence relationship between identification information of a device management apparatus and identification information of a slave unit. Functions as an acquisition unit that acquires first correspondence information, and a processing unit that acquires identification information of the target device management apparatus and transmits a command to establish a communication connection with the slave unit to the target device management apparatus And the processing unit includes the identification information of the slave unit corresponding to the identification information of the target device management apparatus based on the first correspondence information acquired by the acquisition unit. Send.

  With such a configuration, the device management apparatus can selectively permit a connection request from a slave unit that is permitted to communicate with itself based on a command from the management support apparatus. Therefore, an unexpected combination of communication connections between the device management apparatus and the slave unit can be automatically avoided.

  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. Moreover, you may combine arbitrarily at least one part of embodiment described below.

<First Embodiment>
[Configuration and basic operation]
(overall structure)
FIG. 1 is a diagram showing a configuration of a device management system according to the first embodiment of the present invention.

  Referring to FIG. 1, a device management system 301 includes one or more device management apparatuses 101, a server (management support apparatus) 102, a storage device 103, one or more terminal devices 131, and one or more A sensor (slave unit) 151.

  In FIG. 1, three sensors 151A, 151B, and 151Z are shown as an example. In FIG. 1, one device management apparatus 101 and one terminal apparatus 131 are shown as an example.

  The sensor 151 is a temperature / humidity sensor, a door open / close sensor, or a human sensor provided in a facility such as a general home or office.

  The storage device 103 stores a database. The database includes corresponding device information (hereinafter, referred to as “user ID”) and corresponding device information (corresponding to identification information of the device management apparatus 101 (hereinafter referred to as “device ID”)). Second correspondence information) is included.

  The database also includes corresponding sensor information (first correspondence information) indicating the correspondence between the device ID and the identification information of the sensor 151 (hereinafter referred to as “sensor ID”). Further, the database includes a plurality of combinations of user IDs and passwords registered in advance.

  The server 102 can acquire corresponding device information and corresponding sensor information from the database in the storage device 103.

  The device management apparatus 101 is, for example, a HEMS (Home Energy Management System) provided in a facility such as a general home or an office. The device management apparatus 101 manages the sensor 151 by transmitting and receiving information to and from the sensor 151 that has established a communication connection with itself according to a communication protocol such as ZigBee (registered trademark) or Z-Wave.

  In addition, the subunit | mobile_unit 151 may be another kind of apparatus which can establish a communication connection with the apparatus management apparatus 101 not only a sensor.

(Equipment management device)
FIG. 2 is a diagram showing a configuration of the device management apparatus according to the first embodiment of the present invention.

  Referring to FIG. 2, device management apparatus 101 includes a communication unit 11, a processing unit 12, and a storage unit 13. The communication unit 11 can exchange information with other devices. In this example, the communication unit 11 can transmit / receive information to / from the server 102 via the network 161 and transmit / receive information to / from the sensor 151.

  The storage unit 13 holds the device ID of its own device management device 101. The processing unit 22 performs processing for establishing a communication connection with the sensor 151.

  More specifically, referring to FIG. 1, for example, when the user performs an operation of inputting his / her user ID and password to terminal device 131 and the login by the user is completed, terminal device 131 includes the user ID. A pairing request is transmitted to the server 102 via the network 161.

  The server 102 acquires corresponding device information and corresponding sensor information from the database in the storage device 103. Then, the server 102 acquires a device ID and a sensor ID corresponding to the user ID included in the pairing request from the terminal device 131 based on the acquired corresponding device information and corresponding sensor information.

  Then, the server 102 transmits a communication connection command with the sensor 151 to the device management apparatus 101 corresponding to the acquired apparatus ID via the network 161. This communication connection command includes the sensor ID acquired by the server 102. Details of acquisition of the device ID and sensor ID by the server 102 will be described later.

  Referring to FIG. 2 again, the processing unit 12 in the device management apparatus 101 receives a communication connection command from the server 102 via the network 161 and the communication unit 11, and stores a sensor ID included in the received communication connection command. Save to 13. Further, the processing unit 12 operates in a pairing mode in which a connection request from the sensor 151 is received until a predetermined time elapses from the timing at which the communication connection command is received.

  When the processing unit 12 receives a connection request from the sensor 151 via the communication unit 11 during the period of operation in the pairing mode, the processing unit 12 determines whether the connection request should be permitted. That is, the processing unit 12 selectively permits a connection request from a sensor (hereinafter, also referred to as “target sensor”) 151 that is permitted to communicate with its own device management apparatus 101.

  More specifically, the connection request from the sensor 151 includes the sensor ID of the sensor 151. The processing unit 12 checks whether or not a sensor ID that matches the sensor ID included in the received connection request is stored in the storage unit 13.

  Then, when a sensor ID that matches the sensor ID included in the connection request is stored in the storage unit 13, the processing unit 12 determines that the connection request should be permitted, and the sensor 151 corresponding to the sensor ID To establish a communication connection. Then, the processing unit 12 transmits a connection completion notification indicating that the communication connection with the sensor 151 has been established to the server 102 via the communication unit 11 and the network 161.

  The connection completion notification includes, for example, the device ID of the device management apparatus 101 that is the transmission source, the sensor ID of the sensor 151 that has established the communication connection, and the current time.

  On the other hand, the processing unit 12 is connected from a sensor (hereinafter also referred to as “non-target sensor”) 151 that is not permitted to communicate with its own device management apparatus 101 during the period in which it is operating in the pairing mode. When the request is received, that is, when the sensor ID that matches the sensor ID included in the connection request is not stored in the storage unit 13, the connection request from the sensor 151 is rejected. Specifically, the processing unit 12 transmits a connection rejection notification indicating that the connection request from the sensor 151 is rejected to the server 102 via the communication unit 11 and the network 161.

  The connection rejection notification includes, for example, the device ID of the device management apparatus 101 that is the transmission source and the sensor ID of the sensor 151 for which the connection request is rejected.

  When the processing unit 12 receives a connection request from the non-target sensor 151, the processing unit 12 disconnects the communication connection with the non-target sensor 151 after performing a process of establishing a communication connection with the non-target sensor 151. It may be a configuration.

  Further, the processing unit 12 manages the sensor 151 that has established a communication connection with its own device management apparatus 101. Specifically, when the sensor 151 is a temperature and humidity sensor, the sensor 151 transmits, for example, temperature and humidity information indicating the measured temperature and humidity to the device management apparatus 101 regularly or irregularly. The processing unit 12 in the device management apparatus 101 receives the temperature / humidity information from the sensor 151 via the communication unit 11 and stores the received temperature / humidity information in the storage unit 13.

  Then, for example, when the user requests display of temperature and humidity in the facility by operating the terminal device 131, the terminal device 131 manages operation information indicating the user's operation content via the network 161 and the server 102. Send to device 101.

  When receiving the operation information from the terminal device 131 via the communication unit 11, the processing unit 12 in the device management apparatus 101 receives the temperature / humidity information stored in the storage unit 13 via the communication unit 11, the network 161, and the server 102. Transmit to device 131.

  And the terminal device 131 will perform the process which displays the screen based on the said greenhouse degree information on a self monitor etc., for example, if the temperature / humidity information from the apparatus management apparatus 101 is received.

  The processing unit 12 is not limited to the configuration for transmitting the connection completion notification and the connection rejection notification, and may be configured not to transmit at least one of the connection completion notification and the connection rejection notification.

(Server and storage device)
FIG. 3 is a diagram showing a configuration of the server according to the first embodiment of the present invention.

  Referring to FIG. 3, server 102 includes a communication unit (acquisition unit) 21 and a processing unit 22. The communication unit 21 can transmit / receive information to / from other devices. In this example, the communication unit 21 transmits / receives information to / from the device management apparatus 101 via the network 161, transmits / receives information to / from the terminal apparatus 131 via the network 161, It is possible to send and receive information between.

  When the processing unit 22 receives the user ID and password from the terminal device 131 via the network 161 and the communication unit 21, the combination of the user ID and password from the terminal device 131 is stored in the storage device 103. Check if it matches any one of multiple password pairs.

  Then, when the combination of the user ID and password from the terminal device 131 matches any one of the plurality of sets stored in the storage device 103, the processing unit 22 approves the user ID and password. Then, when the login is completed by approving the user ID and password, the processing unit 22 transmits a login completion notification indicating that the login is completed to the terminal device 131 via the communication unit 21 and the network 161.

  When the communication unit 21 receives a pairing request from the terminal device 131 via the network 161 after the login of the user is completed, the communication unit 21 acquires the corresponding device information and the corresponding sensor information from the database in the storage device 103 and acquires the corresponding response. The device information and the corresponding sensor information are output to the processing unit 22.

  Based on the corresponding device information received from the communication unit 21, the processing unit 22 acquires a device ID corresponding to the user ID included in the pairing request from the terminal device 131. Further, the processing unit 22 acquires a sensor ID corresponding to the device ID based on the corresponding sensor information received from the communication unit 21.

  FIG. 4 is a diagram showing an example of corresponding device information stored in the storage device according to the first embodiment of the present invention.

  Referring to FIG. 4, storage device 103 stores, for example, table Ta1 indicating the contents of corresponding device information.

  Specifically, in the table Ta1, the user ID “taro@sample.com” is associated with the device ID “H1111”, and the user ID “hanako@sample.com” is associated with the device ID “H1112”. , The user ID “jiro@sample.com” and the device ID “H1113” are associated with each other.

  Here, when the user ID included in the pairing request from the terminal device 131 is “taro@sample.com”, the processing unit 22 has a device ID “H1111” corresponding to the user ID “taro@sample.com”. Are extracted from the table Ta1.

  FIG. 5 is a diagram illustrating an example of corresponding sensor information stored in the storage device according to the first embodiment of the present invention.

  With reference to FIG. 5, the storage device 103 stores, for example, a table Ta2 indicating the contents of the corresponding sensor information. The correspondence sensor information includes the last communication time between the device management apparatus 101 and the sensor 151, that is, the latest communication time, in addition to the correspondence relationship between the device ID and the sensor ID.

  Specifically, in the table Ta2, the device ID “H1111” and the sensor IDs “S0001” and “S0002” are associated with each other. The sensor ID “S0001” is the sensor ID of the sensor 151A shown in FIG. 1, and the sensor ID “S0002” is the sensor ID of the sensor 151B shown in FIG.

  That is, for the device management apparatus 101 corresponding to the device ID “H1111”, the sensors 151A and 151B are target sensors, and the sensors 151 other than the sensors 151A and 151B are non-target sensors.

  In the table Ta2, the device ID “H1112” and the sensor ID “S0011” are associated with each other. The sensor ID “S0011” is a sensor ID of a sensor 151 (not shown).

  Further, in the table Ta2, the connection state of each sensor 151 is shown. Specifically, in the table Ta2, for example, a character “null” indicating that the sensor 151A is not connected to the device management apparatus 101 is an item of “last communication time” and corresponds to the sensor ID “S0001”. It is displayed in the place to do. Similarly, the characters “null” are displayed at locations corresponding to the sensor IDs “S0002” and “S0011”, which are items of “final communication time”.

  If the device ID extracted from the table Ta1 shown in FIG. 4 is “H1111”, the processing unit 22 uses the sensor IDs “S0001” and “S0002” corresponding to the device ID “H1111” from the table Ta2 shown in FIG. To extract.

  Then, for example, the processing unit 22 sends the extracted sensor IDs “S0001” and “S0002”, the connection status information indicating that the sensor 151A is not connected, and the sensor 151B is not connected, to the communication unit 21 and It transmits to the terminal device 131 via the network 161.

  Further, the processing unit 22 transmits a communication connection command including the extracted sensor IDs “S0001” and “S0002” to the device management apparatus 101 corresponding to the device ID “H1111” via the communication unit 21 and the network 161.

  For example, when the communication connection between the device management apparatus 101 and the sensor 151A is established and the connection completion notification is transmitted from the device management apparatus 101, the processing unit 22 transmits the connection completion notification from the device management apparatus 101 to the network 161. And received via the communication unit 21. Then, based on the received connection completion notification, the processing unit 22 changes and updates the connection state of the sensor 151A among the contents of the corresponding sensor information stored in the storage device 103.

  Further, the processing unit 22 extracts a user ID corresponding to the device ID included in the connection completion notification from the corresponding device information from the communication unit 21, and notifies the terminal device 131 corresponding to the extracted user ID of the connection completion notification. Is transmitted via the communication unit 21 and the network 161.

(Terminal device)
FIG. 6 is a diagram illustrating a configuration of the terminal device according to the first embodiment of the present invention.

  Referring to FIG. 6, terminal device 131 includes a receiving unit 31, a display processing unit 32, a communication unit 33, and a storage unit 34.

  The communication unit 33 can exchange information with other devices. In this example, the communication unit 33 can transmit and receive information to and from the server 102 via the network 161.

  The accepting unit 31 accepts a login instruction from the user, for example. Specifically, when the user operates the terminal device 131 to input a user ID and password to the terminal device 131, the receiving unit 31 in the terminal device 131 receives the user ID and password input by the user as the communication unit 33. And transmitted to the server 102 via the network 161.

  When the server 102 approves the user ID and password and the login is completed, the server 102 transmits a login completion notification to the terminal device 131 via the network 161.

  When receiving the login completion notification from the server 102 via the communication unit 33, the reception unit 31 in the terminal device 131 creates a pairing request including the user ID input by the user. Then, the reception unit 31 transmits the created pairing request to the server 102 via the communication unit 33 and the network 161.

  The display processing unit 32 performs a process of displaying a connection state screen Sc indicating the connection state of each sensor 151 on a monitor or the like in its own terminal device 131. The display processing unit 32 may be configured to perform a process of displaying the connection state screen Sc on a display device different from its own terminal device 131.

  FIG. 7 is a diagram illustrating an example (part 1) of a connection state screen displayed by the terminal device according to the first embodiment of the present invention.

  For example, when the server 102 transmits connection state information indicating the connection state of each sensor 151 to the terminal device 131 via the network 161, the display processing unit 32 in the terminal device 131 receives the connection state information via the communication unit 33. . And the display process part 32 performs the process which displays the connection status screen Sc based on the received connection status information. In addition, the display processing unit 32 stores the received connection state information in the storage unit 34.

  Referring to FIG. 7, for example, sensor 151A and sensor 151B are shown on connection state screen Sc, and further, these sensors 151A and sensor 151B are both shown in an unconnected state.

  Referring to FIG. 6 again, the display processing unit 32 in the terminal device 131 performs processing for the device management apparatus 101 to establish a communication connection with the sensor 151, and sends a connection completion notification via the server 102 and the network 161. When transmitted to the device 131, the connection completion notification is received via the communication unit 33.

  Then, the display processing unit 32 changes and updates the content of the connection state information stored in the storage unit 34 based on the received connection completion notification. Then, the display processing unit 32 performs a process of displaying the connection state screen Sc based on the updated connection state information on a monitor or the like in its own terminal device 131.

  FIG. 8 is a diagram showing an example (part 2) of the connection state screen displayed by the terminal device according to the first embodiment of the present invention.

  Referring to FIG. 8, for example, the connection status screen Sc shows the sensors 151A and 151B, and that the establishment of the communication connection between the sensor 151A and the device management apparatus 101 is completed at 16:28, In addition, it is indicated that the sensor 151B is not connected.

  Referring again to FIG. 6, when device management apparatus 101 rejects the connection request from non-target sensor 151 and transmits a connection rejection notification to terminal apparatus 131 via server 102 and network 161, display processing unit in terminal apparatus 131 32 receives the connection rejection notice via the communication unit 33. Then, the display processing unit 32 performs a process of displaying the connection state screen Sc on a monitor or the like in its own terminal device 131 based on the received connection rejection notification and the connection state information stored in the storage unit 34.

  FIG. 9 is a diagram showing an example (part 3) of the connection status screen displayed by the terminal device according to the first embodiment of the present invention.

  Referring to FIG. 9, for example, sensor 151A and sensor 151B are shown on connection state screen Sc. Furthermore, sensor 151A and sensor 151B are both in an unconnected state, and sensor ID “S9999”. "Indicates that the connection request from the non-target sensor 151 corresponding to" is rejected.

  In addition, the display process part 32 should just be the structure which performs the process which displays sensor ID of each object sensor 151. FIG. In other words, the screen displayed by the display processing unit 32 may not include the connection state of each target sensor 151. Further, the screen displayed by the display processing unit 32 may not include that the connection request from the non-target sensor 151 is rejected.

[Operation]
Each device in the device management system 301 includes a computer, and an arithmetic processing unit such as a CPU in the computer reads and executes a program including a part or all of each step in the following sequence diagram from a memory (not shown). Each of the programs of the plurality of apparatuses can be installed from the outside. The programs of the plurality of apparatuses are distributed while being stored in a recording medium.

  FIG. 10 is a diagram showing an example of a sequence defining a procedure for establishing a communication connection in the device management system according to the first embodiment of the present invention.

  Referring to FIG. 10, first, terminal apparatus 131 accepts a user's login instruction, that is, an input of a user ID and a password (step S11).

  Next, the terminal device 131 transmits the user ID and password input by the user to the server 102 via the network 161 (step S12).

  Next, the server 102 confirms, for example, whether or not the set of the user ID and password from the terminal device 131 matches any one of a plurality of sets stored in the storage device 103. If they match, the server 102 approves the user ID and password from the terminal device 131, and transmits a login completion notification to the terminal device 131 via the network 161 (step S13).

  If the set of the user ID and password from the terminal device 131 does not match any of the plurality of sets stored in the storage device 103, the server 102 sends a login rejection notification via the network 161, for example. Send to. Then, for example, the terminal device 131 receives a login rejection notification from the server 102 via the network 161, and based on the received login rejection notification, displays that the login by the user is rejected on its own monitor or the like. I do.

  Next, when the login by the user is completed, the terminal device 131 transmits a pairing request including the user ID input by the user to the server 102 via the network 161 (step S14).

  Next, when receiving a pairing request from the terminal device 131, the server 102 acquires corresponding device information and corresponding sensor information stored in the storage device 103. Then, the server 102 acquires a device ID corresponding to the user ID included in the pairing request and one or more sensor IDs corresponding to the device ID based on the acquired corresponding device information and corresponding sensor information.

  In addition, the server 102 confirms the connection state of each of the one or more sensors 151 corresponding to the acquired one or more sensor IDs.

  Here, the user ID input by the user is “taro@sample.com”, the device ID corresponding to the user ID is “H1111”, and the sensor IDs corresponding to the device ID are “S0001” and “ S0002 ". Further, it is assumed that the sensor 151A corresponding to the sensor ID “S0001” and the sensor 151B corresponding to the sensor ID “S0002” are not connected (step S15).

  Next, the server 102 sends the acquired sensor IDs “S0001” and “S0002” and connection state information indicating that the sensors 151A and 151B are not connected to the terminal device 131 via the network 161. (Step S16).

  Next, the terminal device 131 stores connection state information from the server 102. Further, the terminal device 131 displays the connection status screen Sc indicating that the sensor IDs “S0001” and “S0002” and the sensors 151A and 151B are not connected based on the connection status information. A display process for displaying on the monitor or the like is performed (step S17).

  Next, the server 102 transmits a communication connection command including the device ID “H1111” and the sensor IDs “S0001” and “S0002” to the device management apparatus 101 corresponding to the device ID “H1111” via the network 161 ( Step S18).

  Next, upon receiving a communication connection command from the server 102, the device management apparatus 101 starts an operation in the pairing mode (step S19).

  In the period when the device management apparatus 101 is operating in the pairing mode, for example, it is assumed that the user presses a pairing button for communication connection provided in the sensor 151A. In this case, the sensor 151A transmits a connection request including its own sensor ID to the device management apparatus 101 (step S20).

  Next, when receiving the connection request from the sensor 151A, the device management apparatus 101 determines whether the transmission source of the received connection request is the target sensor. Here, the sensor ID “S0001” included in the connection request from the sensor 151A matches the sensor ID included in the communication connection command from the server 102. Therefore, the device management apparatus 101 determines that the sensor 151A that is the transmission source of the connection request is a target sensor, and accepts the connection request from the sensor 151A (step S21).

  Next, the device management apparatus 101 transmits a connection response indicating that the connection request has been accepted to the sensor 151A (step S22).

  Next, the device management apparatus 101 performs processing for establishing a communication connection with the sensor 151A and includes its own apparatus ID “H1111”, the sensor ID “S0001” of the sensor 151A with which communication connection is established, and the current time. A connection completion notification is transmitted to the server 102 via the network 161 (step S23).

  Next, when the server 102 receives the connection completion notification from the device management apparatus 101, the server 102 changes and updates the contents of the table Ta2 stored in the storage device 103 based on the received connection completion notification. Specifically, for example, the server 102 changes the item “last communication time” corresponding to the sensor ID “S0001” in the table Ta2 shown in FIG. 5 from “null” to the time indicated by the connection completion notification. Update (step S24).

  Next, the server 102 transmits a connection completion notification from the device management apparatus 101 to the terminal apparatus 131 via the network 161 (step S25).

  Next, when receiving the connection completion notification from the server 102, the terminal device 131 changes and updates the connection state of the sensor 151A in the contents of the stored connection state information based on the connection completion notification. Then, the terminal device 131 performs a display process of displaying the connection state screen Sc based on the updated connection state information on its own monitor or the like (step S26).

  Further, it is assumed that, for example, the user presses the pairing button for communication connection provided in the sensor 151Z during the period in which the device management apparatus 101 operates in the pairing mode. In this case, the sensor 151Z transmits a connection request including its own sensor ID “S9999” to the device management apparatus 101 (step S27).

  Next, when receiving the connection request from the sensor 151Z, the device management apparatus 101 determines whether the transmission source of the received connection request is the target sensor. Here, since the sensor ID “S9999” included in the connection request does not match the sensor ID included in the communication connection command from the server 102, the device management apparatus 101 transmits the sensor 151Z that is the transmission source of the connection request. Is determined to be a non-target sensor, and the connection request from the sensor 151Z is rejected (step S28).

  Next, the device management apparatus 101 transmits a connection response indicating that the connection request has been rejected to the sensor 151Z (step S29).

  Next, the device management apparatus 101 transmits a connection rejection notification including its own apparatus ID “H1111” and the sensor ID “S9999” of the sensor 151Z that rejected the connection request to the server 102 via the network 161 (step S30). .

  Next, when the server 102 receives the connection rejection notification from the device management apparatus 101, the server 102 transmits the connection rejection notification to the terminal device 131 via the network 161 (step S31).

  Next, when the terminal device 131 receives the connection rejection notification from the server 102, based on the connection rejection notification and the stored connection state information, for example, both the sensor 151A and the sensor 151B are in an unconnected state. In addition, a display process for displaying a connection status screen Sc indicating that there is a connection request from the sensor 151Z corresponding to the sensor ID “S9999” on the own monitor or the like is performed (step S32).

  By the way, in the management system as described in Non-Patent Document 1 described above, an unexpected combination of communication connections may be performed between the parent device and the child device. For example, there is a possibility that a child device that is not a management target is connected to the parent device by communication, or the child device is connected to a parent device different from the parent device that manages the child device.

  On the other hand, in the device management apparatus 101 according to the first embodiment of the present invention, the communication unit 11 can communicate with one or a plurality of sensors 151, and communication connection with its own device management apparatus 101 is established. The sensor ID of the permitted target sensor 151 is received from the server 102 via the network 161. Further, the processing unit 12 performs processing for selectively permitting a connection request from the target sensor 151 and establishing a communication connection with the target sensor 151 based on the sensor ID received by the communication unit 11.

  With such a configuration, the connection request from the target sensor 151 is selectively permitted without the user performing registration of the sensor ID of the target sensor 151 in advance. Therefore, an unexpected combination of communication connections between the device management apparatus 101 and the sensor 151 can be automatically avoided.

  In the device management apparatus 101 according to the first embodiment of the present invention, the processing unit 12 rejects a connection request from the non-target sensor 151 that is not permitted to communicate with the own device management apparatus 101. The process or the process of disconnecting the communication connection with the non-target sensor 151 is performed. Further, the processing unit 12 transmits a connection rejection notification indicating that the processing for rejecting the connection request or the processing for disconnecting the communication connection has been performed to the server 102 via the communication unit 11 and the network 161.

  With such a configuration, establishment of a communication connection between the device management apparatus 101 and the non-target sensor 151 can be avoided more reliably. Further, for example, the device management apparatus 101 transmits a connection rejection notification to the user terminal device 131 via the network 161 and the server 102, thereby avoiding establishment of a communication connection between the device management apparatus 101 and the non-target sensor 151. This can be notified to the user.

  Further, in the terminal device 131 according to the first embodiment of the present invention, the communication unit 33 obtains the sensor ID of the target sensor 151 permitted to communicate with the device management apparatus 101 from the server 102 via the network 161. Receive. Further, the display processing unit 32 performs processing for displaying the sensor ID received by the communication unit 33 on the screen.

  With such a configuration, the user can easily grasp the target sensor 151 by confirming the contents of the screen. Therefore, the user avoids an operation for connecting the non-target sensor 151 to the device management apparatus 101. be able to. Therefore, an unexpected combination of communication connections between the device management apparatus 101 and the sensor 151 can be automatically avoided.

  In the terminal device 131 according to the first embodiment of the present invention, the display processing unit 32 rejects the connection request from the non-target sensor 151 that is not permitted to communicate with the device management apparatus 101. Alternatively, a process for further displaying that the communication connection between the device management apparatus 101 and the non-target sensor 151 has been disconnected is performed.

  With such a configuration, the user can easily grasp that establishment of a communication connection between the device management apparatus 101 and the non-target sensor 151 is avoided by checking the contents of the screen. In addition, since it is displayed that the connection request from the sensor 151 has been rejected or the communication connection between the device management apparatus 101 and the sensor 151 has been disconnected, for example, the user can establish a communication connection with the device management apparatus 101. When an operation for establishment is performed on the sensor 151, it is possible to easily confirm whether or not the communication connection between the device management apparatus 101 and the sensor 151 has been established.

  In the server 102 according to the first embodiment of the present invention, the communication unit 21 acquires correspondence sensor information indicating the correspondence between the device ID of the device management apparatus 101 and the sensor ID of the sensor 151. In addition, the processing unit 22 acquires the device ID of the target device management apparatus 101 and transmits a communication connection command with the sensor 151 to the device management apparatus 101. Further, the processing unit 22 transmits a communication connection instruction including a sensor ID corresponding to the device ID of the target device management apparatus 101 based on the corresponding sensor information acquired by the communication unit 21.

  With this configuration, the device management apparatus 101 can selectively permit a connection request from the target sensor 151 that is permitted to communicate with itself based on a communication connection command from the server 102. Therefore, an unexpected combination of communication connections between the device management apparatus 101 and the sensor 151 can be automatically avoided.

  In the server 102 according to the first embodiment of the present invention, the communication unit 21 further acquires corresponding device information indicating a correspondence relationship between the user ID and the device ID. In addition, the processing unit 22 acquires the user ID of the target user, and further, based on the corresponding device information acquired by the communication unit 21, the device ID corresponding to the user ID is the device of the target device management apparatus 101. Obtained as an ID.

  With this configuration, when the user inputs his / her user ID, establishment of a communication connection between the device management apparatus 101 corresponding to his / her user ID and the target sensor 151 which is a management target of the device management apparatus 101 is established. Can be instructed. For this reason, it is not necessary for the user to know the device ID of the device management apparatus 101 or the like.

  Further, in the device management system 301 according to the first embodiment of the present invention, the server 102 performs processing based on the corresponding sensor information indicating the correspondence between the device ID of the device management apparatus 101 and the sensor ID of the sensor 151. A communication connection command including a sensor ID corresponding to the device ID of the device management apparatus 101 is transmitted to the device management apparatus 101.

  With this configuration, the device management apparatus 101 can selectively permit a connection request from the target sensor 151 that is permitted to communicate with itself based on a communication connection command from the server 102. Therefore, an unexpected combination of communication connections between the device management apparatus 101 and the sensor 151 can be automatically avoided.

  Next, another embodiment 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.

<Second Embodiment>
In the device management system 301 according to the first embodiment of the present invention described above, when the user inputs the user ID and password to the terminal device 131 and the login is completed, the terminal device 131 makes a pairing request to the server 102. Send. In contrast, in the device management system 302 according to the second exemplary embodiment of the present invention, the device management apparatus 101 transmits a pairing request to the server 102 when the user operates the device management apparatus 101. The contents other than those described below are the same as those of the device management system 301 according to the first embodiment.

[Configuration and basic operation]
(overall structure)
FIG. 11 is a diagram showing a configuration of a device management system according to the second embodiment of the present invention.

  Referring to FIG. 11, device management system 302 includes one or more device management apparatuses 201, a server 102, a storage device 103, and one or more sensors 151.

  In FIG. 11, three sensors 151A, 151B, and 151Z are shown as an example. In addition, in FIG. 11, one device management apparatus 101 is shown as an example. The server 102 and the storage device 103 have the same configuration as the server 102 and the storage device 103 shown in FIG.

  The device management apparatus 201 is, for example, a HEMS (Home Energy Management System) provided in a facility such as a general home or an office, similarly to the device management apparatus 101 shown in FIG. The device management apparatus 201 manages the sensor 151 by transmitting and receiving information to and from the sensor 151 that has established a communication connection with itself according to a communication protocol such as ZigBee or Z-Wave.

  FIG. 12 is a diagram showing a configuration of a device management apparatus according to the second embodiment of the present invention.

  Referring to FIG. 12, device management apparatus 201 includes a communication unit 51, a processing unit 52, a storage unit 53, and a reception unit 54. The communication unit 51, the processing unit 52, and the storage unit 53 have the same configuration as the communication unit 11, the processing unit 12, and the storage unit 13 illustrated in FIG.

  For example, when the user presses a pairing button (not shown) provided in the device management apparatus 201, the reception unit 54 detects the pressing of the pairing button and stores its own device management apparatus stored in the storage unit 53. A pairing request including the device ID 201 is transmitted to the server 102 via the communication unit 51 and the network 161.

  Referring to FIG. 11 again, when receiving the pairing request from the device management apparatus 201, the server 102 acquires the corresponding sensor information from the database stored in the storage device 103. Then, the server 102 extracts a sensor ID corresponding to the device ID included in the pairing request from the device management apparatus 201 from the acquired corresponding sensor information. Then, the server 102 transmits a communication connection command including the extracted sensor ID to the device management apparatus 201 via the network 161.

  When receiving the communication connection command from the server 102 via the network 161, the device management apparatus 201 starts an operation in the pairing mode, like the device management apparatus 101 according to the first embodiment described above.

[Operation]

  FIG. 13 is a diagram showing an example of a sequence defining a procedure for establishing a communication connection in the device management system according to the second embodiment of the present invention.

  Referring to FIG. 13, first, device management apparatus 201 accepts an operation of a pairing button provided on itself (step S41). When the device management apparatus 201 detects that the pairing button has been pressed, the device management apparatus 201 transmits a pairing request including the device ID of its own device management apparatus 201 to the server 102 via the network 161 (step S42).

  Next, when the server 102 receives the pairing request from the device management apparatus 201, the server 102 acquires corresponding sensor information stored in the storage device 103, and based on the acquired corresponding sensor information, the server 102 receives the corresponding sensor information. A sensor ID corresponding to the device ID included in the pairing request is acquired. Here, it is assumed that the device ID included in the pairing request is “H1111” and the sensor IDs corresponding to the device ID are “S0001” and “S0002” (step S43).

  Next, the server 102 transmits a communication connection command including the acquired sensor IDs “S0001” and “S0002” to the device management apparatus 201 that is the transmission source of the pairing request via the network 161 (step S44).

  Next, when receiving a communication connection command from the server 102 via the network 161, the device management apparatus 201 starts an operation in the pairing mode (step S45).

  In the period when the device management apparatus 201 is operating in the pairing mode, for example, it is assumed that the user presses a pairing button provided on the sensor 151A. In this case, the sensor 151A transmits a connection request including its own sensor ID to the device management apparatus 201 (step S46).

  Next, when receiving a connection request from the sensor 151A, the device management apparatus 201 determines whether or not the transmission source of the received connection request is a target sensor. Here, since the sensor ID “S0001” included in the connection request matches the sensor ID included in the communication connection command from the server 102, the device management apparatus 201 transmits the sensor 151A that is the transmission source of the connection request. Is a target sensor and accepts a connection request from the sensor 151A (step S47).

  Next, the device management apparatus 201 transmits a connection response indicating that the connection request has been accepted to the sensor 151A (step S48).

  Next, the device management apparatus 201 performs a process for establishing a communication connection with the sensor 151A. The device management apparatus 201 has its own device ID “H1111”, the sensor ID “S0001” of the sensor 151A that has established the communication connection with itself, A connection completion notification including the time is transmitted to the server 102 via the network 161 (step S49).

  Next, when receiving the connection completion notification from the device management apparatus 201, the server 102 changes and updates the contents of the table Ta2 stored in the storage device 103 based on the received connection completion notification. Specifically, for example, the server 102 changes the item “last communication time” corresponding to the sensor ID “S0001” in the table Ta2 shown in FIG. 5 from “null” to the time indicated by the connection completion notification. Update (step S50).

  Further, it is assumed that, for example, the user presses a pairing button provided on the sensor 151Z during the period in which the device management apparatus 201 operates in the pairing mode. In this case, the sensor 151Z transmits a connection request including its own sensor ID “S9999” to the device management apparatus 101 (step S51).

  Next, when receiving a connection request from the sensor 151Z, the device management apparatus 201 determines whether or not the transmission source of the received connection request is a target sensor. Here, since the sensor ID “S9999” included in the connection request does not match the sensor ID included in the communication connection command from the server 102, the device management apparatus 201 transmits the sensor 151Z that is the transmission source of the connection request. Is determined to be a non-target sensor, and the connection request from the sensor 151Z is rejected (step S52).

  Next, the device management apparatus 201 transmits a connection response indicating that the connection request has been rejected to the sensor 151Z (step S53).

  Then, the device management apparatus 201 transmits a connection rejection notification including its own apparatus ID “H1111” and the sensor ID “S9999” of the sensor 151Z that rejected the connection response to the server 102 via the network 161 (step S54).

  Since other configurations and operations are the same as those of the first embodiment, detailed description thereof will not be repeated here.

  In addition, some or all of the functions of the server 102 and the storage device 103 according to the first and second embodiments of the present invention may be provided by cloud computing. That is, the server 102 and the storage device 103 according to the first and second embodiments of the present invention may be configured by a plurality of cloud servers or the like.

  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.

  The above description includes the following features.

[Appendix 1]
A device management device,
A communication unit that is capable of communicating with one or a plurality of slave units and receives identification information of a target slave unit that is the slave unit that is permitted to communicate with the device management apparatus of itself from another device;
Based on the identification information received by the communication unit, a processing unit that selectively permits a connection request from the target child device and establishes a communication connection with the target child device, and
The communication unit performs transmission / reception of information to / from the slave unit having established a communication connection with the device management apparatus according to ZigBee or Z-Wave communication protocol,
The said subunit | mobile_unit is an equipment management apparatus which is a temperature / humidity sensor, a door opening / closing sensor, or a human sensor provided in the facility.

[Appendix 2]
A communication unit that receives, from another device, identification information of a target child device that is a child device that is permitted to communicate with the device management device;
A display processing unit that performs processing for displaying the identification information received by the communication unit on a screen;
In addition to the identification information, the communication unit further includes at least one of a connection state between the target slave unit and the device management apparatus and a latest communication time between the target slave unit and the device management apparatus. Receiving connection state information indicating one from the other device;
The display processing unit, based on the connection state information received by the communication unit, the connection state between the target slave unit and the device management device, and the latest communication between the target slave unit and the device management device A terminal device that performs processing for further displaying at least one of the times.

[Appendix 3]
An acquisition unit for acquiring first correspondence information indicating a correspondence relationship between the identification information of the device management apparatus and the identification information of the slave unit;
A processing unit that acquires identification information of the target device management apparatus and transmits a command to establish a communication connection with the slave unit to the target device management apparatus,
The processing unit transmits the command including the identification information of the slave unit corresponding to the identification information of the target device management apparatus based on the first correspondence information acquired by the acquisition unit,
When the communication connection between the target device management apparatus and the slave is established, the processing unit receives a connection completion notification indicating that a communication connection has been established via the acquisition unit, and the received connection completion Send a notification to the terminal device via the acquisition unit,
When the connection request from the slave unit to the target device management apparatus is rejected, or when the communication connection between the target device management apparatus and the slave unit is disconnected, the processing unit, from the slave unit A connection refusal notification indicating that the connection request is rejected or that the communication connection between the device management apparatus and the slave unit has been disconnected is received via the acquisition unit, and the received connection completion notification is acquired. A management support apparatus that transmits the information to the terminal device via a unit.

11, 51 Communication unit 12, 52 Processing unit 13, 53 Storage unit 21 Communication unit (acquisition unit)
DESCRIPTION OF SYMBOLS 22 Processing part 31 Reception part 32 Display processing part 33 Communication part 34 Storage part 54 Reception part 101,201 Device management apparatus 102 Server (management support apparatus)
103 Storage Device 131 Terminal Device 151 Sensor (Slave Device)
161 Network 301, 302 Device management system

Claims (13)

A device management device,
A communication unit that is capable of communicating with one or a plurality of slave units and receives identification information of a target slave unit that is the slave unit that is permitted to communicate with the device management apparatus of itself from another device;
A processing unit that performs processing for selectively allowing a connection request from the target slave unit and establishing a communication connection with the target slave unit based on the identification information received by the communication unit. Management device.   The processing unit is a process of refusing a connection request from a non-target child device that is a child device that is not permitted to communicate with the device management apparatus of itself, or disconnecting a communication connection with the non-target child device The device management apparatus according to claim 1, wherein a connection rejection notification indicating that a connection request is rejected or a communication connection disconnection process is performed is transmitted to another apparatus via the communication unit. A communication unit that receives, from another device, identification information of a target child device that is a child device that is permitted to communicate with the device management device;
A terminal device comprising: a display processing unit that performs a process of displaying the identification information received by the communication unit on a screen.   The display processing unit indicates that a connection request from a non-target child device that is a child device that is not permitted to communicate with the device management device is rejected, or between the device management device and the non-target child device. The terminal device according to claim 3, further performing a process of displaying that the communication connection has been disconnected. An acquisition unit for acquiring first correspondence information indicating a correspondence relationship between the identification information of the device management apparatus and the identification information of the slave unit;
A processing unit that acquires identification information of the target device management apparatus and transmits a command to establish a communication connection with the slave unit to the target device management apparatus,
The processing unit transmits the command including the identification information of the slave unit corresponding to the identification information of the target device management apparatus based on the first correspondence information acquired by the acquisition unit. . The acquisition unit further acquires second correspondence information indicating a correspondence relationship between the identification information of the user and the identification information of the device management apparatus;
The processing unit acquires identification information of the target user, and further, based on the second correspondence information acquired by the acquisition unit, identification information of the device management apparatus corresponding to the identification information of the target user The management support apparatus according to claim 5, wherein the management support apparatus acquires the information as identification information of the target device management apparatus. A device management apparatus capable of communicating with one or a plurality of slave units;
A management support device that transmits a command for establishing a communication connection with the slave unit to the device management device;
The management support device, based on first correspondence information indicating a correspondence relationship between the identification information of the device management device and the identification information of the child device, of the child device corresponding to the identification information of the target device management device A device management system that transmits the command including identification information to the target device management apparatus. A device management method in a device management apparatus,
Receiving, from another device, identification information of a target child device that is a child device that is permitted to communicate with the device management device;
And a step of selectively allowing a connection request from the target slave unit and establishing a communication connection with the target slave unit based on the received identification information. A display processing method in a terminal device,
Receiving the identification information of the target slave unit that is a slave unit allowed to communicate with the device management device from another device;
And a process of displaying the received identification information on a screen. A device management method in a management support device that transmits a command for establishing a communication connection with a slave device to a device management device,
Obtaining first correspondence information indicating a correspondence relationship between identification information of the device management apparatus and identification information of the slave unit, and identification information of the target device management apparatus;
Based on the acquired first correspondence information and identification information of the target device management apparatus, the command including the identification information of the slave corresponding to the identification information of the target device management apparatus is transmitted to the target device management. A device management method comprising: transmitting to the device. A device management program used in a device management apparatus,
Computer
A communication unit that is capable of communicating with one or a plurality of slave units and receives identification information of a target slave unit that is the slave unit that is permitted to communicate with the device management apparatus of itself from another device;
Based on the identification information received by the communication unit, a processing unit that performs processing for selectively allowing a connection request from the target child device and establishing a communication connection with the target child device;
Device management program to function as A display processing program used in a terminal device,
Computer
A communication unit that receives, from another device, identification information of a target child device that is a child device that is permitted to communicate with the device management device;
A display processing unit for performing processing for displaying the identification information received by the communication unit on a screen;
Display processing program to function as A device management program used in a management support device,
Computer
An acquisition unit for acquiring first correspondence information indicating a correspondence relationship between the identification information of the device management apparatus and the identification information of the slave unit;
A processing unit for acquiring identification information of the target device management apparatus and transmitting a command to establish a communication connection with the slave unit to the target device management apparatus,
As a program to function as
The processing unit transmits the instruction including the slave unit identification information corresponding to the identification information of the target device management apparatus based on the first correspondence information acquired by the acquisition unit. .

Images