JP2010177772A - Apparatus for management of equipment - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a remote management system capable of reliably performing communication with a simple structure without causing trouble in the communication even when a plurality of facility equipment groups are connected to a remote management device through different communication carriers and even in the case of a communication carrier in which a private address set in each device dynamically changes. <P>SOLUTION: In this remote management system, connection devices each including: a conversion table storage part for storing address conversion tables each used for relating a device identifier to a communicating address on a communication carrier basis; a communication request reception part for receiving a communication request using the device identifier; an address conversion part for determining the communicating address in a relevant carrier as a communication destination address by referring to the address conversion table; and a communication part for starting communication based on the communication request received by the communication request reception part are respectively inserted between a remote management device and a network and between a plurality of equipment and the network. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a remote management system that manages a plurality of facility devices, and more particularly to a remote management system that transmits and receives data via an IP network and remotely manages a plurality of facility devices such as an air conditioner.

  Equipment equipment such as air conditioners and lighting fixtures installed in buildings and the like are increasingly managed by equipment equipment management devices that collect information on their operating status. Such an equipment management device exists remotely from equipment and equipment management equipment, and remote management devices that remotely manage equipment are often connected.

  A remote management device is installed in a management center or service center, and a plurality of equipment and equipment management devices are connected via a network, and the operation status of each equipment and equipment management device is monitored by the remote management device. Control. In a network that connects such remote management devices and a plurality of equipment, and equipment management devices, information on the operating status of each equipment is sent to the remote management device as a daily report. The device is configured to download from the remote management device.

  As a network that connects such a remote management device, a plurality of facility devices, and a facility device management device, a network provided by a predetermined communication carrier can be used. In the communication carrier, a private address is set for each of the connection system on the remote management device side and the connection system on the facility device side, and a network for connecting the remote management device and each facility device can be constructed.

  The connection system on the remote management device side and the connection system on each facility device side each store a private address set by a communication carrier, and can communicate by designating a private address as a connection destination. .

  When a remote management device is connected to multiple equipment groups, a virtual dedicated path for each equipment group is set in the communication carrier to maintain security between the equipment groups. It has been proposed that the identification code to be set is added to the address for transmission.

  For example, in the technique described in Patent Document 1 (Japanese Patent Laid-Open No. 2001-345843), a private network is connected between a remote connection means serving as an IP network entrance and network termination means connected to a plurality of private networks. A virtual dedicated path is set for each. An identification code is added to the network address on the remote connection means side, and the identification code added to the address is discriminated in the connection control means connected to the remote connection means by the virtual dedicated path and distributed to the virtual dedicated path. ing.

  In such a case, a connection control is performed in which an identification code set for each virtual dedicated path is added to the network address and transmitted, distributed to the virtual dedicated path based on the identification code, and transmitted after deleting the identification code from the network address. Configuration of the means is required.

  In some cases, the remote management apparatus is connected to a network via a different communication carrier for each of a plurality of equipment groups. In this case, a private address is set for each communication carrier with respect to the connection system on the remote management apparatus side and the connection system on the equipment side. Here, the private address used by each communication carrier is an IP address used in an Internet protocol such as IPv4 or IPv6, and the range that can be used as a private address is limited. Therefore, there is a possibility that the private addresses set in the connected devices are duplicated among a plurality of communication carriers.

  In such a case, when communication is performed from the remote management device to each facility device, there is a possibility that normal communication cannot be performed due to duplication of addresses. It may be possible to add an identification code to the address in the connection system on the remote management device side, and to provide a connection control means that distributes the transmission destination based on this identification code. There is a problem such as an increase.

  Furthermore, a communication carrier that connects between a remote management device and a plurality of facility devices may dynamically change a private address assigned to each device. For example, if there is a communication request, it can be assumed that the IP address of the communication source and the communication destination is set each time within the range of private addresses that can be used, and the correspondence between each device and the private address is not saved after the communication is completed. In such a case, the connection system on the remote management device side may not be able to communicate with an appropriate destination even if the destination address is stored.

  Furthermore, when the number of facility devices managed by the remote management device increases, it is difficult to individually assign a communication destination address to each facility device. In particular, when a plurality of communication carriers are used to connect between a remote management device and each facility device, it becomes difficult to assign unique communication destination addresses to all the facility devices to be managed. There is a problem that two-way communication cannot be performed between facility devices to which a unique communication destination address could not be assigned.

  In the present invention, when a plurality of equipment groups are connected to a remote management apparatus via different communication carriers, or in a communication carrier to which a remote management apparatus and a plurality of equipment are connected, the private address set for each apparatus is dynamic. It is an object of the present invention to provide a remote management system that can reliably perform communication with a simple configuration without causing any trouble in communication even if it changes.

  Even if there are multiple communication carriers connecting between the remote management device and each facility device, or even when the communication carrier cannot set a communication address for all the facility devices, the remote management device The purpose is to apply a remote management system in which each facility device is uniquely specified to enable two-way communication.

  A remote management system according to a first aspect of the present invention is a remote management system in which a plurality of devices and a remote management device that remotely manages the plurality of devices are connected via a network, the remote management device and the remote management device Conversion for storing for each communication carrier an address conversion table for associating a device identifier for identifying a plurality of devices with communication addresses set by the communication carrier providing the network to the remote management device and the plurality of devices. Based on a communication request received by the communication request receiving unit, a communication request receiving unit that receives a communication request using the device identifier from any of the table storage unit, the remote management device and the plurality of devices, With reference to the address conversion table, the communication address in the corresponding communication carrier is set to the communication destination address of the communication request. A connection device comprising: an address conversion unit determined as: a communication unit that starts communication based on a communication request received by the communication request reception unit using the communication destination address determined by the address conversion unit; The remote management system is inserted between a management device and the network and between the plurality of devices and the network.

  In this case, even when there are a plurality of communication carriers connecting the remote management device and a plurality of devices, and there is an overlap in communication destination addresses used by each communication carrier, an appropriate communication destination address can be obtained by referring to the address conversion table. Can be connected.

  Here, a local controller connected to the plurality of devices is provided for each of one or a plurality of groups, and each of the local controllers is connected to the network via the connection device and transmitted from the remote management device. A plurality of devices in the corresponding group can be controlled based on the control signal.

  In this case, it is possible to reliably perform communication between the local controller and the remote management device even when connected to the remote management device via a different communication carrier for each group.

  In a remote management system according to another aspect of the present invention, a plurality of devices and a remote management device that remotely manages the plurality of devices are connected via a network, and the remote management device and the network, and between the plurality of devices and the network, respectively. A remote management system in which a connection device is inserted, wherein each connection device has a device identifier for identifying the remote management device and a plurality of devices, and a communication carrier that provides a network is connected to the remote management device and the plurality of devices. An address conversion table for associating a communication address to be set for each communication carrier, and a communication request receiving unit for receiving a communication request using a device identifier from either the remote management device or a plurality of devices And referring to the address conversion table based on the communication request received by the communication request receiving unit. Communication based on the communication request received by the communication request receiving unit using the address conversion unit that determines the communication address in the communication carrier as the communication destination address of the communication request and the communication destination address determined by the address conversion unit. A communication unit that starts, an address update unit that updates an address conversion table based on a communication address change notification transmitted from a communication carrier or a changed communication address transmitted from another connection device, and communication An address change notification unit that transmits the communication address changed based on the communication address change notification transmitted from the carrier to another connection device.

  In this case, even if the communication address set for each device in the communication carrier is dynamically changed, the address conversion table is sequentially updated, so that appropriate communication is possible using the address conversion table.

  Here, a local controller connected to a plurality of devices is provided for each of one or a plurality of groups, and each local controller is connected to a network via a connection device and is based on a control signal transmitted from a remote management device. It can be configured to control a plurality of devices in the corresponding group.

  In this case, communication between the local controller and the remote management device can be performed appropriately, and a plurality of devices can be controlled via the local controller.

  A connection device according to another aspect of the present invention is a remote management system in which a plurality of devices and a remote management device that remotely manages the plurality of devices are connected via a network. A connection device inserted between the networks, a device identifier for identifying the remote management device and the plurality of devices, and a communication address set by the communication carrier providing the network to the remote management device and the plurality of devices An address conversion table for each communication carrier, a communication request receiving unit for receiving a communication request using a device identifier from one of the remote management device and a plurality of devices, and a communication request receiving The address conversion table is referenced based on the communication request received by the Communication that starts communication based on the communication request received by the communication request receiving unit using the address conversion unit that determines the communication address in the communication request address as the communication destination address of the communication request and the communication destination address determined by the address conversion unit A part.

  In this case, an address conversion table for associating the communication address set by the communication carrier with the device identifier is stored in the conversion table storage unit. A communication address is selected to enable reliable communication.

  A connection device according to still another aspect of the present invention is a remote management system in which a plurality of devices and a remote management device that remotely manages the plurality of devices are connected via a network. And a device identifier for identifying the remote management device and the plurality of devices, and a communication address set by the communication carrier providing the network to the remote management device and the plurality of devices. An address conversion table for each communication carrier, a communication request receiving unit for receiving a communication request using a device identifier from one of the remote management device and a plurality of devices, and a communication request receiving The address conversion table is referred to based on the communication request received by the The communication based on the communication request received by the communication request receiving unit is started using the address conversion unit that determines the communication address in the network as the communication destination address of the communication request and the communication destination address determined by the address conversion unit. From the communication unit, the address update unit that updates the address conversion table based on the communication address change notification transmitted from the communication carrier or the changed communication address transmitted from another connection device, and the communication carrier An address change notification unit that transmits the communication address changed based on the transmitted communication address change notification to another connection device.

  In this case, even if the communication carrier connecting the remote management device and a plurality of devices dynamically changes the communication address set for each device, the address conversion stored in the conversion table storage unit By sequentially updating the table, it is possible to reliably communicate with an appropriate communication address.

  Further, in the remote management system according to another embodiment of the present invention, a device group including one or a plurality of devices and a remote management device that remotely manages each device included in the device group are connected via a network. A remote management system comprising a first connection device inserted between a remote management device and a network, and a second connection device inserted between a plurality of devices and the network, wherein the first connection device identifies a device group A first conversion table that stores, for each communication carrier, a first address conversion table that associates a representative identifier for communication with a communication address set by a communication carrier providing a network to a device corresponding to the representative identifier in the device group A communication request using a device identifier composed of a storage unit and a representative identifier from the remote management device and a sub-identifier for identifying each device in the device group is issued. A communication address in a communication carrier corresponding to the representative identifier in the device identifier by referring to the first address conversion table based on the communication request received by the first communication request receiving unit and the communication request received by the first communication request receiving unit. Using the first address conversion unit that determines the communication destination address of the communication request and the communication destination address determined by the first address conversion unit in the communication request received by the first communication request reception unit A first communication unit that starts communication with a sub-identifier attached, and the second connection device includes a sub-identifier in the device identifier and a private address set in the device group corresponding to the sub-identifier. A second conversion table storage unit that stores a second address conversion table to be associated and a communication address of a device in which a representative identifier is set are transmitted as communication destination addresses. A second communication request receiving unit that receives the communication request and a sub-address attached to the communication request by referring to the second address conversion table based on the sub-identifier attached to the communication request received by the second communication request receiving unit. A second address conversion unit that determines a private address in the device group of the device corresponding to the identifier as a communication destination address of the communication request, and a second communication request using the communication destination address determined by the second address conversion unit. And a second communication unit that starts communication based on the communication request received by the receiving unit.

  In this case, bidirectional communication from a remote device is possible for all devices included in the device group.

  Here, the first connection device updates the first address conversion table based on the communication address change notification transmitted from the communication carrier or the changed communication address transmitted from another connection device. A first address change notification unit that transmits a first communication address changed based on a communication address change notification transmitted from a communication carrier to another connection device; The connection device includes a second address update unit that updates the second address conversion table based on a change notification of the communication address transmitted from the communication carrier or the changed communication address transmitted from another connection device. The second address for transmitting the communication address changed based on the communication address change notification transmitted from the communication carrier to another connection device. It can be configured to include a less change notification unit.

  According to the present invention, it is possible to perform appropriate communication even when there are overlaps in private addresses used by a plurality of communication carriers. Further, according to the present invention, communication with an appropriate communication destination is possible even when the private address set for each device is dynamically changed.

