JP2007241380A - Remote device control system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a remote device control system which can improve security. <P>SOLUTION: Control data is transmitted from a management server 3 to a controlled device 7 through middle nodes 5a and 5b, and terminal side device management nodes 5c and 5d in a distributed network. The middle nodes 5a and 5b refer a rule file included with device mapping information that links processing device name information in the control data to next destination information to add the next destination information to the control data. The device management nodes 5c and 5d refer a rule file included with device mapping information that links processing device name information to final destination information to add the final destination information to the control data. In addition, lower level control content information necessary for the controlled device is stored in the device management nodes, and added to the control data at the device management nodes. Thereby, even if the middle nodes are attacked, information on the terminal side controlled device 7 is not easily leaked and terminal side devices cannot be easily accessed. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a remote device control system that sends a control message from a management server to a controlled device via a distributed network composed of a plurality of nodes.

  Conventionally, in a distributed network, a plurality of nodes form a network, and communication is performed via these nodes. The distributed network is, for example, an IP network, and performs overall route control based on information such as IP and port numbers. It has been proposed to apply such a distributed network to a remote device control system. In this case, the management server is connected to a plurality of controlled devices via the distributed network. The controlled device is, for example, a surveillance camera (see, for example, Patent Document 1).

In the field of networks, security is highly important, and various security technologies have been proposed (for example, Patent Documents 2, 3, and 4).
JP-A-4-261289 JP 2000-148698 A JP 11-282661 A JP 2003-69595 A

  However, in a remote device control system using a conventional distributed network, route control is performed based on information such as IP and port numbers. Deprivation of the system causes a security problem that the service of the controlled device at the end is easily accessed.

  The present invention has been made to solve the conventional problems, and an object of the present invention is to provide a remote device control system capable of improving security.

  The remote device control system of the present invention sends a control message from a management server to a controlled device via a distributed network composed of a plurality of nodes, and relays the control message sent from the management server. An intermediate node and a device management node that manages one or more controlled devices and sends a control message received from the intermediate node to the controlled device to be managed, and the management server receives the control message A control message including processing device name information representing a processing device that is a controlled device to be processed is transmitted, and the intermediate node includes an intermediate node rule including device mapping information that associates the processing device name information and next transmission destination information. Intermediate node rule file storage means for storing a file, and the processing of the control message based on the intermediate node rule file An intermediate node message generating unit that adds the next destination information associated with the device name information to the received control message, and the control message is transmitted according to the next destination information added by the intermediate node message generating unit. An intermediate node message transmission unit, and the device management node stores a device management node rule file including a device management node rule file including device mapping information defining final transmission destination information corresponding to the processing device name information. And a device management node message generation unit that adds the final destination information corresponding to the processing device name information of the control message to the control message based on the device management node rule file; and the device management node message generation unit A device pipe that transmits the control message according to the final destination information added by And a node message transmission means.

  With this configuration, the control message is sent to the controlled device via the intermediate node and further via the device management node on the terminal side. The intermediate node refers to the intermediate node rule file including device mapping information that associates the processing device name information indicating the controlled device that should receive the control message with the next transmission destination information, and adds the next transmission destination information to the control message. . Then, the device management node refers to the device management node rule file including the device mapping information that defines the final destination information corresponding to the processing device name information, and adds the final destination information to the control message. The final destination information is, for example, the IP address of the controlled device. Therefore, according to the present invention, even if the intermediate node is attacked, the information on the controlled device at the end is not easily known, and the end device cannot be easily accessed, so that the security can be improved.

  In the remote device control system of the present invention, the control message transmitted from the management server includes higher-level control content information not including lower-level control content information required by the controlled device to be controlled. The device management node rule file of the device management node includes action mapping information for associating the higher level control content information with the lower level control content information, and the device management node message generation means includes the higher level control content The lower level control information associated with content information is added to the control message.

  With this configuration, the lower level control content information necessary for the controlled device is held in the device management node and added to the control message at the device management node. Therefore, even if the intermediate node is attacked, the information on the controlled device at the end is not easily understood and the end device cannot be easily accessed, so that the security can be improved.

  In the remote device control system of the present invention, the processing device name information in the control message transmitted by the management server is a device group name that identifies a group of controlled devices managed by the device management node. The device management node rule file of the device management node associates the device group name information with transmission destination information of a controlled device managed by the device management node, and generates the device management node message The means adds the transmission destination information of the controlled device associated with the device group name information to the control message.

  With this configuration, the information on the controlled device known from the processing device name information of the control message is up to the device group name information. Information on each controlled device belonging to the device group is held in the rule file of the device management node. Therefore, even if the intermediate node is attacked, the information on the controlled device at the end is not easily understood and the end device cannot be easily accessed, so that the security can be improved.

  In the remote device control system of the present invention, the lower level control content information of the device management node rule file is, for example, authentication information required by the controlled device. The authentication information is, for example, an ID and a password. With this configuration, even if an intermediate node is attacked, the authentication information of the controlled device at the end is not easily known and the end device cannot be easily accessed, so that the security can be improved.

  Another aspect of the present invention is a device management node apparatus constituting the remote device control system described above. The device management node apparatus receives a control message, receives a control message including processing device name information indicating a processing device that is a controlled device to be processed, and receives a final message corresponding to the processing device name information. Rule file storage means for storing a device management node rule file including device mapping information that defines transmission destination information, and the final transmission destination corresponding to the processing device name information of the control message based on the device management node rule file A message generation unit that adds information to the control message; and a message transmission unit that transmits the control message according to the final destination information added by the message generation unit. This aspect also provides the above-described advantages of the present invention.

  Another aspect of the present invention is a remote device control method for sending a control message from a management server to a controlled device via a distributed network composed of a plurality of nodes. In this method, a control message sent from the management server is relayed by an intermediate node, sent to a device management node that manages one or more controlled devices, and the control message is sent from the device management node to a controlled device to be managed. Send. The management server transmits a control message including processing device name information representing a processing device that is a controlled device to receive and process the control message, and the intermediate node transmits the processing device name information and a next transmission destination. Refer to an intermediate node rule file including device mapping information for associating information, add the next destination information associated with the processing device name information of the control message to the received control message, and according to the next destination information The control message is transmitted, and the device management node refers to a device management node rule file including device mapping information defining final transmission destination information corresponding to the processing device name information, and the processing device name of the control message The final destination information corresponding to the information is added to the control message, and the control is performed according to the final destination information. To send a message. This method also provides the above-described advantages of the present invention.

  In the remote device control method of the present invention, the control message transmitted from the management server includes upper level control content information not including lower level control content information required by the controlled device to be controlled, The device management node rule file includes action mapping information for associating the higher level control content information with the lower level control content information, and the message generation processing of the device management node is associated with the higher level control content information. The lower level control information is added to the control message.

  In the remote device control method of the present invention, the processing device name information in the control message transmitted by the management server specifies a group of a plurality of controlled devices managed by the device management node. The device management node rule file of the device management node associates the device group name information with the transmission destination information of the controlled device managed by the device management node, and the device management node The message generation process adds the transmission destination information of the controlled device associated with the device group name information to the control message.

  In the remote device control method of the present invention, the lower level control content information of the device management node rule file includes authentication information required by the controlled device.

  These methods can also provide the above-described advantages of the present invention.

  Another aspect of the present invention is a program that causes a node computer constituting a distributed network to execute the remote device control method described above. This program suitably causes the computer to realize the function of the device management node. This configuration also provides the above-described advantages of the present invention.

  Another aspect of the present invention is a recording medium on which the above program is recorded. This configuration also provides the above-described advantages of the present invention.

  In the present invention, since the intermediate node and the device management node have different rule files as described above, even if the intermediate node is attacked, the information of the controlled device at the end is not easily understood and cannot be easily accessed. A remote device control system having an effect of improving security can be provided.

  Hereinafter, a remote device control system according to an embodiment of the present invention will be described with reference to the drawings. The remote device control system controls, for example, a building surveillance camera.

  FIG. 1 shows a remote device control system according to an embodiment of the present invention. In FIG. 1, the remote device control system 1 includes a management server 3, intermediate nodes 5a and 5b, device management nodes 5c and 5d, and controlled devices 7a to 7d. The nodes 5a to 5d form a distributed network, and the management server 3 and a plurality of controlled devices 7a to 7d are connected via the network.

  In FIG. 1, the intermediate nodes 5 a and 5 b relay the control message sent from the management server 3. The device management node 5c manages the controlled devices 7a and 7b, and sends the control message received from the relay nodes 5a and 5b to the controlled devices 7a and 7b to be managed. The device management node 5d manages the controlled devices 7c and 7d, and sends the control message received from the relay nodes 5a and 5b to the controlled devices 7c and 7d to be managed. Thus, in this embodiment, controlled devices are segmented for each group, and a device management node is provided as a configuration for bundling them.

  The intermediate nodes 5a and 5b and the device management nodes 5c and 5d may be realized by computer devices having the same configuration. However, these nodes 5a to 5d store different rule files as described later, and operate by referring to these different rule files. Thereby, as described above, some of the nodes 5a and 5b function as intermediate nodes, and the other nodes 5c and 5d function as device management nodes.

  Hereinafter, the description that does not distinguish between the intermediate nodes 5a and 5b and the device management nodes 5c and 5d is simply referred to as a node 5. Also, the controlled devices 7a to 7d are simply referred to as controlled devices 7 in the description that does not require distinction. In FIG. 1, four nodes 5 and four controlled devices 7 are shown for simplification, but it is a matter of course that a larger number of nodes 5 and controlled devices 7 may be provided.

  FIG. 2 is a block diagram showing the configuration of one node 5. The node 5 may be any device that can realize the function of the relay device. For example, the node 5 may be a server device. The node 5 includes a control message reception unit 11, a control message generation unit 13, a control message transmission unit 15, a device information management unit 17, and a rule file management unit 19.

  The control message receiver 11 receives a control message from the management server 3 or another node 5. The control message is a message for controlling the controlled device 7. The control message generator 13 refers to the rule file managed by the rule file manager 19 and generates a control message for transmission from the received control message. The control message transmission unit 15 transmits the control message generated by the control message generation unit 13 to another node 5 or the controlled device 7. The device information management unit 17 is configured to manage information on surrounding devices, and acquires and manages device information from the surrounding nodes 5 at the time of activation. When the controlled device 7 is connected to the node 5, the device information management unit 17 performs a process of assigning a logical ID to the controlled device 7, and the node 5 becomes a device management node. The rule file management unit 19 stores and manages a rule file used for message generation by the control message generation unit 13.

  As already described, the node 5 in FIG. 2 can function as both an intermediate node and a device management node of the present invention. One node 5 may function as a device management node and may also function as an intermediate node for other nodes 5. When the node 5 functions as an intermediate node, an intermediate node rule file (rule file for the intermediate node) is stored in the rule file management unit 19, and this intermediate node rule file is processed by the control message generation unit 13. Similarly, when the node 5 functions as a device management node, a device management node rule file (rule file for the device management node) is stored in the rule file management unit 19, and this device management node rule file is stored in the control message generation unit. 13 is processed.

  FIG. 3 is a schematic diagram showing the control message together with the intermediate node rule file and the device management node rule file (a detailed example of the control message etc. will be described later). The control message includes processing device name information as illustrated. The processing device name information is information representing the processing device that is the controlled device 7 that should receive and process the control message. That is, the processing device name information is information for specifying a device for which the management server 3 requests control processing, and specifically, the logical ID of the controlled device 7 may be described.

  The intermediate node rule file includes device mapping information that associates the processing device name information with the next transmission destination information. The next transmission destination information specifies a node to which a control message is to be passed next by relay processing. Based on the intermediate node rule file, the control message generator 13 (FIG. 2) of the node 5 adds the next transmission destination information associated with the processing device name information of the control message to the control message. Then, the control message transmission unit 15 transmits a control message according to the next transmission destination information added by the control message generation unit 13. At this time, the rule file management unit 19 functions as an intermediate node rule file storage unit, the control message generation unit 13 functions as an intermediate node message generation unit, and the control message transmission unit 15 functions as an intermediate node message transmission unit.

  On the other hand, the device management node rule file includes device mapping information and action mapping information. First, the device mapping information is information for determining final destination information corresponding to the processing device name information. The final transmission destination information is destination information of the controlled device managed by the device management node, for example, an IP address. Based on the device management node rule file, the control message generator 13 adds the final destination information associated with the processing device name information of the control message to the control message. Then, the control message transmission unit 15 transmits a control message according to the final transmission destination information added by the control message generation unit 13. At this time, the rule file management unit 19 functions as a device management node rule file storage unit, the control message generation unit 13 functions as a device management node message generation unit, and the control message transmission unit 15 functions as a device management node message transmission unit. To do.

  In the present embodiment, in the control message transmitted from the management server 3, device group name information for specifying a group of a plurality of controlled devices 7 managed by the device management node is specified as processing device name information. You can also. In this case, the device group name information is associated with the final transmission destination information of each controlled device 7 belonging to the device group in the device management node rule file. Then, based on the device management node rule file, final destination information is added to the control message.

  Next, action mapping information in the device management node rule file will be described. The control message transmitted from the management server includes higher level control information as control content information. Here, the high-level control content information is so-called rough control content information and does not include detailed control content information required by the controlled device 7, in other words, the controlled device 7 The control content information lacks some of the necessary information. On the other hand, the detailed control content information required by the controlled device 7 is referred to as lower level control content information in the present invention. The action mapping information associates such higher level control content information and lower level control content information. When the node 5 functions as a device management node, the control message transmitting unit 15 refers to the action mapping information and adds lower level control information associated with the higher level control content information to the control message. As a result, the control message is converted into detailed information that can be used by the controlled device at the stage of the device management node.

  Here, a simple example of action mapping information will be described. Upper level control content information is an instruction for alarm output, and lower level control content information is a user ID and password of a terminal device that outputs an alarm. In this case, the device management node obtains the user ID and password from the action mapping information, adds them to the control message, sends this control message to the terminal device, and receives this to enable the terminal device to operate. And outputs an alarm. This example is also used in the description of specific examples described later.

  The configuration of each part of the remote device control system 1 has been described above. Next, the operation of the remote device control system 1 will be described. First, the operation of each node 5 will be described.

  FIG. 4 shows a startup sequence of the node 5. When the node 5 is activated (S1), the rule file management unit 19 reads the rule file (S3). If the controlled device 7 is connected to the node 5, the device information management unit 17 gives a logical ID to the controlled device 7 (S5), and the node 5 becomes a device management node. The device information management unit 17 acquires and manages device information from the surrounding nodes 5.

  FIG. 5 shows a telegram transmission sequence in the node 5. When the control message receiver 11 receives the control message (S11), the control message generator 13 acquires the rule file data of the rule file manager 19 (S13). The node 5 determines whether or not the control message is a message addressed to itself (S15). If the determination in step S15 is YES, the node 5 reads and processes the contents of the message (S17). The processing result is returned to (S23).

  If the determination in step S15 is NO, the control message generator 13 dynamically generates a control message for transmission to the next destination based on the rule file, and assigns the own logical ID to the control message as a route history. (S19). Then, the control message is transferred from the control message generator 13 to the control message transmitter 15, and the control message transmitter 15 transmits the control message to the next destination (S21). Then, the node 5 returns the processing result to the sender (S23).

  Next, the operation of the entire system will be described. When each node 5 operates according to each rule file as described above, a control message is sent from the management server 3 to the controlled device 7 through the plurality of nodes 5 in the entire system. Here, as an example, an operation when a control message is sent from the management server 3 to the controlled devices 7a and 7b via the intermediate node 5a and the device management node 5c in the system of FIG. 1 will be described.

  The application of the management server 3 sends a control message including processing device name information and higher level control content information to the intermediate node 5a. In the intermediate node 5a, the next transmission destination information corresponding to the processing device name information is added to the control message based on the device mapping information of the intermediate node rule file, and the control message is sent to the next destination based on the additional information. In this example, the next destination is the device management node 5c. However, a control message may be sent from the intermediate node 5a to the device management node 5c via one or more other intermediate nodes (not shown) and processing using the same rule file.

  When the control message reaches the device management node 5c in this way, the device management node 5c adds the destinations of the controlled devices 7a and 7b, which are final transmission destinations, to the control message based on the device management node rule file. At this time, the control message is divided into a message addressed to the controlled device 7a and a message addressed to the controlled device 7b. Further, lower level control content information corresponding to the upper level control content information of the control message is obtained from the device management node rule file and added to the control message. A control message including the control content information thus processed is sent to the controlled devices 7a and 7b. The controlled devices 7a and 7b operate according to the received control message.

  Next, a more detailed example of the remote device control system according to the present embodiment will be described. Here, the remote device control system is applied to a building monitoring system.

  FIG. 6 shows the remote device control system 100 of this example. The integrated management server 102 is connected to the 2F central management node 108 and the 1F equipment management node 110 via the intermediate node 106 of the distributed network 104. The 2F data central management node 108 is connected to a data center and a device management terminal (3F-PC). The 1F device management node 110 is connected to the camera A and the camera B.

  FIG. 7 shows the configuration of FIG. 6 in the same format as FIG. As illustrated, the integrated management server 102 corresponds to the management server, and the 2F central management node 108 and the 1F device management node 110 correspond to the device management node. The 2F central management node 108 manages 3F-PC as a controlled device. The 1F device management node 110 manages cameras A and B as controlled devices.

  FIG. 8 shows a specific example of the control message. The control message M includes header information M1 and processing service information M2. The processing service information M2 includes control contents and processing device name information of the present embodiment shown in FIG. The processing service information M2 includes an action rule M21, a category M22, a device name M23, a path history M24, property information M25, a processing method M26, and parameter information M27.

  The action rule M21 is a rule obtained by collecting a plurality of control contents, and is information for forming the above-described high-level control contents. The category M22 is classification information based on the type of control message. The device name M23 corresponds to the above-described processing device name information, and as a specific value, a logical ID given to the controlled device at startup is written. The route history M24 is information on a route through which a message passes, and a node name is added each time a node passes as described later. The property information M25 is information unique to the device. The processing method M26 is information of a minimum function unit, and for example, “play”, “stop”, “restart”, etc. for AV equipment, and forms high-level control content information. The parameter information M27 is a value necessary for executing the method. Services for controlling controlled devices are abstracted by the attributes such as the action rule M21, category M22, device name M23, property information M25, processing method M26, and parameter information M27, that is, these attributes are controlled. Represents the content. The server application controls the controlled device 7 by designating the values of these attributes from the top.

  In FIG. 8, the device name M23 is the processing device name information, and more specifically, the logical ID of the transmission destination controlled device that should receive and process the control message. A device group name can be specified instead of the device name. The device group name specifies a group of a plurality of controlled devices bundled by the device management node. The device group name is also a form of processing device name information. This point has already been described as a variation of designation of processing device name information.

  FIG. 9 shows an operation example of the remote device control system 100. As a scenario of this operation example, information rises from the 1F suspicious person detection sensor to the integrated management server 102, and in response to this, the integrated management server 102 operates “WarnLevel4” on the 1F cameras A and B. To instruct. At the same time, the integrated management server 102 displays a warning message on the 3F-PC (3F administrator terminal). This operation is realized as follows.

  In FIG. 9, the integrated management server 102 transmits a control message to the intermediate node 106 (S100), and the intermediate node 106 performs a message generation process (S102). Here, rule merging and message division are performed. The rule merging is a process of combining the rule file with the message and adding the information of the rule file, and is a process performed by the control message generator 13 described above. The message division is a process of dividing a message for each transmission destination when there are a plurality of transmission destinations. After the message generation process in step S102, the control message is sent to the 2F central management node 108 and the 1F device management node 110 (S104, S106).

  The 2F central management node 108 performs a message generation process (S108), and rule file information is added by rule merging. The generated control message is sent to the 3F-PC (S110).

  Also, the electronic message generation process is performed in the 1F device management node 110 (S112). Also here, rule file information is added by rule merging, the message is divided, and messages to cameras A and B are generated. Then, a message is transmitted to camera A and camera B (S114, S116).

  FIG. 10A to FIG. 10D show processing performed in the intermediate node 106. FIG. 10A shows a control message that the intermediate node 106 receives from the integrated management server 102. FIG. 10B is an intermediate node rule file held in the intermediate node 106. FIG. 10C and FIG. 10D are control messages for the 2F central management node 108 and the 1F device management node 110 generated by the intermediate node 106.

  As shown in FIG. 10A, in the first control message, the action rule M21 is “doWarnLevel4Action”, and the category M21 is “Control”. The device group name M23a is “1F camera group”, the path history M24 is “intermediate node”, and the processing method M26 is “doWarnLevel4”. Also, information about another processing request destination is described, the device name M23 is “3F-PC”, the path history M24 is “intermediate node”, the processing method M26 is “displayMessage”, and the parameters The information M27 is “message” “suspicious person found”. In the figure, the property information M25 is not shown (the same applies hereinafter).

  As shown in FIG. 10B, the intermediate node rule file includes device mapping information R1. In the device mapping information R1, the device group name R13a “1F camera group” is associated with the path information R14 “1F device management node”. Further, the device name R13 “3F-PC” is associated with the route information R14 “2F central management node”. In the intermediate node rule file, the route information R14 is the next transmission destination information.

  The control message for transmission shown in FIGS. 10C and 10D is created from the original control message shown in FIG. 10A and the intermediate node rule file shown in FIG. As shown in the figure, the original control message in FIG. 10A is divided into two, which is a control message addressed to each device.

  FIG. 10C shows a control message related to the device name M23 “3F-PC”. “3F-PC” is associated with the route information R14 “2F central management node” in the intermediate node rule file. In FIG. 10C, “2F centralized management node” is added to the route history M24. Further, the intermediate node itself is assigned to the route history M24. The control message is transmitted to the “2F central management node” according to the device mapping information.

  FIG. 10D shows a control message related to the device group name M23a “1F camera group”. The “1F camera group” is associated with the route information R14 “1F device management node” in the intermediate node rule file. In FIG. 10D, “1F device management node” is added to the route history M24. Further, the intermediate node itself is assigned to the route history M24. The control message is transmitted to the “1F device management node” according to the device mapping information.

  Next, FIG. 11A to FIG. 11C illustrate processing performed by the 2F central management node 108. FIG. 11A shows a control message received by the 2F central management node 108 from the intermediate node 106, and is the same as FIG. 10C. FIG. 11B is a device management node rule file held in the 2F central management node 108. FIG. 11C shows a control message for 3F-PC generated by the 2F central management node 108.

  As shown in FIG. 11B, the device management node rule file includes device mapping information R1 and action mapping information R2. In the device mapping information R1, the device name R13 “3F-PC” is associated with the path information R14 “3F-PC IP address”. In the device management node rule file, the route information R14 is the final destination information. In the control message for transmission in FIG. 11C, “3F-PC” is added to the route history M24. Further, the 2F central management node 108 itself is assigned to the route history M24.

  In the action mapping information R2, the action rule R21 is “doWarnLevel4Action”, the category R22 is “Control”, the device name R23 is “3F-PC”, the processing method R26 is “displayMessage”, The parameter information R27 is “user”, “administrator ID”, “password”, “administrator password”. Therefore, parameter information that does not exist in the original control message is added to the control message in FIG. This parameter information is an example of lower level control content information of the present invention. The control message to which the parameter information is added is sent to the “3F-PC IP address” specified by the device mapping information.

  Next, FIG. 12A to FIG. 12C illustrate processing performed in the 1F device management node 110. FIG. 12A shows a control message received by the 1F device management node 110 from the intermediate node 106, and is the same as FIG. 10D. FIG. 12B is a device management node rule file held in the 1F device management node 110. FIG. 12C is a control message for the camera A generated by the 1F device management node 110.

  As shown in FIG. 12B, the device management node rule file includes device mapping information R1 and action mapping information R2. 12B, in the device mapping information R1, the device group name R13a “1F camera group” is associated with the device names “camera A” “camera B”, and further above , The device name “camera A” is associated with the route information R14 “camera A”, and the device name “camera B” is associated with the route information R14 “camera B”. Thereby, the device group name (1F camera group) is associated with the final transmission destination information (cameras A and B). In the control message for camera A in FIG. 12C, “camera A” is added to the route history M24, and the 1F device management node 110 itself is also assigned to the route history M24.

  In the action mapping information R2, the action rule R21 is “doWarnLevel4Action”, the category R22 is “Control”, the device group name R23a is “1F camera group”, and the processing method R26 is “zoom”. The parameter information R27 is “magnification” “120%”. Therefore, the processing method R26 and the parameter information R27 are added to the control message in FIG.

  Such a control message is transmitted to the camera A according to the device mapping information. Although not shown, a control message to camera B is generated in the same manner and transmitted to camera B.

  The detailed example of the remote device control system has been described above. As described above, in this example, when 3F-PC is controlled, the intermediate node 106 refers to the intermediate node rule file and relays the control message to the next transmission destination associated with the device name M23 of the control message. To do. The intermediate node 106 does not know the information (final action rule, processing method, parameter, category) of the final control message necessary for 3F-PC control. These designated variable names are prepared at the 2F central management node 108, and the 3F-PC can be operated only after a regular control message is sent from the 2F central management node 108 to the 3F-PC. Even if the intermediate node 106 is attacked by an unauthorized intruder, the route to 3F-PC, which is a terminal device, and necessary information cannot be determined. Without the action instruction content from the host and the information on the 2F central management node 108, an unauthorized intruder cannot execute the 3F-PC service, and thus the security can be improved.

  When the cameras A and B on the first floor are controlled, the intermediate node 106 refers to the intermediate node rule file and relays the control message to the next transmission destination associated with the device group name M23a of the control message. The intermediate node 106 does not have information on cameras A and B, which are belonging devices corresponding to the device group name M23a. The cameras A and B are to be controlled only after the 1F device management node 110 refers to the device management node rule file. In this way, even if the intermediate node 106 is attacked by an unauthorized intruder, the information of the cameras A and B, which are end devices, is concealed, and the unauthorized intruder sends a correct control message directly to these devices. Therefore, security can be improved.

  In addition, this embodiment can improve security as follows. First, by using control message segmentation processing and hierarchical structure as shown in the above example, the system can, for example, "encrypt service information about this device from an intermediate communication path and send it" or " A rule file can be defined such that only parameters including user information are sent encrypted. As a result, advanced encryption switching processing according to the provided service and the state of the communication path is possible.

  In addition, the above system determines whether the control message is addressed to itself on each device based on the contents of the header and the name attribute value of <device>, and looks at the message only when addressed to itself. It is a mechanism that can transmit to the destination of the data, and unnecessary data cannot be acquired or rewritten at a node in the middle. This can prevent unauthorized rewriting of messages in the middle of the route.

  In addition, the above system can restrict the contents of the processing service so that only the message addressed to itself can be viewed, and basically the node can only add the route information. . Therefore, falsification of the route history information can be prevented, and the route information can be added safely at the node.

  Further, the message structure described above makes it possible to determine whether or not the message is correct based on the transmission source / destination information in the header part and the processing content for the device. Therefore, it is possible to provide a more reliable and broad message validity authenticating means.

  The remote device control system 1 according to the embodiment of the present invention has been described above. According to the present embodiment, the control message is sent to the controlled device via the intermediate node and further via the device management node on the terminal side. The intermediate node refers to the intermediate node rule file including device mapping information that associates the processing device name information indicating the controlled device that should receive the control message with the next transmission destination information, and adds the next transmission destination information to the control message. . Then, the device management node refers to the device management node rule file including the device mapping information that defines the final destination information corresponding to the processing device name information, and adds the final destination information to the control message. In this way, even if an intermediate node is attacked, the information of the controlled device at the end is not easily known, the device control route cannot be easily entered, and the end device cannot be easily accessed, so that the security can be improved.

  Further, according to the present embodiment, the control message includes higher level control content information. The lower level control content information necessary for the controlled device is contained in the device management node rule file, held in the device management node, and added to the control message at the device management node. Therefore, even if the intermediate node is attacked, the information on the controlled device at the end is not easily understood, the device control route cannot be easily entered, and the end device cannot be easily accessed, so that the security can be improved.

  Further, according to the present embodiment, the processing device name information of the control message is device group name information that identifies a group of a plurality of controlled devices. The information of the controlled device that can be understood from the device name information of the control message processing in the intermediate node is up to the device group name information. Information on each controlled device belonging to the device group is held in the rule file of the device management node. Therefore, even if the intermediate node is attacked, the information on the controlled device at the end is not easily understood, the device control route cannot be easily entered, and the end device cannot be easily accessed, so that the security can be improved.

  Further, according to the present embodiment, the lower-level control content information in the device management node rule file is, for example, authentication information required by the controlled device, and more specifically, the above-described user ID and password. . As a result, even if an intermediate node is attacked, the authentication information of the controlled device at the end is not easily known, the device control route cannot be easily intruded, and the end device cannot be easily accessed, thereby improving security. .

  The preferred embodiments of the present invention have been described above. However, the present invention is not limited to the above-described embodiments, and it goes without saying that those skilled in the art can modify the above-described embodiments within the scope of the present invention.

  As described above, the remote device control system according to the present invention has an effect of improving security, and is useful as a monitoring system or the like.

