JP2007179278A - Information storage system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To easily, inexpensively and quickly achieve the setting of a device controller without adopting any setting method by the manual operation of an operator or any setting method for connection to a server. <P>SOLUTION: A device controller is provided with a configuration description information driver 14 for storing a self-configuration description file and a distributed shared memory 13 for storing the configuration description file of the other device controller. When newly participating in a network NW, a storage control part 12 transmits a file transfer request with its own ID to other device controller, and stores the configuration description file from the other device controller in the configuration description information driver 14. A field bus monitoring/control part 17 and field bus interfaces 18A, 18B and 18C control the devices of the field buses A, B and C by referring to the configuration description file. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to an information storage system that multiplexes and stores setting information between device controllers that control and monitor devices according to predetermined setting information.

  Conventionally, when a device controller is connected to a sub-network composed of a plurality of devices on a general-purpose bus and the device controller is exchanged, it is necessary to reset the device controller to enable control of the sub-network.

  As a method for resetting the device controller, the setting of the device controller can be installed manually by a worker. For example, a portable medium (CD, floppy (registered trademark) disk, USB (Universal Serial Bus) memory) in which a worker stores a setting file is inserted into a device controller for resetting. As a result, the device controller can detect and automatically set the setting file used by itself.

As another method for resetting the device controller, the device controller is connected to the server storing the setting file, and the setting file is downloaded from the server. Thus, when the device controller is replaced, the device controller can monitor and control the device by issuing a search request for its own configuration file to the server. As a technique for backing up the setting file to the server in this way, the following Patent Document 1 and the like can be cited.
JP 2004-102450 A

  However, in the device controller setting method described above, the portable medium storing the setting file may be lost, and in this case, the device controller cannot be set. Further, the lost portable media may be used by a malicious third party. In addition, there is a possibility that the setting file stored in the portable medium may be damaged and become unreadable, and it is necessary to always prepare a new portable medium in preparation for this. Furthermore, there is a case where erroneous data is stored in the portable medium due to a setting error of an operator who manages creation and use of the portable medium storing the setting file. In addition, it is necessary to provide the device controller with a disk playback device for reading portable media, resulting in high costs.

  Furthermore, the device controller needs to be provided with a means for connecting to the server, which increases the cost. Furthermore, the device controller cannot be set when the server cannot be used.

  Therefore, the present invention has been proposed in view of the above-described circumstances, and it is simple, low-cost, and short-time without adopting a manual setting method of an operator or a setting method for connecting to a server. An object is to provide an information storage system capable of setting a controller.

  The information storage system according to the present invention is connected to a sub-network composed of a plurality of devices, notifies an event that has occurred in each device to the outside, and notifies each device of an external request. A plurality of device controllers for operating the device.

  In order to solve the above-described problem, each device controller is information for communicating with a device of a subnetwork connected to the device controller, and stores configuration description information indicating the device configuration of the subnetwork. Reference is made to information storage means, device control means for communicating with the devices of the sub-network with reference to the configuration description information, and connected to another device controller via a communication line to communicate with the other device controller. Performing communication means; storing configuration description information transmitted from another device controller and received by the communication means; and storage means for backup functioning as a backup memory for the configuration description information of the other device controller; and the configuration description The configuration description information stored in the information storage means is stored in another device. A storage control means for storing the configuration description information of another device controller in its own backup storage means, and storing it in the configuration description information storage means of each device controller. The description information is stored in multiple in the backup storage means of one or more other device controllers.

  In the information storage system according to the present invention, the configuration description information stored in the configuration description information storage means of each device controller is multiplexed and stored in the backup storage means of one or more other device controllers. The device controller can be set simply by downloading the stored configuration description information, and it is simple, low-cost, without adopting the manual setting method of the worker or the setting method of connecting to the server. The device controller can be set in a short time.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  In the present invention, for example, as shown in FIG. 1, a plurality of device controllers D1 to D4 (hereinafter simply referred to as “device controller Di” when collectively referred to) are connected to a network NW that is a general-purpose bus. Applies to storage systems. Examples of the network NW that is a general-purpose bus include the Internet using IP (Internet Protocol). Each of the plurality of device controllers D1 to D4 can perform P2P (Peer-to-peer) communication, and can exchange information with each other.

  Each device controller Di is connected to a subnetwork in which a plurality of devices are connected to a fieldbus. The device controllers D1 to D4 store configuration description files (F1 to F4) that store information for controlling and monitoring a plurality of devices connected to the fieldbus. The device controllers D1 to D4 store the configuration description files of the other device controllers Di in their own distributed shared memories 1-D1, 1-D2, 1-D3, and 1-D4, respectively. The distributed shared memory 1 is provided separately from the storage means for storing its own configuration description file, and functions as a backup storage means for the configuration description file of another device controller Di.

  The device controller Di is configured as shown in FIGS. As shown in FIG. 2, the device controller Di includes a field in which the device and the device controller Di communicate using an embedded network technology (EMIT (Embedded Micro Internetworking Technology), hereinafter referred to as EMIT technology). The bus A, the device and the device controller Di perform baseband transmission for modulating the pulse width to perform signal transmission / reception, a field bus B that performs communication in a predetermined multiplex transmission scheme (Nmast scheme), and a LON (Local A field bus C that performs communication by a distributed control network method called “Operating Network” is connected. The field bus may be connected to the device controller Di not only in the case of using the EMIT technique, the enmast system, and the LON, but in any system.

  A plurality of devices such as devices A0 to A2, S3 to S7,... Are connected to the field bus A, and a human sensor is included as the device S3. A plurality of devices such as devices S0, S1, A1, A3, A4... Are connected to the field bus B, and the device A1 includes illumination. Further, a plurality of devices such as devices A0 to A2, S3 to S5,... Are connected to the field bus C, and a temperature sensor is included as the device S2.

  The device controller Di includes a P2P communication processing unit 11 connected to a network NW that performs P2P communication with other device controllers Di, a storage control unit 12, and the above-described distributed shared memories 1-D1, 1-D2, 1-D3. , 1-D4, distributed shared memory 13, configuration description information driver 14, variable table 15, application processing unit 16, fieldbus monitoring / controlling unit 17, and a plurality of fieldbuses connected to itself. Fieldbus interfaces 18A, 18B, and 18C corresponding to A, B, and C are provided.

  The fieldbus interfaces 18A, 18B, and 18C are set so as to perform communication by a method corresponding to each fieldbus A, B, and C. For example, the fieldbus interface 18A employing the EMIT technology and the devices connected to the fieldbus interface 18A are configured as shown in FIG.

  The device includes a MOS (Micro Object Server) function unit 21 that transmits and receives various device control data, device status signals, and the like between EMIT middleware, and the fieldbus interface 18A includes routing processing between EMIT middleware, device An OAS (Object Access Server) function unit 31 for performing recognition processing of the device is mounted, and a control / monitoring request to the device to be controlled is output to a user terminal (not shown) managing the device and the device An OAL (Object Access Library) function unit (not shown) that performs status display and the like is mounted. Although FIG. 4 illustrates a case where only the OAS function unit 31 is mounted on the fieldbus interfaces 18A, 18B, and 18C, the OAL function unit may be mounted.

  In the device, an application processing unit 22 and an interface module 23 are connected to the MOS function unit 21.

  For example, when the application processing unit 22 functions as a sensor, an application code for acquiring a detection value (I / F value) is stored, and the detection value is held and transferred to the MOS function unit 21.

  The interface module 23 performs processing such as a data link layer in an OSI (Open Systems Interconnection) reference model. For example, processing according to Ethernet (registered trademark) is performed in the data link layer. Capabilities such as a communication protocol version and a communication speed of the interface module 23 are stored in the capability table 24 and can be acquired by the OAS function unit 31.

  The MOS function unit 21 functions as EMIT middleware between the application layer by the application processing unit 22 and the transport layer by the interface module 23. The MOS function unit 21 is given an object ID 21d by the OAS function unit 31 of the fieldbus interface 18A in order to identify that the device is an object in EMIT.

  The MOS function unit 21 performs an operation defined by a function 21a, an event 21b, and a variable 21c. The operation of the MOS function unit 21 is defined as a service table 21e and can be acquired as an interface ID by the OAS function unit 31 of the fieldbus interface 18A.

  When the device is a sensor, the function 21a is a detection value output function, the event 21b is, for example, an event that outputs a detection value when the detection value reaches a predetermined value, and the variable 21c is the detection value itself. Such a device generates an event at event 21b when the detected value reaches a predetermined value, and outputs the detected value of variable 21c by function 21a.

  A communication module 32 is connected to the OAS function unit 31 of the fieldbus interface 18A.

  The OAS function unit 31 is connected to a fieldbus monitoring / control unit 17 described later, and communicates with a device of the fieldbus A according to the control of the fieldbus monitoring / control unit 17. When the user and the administrator want to perform communication for controlling and monitoring a certain device, the fieldbus monitoring / control unit 17 is supplied with a control / monitoring request to that effect and returns a response to the control / monitoring request.

  The communication module 32 communicates with the interface module 23 of the device and also communicates with the communication module 32 of the apparatus in which the other OAS function unit 31 is mounted. The communication module 32 performs processing such as a data link layer in the OSI reference model. When each device is composed of various interface modules 23, the communication module 32 is configured such as a communication protocol version and a communication speed for each device or other device having the OAS function unit 31 according to the control of the device access controller 31 c. Performs communication processing according to the capabilities of the device.

  The OAS function unit 31 functions as EMIT middleware between the processing of the fieldbus monitoring / control unit 17 and the processing of the communication module 32. The OAS function unit 31 includes a device access server 31a, service information 31b stored in a predetermined memory, and a device access controller 31c.

  The device access server 31a receives a request from the client via the communication module 32, the fieldbus monitoring / control unit 17, and the P2P communication processing unit 11 in order to perform communication with the client (OAL). The device access server 31a controls the operation of transmitting the control / monitoring request to the device via the device access controller 31c and the communication module 32. Thus, the device access controller 31c transmits a request from the client to the device and controls the device.

  The device access controller 31 c searches the device service table 21 e and the capability table 24 via the communication module 32 in order to obtain the device interface definition and service information. Accordingly, the device access controller 31c determines what service (function 21a, event 21b, variable 21c) each device has, and service information indicating the correspondence between the object ID 21d of each device and the service list. 31b is created. The device access controller 31c recognizes what capabilities (communication protocol version and communication speed) each device has.

  When the MOS function unit 21 receives an event packet of an event at the communication module 32, the device access controller 31c analyzes the event packet by the device access controller 31c and notifies the device access server 31a. When a control / monitoring request from the client is transmitted to the device, the MOS function unit 21 that can respond to the control / monitoring request is recognized with reference to the service information 31b. Then, the destination object ID 21d is added to the control / monitoring request, and the packet is transmitted from the communication module 32 to the device in accordance with the capability of the device.

  The OAS function unit 31 is provided with an object ID 31d so that other EMIT middleware-compatible devices can identify the OAS function unit 31. The object ID 31d is stored in a packet to be transmitted when communicating with the device corresponding to the EMIT middleware such as the MOS function unit 21 of the device or a client (personal computer) in which another OAL is mounted.

  As shown in FIG. 3, the fieldbus interfaces 18A, 18B, and 18C including the OAS function unit 31 are configured to include a fieldbus driver 18a and a fieldbus interface unit 18b.

  When receiving the control data from the fieldbus monitoring / control unit 17, the fieldbus driver 18a refers to the configuration description information from the configuration description information driver 14, determines which device is to be operated, Send a command to the device. When the fieldbus interface unit 18b receives a command from the fieldbus driver 18a, the fieldbus interface unit 18b converts the command into a signal corresponding to the fieldbus A, B, or C, and sends the signal to the fieldbus A, B, or C.

  When the field bus interface unit 18b receives monitor data from the field buses A, B, and C to notify the field bus monitoring / control unit 17 of device state change and event occurrence, the field bus interface unit 18b receives the monitor data from the field bus. It is passed to the driver 18a and sent to the fieldbus monitoring / control unit 17.

  The fieldbus monitoring / control unit 17 refers to the variable table 15 and controls the fieldbuses A, B, and C. As shown in FIG. 6, the variable table 15 is configured by associating a device name, a device state, a variable type, a field bus ID, and an address in the field bus for each of the field buses A, B, and C. Then, the field bus monitoring / control unit 17 monitors the devices of the field buses A, B, and C, updates the contents of the variable table 15, and refers to the variable table 15 to change the devices of the field buses A, B, and C. Send control data to.

  As shown in FIG. 3, the fieldbus monitoring / control unit 17 is configured by dividing a function into a fieldbus monitoring unit 17A and a fieldbus control unit 17B. When receiving the monitor data from the fieldbus driver 18a, the fieldbus monitoring unit 17A updates the contents of the variable table 15. At this time, the fieldbus monitoring unit 17A recognizes the device name based on the object ID of the device included in the monitor data, and rewrites the state of the device. When the field bus control unit 17B receives control data from the application processing unit 16, the field bus control unit 17B refers to the variable table 15 and the configuration description file to determine the destination field bus and device of the control data, and the field bus driver 18a. Forward to.

  The application processing unit 16 controls application processing realized by the device. The application processing unit 16 refers to the variable table and gives a control / monitoring request to the fieldbus monitoring / controlling unit 17. As a result, the device is operated in accordance with the monitoring request and control request transmitted from the user via the network NW.

  Further, as shown in FIG. 3, the application processing unit 16 updates the application table 16A that sends control data to the device, the linkage table 16B in FIG. 7 described later, and the linkage table 16B according to its own configuration description information. The application updating unit 16C may be configured.

  The configuration description information driver 14 stores a configuration description file for controlling the field buses A, B, and C connected thereto. As shown in FIG. 3, the configuration description information driver 14 is connected to the storage control unit 12 and includes a configuration description file storage unit 14a for storing its own configuration description file. When a plurality of configuration description files are transmitted from another device controller, the configuration description information driver 14 rewrites the configuration description file in the configuration description file storage unit 14a with the configuration description file selected by the information selection unit 12E. The configuration description information driver 14 indicates that, for example, when a new device is connected to the field buses A, B, and C, information about the new device is added to the variable table 15 by the field bus monitoring unit 17A. When notified from the device controller ID storage unit 19, the changes of the field buses A, B, and C are reflected in the configuration description file. As a result, the configuration description file can always be kept up-to-date.

  Information included in the configuration description file (configuration description information) includes a fieldbus table that defines a fieldbus connected to itself as shown in FIG. 5, a variable table 15 in FIG. 6, and a configuration as shown in FIG. A linkage table that defines linkage operations performed between devices and software parameters storing other parameters as shown in FIG. 8 are included.

  The field bus table shown in FIG. 5 includes the field bus IDs (fb0, fb1, fb2,...) Of the field buses A, B, and C, and the methods (EMIT, Fieldbus information defining Nmast and Ron). This field bus table is read by the field bus monitoring / control unit 17 and referred to in order to identify the field buses A, B, and C connected thereto.

  The variable table 15 shown in FIG. 6 is configured as described above, and is referred to by the fieldbus monitoring / control unit 17 and the application processing unit 16 in order to specify the state of the device connected to itself. The variable table 15 is updated by referring to the configuration description information by the variable table updating unit 15A shown in FIG.

  The linkage table shown in FIG. 7 includes linkage event information that defines an event of a device that is a trigger for starting a linkage operation, linkage response device information that defines a device that responds when the linkage occurrence event occurs, Association result information that defines the result of the cooperation response device operating is associated. This linkage table is referred to by the application processing unit 16 when an event occurrence is detected by the fieldbus monitoring / control unit 17 via the fieldbus interfaces 18A, 18B, and 18C. If the application processing unit 16 determines that an event corresponding to the cooperation table has occurred, the application processing unit 16 operates so that the cooperation response device satisfies the cooperation result. In addition, this cooperation table may be comprised as a part function (cooperation table 16B) of the application process part 16, as shown in FIG.

  The software parameters shown in FIG. 8 store information types stored as parameters, parameter type information, and parameter values in association with each other. In this example, the size of the distributed shared memory 13, the capacity of its own configuration description file, and the number of times of device control are stored as parameters. The software parameters include parameters used in the fieldbus interfaces 18A, 18B, and 18C, parameters used in the application processing unit 16, parameters used in the storage control unit 12, parameters used in the P2P communication processing unit 11, and the like. Including.

  For example, the size of the distributed shared memory 13 is referred to by the storage controller 12 to determine whether or not the configuration description file of another device controller Di can be stored. It is determined whether or not the controller Di can store its own configuration description file.

  The storage control unit 12 uses the distributed shared memory 1 in the entire network NW to back up its own configuration description file to the distributed shared memory 13 of the other device controller Di, and the other device controller Di The configuration description file is backed up to its own distributed shared memory 13. When the storage control unit 12 backs up its own configuration description file to another device controller Di, the storage control unit 12 reads out its own configuration description file stored in the configuration description information driver 14 and reads it from the P2P communication processing unit 11 to the other device controller. Send to Di. Further, the storage control unit 12 receives a backup request from another device controller Di via the P2P communication processing unit 11 and stores the configuration description file of the other device controller Di in the distributed shared memory 13.

  Also, as shown in FIG. 4, the device controller Di is given a device controller ID by the operator's operation on the operation panel, operation on the dip switch, or the like. The device controller ID is stored in the device controller ID storage unit 19.

  As shown in FIG. 3, the device controller Di includes an information receiving unit 12A, an information updating unit 12B, an information requesting unit 12C, a configuration description information memory 12D, and an information selecting unit 12E as the storage control unit 12. .

  When the information request unit 12C detects that there is no configuration description file from the software parameters in the configuration description file storage unit 14a, the information request unit 12C causes the P2P communication processing unit 11 to transmit a file transfer request including the device controller ID. When the P2P communication processing unit 11 receives one or a plurality of configuration description files from another device controller Di in response to the transmission of this file transfer request, the information reception unit 12A receives the configuration description file. When the information receiving unit 12A accumulates a plurality of configuration description files in the configuration description information memory 12D, the information selection unit 12E includes a plurality of configuration description files stored in a voted form in the configuration description information memory 12D. Then, a configuration description file CFGi that is the latest and not falsified is selected and can be used by the configuration description information driver 14. At this time, the information selection unit 12E refers to the time stamp added to the configuration description file CFGi and selects the latest configuration description file CFGi. As a result, the configuration description information driver 14 updates the configuration description file stored in the configuration description file storage unit 14a.

  Further, the storage control unit 12 updates the configuration description file when, for example, the configuration of the field buses A, B, and C is changed, or when the device controller Di storing the old configuration description file is detected. There is a need. At this time, the storage control unit 12 detects from the software parameter of the configuration description file storage unit 14a that the information update unit 12B needs to update the configuration description file. Then, the information update unit 12B includes the device controller ID in the file update request for updating its own configuration description file and broadcasts it from the P2P communication processing unit 11.

  In this way, when the configuration of the subnetwork connected to itself changes, the configuration description file of the device is updated according to the changed configuration, and the configuration description file of the other device controller is updated. The configuration description file can be stored.

  Further, when the information receiving unit 12A receives the configuration description file from another device controller Di, the storage control unit 12 stores the configuration description file of the other device controller Di in the distributed shared memory 13. When the storage control unit 12 receives a file transfer request of the device controller Di from another device controller Di, the information receiving unit 12A causes the configuration description corresponding to the device controller ID included in the file transfer request. Read the file and send it.

  For example, as shown in FIG. 9, when the configuration description file of the device controller D4 is replaced with the latest configuration description file (4+) by the operator, the device controller D4 sends its own device to the other device controllers D1 to D3. A file update request including the controller ID is broadcast. Thus, the configuration description file of the distributed shared memories 1-D1, 1-D2, 1-D3 of the other device controllers D1 to D3 can be changed to the latest configuration description file (4+).

  As shown in FIG. 10A, when a device controller that has been P2P connected to the device controllers D1 to D3 is replaced, no device controller ID is given at the time of replacement. Then, as shown in FIG. 10B, when the device controller ID (ID: 4) is given to the device controller D4 and stored in the device controller ID storage unit 19, the information request unit 12C displays the device controller ID. Broadcast a file transfer request containing. As a result, as shown in FIG. 10C, the configuration description file corresponding to the device controller ID (4) is transmitted from the device controllers D1 and D2 among the device controllers D1 to D3, and can be received by the device controller D4. Here, the device controller Di3 cancels the file transfer request from the device controller D4 because the processing load including the storage controller 12 is currently high.

  Next, the operation procedure of the distributed storage system configured as described above and operating as shown in FIGS. 9 and 10 will be described with reference to FIGS. In FIGS. 11 and 12, the relationship among the configuration requirements of the user, another device controller, and the device controller Di is indicated by an arrow, and the operation content (step) of the arrow is described at the left end.

  As shown in FIG. 11, first, when the device controller ID (= 4) is set by the operation of the worker (user) (step S1), the device controller ID in the device controller ID storage unit 19 is set. Is changed (step S2).

  Next, the device controller ID storage unit 19 notifies the configuration description information driver 14 that the device controller ID has been changed, and the configuration description information driver 14 resets the configuration description file in the configuration description file storage unit 14a ( Step S3).

  Next, the configuration description file storage unit 14a notifies the information requesting unit 12C that the configuration description file has been reset and is empty (step S4), and the information requesting unit 12C sends a file transfer request to the P2P communication. The data is transferred to the processing unit 11 (step S5). This file transfer request includes its own device controller ID given in step S2. Next, the P2P communication processing unit 11 converts the file transfer request received from the information requesting unit 12C into a predetermined packet and broadcasts it to the other device controllers D1 to D3 (step S6).

  When the device controllers D1 to D3 receive the file transfer request, the device controllers D1 to D3 return the configuration description file corresponding to the device controller ID (= 4) included in the file transfer request, thereby transferring the plurality of configuration description files to the device controller. The data is received by the P2P communication processing unit 11 of D4 and transferred to the information receiving unit 12A (step S7).

  As a result, the information receiving unit 12A receives a plurality of its own configuration description files (step S7) and stores the plurality of configuration description files in the configuration description information memory 12D (step S8).

  Next, the information selecting unit 12E selects the latest and not corrupted configuration description file from the plurality of configuration description files stored in the configuration description information memory 12D in the form voted by the other device controllers D1 to D3. (Step S9), and the configuration description information driver 14 stores the configuration description file in the configuration description file storage unit 14a (step S10).

  Next, as shown in FIG. 12, the operations of the fieldbus control unit 17B, the fieldbus monitoring unit 17A, the fieldbus driver 18a, and the fieldbus interface unit 18b are updated by the configuration description file updated in step S16 of FIG. Further, the variable table 15 is updated by the variable table updating unit 15A (step S13), and the linkage table 16B is updated by the application processing unit 16 fieldbus C (step S14).

  In this way, by storing the device controller configuration description file in the distributed shared memory 13 of one or more other device controllers in a distributed manner, the device controller can be simply downloaded by downloading the distributed configuration description file. The device controller can be set easily, at low cost and in a short time without employing a manual setting method by an operator or a setting method for connecting to a server. In addition, even if there is a bug in a certain configuration description file, it can be set using another configuration description file.

  When the operations of the field bus control unit 17B, the field bus monitoring unit 17A, the field bus driver 18a, and the field bus interface unit 18b are updated, the field buses A, B, and C are started to operate (step S15), and the variable table is set. 15 and the linkage table 16B are updated, the operation of the application processing unit 16 is started (step S16).

  When the fieldbus interface 18b receives sensor information from the temperature sensors and human sensors of the fieldbus A, B, and C (step S17), the fieldbus driver 18a creates monitor data to monitor the fieldbus. The field bus monitoring unit 17A updates the sensor value of the variable table 15 related to the device that has transmitted the sensor information (step S18). Here, it is assumed that an event based on the sensor value is generated by the MOS function unit 21 of the device, and the sensor value and the event are detected by the fieldbus monitoring unit 17A (OAS function unit 31).

  Next, the application processing unit 16 reads the state of the field buses A, B, and C from the variable table 15 (step S19), and the event received in step S23 from the linkage table 16B is a linkage occurrence event in the linkage table 16B. It is stored and it is determined whether a cooperation response device is set (step S20). Next, the application processing unit 16 updates the device state of the variable table 15 with the received sensor value, and updates the device state of the variable table 15 corresponding to the cooperation response device determined by the cooperation table 16B (step S21). .

  Accordingly, when the field bus control unit 17B detects a change in the variable table 15, the field bus driver 17a transmits control data corresponding to the cooperative operation to the field bus driver 18a according to the updated content (step S22). Data is converted into a command and transmitted from the fieldbus interface unit 18b (step S23).

  The above-described embodiment is an example of the present invention. For this reason, the present invention is not limited to the above-described embodiment, and various modifications can be made depending on the design and the like as long as the technical idea according to the present invention is not deviated from this embodiment. Of course, it is possible to change.

1 is a system diagram showing a configuration of a distributed storage system to which the present invention is applied. It is a block diagram which shows the structure of a device controller in the distributed storage system to which this invention is applied. It is a block diagram which shows the detailed structure of a device controller in the distributed storage system to which this invention is applied. FIG. 2 is a block diagram showing a configuration of a device and fieldbus interface adopting EMIT technology in a distributed storage system to which the present invention is applied. It is a block diagram of a fieldbus table. FIG. 3 is a configuration diagram of a variable table included in a configuration description file stored in a device controller in a distributed storage system to which the present invention is applied. In the distributed storage system to which the present invention is applied, it is a configuration diagram of a linkage table included in a configuration description file stored in a device controller. FIG. 4 is a diagram showing software parameters included in a configuration description file stored in a device controller in a distributed storage system to which the present invention is applied. FIG. 3 is a system diagram for explaining an operation when a device controller configuration description file is updated in a distributed storage system to which the present invention is applied. (A) shows a state where a device controller is exchanged, (b) shows a state where an ID is given to the device controller, and (c) shows a configuration description file from another device controller to the device controller given the ID. It is a figure which shows a mode that it transmits. In the distributed storage system to which the present invention is applied, it is a sequence diagram showing processing from when a device controller ID is given until a configuration description file is updated. In the distributed storage system to which the present invention is applied, a sequence diagram showing processing from when a device controller configuration description file is updated until a device is controlled by the device controller.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Distributed shared memory 11 P2P communication processing part 12 Storage control part 12A Information receiving part 12B Information update part 12C Information request part 12D Configuration description information memory 12E Information selection part 13 Distributed shared memory 14 Configuration description information driver 14a Configuration description file storage Unit 15 variable table 15A variable table update unit 16, 16A application processing unit 16B linkage table 16C application update unit 17 field bus monitoring / control unit 17A field bus monitoring unit 17B field bus control unit 18A, 18B, 18C field bus interface 18a field bus Driver 18b Fieldbus interface unit 19 Device controller ID storage unit 21 MOS function unit 21a Function 21b Event 21c Variable 21d, 31d Object ID
21e service table 22 application processing unit 23 interface module 24 capability table 31 OAS function unit 31
31a Device access server 31b Service information 31c Device access controller 32 Communication module

Claims (5)

At least one of processing for notifying an event that has occurred in each device connected to a subnetwork composed of a plurality of devices and operating the device by notifying each device of an external request With multiple device controllers
Each device controller
Configuration description information storage means for storing configuration description information that is information for communicating with a device of a subnetwork connected to the subnetwork and that indicates a device configuration of the subnetwork;
Referring to the configuration description information, device control means for communicating with the devices of the sub-network;
A communication means connected to another device controller via a communication line and communicating with the other device controller;
Backup storage means for storing configuration description information transmitted from another device controller and received by the communication means, and functioning as a backup memory for the configuration description information of the other device controller;
Storage control for storing own configuration description information stored in the configuration description information storage means in backup storage means of another device controller, and storing configuration description information of other device controllers in its backup storage means Means and
An information storage system, wherein the configuration description information stored in the configuration description information storage means of each device controller is multiplexed and stored in the backup storage means of one or more other device controllers.   When the configuration of the subnetwork connected to the device controller changes, the device controller updates the configuration description information stored in the configuration description information storage unit according to the changed configuration, and configures the other device controller The information storage system according to claim 1, wherein a request for updating the description information is transmitted.   When the device controller is newly connected to a communication line and given its own identifier, the device controller sends a transmission request for requesting transmission of its own configuration description information including the own identifier to another device controller. 2. The information storage system according to claim 1, wherein the configuration description information stored in another backup storage means is acquired.   When the device controller receives a plurality of pieces of configuration description information in response to transmitting a transmission request for requesting transmission of its own configuration description information, the device controller selects the newest configuration description information, and The information storage system according to claim 1, wherein the information storage system is stored in a storage unit. When the device controller receives a transmission request for requesting transmission of configuration description information from another device controller and does not have the processing capability to return the configuration description information at the time when the transmission request is received, the device controller The information storage system according to claim 1, wherein transmission of information is stopped.

Images