1 is a schematic configuration diagram of a first embodiment of the present invention. The functional block diagram of a connection apparatus. Explanatory drawing which shows an example of an address conversion table. Explanatory drawing which shows the other example of an address conversion table. The flowchart of 1st Embodiment. The functional block diagram of the connection apparatus of 2nd Embodiment. The flowchart of 2nd Embodiment. 1 is a configuration diagram of Embodiment 1. FIG. FIG. 3 is a functional block diagram of the remote management device according to the first embodiment. FIG. 3 is a functional block diagram of a local controller according to the first embodiment. FIG. FIG. 6 is a configuration diagram of Example 3. FIG. FIG. 10 is an explanatory diagram illustrating an example of an address conversion table used in the fourth embodiment. The outline block diagram of 3rd Embodiment. The functional block diagram of a 1st connection apparatus. The functional block diagram of a 2nd connection apparatus. Explanatory drawing of a 1st address conversion table. Explanatory drawing of a 2nd address conversion table. FIG. 6 is a configuration diagram of Example 5.

  Hereinafter, a remote management system according to an embodiment of the present invention will be described with reference to the drawings.

<< First Embodiment >>
FIG. 1 is an explanatory diagram showing a schematic configuration of a remote management system according to the first embodiment of the present invention.

  In FIG. 1, equipment devices 16-1 to 16-m, 17-1 to 17-n such as air conditioners and lighting fixtures installed in one or more buildings are connected via communication carriers 12 and 13. 1 shows a system for remote management by a remote management device 10. Although what is illustrated assumes the case where two installation equipment groups are managed, it is not limited to this, It can comprise so that 1 or several installation equipment groups may be managed remotely.

  The remote management device 10 receives information on the operation status from each equipment device as a daily report, transmits control information and firmware update information for each equipment device, and downloads necessary firmware to each equipment device.

  The remote management device 10 is connected to the communication carriers 12 and 13 via the connection device 11.

  The connection device 11 includes a communication destination address conversion table. When a communication request from the remote management device 10 is generated, the connection device 11 refers to the address conversion table and converts it into a corresponding communication destination address. Select the appropriate route and start communication.

  Communication carriers 12 and 13 provide different communication paths corresponding to each equipment group of equipment equipment 16-1 to 16-m, 17-1 to 17-n, and each connected device By setting a private address, a network capable of communication using the Internet protocol is provided.

  The communication carrier 12 is connected to the equipment devices 16-1 to 16-m via the connection device 14. The communication carrier 13 is connected to the equipment devices 17-1 to 17-n via the connection device 15.

  Similar to the connection device 11 installed on the remote management device 10 side, the connection devices 14 and 15 have an address conversion table of the communication destination, and refer to the address conversion table when a communication request from the equipment side occurs. Thus, by converting to a corresponding communication destination address, a route corresponding to the communication destination is selected and communication is started.

  Equipment devices 16-1 to 16-m and 17-1 to 17-n include equipment such as air conditioners and lighting equipment. In the case of air conditioners, the control unit on the indoor unit side or the outdoor unit side It is possible to adopt a configuration in which both control units are connected to the connection devices 14 and 15, and both are connected to the connection devices 14 and 15 so that the indoor unit and the outdoor unit can be individually controlled. Is also possible.

