JP5219860B2 - Domain management method, node and domain management system - Google Patents

Description

  The present invention relates to a domain management method, a node, and a domain management system in a system that forms a domain with a plurality of devices.

  In a network composed of devices having a wired communication function or a wireless communication function, such as a ship, an aircraft device, a large-scale device-to-device network, or a unit on the battlefield, one or more devices are linked together. Often has the function of. In such a case, it is often the case that a device organization (zone) composed of a plurality of devices to be linked is formed and functions are realized for each zone. Although this zone is composed of a plurality of devices, one device may belong to a plurality of zones. For this reason, in order to use these networks efficiently, it is necessary to be able to easily switch zones as necessary.

  For example, it is assumed that the above zone is composed of entities included in each device and functions as a monitoring system. In this case, if an entity that does not operate in part due to an attack or failure occurs on an entity included in a plurality of devices constituting the zone functioning as a monitoring system, the zone (monitoring system) does not function. In such a case, the function of the monitoring system can be recovered by switching the zone and reconstructing the zone so as to realize the function of the management system without including devices that do not operate.

  Furthermore, when the command authority for each zone is specified according to the management level of the manager who performs management in the unit, etc., the management level of the manager is changed for some reason, etc. The zone needs to be rebuilt. Therefore, when the zone is reconstructed as described above, it can be efficiently performed based on the management level of the administrator.

  In addition, when a domain is configured by a plurality of devices as in the case of a zone, an example of a conventional technology for changing a device that configures a domain is, for example, a technology described in Patent Document 1 below. Patent Document 1 below discloses a network management method that allows a user to directly control the joining and withdrawal of domain component devices.

JP-T-2007-52795

  However, in the technology using a zone configured by entities included in each conventional device, the zone is a network configuration between devices logically configured on the entity included in each device. There is a problem that the network configuration between the devices is easily broken if it does not function due to an attack or failure. In addition, there is a problem that even if the network between devices is physically connected, the zone of the broken network configuration cannot be switched, and it takes time to reconstruct the network configuration.

  Moreover, in the above-mentioned Patent Document 1, a method is shown in which a user controls the joining and withdrawal of domain constituent devices, but the devices logically configured on the entities included in each device as described above. It does not describe how to reconstruct the inter-network configuration. In addition, there is a stage in the strength of command of the commander who is the user, and there is no mention of a method for restructuring the domain corresponding to the strength.

  The present invention has been made in view of the above, and in the case where a domain (zone) is configured by entities included in each device, a domain management method and a domain that can efficiently perform domain reconstruction The purpose is to obtain a management system.

In order to solve the above-described problems and achieve the object, the present invention provides a domain management method in a case where a plurality of nodes configure a domain and perform processing in units of domains, and the nodes are configured to perform user authority. Domain management information which is information that associates a node that constitutes a domain to which the node belongs with the domain, and holds the command strength indicating the degree as a command strength information in association with a user identifier. A domain management information holding step for holding the domain information, domain information relating to the domain configuration in the command data for instructing the operation content, the command authority strength of the user who has instructed transmission of the command data, and the identifier of the user In addition to the command data transmission step to be transmitted and the node that received the command data from other nodes, the command data And domain management information managing step of stomach itself updates the domain management information held, the node receiving the command data, the user who instructed the transmission of the command data and the command authority intensities added to the conductor data And a command data determination step of validating the command data when the response matches the command authority strength information, and discarding the command data when the response does not match .

  According to this invention, since the domain is formed based on the command data for instructing the operation content, there is an effect that the domain can be reconstructed efficiently. Moreover, processing can be performed efficiently according to the strength of command. For this reason, when there is a change in a commanded device or person during a large-scale disaster or battle, it is efficient and safe to transfer the command strength associated with the device or person to another device or person. It becomes possible to carry out the transfer.

  Embodiments of a domain management method, a node, and a domain management system according to the present invention will be described below in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