The figure which shows the whole structure of the remote equipment control system which concerns on embodiment of this invention The figure which shows the structure of the node of the remote equipment control system Diagram showing control message, intermediate node rule file, and device management node rule file Diagram showing node startup sequence Diagram showing message transmission sequence in node Diagram showing an application example of a remote device control system Diagram showing an application example of a remote device control system Figure showing an example of a control message Diagram showing operation of remote device control system (A) Diagram showing control message received by intermediate node from integrated management server (b) Diagram showing intermediate node rule file held in intermediate node (c) Control message for 2F centralized management node generated at intermediate node (D) The figure which shows the control message for 1F apparatus management nodes produced | generated by the intermediate node (A) The figure which shows the control message which 2F central management node receives from the intermediate node (b) The figure which shows the equipment management node rule file hold | maintained at 2F central management node (c) The control message produced | generated by 2F central management node Figure showing (A) Diagram showing control message received by 1F device management node from intermediate node (b) Diagram showing device management node rule file held by 1F device management node (c) Camera A generated by 1F device management node Of control message for

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Remote device control system 3 Management server 5 Node 7 Controlled device 11 Control message receiver 13 Control message generator 15 Control message transmitter 17 Device information manager 19 Rule file manager

Claims (11)

A remote device control system that sends a control message from a management server to a controlled device via a distributed network composed of a plurality of nodes,
An intermediate node that relays the control message sent from the management server;
A device management node that manages one or more controlled devices and sends a control message received from the intermediate node to the controlled device to be managed;
The management server transmits a control message including processing device name information representing a processing device that is a controlled device to receive and process the control message;
The intermediate node is
Intermediate node rule file storage means for storing an intermediate node rule file including device mapping information for associating the processing device name information and next destination information;
Intermediate node message generation means for adding the next transmission destination information associated with the processing device name information of the control message to the received control message based on the intermediate node rule file;
An intermediate node message transmission unit that transmits the control message according to the next transmission destination information added by the intermediate node message generation unit;
The device management node is
Device management node rule file storage means for storing a device management node rule file including device mapping information defining final destination information corresponding to the processing device name information;
Device management node message generation means for adding the final transmission destination information corresponding to the processing device name information of the control message to the control message based on the device management node rule file;
A remote device control system comprising: a device management node message transmission unit that transmits the control message according to the final destination information added by the device management node message generation unit. The control message transmitted from the management server includes higher level control content information not including lower level control content information required by the controlled device to be controlled,
The device management node rule file of the device management node includes action mapping information that associates the upper level control content information with the lower level control content information,
The remote device control system according to claim 1, wherein the device management node message generation unit adds the lower level control information associated with the higher level control content information to the control message. The processing device name information in the control message transmitted by the management server is device group name information for specifying a group of a plurality of controlled devices managed by the device management node,
The device management node rule file of the device management node associates the device group name information with transmission destination information of a controlled device managed by the device management node,
The remote device control according to claim 1 or 2, wherein the device management node message generation unit adds the transmission destination information of the controlled device associated with the device group name information to the control message. system.   The remote device control system according to claim 2, wherein the lower-level control content information of the device management node rule file includes authentication information required by the controlled device. A device management node device constituting a remote device control system, connected to a distributed network and managing one or more controlled devices and transmitting a control message received from the distributed network to the controlled device,
A message receiving means for receiving a control message including processing device name information representing a processing device that is a controlled device to receive and process the control message;
A rule file storage means for storing a device management node rule file including device mapping information defining final destination information corresponding to the processing device name information;
Message generating means for adding the final destination information corresponding to the processing device name information of the control message to the control message based on the device management node rule file;
A message transmission means for transmitting the control message according to the final transmission destination information added by the message generation means;
A device management node device comprising: A control message sent from a management server is relayed by an intermediate node via a distributed network composed of a plurality of nodes, sent to a device management node that manages one or more controlled devices, and is managed from the device management node. A remote device control method for sending the control message to a controlled device,
The management server transmits a control message including processing device name information representing a processing device that is a controlled device to receive and process the control message;
The intermediate node receives the next destination information associated with the processing device name information of the control message with reference to an intermediate node rule file that includes device mapping information that associates the processing device name information with the next destination information Added to the control message, and transmits the control message according to the next destination information,
The device management node refers to a device management node rule file including device mapping information that defines final destination information corresponding to the processing device name information, and the final transmission corresponding to the processing device name information of the control message A remote device control method characterized by adding destination information to the control message and transmitting the control message according to the final destination information. The control message transmitted from the management server includes higher level control content information not including lower level control content information required by the controlled device to be controlled,
The device management node rule file includes action mapping information for associating the upper level control content information with the lower level control content information,
The remote device control method according to claim 6, wherein the message generation processing of the device management node adds the lower level control information associated with the higher level control content information to the control message. The processing device name information in the control message transmitted by the management server is device group name information for specifying a group of a plurality of controlled devices managed by the device management node,
The device management node rule file of the device management node associates the device group name information with transmission destination information of a controlled device managed by the device management node,
The remote device according to claim 6 or 7, wherein the message generation processing of the device management node adds the transmission destination information of the controlled device associated with the device group name information to the control message. Control method.   The remote device control method according to claim 7, wherein the lower level control content information of the device management node rule file includes authentication information required by the controlled device. A program that is connected to a distributed network and that is executed by a node computer that constitutes a remote device control system that manages one or more controlled devices by transmitting control messages received from the distributed network to the controlled devices. And
Receiving a control message including processing device name information representing a processing device that is a controlled device to receive and process the control message, and device mapping information defining final destination information corresponding to the processing device name information The device management node rule file included is referred to, and the final destination information corresponding to the processing device name information of the control message is added to the control message based on the device management node rule file, and according to the final destination information A program for causing the node computer to execute processing for transmitting the control message. A program that is connected to a distributed network and that transmits a control message received from the distributed network to a controlled device and records a program executed by a node computer constituting a remote device control system that manages one or more controlled devices. A computer-readable recording medium,
Receiving a control message including processing device name information representing a processing device that is a controlled device to receive and process the control message, and device mapping information defining final destination information corresponding to the processing device name information The device management node rule file included is referred to, and the final destination information corresponding to the processing device name information of the control message is added to the control message based on the device management node rule file, and according to the final destination information A recording medium recording a program for causing the node computer to execute a process of transmitting the control message.

Images