<Connecting device>
In the remote management system as described above, a unique device identifier is assigned to each of the remote management device 10, the equipment 16-1 to 16-m, and 17-1 to 17-n. When communicating with a device, a communication request is generated using the device identifier of the communication destination.

  In addition, in the communication carriers 12 and 13, a private address is assigned to each device that provides a network, and a child and a work using the IP protocol are provided using the private address.

  In connection devices 11, 14, and 15, the correspondence between the device identifier used in the remote management system and the private address used by the communication carrier is held as an address conversion table. If there is a communication request from the device, address conversion is performed. The communication destination address is determined with reference to the table, and communication is started based on the communication destination address.

  The configuration of such connection devices 11, 14, and 15 will be described using the blocks shown in FIG. Here, the connection device 11 is shown as a representative, but the connection devices 14 and 15 can have the same configuration.

  The connection device 11 includes a control unit 21 that controls each unit including a CPU, a ROM, a RAM, a conversion table storage unit 22 that stores an address conversion table, a communication request reception unit 23 that receives a communication request from the device, An address conversion unit 24 and a communication unit 25 are provided.

  The conversion table storage unit 22 is a unique device identifier assigned to each device such as the remote management device 10, the equipment 16-1 to 16-m, 17-1 to 17-n in the remote management system, An address conversion table for associating private addresses set to devices to which the communication carriers 12 and 13 are connected is stored.

  An example of the address conversion table is shown in FIG.

  As shown in FIG. 3, the address conversion table 31 includes items of a device identifier column 32 and an address column 33.

  The address conversion table 31 is created for each communication carrier, and stores a correspondence between a device identifier of a device connected to each communication carrier and a private address set for the device. The device identifier column 32 stores a unique device identifier for specifying each device used in the remote management system. The address column 33 stores a private address set by the communication carrier for the device. The illustrated example shows a case where the private address set by the communication carrier is “192.168.1.1” for the device assigned the device identifier “A00001”. In this example, the case where the private address set by the communication carrier is an IPv4 compliant address is shown.

  In this way, when creating an address conversion table for each communication carrier and storing it in the conversion table storage unit 22, in order to identify which communication carrier each device is connected to, a device identifier It is also possible to prepare a table showing the correspondence between communication carriers and communication carriers.

  Another example of the address conversion table is shown in FIG. The address conversion table 41 shown in FIG. 4 includes a device identifier column 42, a communication carrier column 43, and an address column 44. The device identifier column 42 stores a unique device identifier for specifying each device used in the remote management system. The communication carrier column 43 stores a communication carrier identifier for specifying a communication carrier to which the device is connected. The address field 43 stores a private address set by the communication carrier for the device. This example also shows a case where the private address set by the communication carrier is “192.168.1.1” for the device assigned the device identifier “A00001”. In this example, as described above, a case where the private address set for each device by the communication carrier is an address based on IPv4 is shown.

  The communication request receiving unit 22 receives a communication request transmitted to the equipment from the remote management device 10, and notifies the control unit 11 that there has been a communication request for the communication destination specified by the device identifier. Send to.

  Based on the device identifier specified in the communication request, the address conversion unit 24 refers to the address conversion table stored in the conversion table storage unit 22, and identifies the private address set for the device by the corresponding communication carrier To do. The address conversion unit 24 changes the device identifier in the communication request to the private address of the specified communication carrier.

  The communication unit 25 starts communication between corresponding devices based on the communication destination address converted by the address conversion unit 24.

<Communication processing>
Processing in the connection device 11 when there is a communication request from the remote management device 10 will be described based on the flowchart shown in FIG.

  When the remote management device 10 communicates with any of the equipment devices 16-1 to 16-m, 17-1 to 17-n connected via the communication carriers 12 and 13, the corresponding device identifier is transmitted to Send the communication request specified as. In the connection device 11, the communication request receiving unit 23 receives the communication request transmitted from the remote management device 10 (step S51).

  When the communication request receiving unit 23 receives a communication request from the remote management device 10, the control unit 21 refers to the address conversion table (31, 41) stored in the conversion table storage unit 22 (step S52), and a communication request is being made. A communication carrier to which a corresponding device is connected by searching for the device identifier specified in the above and a communication destination address set in the device by the communication carrier are specified (step S53).

  The control unit 21 changes the device identifier in the communication request transmitted from the remote management device 10 to the corresponding communication destination address, and starts communication processing via the corresponding communication carrier (step S54).

  According to 1st Embodiment of this invention comprised in this way, when several installation equipment groups are connected via several communication carriers, each communication carrier sets with respect to each installation apparatus. Even when private addresses to be overlapped, since the address conversion table is provided for each communication carrier, communication to an appropriate communication destination is possible.

  Here, the connection device 11 connected to the remote management device 10 has been described, but the connection devices 14 and 15 connected to the equipment side can also have the same configuration. For example, when performing communication to the remote management device based on a communication request from each facility device, the communication destination address is determined by referring to the address conversion table based on the device identifier specified in the communication request. The communication can be configured to start based on the communication destination address.

<< Second Embodiment >>
A remote management system according to a second embodiment of the present invention will be described.

  The general configuration of the remote management system according to the second embodiment is the same as that shown in FIG. 1 as in the first embodiment. Among these, the configuration of the connection device 11 will be described below.

  The connection device 11 used in the second embodiment has a configuration as shown in FIG.

  The connection device 11 includes a control unit 21 that controls each unit including a CPU, a ROM, a RAM, a conversion table storage unit 22 that stores an address conversion table, a communication request reception unit 23 that receives a communication request from the device, An address conversion unit 24, a communication unit 25, an address update unit 61, and an address change notification unit 62 are provided.

  The conversion table storage unit 22 is a unique device identifier assigned to each device such as the remote management device 10, the equipment 16-1 to 16-m, 17-1 to 17-n in the remote management system, An address conversion table for associating private addresses set to devices to which the communication carriers 12 and 13 are connected is stored.

  As the address conversion table stored in the conversion table storage unit 22, the one shown in FIG. 3 or 4 can be used.

  The communication request receiving unit 22 receives a communication request to the equipment transmitted from the remote management device 10, and notifies the control unit 21 that there is a communication request for the communication destination specified by the device identifier. Send to.

  Based on the device identifier specified in the communication request, the address conversion unit 24 refers to the address conversion table stored in the conversion table storage unit 22, and identifies the private address set for the device by the corresponding communication carrier To do. The address conversion unit 24 changes the device identifier in the communication request to the private address of the specified communication carrier.

  The communication unit 25 starts communication between corresponding devices based on the communication destination address converted by the address conversion unit 24.

  The address update unit 61 uses the address conversion stored in the conversion table storage unit 22 based on the communication address change notification transmitted from the communication carrier or the changed communication address transmitted from another connected device. Update the table. For example, when the communication carrier dynamically changes the private address set for each device, an address change notification is transmitted together with the changed private address from the connected communication carrier. Based on the address change notification transmitted from the communication carrier, the address update unit 61 updates the address conversion table stored in the conversion table storage unit 22. In another device (facility equipment or remote management device), if the connected communication carrier changes the private address set in the device, the private address changed from that device At the same time, an address change notification is sent. The address update unit 61 updates the address conversion table stored in the conversion table storage unit 22 based on the address change notification transmitted from the other connection device.

  Based on the address change notification transmitted from the communication carrier, the address change notification unit 62 transmits an address change notification together with the changed private address to other connection devices.

  In the above description, the configuration of the connection device 11 connected to the remote management device 10 has been described. However, the connection devices 14 and 15 connected to the facility equipment side can also have the same configuration.