Embodiment 1 FIG.
FIG. 1 is a diagram showing a configuration example of a first embodiment of a monitoring system for realizing a domain management method according to the present invention. As shown in FIG. 1, the monitoring system of the present embodiment is a system for monitoring information during an earthquake or disaster, or on the battlefield, and includes sensors 1-1 to 1-6 that acquire information to be monitored. , Relay devices 2-1 to 2-3 that are monitoring devices that relay data acquired by the sensors 1-1 to 1-6, and relay devices 2-1 to 2- 3, the middle servers 3-1 and 3-2 that are monitoring devices that further relay the data received from 3, and the rear server device 4 that is a monitoring device installed behind the field.

  Data information # 1 and information # 2 respectively acquired by the sensors 1-1 and 1-2 are processed as information A by the relay device 2-1, and the information A is transmitted to the middle server device 3-1. Data information # 3 and information # 4 respectively acquired by the sensors 1-3 and 1-4 are processed as information B by the relay device 2-2, and the information B is converted into the middle server device 3-1 and the middle server device 3-2. Sent to. Data information # 5 and information # 6 respectively acquired by the sensors 1-5 and 1-6 are processed as information C by the relay device 2-3, and the information C is transmitted to the middle server device 3-2.

  Further, the middle server device 3-1 processes the information A and the information B into the information D, and transmits the information D to the rear server device 4. The middle server device 3-2 processes the information B and the information C into information E, and transmits the information E to the rear server device 4. Thus, the rear server device 4 receives the information D in which the information # 1 to # 4 is processed and the information E in which the information # 3 to # 6 is processed. The processing performed by the relay devices 2-1 to 2-3 and the middle server devices 3-1 and 3-2 is a plurality of processing target data received from different transmission sources (for example, the relay device 2-1). In this case, a process for connecting information # 1 and information # 2) and a predetermined process necessary for relaying are included.

  The rear server device 4 and the middle server devices 3-1 and 3-2 use these received information, for example, in order to obtain more necessary information for the sensor according to the purpose. Send command data to instruct the acquisition method. FIG. 2 is a diagram illustrating a functional configuration example of each device configuring the monitoring system of the present embodiment illustrated in FIG. As shown in FIG. 2, the sensor 1-i (i = 1 to 6) includes a history information storage unit 11 and an entity 12. The relay device 2-j (j = 1 to 3) includes a history information storage unit 21 and an entity 22, and the middle server device 3-k (k = 1, 2) includes a history information storage unit 31 and an entity. The rear server device 4 includes a history information storage unit 41 and an entity 42. Here, a configuration example using the sensors 1-1 to 1-4 among the devices shown in FIG. 1 is shown.

  The sensors 1-1 to 1-4 acquire information on information to be monitored (for example, images) according to a predetermined condition (for example, periodically), and the acquired information is stored as history information (History Cash). The information is stored in the information storage unit 11. Also, the relay devices 2-1 to 2-3 hold the information received from the sensors 1-1 to 1-4 as history information in the history information storage unit 21, and the middle server devices 3-1 and 3-2 Information received from the relay devices 2-1 to 2-3 is held as history information in the history information storage unit 31, and the rear server device 4 stores information received from the middle server devices 3-1 and 3-2 as history information. It is assumed that the unit 41 holds it.

  Here, the relay devices 2-1 to 2-3, the middle server devices 3-1 and 3-2, and the rear server devices 4 which are monitoring devices process information acquired by the sensors 1-1 to 1-4. It is also assumed that it has a function to determine whether more detailed information acquisition or specific condition information is necessary as topic data based on the processing result. In addition, the judgment is made by notifying the conductor of the processed information by display, voice, etc., and the conductor instructs the acquisition of the topic data and determines whether the topic data is necessary based on the instruction. May be.

  The command method according to this embodiment will be described with reference to FIG. First, it is assumed that the middle server device 3-1 receives the information D as described with reference to FIG. 1 and determines that the information of the sensor 1-1 needs to be acquired as topic data based on the information D. The middle server device 3-1 transmits command data for requesting acquisition of the topic data to the relay device 2-1 that relays information of the sensor 1-1. The relay device 2-1 searches its history information storage unit 21 and confirms whether the information requested to be acquired by the command data exists in the history information storage unit 21.

  When the information requested to be acquired by the command data exists in the history information storage unit 21, the relay device 2-1 transmits the result obtained by the search to the middle server device 3-1 as topic data. At this time, the result obtained by the search is stored in the entity 22.

  Further, when the information requested to be acquired by the command data does not exist in the history information storage unit 21, the relay device 2-1 transmits the command data for requesting the sensor 1-1 to acquire the topic data. And the sensor 1-1 searches its own history information storage part 11, and when the information requested | required acquisition by command data is obtained as a search result, the search result is transmitted to the relay apparatus 2-1 as topic data. To do. At this time, in the sensor 1-1, the result obtained by the search is stored in the entity 12. The relay device 2-1 transmits the received topic data to the middle server device 3-1.

  Next, the middle server device 3-1 determines that it is necessary to acquire information on the sensor 1-2 as topic data, and transmits the command data for requesting acquisition of information on the sensor 1-2 to the relay device 2-2. Send to. Here, the command data is transmitted to the relay device 2-2, but may be transmitted to the relay device 2-1.

  The relay device 2-2 searches its history information storage unit 21 and confirms whether the information requested to be acquired by the command data exists in the history information storage unit 21. When the information requested to be acquired by the command data exists in the history information storage unit 21, the relay device 2-2 transmits the result obtained by the search to the middle server device 3-1 as topic data. At this time, the result obtained by the search is stored in the entity 22.

  Further, when the information requested to be acquired by the command data does not exist in the history information storage unit 21, the relay device 2-2 transmits the command data requesting the sensor 1-2 to acquire the topic data. And the sensor 1-2 searches its own history information storage part 11, and when the information requested to be acquired by the command data is obtained as a search result, the search result is transmitted to the relay device 2-2 as topic data. To do. At this time, in the sensor 1-2, the result obtained by the search is stored in the entity 12. Then, the relay device 2-2 transmits the received topic data to the middle server device 3-1.

  Next, the rear server apparatus 4 determines that it is necessary to acquire information on the sensor 1-3 as topic data, and sends command data requesting acquisition of information on the sensor 1-3 to the middle server apparatus 3-2. Send. The middle server apparatus 3-2 searches its own history information storage unit 31 and determines whether there is information requested to be acquired by command data. When information requested to be acquired by command data is obtained as a search result, the information is transmitted as topic data to the backward server device 4 and the information is stored in the entity 32.

  When the information requested to be acquired by the command data is not obtained as a search result, the command data is transmitted to the relay device 2-3. The relay device 2-3 searches its history information storage unit 21 and confirms whether the information requested to be acquired by the command data exists in the history information storage unit 21. When the information requested to be acquired by the command data is present in the history information storage unit 21, the relay device 2-3 transmits the result obtained by the search to the middle server device 3-2 as topic data. Information is stored in the entity 22.

  Further, when the information requested to be acquired by the command data does not exist in the history information storage unit 21, the relay device 2-3 transmits the command data for requesting acquisition of the topic data to the sensor 1-3. Then, the sensor 1-3 searches its own history information storage unit 11, and when the information requested to be acquired by the command data is obtained as a search result, the search result is transmitted as topic data to the relay device 2-3. At the same time, the information is stored in the entity 12. Then, the relay device 2-3 transmits the received topic data to the middle server device 3-2, and the middle server device 3-2 transmits the topic data to the rear server device 4. The backward server device 4 stores the received topic data in the entity 42.

  The flow of command data processing and topic data processing have been described above. Next, a case where the command data includes information on the strength of command is described. FIG. 3 is a flowchart showing an example of a normal process using the command authority strength. In the example of FIG. 3, the command method according to the present embodiment is applied to an attack system in which an instruction such as attack or withdrawal is instructed to a soldier, and the soldier performs an attack using a shooting device used by the soldier. An example will be described.

  Here, it is assumed that the power of command is given to each owner. Here, a monitoring device to be used for each owner is determined, and the monitoring device is used by one owner. The command strength is higher as the value is larger. When command data is transmitted, the command strength corresponding to the monitoring device of the transmission source as the command data attribute (the command of the user who uses the monitor device) Authority) is transmitted. First, the owner # 1 operates a rear server device that is his / her own monitoring device, and transmits command data instructing an operation including an attack command to the middle server device (step S11). On the other hand, owner # 2, which is another owner, operates the rear server device used by himself / herself and transmits command data instructing a withdrawal command to the middle server device (step S12).

  The middle server device compares the command strengths of the two command data transmitted in step S11 and step S12 (step S13), selects the command data transmitted in step S11 having a higher command command strength, and selects the selected command. Data is transmitted to the monitoring device used by soldier # 1 (step S14). The command data transmitted in step S12 having a low command authority is discarded. Each soldier uses a unique monitoring device, and this monitoring device has a function of displaying command data. Similarly, the middle server device transmits the selected command data to the monitoring device used by the soldier # 2 (step S15).

  The monitoring device used by the soldier # 1 displays the content of the command data using its command data display device (step S16). Since the command data including the attack command is selected in step S13, the content including the attack command is displayed. Similarly, the monitoring device used by the soldier # 2 displays the content of the command data using its command data display device (step S17).

  Soldier # 1 obtains by confirming the display of the content of the command included in the command data from the monitoring device used by himself or by receiving the data of the content of the command (step S18). The contents of the command included in the command data are confirmed by display or received by receiving the data of the contents of the command from the monitoring device used by the computer (step S19). Soldier # 1 and soldier # 2 then perform an attack using the shooting device based on the content of the command (step S20, step S21).

  Next, a case where the strength of the command authority is changed when the processing described in FIG. 3 is performed will be described. FIG. 4 is a flowchart illustrating an example of processing after the change of the command authority strength. Assume that a failure occurs in the backward server device used by the owner # 1 described above, and an attack command cannot be transmitted from the device (step S31). In order to transmit an attack command using the backward server device used by owner # 2, owner # 1 first changes the command strength corresponding to owner # 2 from 3 to 5, and after the change The command data including the attack command is transmitted from the rear server device used by the owner # 2 to the middle server device (step S32).

  The middle server device receives the command data transmitted after the change of command authority strength (step S33), and transmits the command data to the monitoring device used by the soldier # 1 and the monitoring device used by the soldier # 2 (step S34, step S35). ). Thereafter, Steps S16 to S21 are performed in the same manner as before the change of the command authority strength.

  As described above, the device corresponding to the soldier # 1 and the device corresponding to the soldier # 2 in the state before the change of the command authority strength explained in FIG. 3 and the state after the change of the command authority strength explained in FIG. It is possible to change the owner who manages the device group composed of In this way, by changing the command authority strength corresponding to the owner, it is possible to manage a domain composed of devices using command data (a set of devices for realizing one function by a plurality of devices). it can.

  Next, the mechanism for changing the power of command will be described. FIG. 5 is a diagram illustrating an example of processing related to the command authority strength among the entities held by the respective monitoring devices (monitoring devices including the rear server device) before the change of the command authority strength. An entity E1 indicates an entity held by a certain monitoring device, and entities E2 to E4 indicate entities held by different devices. The command authority strength tables T1 to T4 are tables of command authority strength data held in the entities E1 to E4, respectively, and hold the identifier of the owner and the command authority strength in association with each other. Before the change of command strength, as shown in the command strength tables T1 to T4, the command strength corresponding to the owner User # 1, User # 2, User # 3, User # 4, User # 5 is , 3, 4, 5, 2, and 4.

  For example, it is assumed that the command data operated by User # 3 is transmitted from the device holding entity E1 to the device holding entity E2 (step S51). At this time, the command data to be transmitted has attributes of owner = User # 3 and command authority strength = 5. When the device holding the entity E2 receives the command data, the device compares the command power strength table T2 held by the device with the attribute of the command data, and is in agreement (User # 3 and the command power). If it is determined that the strength is 5), the command data is retained without being discarded.

  Similarly, it is assumed that the command data operated by User # 3 is transmitted from the device holding entity E1 to the device holding entity E3 and the device holding entity E4 (steps S52 and 53). When the device holding the entity E3 and the device holding the entity E4 each receive the command data, the command power strength table T3 or T4 held by the device itself is compared with the attribute of the command data, and they match. If judged, the command data is retained without being discarded.

  FIG. 6 is a diagram illustrating an example of processing related to the command authority strength after the change of the command authority strength is performed from the state of FIG. 5. Assume that each device holds command authority strength tables T1 to T4 similar to those in FIG. In this state, it is necessary to delete the entry of User # 3, and the command authority strength of User # 3 in the command authority strength table T1 is changed to zero. Then, instead of User # 3, the command authority of User # 5 in the command authority strength table T1 is changed from 4 to 5 (step S54).

  When the content of the command authority strength table T1 is changed as described above, the device holding the entity E1 sends control data for notifying the change to the device holding the entity E2 and the device holding the entity E3. Transmit (step S55, step S56). This control data includes information to be changed, that is, information indicating that the command strength is 5 for the owner User # 5 and that the command strength is 0 for the owner User # 3.

  The device holding the entity E2 compares the content of the received control data with the content of the command authority strength table T2 held by itself, and the comparison result does not match, so the command authority of the command authority strength table T2 is based on the control data. The intensity is changed (step S57). Similarly, the device holding the entity E3 compares the content of the received control data with the content of the command authority strength table T3 held by itself, and the comparison result does not match, so the command authority strength table T3 is based on the control data. Is changed (step S58).

  FIG. 7 is a diagram illustrating an example of another processing procedure for changing the power of command. In the example of FIG. 7 as well, as in the case of FIG. 6, it is necessary to delete the entry of User # 3, and the command authority strength of User # 3 in the command authority strength table T1 is changed to zero. Then, instead of User # 3, the command authority of User # 5 in the command authority strength table T1 is changed from 4 to 5 (step S60).

  Then, the device that holds the entity E1 includes control data for notifying the change in the command data that indicates the content of the command, and the device that holds the entity E2, the device that holds the entity E3, and the entity E4. Is transmitted to the device holding the entity E5 and the device holding the entity E5 (steps S61 to S64). And each apparatus holding entity E2-E5 changes the table of the command authority strength which self hold | maintains based on command data.

  In the above example, the operation of each device has been described based on the command data, taking the monitoring system and the attack system as examples. As described above, in order to realize various functions, a plurality of devices perform operations based on command data including contents related to the device based on command data, thereby forming a domain based on the command data. Will be realized. Therefore, if domain members are notified within the same domain using command data, the domain can be managed autonomously. In the present embodiment, it is assumed that the constituent members of the domain are notified using the command data as described above, and the information is held in the entity of each device.

  In addition, by changing the command authority strength that is an attribute of the command data, the owner who conducts the domain formed by the command data can be changed.

  Further, the command authority strength may be handled as a management level, and conditions such as the operation of each domain and the possibility of domain configuration change may be determined for each management level.

  Further, when transmitting the command data, it is necessary to transmit the command data to a plurality of entities, and when the instruction content includes data, the transmission time becomes long. For this reason, the correspondence between the contents of the data to be transmitted as command data and the number for specifying the contents is determined, each entity holds the correspondence, and by specifying the number in the command data, the transmission time is set. You may make it shorten.

  Thus, in this embodiment, command data to be adopted is selected based on the command authority strength, and a domain is formed based on the selected command data. Therefore, domain reconstruction can be performed efficiently. Moreover, processing can be performed efficiently according to the strength of command. For this reason, when there is a change in a commanded device or person during a large-scale disaster or battle, it is efficient and safe to transfer the command strength associated with the device or person to another device or person. It becomes possible to carry out the transfer.

Embodiment 2. FIG.
FIG. 8 is a diagram showing a configuration example of a network system for realizing the domain management method according to the second embodiment of the present invention. As shown in FIG. 8, the network system according to the present embodiment includes nodes 5-1 to 5-6. In this network system, one or more of the nodes 5-1 to 5-6 form a domain, and the domain D1 is a domain # 1 composed of the nodes 5-1 to 5-4. The domain D2 indicates the domain # 2 configured by the nodes 5-1 and 5-4, and the domain D3 indicates the domain # 3 configured by the nodes 5-5 and 5-6. . Each node holds information on members of the domain to which it belongs as an entity in the node. The entity is held in an entity included in each node.

  For example, the entities of node 5-1 and node 5-4 include members of domain # 1 and members of domain # 2. The entities of the node 5-2 and the node 5-3 include members of the domain # 1, and the entities of the nodes 5-5 and 5-6 include members of the domain # 3. This member (node constituting the domain) is dynamically changed by recombination (reconstruction) of the domain.

  Each domain is configured using the command data described in the first embodiment, and the command data has command authority strength as an attribute. For example, by transmitting a node constituting a domain and an identifier for identifying the domain based on the command data, the node that has received the command data can know information on the domain to which the node belongs. The command authority strength of the command data used in configuring the domain is held as the command authority strength configuring the domain. Here, it is assumed that domain # 1 is configured with command authority strength 5 and domain # 2 is configured with command authority strength 4.

  FIG. 9 is a flowchart illustrating an example of a process for executing an instruction in a domain based on command authority strength. First, it is assumed that an entity E1 of a certain node transmits command data having an integer value on the instance as the command authority strength from another node (step S71). In this command data, it is assumed that the command strength is 1 and the content of the data (command) included in the command data is “withdrawal”. The entity E1 performs a process (write process) for holding the content of the data (command) included in the command data (step S72). Here, it is assumed that the command “withdrawal” is included in the command data, and the entity E1 writes the command “withdrawal”. Next, the entity E1 receives the data transmitted from the command issuer (step S73).

  Further, to the entity E2 of a node different from the entity E1, another command data is transmitted from the node that transmitted the command data to the entity E1 in step S71 (step S74). In this command data, it is assumed that the command strength is 4 and the content of the data (command) included in the command data is “launch”. The entity E2 performs a process of writing a “fire” command (step S75). Then, the entity E2 receives the data transmitted from the command issuer (step S76).

  Then, the entity E1 and the entity E2 compare the retained (written) instruction with the data transmitted from the instruction issuer, and direct the retained instruction and the data transmitted from the instruction issuer. If the right strengths match, that is, if the right owner's data, the data is applied (step S77). If the command held and the command sent by the command issuer do not match, the data is rejected.

  Then, the applied data is transmitted to the entity E3, and the entity E3 performs reading processing of the retained instruction based on the transmitted data (step S78), and the instruction (such as “launch”, “withdraw”) ( In this case, since “fire” has been applied, a “fire” command is transmitted to the command executor (step S79).

  Next, the command authority strength determination process of the present embodiment will be described. FIG. 10 is a diagram illustrating a configuration example of the entity 51 included in the node according to the present embodiment. The entity 51 includes an authentication mechanism unit 52, a discrimination / determination mechanism unit 53, and an authentication non-permitted data discard mechanism unit 54. Also, the entity 51 receives command data 50 having various command strengths (command strength S = 1, 2, 3, 4, 5) transmitted from other nodes. The authentication mechanism unit 52 authenticates the command data. If the command data is authenticated, the command data is sent to the determination / determination mechanism unit 53. The data is sent to the unit 54. The authentication disapproval data discard mechanism unit 54 discards the input command data.

  The authentication performed by the authentication mechanism unit 52 performs, for example, authentication of whether the owner information that has transmitted the command data is an owner managed by the authentication mechanism unit 52 or the like. This authentication process is similar to the process performed by the command authority determining unit 62 of the determining / determining mechanism unit 53, and any of the processes may be omitted.

  FIG. 11 is a diagram illustrating a configuration example of the discrimination / determination mechanism unit 53. The determination / determination mechanism unit 53 includes a data reception unit 61, a command authority strength determination unit 62, an instruction hierarchy determination unit 64, a domain management unit 66, and a data transmission unit 68. An intensity table 63, an instruction hierarchy table 65, and a domain management table 67 are held.

  The data reception unit 61 receives command data and performs predetermined data reception processing, and the command authority strength determination unit 62 performs command power strength determination processing described later on the command data after the reception processing. Then, the command hierarchy determination unit 64 refers to the command hierarchy table 65 for the command data after the command authority strength determination process, and determines the command hierarchy (owner or the like). Then, the domain management unit 66 refers to the domain management table 67 and manages domain information, and the data transmission unit 68 transmits the command data to another entity.

  FIG. 12 is a diagram illustrating a configuration example of the command authority strength determination unit 62. The command authority strength determination unit 62 includes a command authority strength acquisition unit 71, a command authority strength comparison unit 72, a command authority strength determination unit 74, a discard processing unit 75, and a control unit 76. Reading from the authority level table 73 (same as the authority level table 63) and writing to the authority level table 73 are performed.

  The command data input from the data reception unit 61 to the command authority strength determination unit 62 is first input to the command authority strength acquisition unit 71. The command authority strength acquisition unit 71 acquires (extracts) the owner identifier and command authority strength of the data from the command data, and sends them to the command authority strength comparison unit 72. The command authority strength comparison unit 72 compares the value stored in the command authority strength table 73 with the command authority strength acquired from the command data, and sends the comparison result to the command authority strength determination unit 74. The command authority strength determination unit 74 transmits the command data to the discard processing unit 75 when the comparison result does not match, and transmits the command data to the control unit 76 when the comparison result matches. Assume that the command authority strength table 73 stores the command authority strength for each owner as illustrated in FIG. 5 of the first embodiment. The discard processing unit 75 discards the received data, and the control unit 76 sends the received data to the outside (instruction hierarchy determination unit 64).

  FIG. 13 shows a configuration example of the instruction hierarchy determination unit 64. The instruction hierarchy determination unit 64 is a processing unit that determines an instruction hierarchy indicating an owner or the like. The instruction hierarchy determination unit 64 includes an instruction hierarchy acquisition unit 81, an instruction hierarchy comparison unit 82, an instruction hierarchy determination unit 84, a discard processing unit 85, and a control unit 86, and also includes an instruction hierarchy table 83 (instruction hierarchy). Read from the hierarchy table 65) and write to the instruction hierarchy table 83.

  The instruction hierarchy acquisition unit 81 of the instruction hierarchy determination unit 64 acquires (extracts) information such as the owner and instruction contents necessary for determining the instruction hierarchy from the command data input from the command authority strength determination unit 62. Then, the instruction hierarchy comparison unit 82 compares the acquired information with the contents stored in the instruction hierarchy table 83. Here, in the instruction hierarchy table 83, for each owner (owner identifier), information such as instructions and conditions that can be issued by the owner is stored. The acquired information is compared with the contents (conditions) stored in the instruction hierarchy table 83 corresponding to the owner included in the acquired information. If the comparison result does not match based on the comparison result of the instruction hierarchy comparison unit 82, the command hierarchy determination unit 84 transmits the command data to the discard processing unit 85, and if the comparison result matches. Transmits command data to the controller 86. The discard processing unit 85 discards the input command data, and the control unit 86 sends the command data to the outside (domain management unit 66).

  FIG. 14 is a diagram illustrating a configuration example of the domain management unit 66. The domain management unit 66 includes a domain information acquisition unit 91, a domain information comparison unit 92, a domain information determination unit 94, and a domain recombination unit 95, and includes a domain management table 93 (same as the domain management table 67). And writing to the domain management table 93.

  The domain information acquisition unit 91 extracts information related to the domain configuration from the command data input from the command hierarchy determination unit 64, sends the information to the domain information comparison unit 92, and sends the command data to the data transmission unit 68. Note that if the information related to the domain configuration does not exist in the command data, only the command data may be transmitted to the data transmission unit 68 without performing the subsequent processing of the domain management unit 66.

  The domain information comparison unit 92 compares the extracted information with information stored in the domain management table 93. Assume that the domain management table 93 stores the members of the domain to which it belongs for each domain. When the comparison result of the domain information comparison unit 92 matches, the domain information determination unit 94 notifies the domain recombination unit 95 that the recombination of the domain has been detected, and the comparison result of the domain information comparison unit 92 matches. If not, it is determined that there is no domain recombination, and the domain recombination unit 95 is not notified. Note that this notification includes an instruction of a location that does not match (that is, a changed location).

  The domain recombination unit 95 updates the domain management table 93 based on the notification of domain recombination.

  FIG. 15 is a diagram illustrating an example of the domain management table. In the example of FIG. 15, the correspondence between the entities E1 to EN (N is a natural number) and the domains to which each belongs (domains D1 to DK (K is a natural number)) is shown. Assume that each entity holds an entity constituting a domain to which the entity belongs as a domain member in the domain management table. That is, it is assumed that the entities E1, E2, and E3 indicated by the same fill hold information that the constituent members of the domain D1 are the entities E1, E2, and E3.

  In the upper example of FIG. 15, one entity belongs to one domain, and the lower part is an example where one entity belongs to a plurality of domains. In the upper example, the entities E1 to E3 belong to the domain D1, the entities E4 and E5 belong to the domain D2, and the entities E6 and E7 belong to the domain D3.

  On the other hand, in the lower example of FIG. 15, entities E1, E2, E3 belong to domain D1, entities E3, E4, E5 belong to domain D2, and entities E4, E6 belong to domain D3.

  In this way, the network configuration is switched in the present embodiment by utilizing the fact that each entity can belong to a plurality of domains. FIG. 16 is a diagram illustrating a configuration example before network switching. FIG. 17 is a diagram illustrating a configuration example after network switching. As shown in FIGS. 16 and 17, this network system is composed of a large number of nodes including nodes 100-1 to 100-14, and a plurality of nodes are grouped to have one function. In the following description, in order to distinguish between before and after network switching, a group before network switching is expressed as a zone, and a group after switching is expressed as a domain. The function is the same for the zone and the domain.

  In FIG. 16, the nodes 100-1 to 100-6 constitute the zone 110, the nodes 100-7 to 100-10 constitute the zone 111, and the nodes 100-11 to 100-14 constitute the zone 112. . In this state, it is assumed that a failure has occurred in the node 100-4, and the network configuration is switched so as to bypass the node in which the failure has occurred. Here, as shown in FIG. 17, a domain D1 is formed by the nodes 100-1 to 100-8, and a domain D2 is formed by the nodes 100-7 to 100-10.

  At this time, the entities of the nodes 100-7 and 100-8 hold both members of the domain D1 and the domain D2. As described above, since the entity has information of a plurality of domains overlappingly, the failure path of the node 100-4 can be bypassed without reducing the number of nodes belonging to the domain D2 (zone 111 before the change). . For example, the node 100-5 cannot connect to the node 100-4, but can transmit data to other nodes via the node 100-7.

  In this embodiment, the method of switching the domain configuration using the command data accompanied by the command authority strength has been described. However, the apparatus that performs the domain management using the command data accompanied by the command authority strength is configured as follows. You may make it grasp | ascertain whether the structure of each domain dynamically entered / leaved by collecting the information about the domain which belongs from an entity. By doing so, it is possible to efficiently grasp the domain configuration and realize domain management.

  When switching the domain, for example, if there is a problem if switching occurs during operation, a mode for switching is provided, and the domain is switched only when switching to the switching mode. By enabling this, domain switching may be suppressed.

  As described above, in this embodiment, the domain to which a node belongs is switched using command data, and at that time, one node can belong to a plurality of domains. Each domain can be managed autonomously by holding members of the domain belonging to the entity. For this reason, even when a failure occurs in a node, communication and operation can be continued efficiently. In addition, the domain management method and device based on the power of command of the invention are useful for carrying out relief activities in areas or seas where large-scale natural disasters or man-made disasters have occurred. It is also useful when performing. Each of the device apparatus entity and the network system of the present invention can be variously modified, modified, combined, etc. in addition to those described above.

  As described above, the domain management method, the node, and the domain management system according to the present invention are useful for a system that configures a domain with a plurality of devices, and are particularly suitable for a system that functions in an earthquake, disaster, or battlefield. Yes.