<Address update processing>
The address update process in the second embodiment of the present invention will be described based on the flowchart shown in FIG.

  When the communication unit 25 receives the address change notification from the other connection devices 14 and 15 or the address change notification from the connected communication carrier (step S17), the connection device 11 receives the address change notification from the other connection device. The control unit 21 determines whether or not it is from 14, 15 (step S72).

  When the control unit 21 determines that the address change notification is transmitted from another connection device 14 or 15, the address update unit 61 updates the address conversion table stored in the conversion table storage unit 22. (Step S73).

  The control unit 21 determines whether or not the address change notification is transmitted from the communication carriers 12 and 13 (step S74).

  When the control unit 21 determines that the address change notification is transmitted from the communication carriers 12 and 13, the address change notification unit 62 generates an address change notification for the other connection devices 14 and 15, and generates another connection. The data is transmitted to the devices 14 and 15 (step S75). Thereafter, the control unit 21 executes another process (step S76) and ends the process.

  The address update process has been described as a process executed by the connection device 11 connected to the remote management device 10, but the connection devices 14 and 15 on the equipment side can also be configured to execute the same process.

  When there is a communication request from each connected device, the communication carriers 12 and 13 may dynamically change the private address set in each device each time. In such a case, there is a possibility that communication according to a communication request from a device to which the connection devices 11, 14, and 15 are connected cannot be performed.

  According to the second embodiment of the present invention, even if the communication carriers 12 and 13 dynamically change the private address in this way, the contents of the address conversion table stored in the conversion table storage unit 22 are Since it is updated each time, an appropriate communication destination address can be selected according to a communication request from each device, and normal communication is possible.

  In the remote management system according to the present invention, a configuration in which the connection device 11 is built in the remote management device 10 and a configuration in which the connection devices 14 and 15 are built in the local controller that supervises the equipment are shown as a first embodiment.

  FIG. 8 is a configuration diagram of the remote management system according to the first embodiment.

  The remote management system according to the first embodiment includes a remote management device 10, firewalls 81 and 82, modem routers 83 and 84, modems 85 and 86, local controllers 87 and 88, and equipment devices 16-1 to 16-m, 17-1. It consists of ~ 17-n.

  The remote management device 10 receives information related to the operation status from each equipment device as a daily report, transmits control information and firmware update information for each equipment device, and downloads necessary firmware to each equipment device. And the configuration of the connection device 11 is included therein.

  The remote management device 10 can be configured by a general computer system such as a personal computer or a workstation, and includes a control unit 91, a communication interface 92, an input / output interface 93, and the like as shown in FIG. Yes. The control unit 91 includes a CPU for controlling each unit of the computer system, a ROM for storing various parameters and BIOS, a RAM that is a temporary storage unit necessary for various calculations, and the like. The communication interface 92 is an interface for providing data input / output with other devices. The input / output interface 93 receives an instruction signal input by an operator via a keyboard, a mouse, or the like, and provides an interface for displaying various information on a display or the like.

  The remote management device 10 further stores various parameters of the connected equipment 16-1 to 16-m, 17-1 to 17-n and data such as daily reports sent in the database 96, as necessary. The device management unit 94 that provides editing processing to the user, the equipment device 16-1 to 16-m, 17-1 to 17-n based on the current operating status and instructions from the operator, the instruction signal for each equipment device A device control unit 95 that generates and transmits to the corresponding facility device is provided. The device management unit 94 and the device control unit 95 can function as a remote management server by starting a predetermined application on the remote management device 10 configured by a computer system.

  The connection device 11 of the first embodiment or the second embodiment described above can be configured in the remote management device 10. In this case, the control unit 21 of the connection device 11 can be the same as the control unit 91 of the remote management device 10.

  The firewalls 81 and 82 are connected to the communication carriers 12 and 13 to be connected via the modem routers 83 and 84, respectively. The firewalls 81 and 82 prevent unauthorized access from the outside by performing packet filtering, and can also be configured as a single hardware configuration. , 84 can be configured by software.

  The modem routers 83 and 84 are provided for the communication carriers 12 and 13, respectively, to establish a communication path via the communication carriers 12 and 13, and the local router on which the remote management device 10 is installed and the communication carrier It has a routing function to interconnect between networks provided by 12,13.

  On the equipment devices 16-1 to 16-m and 17-1 to 17-n sides, local controllers 87 and 88 that perform control in a unified manner for each device group are provided.

  The local controllers 87 and 88 are provided for each set of predetermined equipment such as each building and each client, and control each equipment. For example, the local controller 87 is installed in the local area network to which the equipment devices 16-1 to 16-m are connected, and data regarding the operating status of each equipment device 16-1 to 16-m is transmitted at a predetermined interval. It collects and manages the operational status data of each connected equipment. Similarly, the local controller 88 is installed in the local area network to which the equipment devices 17-1 to 17-n are connected, and data regarding the operating status of each equipment device 17-1 to 17-n It collects data at intervals and manages the operational status data of each connected equipment.

  The local controllers 87 and 88 are connected to the communication carriers 12 and 13 via the modems 85 and 86, respectively, and can communicate with the remote management device 10. As a result, the local controllers 87 and 88 can be configured to transmit the collected operation status data of each equipment device to the remote management device 10 at a predetermined interval, for example, as daily report data once a day. Can be configured.

  The local controllers 87 and 88 can be configured to include the connection devices 14 and 15 respectively, and the configuration in this case is shown in FIG.

  The local controller 87 (88) includes a control unit 1001 including a CPU for controlling each unit, a ROM for storing various parameters, a RAM for providing a storage unit necessary for calculation, and the modem 85 (86) on the communication carrier side. The first communication unit 1002 connected to the LAN, the second communication unit 1003 connected to the LAN on the equipment 16-1 to 16-m (17-1 to 17-n) side, and the operating status collected from each equipment A storage unit 1004 for storing data is provided.

  The local controller 87 (88) includes the connecting device 14 (15) as shown in the first embodiment or the second embodiment. In this case, the control unit 21 of the connection device 14 (15) can be configured in common with the control unit 1001 of the local controller 87 (88).

  Such a local controller 87 (88) includes a management application for equipment, and for example, the equipment 16-1 to 16-m (17-1 to 17-17) via the second communication unit 1003 at intervals of 30 minutes. -n) is configured to collect operational status data for each facility device. The operational status data collected by the local controller 87 (88) includes the values of the sensors attached to the indoor unit and the outdoor unit and the power supply of the outdoor unit and the indoor unit when the equipment is an air conditioner. This includes on / off recordings.

  The control unit 1001 creates management data to be transmitted to the remote management device 10 based on the collected operation status data every time the facility device operation status data is collected every 30 minutes, and stores it in the storage unit 1004 To do. The management data created by the control unit 1001 is calculated based on sensor values such as the maximum and minimum values of each sensor attached to the indoor unit and the outdoor unit, and the degree of supercooling and superheat in the refrigeration cycle. The maximum and minimum parameter values are also included.

  The local controller 87 (88), for example, creates daily report data that summarizes the operation status data of each facility device for one day at a predetermined time once a day, and transmits the daily report data to the remote management device 10.

  When the local controller 87 (88) sends daily report data to the remote management device 10, it generates a communication request packet with the device identifier of the remote management device 10 added to the header and sends it to the connection device 14 (15). To do. In the connection device 14 (15), the control unit 21 refers to the conversion table 22 based on the device identifier given to the packet, specifies the corresponding communication address, and adds the communication address to the header. 1 Send out via communication unit 1002.

  In addition, the local controller 87 (88) instructs to control each facility device 16-1 to 16-m (17-1 to 17-n) based on the control information transmitted from the remote management device 10. A signal is produced | generated and each equipment 16-1-16-m (17-1-17-n) is controlled.

  The connection device 14 (15) thus configured can be configured as application software installed in the local controller 87 (88).

  The modems 85 and 86 can be configured to be included in the local controllers 87 and 88, respectively. For example, the first communication unit 1002 in FIG. 10 can be configured to include a modem function.

  It is also possible to insert the connection devices 14 and 15 as a single hardware configuration between the modems 85 and 86 and the local controllers 87 and 88, respectively.

  In the remote management system according to the present invention, a configuration in which the connection device 11 is built in a firewall for controlling communication with the outside is shown as a second embodiment.

  FIG. 11 is a configuration diagram of a remote management system according to the second embodiment. Hereinafter, description overlapping with that of the first embodiment will be omitted, and description will be made focusing on the features of the second embodiment.

  The remote management system according to the second embodiment includes a remote management device 10, a firewall 81, modem routers 83 and 84, modems 85 and 86, local controllers 87 and 88, equipment devices 16-1 to 16-m, 17-1 to 17 Consists of -n.

  The remote management device 10 according to the second embodiment is different from the remote management device 10 according to the first embodiment in that the configuration of the connection device 11 is not included.

  The firewall 81 is connected to the communication carriers 12 and 13 to be connected via modem routers 83 and 84, respectively. The firewall 81 prevents unauthorized access from the outside by performing packet filtering, and is configured by a single hardware here.

  The firewall 81 has the configuration of the connection device 11. The connection device 11 included in the firewall 81 can have the configuration of the connection device 11 of the first embodiment shown in FIG. 2 or the configuration of the connection device 11 of the second embodiment shown in FIG.

  The configurations of the modem routers 83 and 84, the local controllers 87 and 88, and the modems 85 and 86 are the same as those of the first embodiment, and detailed description thereof is omitted here.

  In the case of the configuration of the second embodiment, it is not necessary to install individual firewalls for the communication carriers 12 and 13, and a single firewall can support a plurality of communication carriers.

  Such a firewall 81 can be incorporated in the remote management device 10 together with the connection device 11. In this case, application software installed in the remote management device 10 together with the firewall 81 and the connection device 11 is also possible. It is also possible to configure.

  When the communication carrier 12 (13) dynamically changes the private address, the address change on the equipment side (local controller 87, 88) is performed from the connection device 14 (15) on the local controller 87 (88) side as a remote management device. 10 is sent as an address change notification. When the connection device 11 on the remote management device 10 side receives the address change notification from the connection device 14 (15) on the local controller 87 (88) side, it updates the corresponding address conversion table in the conversion table storage unit 22, When a communication request is generated from the remote management device 10, communication to a normal communication destination is possible.

  In addition, when the private address set in the connection device 11 on the remote management device 10 side is changed, if the number of local controllers connected to this system is relatively small, the connection device 11 to the equipment device side The address change notification is transmitted to the connection devices 14 and 15 by multicast to notify the private address set on the remote management device 10 side.

  If the number of equipment or local controllers 87 and 88 connected to this remote management system is very large, the amount of packets for sending address change notifications will increase and it will take a long time for communication. The If the local controller 87 (88) makes a communication request to the remote management device 10 while transmitting the address change notification, normal communication may not be possible. As a method for solving such inconvenience, the configuration of the third embodiment will be described below.

  FIG. 12 is a configuration diagram for explaining the configuration of the third embodiment.

  In the remote management system according to the third embodiment, the equipment devices 16-1 to 16-m are connected to the communication carrier 12 via the modem 85 and the local controller 87.

  The remote management device includes two servers, a master and a slave, which are referred to as a remote management device master 1201 and a remote management device backup 1202, respectively. The remote management device master 1201 is connected to the communication carrier 12 through a firewall 81 and a modem router 83 that incorporate the connection device 11. The remote management apparatus backup 1202 is connected to the communication carrier 12 via a firewall 1203 and a modem router 1205 that incorporate the connection apparatus 1204.

  When the local controller 87 makes a communication request to the remote management apparatus master 1201, if normal communication is not possible, a setting is made so that a communication request to the remote management apparatus backup 1202 is made.

  In addition, when the private address set in the remote management device master 1201 is changed, an address change notification indicating that the address has been changed is sent to the connection device 1204 on the remote management device backup 1202 side together with the changed private address. Send.

  If there is a communication from the local controller 87 to the remote management device master 1201 and the remote management device master 1201 has an address change and communication is not possible, the local controller 87 sets the communication address on the remote management device backup 1202 side. Communicate with it. Upon receiving a communication request from the local controller 87, the connection device 1204 on the remote management device backup 1202 side transmits the changed private address of the remote management device master 1201 to the connection device 14 of the local controller 87. Further, the connection device 1204 on the remote management device backup 1202 side transmits the communication request received from the local controller 87 to the connection device 11 of the remote management device master 1201.

  The connection device 14 of the local controller 87 that has received the changed private address on the remote management device master 1201 side from the connection device 1204 on the remote management device backup 1202 side updates the address conversion table in the conversion table storage unit 22, and thereafter Communication is performed using the changed communication address.

  When the connection device 1204 on the remote management device backup 1202 side receives a communication request from the connection device 14 of the local controller 87, if the private address on the remote management device master 1201 side is not changed, the remote management device master 1201 Therefore, the communication request is transmitted to the remote monitoring device backup 1202, and communication on the backup side is started.

  Also, if a communication request from the remote management device master 1201 to the local controller 87 occurs first, a notification that the communication address of the remote management device master 1201 has changed is sent to the local controller 87 side. 14 and then start communication.

  When multiple local controllers are connected to one connection device on the equipment side, the communication carrier sets a private address only for the connection device. Cannot be specified. In such a case, the remote management device can directly control the local controller by adding a part of the device identifier to the packet transmitted to the communication carrier and transmitting the packet.

  FIG. 13 is a configuration diagram for explaining the configuration of the fourth embodiment.

  In the remote management system according to the fourth embodiment, the remote management device 10 is connected to the communication carrier 12 via the connection device 11, the firewall 81, and the modem router 83. Further, the connection device 14 on the facility equipment side is connected to the communication carrier 12 via the modem 85. The connection device 14 is connected to local controllers 87 and 88 that control the equipment devices 16-1 to 16-m and 17-1 to 17-n, respectively.

  In the remote management system configured as described above, the communication carrier 12 sets private addresses for the connection devices 11 and 14.

  Assume that the device identifier of the connection device 14 in this remote management system is “A00001” and the communication carrier 12 sets a private address “192.168.1.1” for the connection device 14.

  A plurality of local controllers 87 and 88 are connected to the connection device 14, and as device identifiers of these local controllers 87 and 88, device identifiers “A00001” of the connection devices 14 are device sub-identifiers “−1”, respectively. , "-2" is added to the device identifier.

  An example of the address conversion table in this case is shown in FIG.

  As shown in FIG. 4, the address conversion table 141 includes items of a device identifier column 142, an address column 143, and a device sub-identifier column 144.

  The address conversion table 141 is created for each communication carrier, and stores the correspondence between the device identifier of the device connected to each communication carrier and the private address set in the device. It is the same. In particular, the device identifier column 142 stores device identifiers of the connection devices 11 and 14 connected to the communication carrier 12.

  The address field 143 stores a private address set by the communication carrier 12 for the device. The illustrated example shows a case where the private address set by the communication carrier is “192.168.1.1” for the connection device 14 to which the device identifier “A00001” is assigned. This example also shows a case where the private address set by the communication carrier is an address compliant with IPv4.

  In the device sub-identifier column 144, device sub-identifiers set by the remote management system for the local controllers 87 and 88 connected to the connection device 14 are stored. For example, when the device sub-identifiers set in the local controllers 87 and 88 are “−1” and “−2”, respectively, these can be configured to be stored.

  When a communication request to the local controllers 87, 88 is transmitted from the remote management device 10 side, the device identifier of the connection device 14 to which the local controllers 87, 88 are connected and the local controllers 87, 88 are set. A packet in which the device identifier to which the device sub-identifier is added is specified as a communication destination is generated and transmitted to the connection device 11.

  The connection device 11 refers to the address conversion table 141 and searches for a device identifier that matches the predetermined bit at the beginning of the device identifier specified as the communication destination of the packet. When the corresponding device identifier hits, this device identifier is specified as the connection device 14 of the communication destination. When the device identifier of the connection device 14 as the communication destination is specified, the device sub-identifier obtained by removing the device identifier of the connection device 14 from the device identifier specified as the communication destination of the packet is the corresponding device sub-identification field. Check whether it exists in 144. If the corresponding device sub-identifier exists in the device sub-identifier column 144, the connecting device 11 uses the private address stored in the corresponding address column 143 as the communication destination of the packet as the communication destination, A communication packet with a device sub-identifier added thereto is generated and transmitted via the communication carrier 12. If there is no corresponding device sub-identifier in the device sub-identifier column 144, the connecting device 11 does not transmit a packet, but transmits a notification that the corresponding device identifier does not exist to the remote management device 10 side.

  When the connection device 14 on the local controller 87, 88 side receives the packet transmitted via the communication carrier 12, the local controller that is the communication destination of the packet is determined using the device sub-identifier added in the packet body. The device identifier specified by adding the device sub-identifier to the device identifier of the connection device 14 is transmitted to the corresponding local controllers 87 and 88 as a packet designated as the communication destination.

  By adopting such a configuration, even when a plurality of local controllers 87 and 88 are connected to the connection device 14, it is possible to perform communication by designating the local controllers 87 and 88 from the remote management device 10. It becomes.

  When private is set for each of the plurality of local controllers 87 and 88, it is not necessary to set a device sub-identifier.

  Each of the equipment devices 16-1 to 16-m and 17-1 to 17-n has a communication function, and is connected to the remote management device 10 through the connection device 14, the modem 85, and the communication carrier 12. Such a case can also be assumed. Also in this case, the same communication as described above can be performed by setting a device identifier including a device sub-identifier for each of the facility devices 16-1 to 16-m and 17-1 to 17-n.

<< Third Embodiment >>
FIG. 15 is an explanatory diagram showing a schematic configuration of a remote management system according to the third embodiment of the present invention.

  In FIG. 15, a system for remotely managing equipment devices 16-1 to 16-m such as air conditioners and lighting fixtures installed in one or more buildings by a remote management device 10 connected via a communication carrier 12. Indicates. In the illustrated example, it is assumed that one facility device group 151 is managed. However, the present invention is not limited to this, and one or a plurality of facility device groups can be remotely managed.

  The remote management device 10 receives information on the operation status from each equipment device as a daily report, transmits control information and firmware update information for each equipment device, and downloads necessary firmware to each equipment device.

  The remote management device 10 is connected to the communication carrier 12 via the first connection device 11.

  The communication carrier 12 sets a communication address for a device that is directly connected to the network provided by the communication carrier 12 in the equipment device group 151. The communication address set by the communication carrier 12 is a private address in the network provided by the communication carrier 12, and is hereinafter referred to as a first private address. For example, when a local controller that controls and controls one or more facility devices has a communication function and is directly connected to a network provided by the communication carrier 12, the local controller or the local controller and the network A first private address is set for the modem existing in between.

  Equipment equipment group 151 including one or more equipment equipment 16-1 to 16-m is connected by a local area network (LAN), and a private address for communication within each LAN is set. This is referred to as a second private address.

  The first connection device 11 associates a representative identifier for identifying a facility device group with a first private address set by the communication carrier 12 that provides the network to a facility device corresponding to the representative identifier in the facility device group 151. If there is a communication request using a device identifier comprising a first address conversion table and comprising a representative identifier and a sub-identifier for identifying each equipment device in the equipment device group 151 from the remote device 10, The first private address corresponding to the representative identifier included in the communication request is converted to a communication destination address with reference to the one address conversion table, and a route corresponding to the communication destination is selected to start communication. The representative identifier may be a second private address that is set on the LAN of the equipment group 151 for equipment equipment that is directly connected to the network provided by the communication carrier 12 in the equipment group 151. The sub-identifier is a common part between the second private address of the equipment that is not directly connected to the network provided by the communication carrier 12 and the second private address of the equipment that is directly connected to the network provided by the communication carrier 12. The difference can be excluded. For example, if the second private address on the LAN of the equipment that is directly connected to the network provided by the communication carrier 12 is (150.35.10.0), the equipment that is not directly connected to the network provided by the communication carrier 12 When the second private address on the LAN of the device 16-1 is (150.35.10.1), the sub-identifier of the facility device 16-1 can be set to (-1).

  The first connection device 11 receives from the remote management device 10 a communication request including a device identifier including a representative identifier of the facility device group 151 and a sub-identifier set for the facility device that communicates, and uses the sub-identifier as a communication request. At the same time, the transmission destination address is converted into the corresponding representative identifier and the transmission process is started.

  FIG. 16 is a functional block diagram of the first connection device 11.

  The first connection device 11 includes a control unit 161, a first conversion table storage unit 162, a first communication request reception unit 163, a first address conversion unit 164, and a first communication unit 165.

  The control unit 161 includes a processor that controls each unit and a CPU that includes a memory such as a ROM and a RAM.

  The first conversion table storage unit 162 associates a representative identifier for identifying the device group 151 with a communication address set by the communication carrier 12 providing the network to a device corresponding to the representative identifier in the device group 151. One address conversion table is stored for each communication carrier.

  The first communication request receiving unit 163 receives a communication request using a device identifier including a representative identifier and a sub-identifier for identifying each device in the device group from the remote management device 10.

  The first address converting unit 164 refers to the first address conversion table based on the communication request received by the first communication request receiving unit 163, and determines the communication address in the communication carrier corresponding to the representative identifier in the device identifier. It is determined as the communication destination address of the communication request.

  The first communication unit 165 starts communication by attaching the sub-identifier in the device identifier to the communication request received by the first communication request receiving unit 163 using the communication destination address determined by the first address conversion unit 164 To do.

  The second connection device 14 has a correspondence relationship between the device identifier and the second private addresses set in the equipment devices 16-1 to 16-m on the LAN of the equipment device group 151, in particular, the sub-identifier in the device identifier. A second conversion table indicating a correspondence relationship with the second private address is provided, and the facility corresponding to the communication request is based on the second private address of the corresponding facility device based on the sub-identifier attached to the communication request. Send to device.

  FIG. 17 is a functional block diagram of the second connection device 14.

  The second connection device 11 includes a control unit 171, a second conversion table storage unit 172, a second communication request reception unit 173, a second address conversion unit 174, and a second communication unit 175.

  The control unit 171 includes a processor that controls each unit and a CPU that includes memories such as ROM and RAM.

  The second conversion table storage unit 172 stores a second address conversion table that associates the sub-identifier in the device identifier with the second private address set in the equipment group 151 of the equipment corresponding to the sub-identifier.

  The second communication request receiving unit 173 receives a communication request transmitted using the representative identifier as a communication destination address.

  The second address conversion unit 174 refers to the second address conversion table 172 based on the sub-identifier attached to the communication request received by the second communication request reception unit 173, and corresponds to the sub-identifier attached to the communication request. The second private address on the LAN of the equipment to be used is determined as the communication destination address of the communication request.

  The second communication unit 175 starts communication based on the communication request received by the second communication request reception unit 173, using the communication destination address determined by the second address conversion unit 174.

  FIG. 18 is an explanatory diagram showing an example of the first address conversion table 181 managed in the first conversion table storage unit 162.

  The first address conversion table 181 includes a device identifier field 182 and a first private address field 185. The remote management device 10 specifies a device identifier for each facility device and a facility device group to which the facility device belongs. Is stored in correspondence with the first private address set by the communication carrier 12 to which is connected. The device identification column 182 includes a representative identifier column 183 in which a representative identifier corresponding to a device directly connected to the network provided by the communication carrier 12 is stored, and a facility device not directly connected to the network provided by the communication carrier 12 Is provided with a sub-identifier field 184 for storing a sub-identifier corresponding to.

  If the second private address set for each equipment device 16-1 to 16-m connected on the LAN of the equipment device group 151 is (150.35.10.1) to (150.35.10.m), this The second private address is also specified by (150.35.10. *) For devices connected on the LAN and directly connected to the network provided by the communication carrier 12. Therefore, the representative identifier stored in the representative identifier column 183 can be a part of the second private address such as (150.35.10). The sub-identifier stored in the sub-identifier column 184 is a difference from the representative identifier among the device identifiers, and 1 to m are stored.

  The first private address field 185 stores a first private address set by the communication carrier 12 for a device directly connected to the network provided by the communication carrier 12. In the illustrated example, the first private address (192.168.1.1) is stored.

  On the remote management device 10 side, a device identifier different from the second private address used on the LAN of the equipment group 151 can be used. For example, in the equipment group 16-1 to 16-m, the representative identifier of equipment connected to the network provided by the communication carrier 12 is (A00001), and the equipment is connected to the network provided by the communication carrier 12. The sub-identifiers of non-equipment equipment can be (-1) to (-m). Therefore, when the remote management device 10 designates each of the equipment devices 16-1 to 16-m as the communication destination, it can be configured to select from the device identifiers (A0001-1) to (A00001-m).

  FIG. 19 is an explanatory diagram showing an example of the second address conversion table 191 managed in the second conversion table storage unit 172.

  The second address conversion table 191 includes a first private address column 192, a sub-identifier column 193, and a second private address column 194.

  The first private address column 192 stores a first private address set by the communication carrier 12 for the equipment connected directly to the network provided by the communication carrier 12. The sub-identifier column 193 stores sub-identifiers set on the remote management apparatus 10 side for equipment that is not directly connected to the network provided by the communication carrier 12. The second private address column 194 stores the second private address of the corresponding equipment on the equipment equipment group 151 side LAN.

  The remote management system according to the third embodiment of the present invention has the above-described configuration. When the remote management device 10 makes a communication request using the device identifier, the first connection device 11 becomes the representative identifier in the device identifier. The corresponding first private address is specified and set as the communication destination address of the communication request, and the sub-identifier is attached to the communication request to start communication processing through the corresponding communication carrier 12. The second connection device 14 that has received the communication request from the remote management device 10 specifies the second private address from the sub-identifier attached to the communication request, and pays out a communication request using this as the communication destination address. Send to equipment.

  In the above description, a configuration is shown in which the remote management device 10 and the equipment device group 151 are connected via one communication carrier 12, but a plurality of equipment device groups are managed via a plurality of communication carriers. It can be similarly applied to.

  In the remote management system according to the third embodiment of the present invention, the first connection device 11 is built in the remote management device 10, and the second connection device 14 is connected to the communication carrier 12 via the modem 85, and the modem 85, a configuration in which the second connection device 14 and a plurality of local controllers 201-1 to 201-p are connected on a LAN is shown as a fifth embodiment.

  FIG. 20 is a configuration diagram of a remote management system according to the fifth embodiment.

  The remote management system according to the fifth embodiment includes a remote management device 10, a firewall 81, a modem router 83, a modem 85, a second connection device 14, local controllers 201-1 to 201-p, and local controllers 201-1 to 201-. It consists of a group of equipment (not shown) connected to p.

  The remote management device 10 receives information related to the operation status from each equipment device as a daily report, transmits control information and firmware update information for each equipment device, and downloads necessary firmware to each equipment device. And the configuration of the first connection device 11 is included therein.

  The remote management device 10 can be configured by a general computer system such as a personal computer or a workstation, and has the same configuration as the remote management device 10 used in the first embodiment shown in FIG. Details are omitted here. The first connection device 11 may be configured independently of the remote management device 10.

  The firewall 81 is connected to the communication carrier 12 to be connected via the modem router 83. The configurations of the firewall 81 and the modem router 83 are the same as the configurations of the first embodiment, and detailed description thereof is omitted here.

  The communication carrier 12 sets a private address (first private address) on the network to be provided to a directly connected device. Here, the first private is set for the modem 85 connected directly to the network. An address is set.

  Each of the local controllers 201-1 to 201-p controls one or a plurality of equipment belonging to the equipment equipment group, and is connected to the LAN together with the modem 85 and the connection device 14, and is connected to the LAN. The private address (second private address) set by (1) is provided.

  The first private address set to the modem 85 by the communication carrier 12 is (192.168.0.1), and the second private address set for each local controller 201-1 to 201-p in the LAN on the equipment side Are (150.35.10.1) to (150.35.10.p), respectively. When the remote management device 10 transmits a communication request to the local controller 201-1, the remote management device 10 transmits a communication request using the device identifier of the local controller 201-1 as a communication destination address. For example, the remote management device 10 can transmit a communication request using the second private address (150.35.10.1) on the equipment side as a device identifier.

  When receiving the communication request from the remote management device 10, the first connection device 11 refers to the first address conversion table 181 (see FIG. 18) and uses the first private address set by the communication carrier 12 as the communication destination address. Communication request to be generated, and transmitted via the communication carrier 12 with the sub-identifier attached. For example, if the communication request from the remote management device 10 is the device identifier (150.35.10.1) as the communication destination address, the corresponding first private address (192.168.1.1) is set as the communication destination address. A communication request attached with the sub-identifier (1) is transmitted via the communication carrier 12.

  On the equipment side, the modem 85 transmits the communication request received via the communication carrier 12 to the second connection device 14. The second connection device 14 refers to the second address conversion table 191 (see FIG. 19) based on the first private address that is the communication destination address of the communication request and the attached sub-identifier, and is the actual communication destination. The second private address set in the local controller is specified. For example, when the communication destination address of the communication request is the first private address (192.168.1.1) and the sub-identifier (1) is attached, the corresponding local controller 201- on the LAN on the equipment side. A communication request with the second private address (150.35.10.1) set to 1 as the communication destination address is generated and transmitted via the LAN.

  The fifth embodiment shows a case where the remote management apparatus 10 can perform bidirectional communication with a plurality of local controllers 201-1 to 201-p. In addition, lower sub-identifiers are set for the equipment connected to each of the local controllers 201-1 to 201-p, and the remote management apparatus 10 performs direct two-way communication with each equipment. Is also possible.

  As the device configuration of the first connection device 11, the firewall 81, the modem router 83, the modem 85, the second connection device 14, and the local controllers 201-1 to 201-p, various configurations can be used as in the above-described embodiment. Is possible.

  Further, the remote management device 10 can be configured to control a plurality of equipment groups connected via a plurality of communication carriers, as in the above-described embodiment.

  The present invention can be applied to a remote management system that remotely manages equipment such as air conditioners and lighting equipment, and is particularly suitable when connected to a large number of equipment using a plurality of communication carriers. Data communication is possible.