It is a figure which shows the structural example of Embodiment 1 of the monitoring system which implement | achieves the domain management method concerning this invention. FIG. 3 is a diagram illustrating an example of a functional configuration of each device configuring the monitoring system according to the first embodiment. It is a flowchart which shows an example of the normal process using command authority strength. It is a flowchart which shows an example of the process after implementing change of command authority strength. It is a figure which shows an example of the process regarding the power of command. It is a figure which shows an example of the process regarding the command authority strength after implementing change of the command authority strength. It is a figure which shows an example of another processing procedure of the change of command authority strength. 6 is a diagram illustrating a configuration example of a network system according to a second embodiment. FIG. It is a flowchart which shows an example of the process which implements an instruction within a domain based on command authority strength. It is a figure which shows the structural example of the entity with which the node of this Embodiment is provided. It is a figure which shows the structural example of a discrimination | determination / determination mechanism part. It is a figure which shows the structural example of a command authority strength determination part. It is a figure which shows the structural example of a command hierarchy discrimination | determination part. It is a figure which shows the structural example of a domain management part. It is a figure which shows an example of a domain management table. It is a figure which shows the structural example before switching of a network. It is a figure which shows the structural example after switching of a network.

1-1 to 1-6 sensor 2-1 to 2-3 relay device 3-1 and 3-2 middle server device 4 backward server device 5-1 to 5-6, 100-1 to 100-14 node 11 and 21 , 31, 41 History information storage unit 12, 22, 32, 42, 51 Entity 50 Command data 52 Authentication mechanism unit 53 Discrimination / determination mechanism unit 54 Authentication disapproval data discard mechanism unit 61 Data reception unit 62 Command authority strength determination unit 63 Command Strength Table 64 Command Hierarchy Determination Unit 65 Command Hierarchy Table 66 Domain Management Unit 67, 93 Domain Management Table 68 Data Transmission Unit 71 Command Power Strength Acquisition Unit 72 Command Power Strength Comparison Unit 73 Command Power Strength Table 74 Command Power Strength Determination Unit 75, 85 Discard processing part 76, 86 Control part 81 Instruction hierarchy acquisition part 82 Instruction hierarchy comparison part 83 Instruction hierarchy table 84 Instruction Layer determination unit 91 domain information obtaining unit 92 domain information comparison unit 94 domain information determining unit 95 domain rearrangement unit 110-112 zone E1~EN entity T1~T4 command authority strength management table D1~D3 domain