DESCRIPTION OF SYMBOLS 10 Remote management apparatus 11 Connection apparatus 12, 13 Communication carrier 14, 15 Connection apparatus 16-1 to 16-m, 17-1 to 17-n Equipment

JP 2001-345843 A

Claims (8)

A remote management system in which a plurality of devices and a remote management device for remotely managing the plurality of devices are connected via a network,
An address conversion table for associating the device identifier for identifying the remote management device and the plurality of devices with a communication address set in the remote management device and the plurality of devices by a communication carrier providing the network; A conversion table storage for storing each carrier;
A communication request receiver that receives a communication request using the device identifier from any of the remote management device and the plurality of devices;
Based on the communication request received by the communication request receiving unit, referring to the address conversion table, an address converting unit that determines a communication address in a corresponding communication carrier as a communication destination address of the communication request;
A communication unit that starts communication based on a communication request received by the communication request reception unit, using a communication destination address determined by the address conversion unit;
A remote management system in which a connection device is inserted between the remote management device and the network and between the plurality of devices and the network.   A control signal which is provided with a local controller connected to the plurality of devices for each one or a plurality of groups, the local controller being connected to the network via the connection device and transmitted from the remote management device; The remote management system according to claim 1, wherein a plurality of devices in a corresponding group are controlled based on the information. A plurality of devices and a remote management device that remotely manages the plurality of devices are connected via a network, and connection devices are inserted between the remote management device and the network, and between the plurality of devices and the network, respectively. A remote management system,
Each of the connection devices is
An address conversion table for associating the device identifier for identifying the remote management device and the plurality of devices with a communication address set in the remote management device and the plurality of devices by a communication carrier providing the network; A conversion table storage for storing each carrier;
A communication request receiver that receives a communication request using the device identifier from any of the remote management device and the plurality of devices;
Based on the communication request received by the communication request receiving unit, referring to the address conversion table, an address converting unit that determines a communication address in a corresponding communication carrier as a communication destination address of the communication request;
A communication unit that starts communication based on a communication request received by the communication request reception unit, using a communication destination address determined by the address conversion unit;
An address update unit that updates the address conversion table based on a change notification of a communication address transmitted from the communication carrier or a changed communication address transmitted from another connection device;
An address change notification unit for transmitting the communication address changed based on the communication address change notification transmitted from the communication carrier to another connection device;
A remote management system comprising:   A control signal which is provided with a local controller connected to the plurality of devices for each one or a plurality of groups, the local controller being connected to the network via the connection device and transmitted from the remote management device; The remote management system according to claim 3, wherein a plurality of devices in a corresponding group are controlled based on the information. In a remote management system in which a plurality of devices and a remote management device that remotely manages the plurality of devices are connected via a network, the remote management device is inserted between the remote management device and the network, and between the plurality of devices and the network, respectively. A connecting device,
An address conversion table for associating the device identifier for identifying the remote management device and the plurality of devices with a communication address set in the remote management device and the plurality of devices by a communication carrier providing the network; A conversion table storage for storing each carrier;
A communication request receiver that receives a communication request using the device identifier from any of the remote management device and the plurality of devices;
Based on the communication request received by the communication request receiving unit, referring to the address conversion table, an address converting unit that determines a communication address in a corresponding communication carrier as a communication destination address of the communication request;
A communication unit that starts communication based on a communication request received by the communication request reception unit, using a communication destination address determined by the address conversion unit;
A connection device comprising: In a remote management system in which a plurality of devices and a remote management device that remotely manages the plurality of devices are connected via a network, the remote management device is inserted between the remote management device and the network, and between the plurality of devices and the network, respectively. A connecting device,
An address conversion table for associating the device identifier for identifying the remote management device and the plurality of devices with a communication address set in the remote management device and the plurality of devices by a communication carrier providing the network; A conversion table storage for storing each carrier;
A communication request receiver that receives a communication request using the device identifier from any of the remote management device and the plurality of devices;
Based on the communication request received by the communication request receiving unit, referring to the address conversion table, an address converting unit that determines a communication address in a corresponding communication carrier as a communication destination address of the communication request;
A communication unit that starts communication based on a communication request received by the communication request reception unit, using a communication destination address determined by the address conversion unit;
An address update unit that updates the address conversion table based on a change notification of a communication address transmitted from the communication carrier or a changed communication address transmitted from another connection device;
An address change notification unit for transmitting the communication address changed based on the communication address change notification transmitted from the communication carrier to another connection device;
A connection device comprising: A device group including one or a plurality of devices and a remote management device that remotely manages each device included in the device group are connected via a network, and is inserted between the remote management device and the network. A remote management system comprising a connection device and a second connection device inserted between the plurality of devices and the network,
The first connection device includes:
A first address conversion table that associates a representative identifier for identifying the device group with a communication address set by a communication carrier providing the network to a device corresponding to the representative identifier in the device group; A first conversion table storage unit for storing each;
A first communication request receiving unit that receives a communication request using a device identifier composed of the representative identifier and a sub-identifier for identifying each device in the device group from the remote management device;
Based on the communication request received by the first communication request receiver, the first address conversion table is referred to, and the communication address in the communication carrier corresponding to the representative identifier in the device identifier is set as the communication destination of the communication request. A first address conversion unit determined as an address;
A first communication unit that starts communication by attaching a sub-identifier in the device identifier to the communication request received by the first communication request receiving unit using the communication destination address determined by the first address converting unit; ,
The second connection device includes:
A second conversion table storage unit that stores a second address conversion table that associates a sub-identifier in the device identifier with a private address set in the device group of the device corresponding to the sub-identifier;
A second communication request receiving unit that receives a communication request transmitted using a communication address of a device in which the representative identifier is set as a communication destination address;
Based on the sub-identifier attached to the communication request received by the second communication request receiver, the second address conversion table is referred to and the device group of the devices corresponding to the sub-identifier attached to the communication request A second address conversion unit that determines a private address at the communication destination address of the communication request;
A second communication unit that starts communication based on the communication request received by the second communication request reception unit using the communication destination address determined by the second address conversion unit;
Including remote management system. The first connection device updates the first address conversion table based on a communication address change notification transmitted from the communication carrier or a changed communication address transmitted from another connection device. 1 address update unit, and a first address change notification unit that transmits the first communication address changed based on the communication address change notification transmitted from the communication carrier to another connection device,
The second connection device updates the second address conversion table based on a communication address change notification transmitted from the communication carrier or a changed communication address transmitted from another connection device. And a second address change notification unit that transmits a communication address changed based on a communication address change notification transmitted from the communication carrier to another connection device. The remote management system described in 1.

Images