Claims (10)

A domain management method when a plurality of nodes configure a domain and perform processing in units of domains,
The node retains the command authority strength indicating the degree of authority of the user as the command authority strength information in association with the user identifier,
A domain management information holding step in which the node holds domain management information which is information in which a node constituting a domain to which the node belongs is associated with the domain;
A command data transmission step in which the node adds the domain information related to the domain configuration to the command data for instructing the operation content, the command authority strength of the user instructed to transmit the command data, and the identifier of the user ; ,
A domain management information management step in which a node receiving command data from another node updates domain management information held by itself based on the command data;
The node that has received the command data receives the command data when the correspondence between the command strength added to the command data and the user instructing transmission of the command data matches the command strength information. A command data determination step for validating and discarding the command data if they do not match,
A domain management method comprising: A control information transmission step in which the node transmits control information instructing a change in correspondence between the command authority strength and the identifier of the user;
A control information reflecting step in which the node that has received the control information changes the correspondence between the power of command held by the node and the identifier of the user based on the control information;
The domain management method according to claim 1 , further comprising: Each node holds command information that corresponds to an operation that can be instructed by command data having the command strength for each command strength.
further,
The node that has received the command data validates the command data when the correspondence between the action instructed by the command data and the command strength added to the command data matches the command information, Order decision step to discard the command data if they do not match,
Domain management method according to claim 1 or 2, characterized in that it comprises a. For each domain, define a command strength value that can indicate what to do in that domain,
When there is a change in command authority strength of the user, the domain management method according to claim 1, 2 or 3, characterized in that to change the domain configuration based on the new command authority intensity after the change. Allowing the node to belong to multiple domains;
In the domain management information holding step, as said domain management information, according to any one of claims 1-4, characterized in that for holding the nodes of the plurality of domains by the own apparatus belongs in correspondence with the domain Domain management method. A domain configuration instruction step of transmitting, as the command data, a configuration switch that is a change of a node configuring the domain;
Further including
The configuration switching, domain management method according to any one of claims 1-5, characterized in that run without stopping the network. A domain configuration instruction step of transmitting, as the command data, a configuration switch that is a change of a node configuring the domain;
Further including
The node comprises a switching mode for executing the switching of the domain, when operating in the switching mode, according to any one of claims 1-5, characterized in that to perform the switching of domains Domain management method. The node holds the correspondence between the processing content to be transmitted as command data and the number for designating the processing content,
Wherein the command data transmission step, as the conductor data, the domain management method according to any one of claims 1-6, characterized in specifying the number corresponding to the process content. The node in a system in which a plurality of nodes constitute a domain and perform processing in units of domains,
The command authority strength indicating the degree of authority of the user is associated with the user identifier and held as the command authority strength information.
Domain information holding means for holding domain management information, which is information associating nodes constituting the domain to which the node belongs with the domain;
Transmitting means for adding the domain information related to the domain configuration to the command data for instructing the operation content, the command authority strength of the user who instructed the transmission of the command data, and the identifier of the user ;
Domain management means for updating domain management information held by itself based on command data received from other nodes;
With
When the command data is received, the command data is validated when the correspondence between the command strength added to the command data and the user instructing the transmission of the command data matches the command strength information. , if they do not match the node, it characterized that you discard the command data. A domain management system in which a plurality of nodes configure a domain and perform processing in units of domains
The node retains the command authority strength indicating the degree of authority of the user as the command authority strength information in association with the user identifier,
The node holds domain management information, which is information associating a node constituting a domain to which the node belongs with the domain,
The node transmits the domain data related to the domain configuration to the command data for instructing the operation content, the command authority strength of the user who instructed the transmission of the command data, and the identifier of the user .
A node that receives command data from another node updates its own domain management information based on the command data ,
The node that has received the command data receives the command data when the correspondence between the command strength added to the command data and the user instructing transmission of the command data matches the command strength information. A domain management system characterized in that if it does not match, the command data is discarded .

Images