KR100953015B1 - Information Acquisition Method for Automatic Identification Device, Information Memory System and Information Memory System - Google Patents

Abstract

In order to automatically generate identification information relating to the role of the device controller, a plurality of devices xy are connected to the fieldbuses FBx and FBy, and communicate with the device xy in the device controller D. The ID generator 10 performs a software stack scan to identify the types of fieldbuses FBx and FBy, and communicates in a manner based on the identified subnetwork type to identify the characteristics of the device. The topology information consisting of the characteristics of (FBx, FBy) and the characteristics of the device (xy) is taken as its identification information.

Identification, fieldbus, software stack scan

Description

AUTOMATIC IDENTIFIER GENERATION DEVICE, INFORMATION STORAGE SYSTEM, AND INFORMATION STORAGE SYSTEM INFORMATION ACQUISITION METHOD}

The present invention provides an information acquisition method of an automatic identification information generation device, an information storage system, and an information storage system in a communication system that multi-memorizes the setting information between device controllers that control and monitor a device according to predetermined setting information. It is about.

Conventionally, it is necessary to connect a device controller to a subnetwork composed of a plurality of devices on a general-purpose bus, and to set the device controller to enable control of the subnetwork and the like. For example, the technique described in Japanese Patent Application Laid-Open No. 2004-102450 may be cited as a technique for backing up a setting file to a server and installing the setting file to operate the device.

For example, in a communication system in which a device controller is connected to a complex subnetwork that monitors and controls a large number of devices, such as 10 to 100 devices, the configuration information of the device controller is managed as a file in order to cope with the large and complicated configuration information. Doing.

When constructing a system having a large number of devices, the worker brought a file storing the setting information and a device controller to the installation site, and installed the file storing the setting information by hand in the device controller. This operation was to assign an ID to each device controller, and then find and install setting information corresponding to the ID from a file.

As a method of assigning an ID to the device controller, a method of inputting a serial number written on a sticker attached to the device controller, or a MAC (Media Access) stored in an Ethernet (registered trademark) chip, for example. As a control address, there is a method of using a hardware identifier added to a component of a device controller as an identifier of the device controller. In addition, when a device controller is connected to a sub-network composed of a plurality of devices on a general-purpose bus, and the device controllers are exchanged, it is necessary to reset the device controller and enable control of the sub-network.

As a method of resetting this device controller, the setting of a device controller setting by manual operation of a worker is mentioned. For example, the worker inserts the portable media (CD, floppy (registered trademark) disk, USB (Universal Serial Bus) memory) storing the setting file into the device controller to be reset. For this reason, the device controller detects the setting file used by the device controller and automatically enables the setting.

As another method of resetting the device controller, the device controller and the server storing the configuration file of the device controller are connected to download the configuration file from the server to the device controller. For this reason, when the device controller is exchanged, the device controller can monitor and control the device by sending a search request for the self setting file from the device controller to the server. As such a technique for backing up a configuration file to a server, the technique described in Japanese Patent Application Laid-Open No. 2004-102450 can be cited.

Moreover, conventionally, the problem of data immunity in a client server system is solved by the advancement of the embedded device network which performs plug and play and peer-to-peer communication. It is proposed to do it. The technology for realizing this embedded device network realizes distributing device data and computer processing programs in a network. In this embedded device network, in order to maintain data immunity, it is necessary to protect the integrity of the computer processing program and data even when a part of the system is broken.

As a technique for maintaining the tolerance of computer processing programs and data, it is generally carried out to duplicate and store computer processing programs and data in a network. By overlapping the data, even if a part of the system is broken, the data can be repaired after the system repair.

As described above, in order to maintain data immunity, an information backup server which provides a service with high reliability while simultaneously backing up information on a network, or a distributed RAID that distributes data among a plurality of terminals. Consider using a Redundant Array of lnexpensive Disks system. Moreover, as a technique of backing up data to a server, the technique of Unexamined-Japanese-Patent No. 2004-102450 etc. is mentioned.

Further, conventionally, a technique of overlapping and storing information copies in the entire system by devices constituting a network, or a technique of equally distributing the information of the entire system in all devices has been proposed.

However, as described above, the method of adding an ID to the device controller adds an ID that is irrelevant to the role or purpose even if the device controller has any role or purpose in the system as a whole. Therefore, careful work was required as an operator in setting up the device controller by adding an ID to the plurality of device controllers.

In addition, since the role and characteristics of the device controller in the system and the physical connection relationship are different, adding an ID to the device controller is cumbersome and is likely to cause configuration errors.

Therefore, the method of making the ID described on the sticker attached to the device controller as the ID of the device controller has nothing to do with other device controllers, and it is difficult to add an ID to each device controller to perform operation setting. It was. In addition, when the ID of the device controller component is used, it cannot be visually confirmed after setting the ID, and the reliability of whether the work is properly completed is low.

In the device controller setting method, there is a possibility that the portable media storing the setting file is lost. In this case, the device controller cannot be set. Moreover, lost portable media may be used by malicious third parties. In addition, there is a possibility that the setting file stored in the portable media may be damaged and may become unreadable. In preparation for this, it is necessary to always prepare a new portable media. In addition, incorrect data may be stored in the portable media due to a setting mistake of an operator who manages the creation and use of the portable media storing the setting file. In addition, it is necessary to include a disk player for reading portable media in the device controller, which results in high cost.

Moreover, when downloading the setting file from the server, the device controller needs to have a means for connecting to the server, resulting in high cost. In addition, the device controller cannot be set when the server is unavailable.

Moreover, in the conventional network technology, in a system including an information backup server, connecting the information backup server and a device itself may be a problem of reliability. For example, when the device controller cannot access the information backup server, the information backup server cannot respond, and the backed-up computer processing program or data cannot be used, resulting in the possibility of data loss.

In addition, in the system using the distributed RAID, in order to use a plurality of terminals, the cost, the maintenance cost, and the repair cost for constructing the system become high. In addition, the capacity of the system is increased, resulting in higher power consumption.

Furthermore, a technique for storing the system-wide information by overlapping or distributing the information in a device needs to have a data storage capability of the same capacity in all the devices constituting the network. Participation is not possible and resistance to data loss becomes low. Therefore, the technique of storing the information of the whole system by overlapping or disperse | distributing to a device is a technique applicable only to the high functional device with a high memory capacity, and the cost in the whole system becomes high.

In addition, the technique of overlapping and storing the information of the whole system in a device needs to be that there is a huge amount of redundant data, and that each device can store the information of the whole system. For this reason, it is not suitable for the device with small memory capacity from the said restriction.

In a network employing this technology, when each device memory capacity is constant, the information of the entire system is simply proportional to the number of devices, and reliability is lost when the number of devices is higher than the memory capacity of each device. .

In addition, an embedded device network in which a device having a low memory capacity or a device having a high memory capacity such as a terminal is mixed is heterogeneous, but most devices have a small memory capacity. In the technique of overlapping the information of the entire system, the amount of data that can store each device is limited to the device having the smallest memory capacity, and only a part of the memory capacity range of the device having the high memory capacity can be used. Thus, there is a problem that the memory capacity available to the entire embedded device network becomes useless.

For this reason, the present invention has been proposed in view of the above circumstances, and provides an information acquisition method of an automatic identification information generating device, an information storage system, and an information storage system capable of supplying identification information related to the role of a device controller. The purpose.

Moreover, an object of this invention is to provide the information storage system which can set a device controller in a simple, low cost, and short time, without employ | adopting the setting method by a worker's manual operation, or the setting method which connects to a server. do.

Furthermore, the present invention provides an information storage system which can effectively use the memory capacity of the entire system even when the memory capacity of the network devices constituting the system is not uniform while maintaining resistance to data loss in the network. It aims to provide.

[Initiation of invention]

In order to solve the above problems, the present invention is a device for automatically generating identification information of a device controller which is connected to a subnetwork in which a plurality of devices are connected to a fieldbus, and communicates with the device, and identifies the characteristics of the subnetwork. At least one of a subnetwork identification means, a device identification means for identifying a feature of a device included in the subnetwork, and a feature of the device identified by the device identification means and a feature of the subnetwork identified by the subnetwork identification means. Identification information generating means for making the topology information self identification information is provided.

In the information storage system according to the present invention, a subnetwork composed of a plurality of devices is connected, and a process of notifying the external device of an event occurring in each of the devices and a request from the outside to each device to operate the device. A plurality of device controllers for performing at least one of the processes, each device controller comprising: configuration description information storage means for storing configuration description information for communicating with a device of a subnetwork connected to itself; Device control means for referring to information and communicating with devices of a subnetwork, communication means for communicating with another device controller via a communication line, and communication with the other device controller, and transmitted from another device controller, Received configuration technology And a backup storage means which functions as a backup memory of the configuration description information of the other device controller, and the self-configuration description information stored in the configuration description information storage means in the backup storage means of the other device controller, And storage control means for storing the configuration description information of the device controller in the magnetic backup storage means.

In order to solve the above problems, the information storage system includes a subnetwork identification means for identifying a feature of a subnetwork, a device identification means for identifying a feature of a device included in the subnetwork, and a subnetwork identification means. Identification information generating means for making topology information, which consists of at least one of the characteristics of the subnetwork and the characteristics of the device identified by the device identification means, as self identification information, and the storage control means includes the identification generated by the identification information generation means. The information is transmitted to the other device controller by the communication means to notify the self identification information, and the self-configuration technology information stored in the backup storage means of the other device controller is acquired and stored in the configuration technology information storage means.

The information acquisition method of the information storage system which concerns on this invention is connected with the subnetwork which consists of a some device, The process which notifies the external device of the event which generate | occur | produced in said each device, and the request from the outside is notified to each said device, An information acquisition method of an information storage system which includes a plurality of device controllers which perform at least one of the processes for operating a device, and which multiplely stores configuration description information for operating the device, wherein each device controller is a sub connected to its own. Topology information comprising at least one of a step of identifying a feature of the network, a step of identifying a feature of a device included in the subnetwork, and a feature of the identified subnetwork and a feature of the identified device as its identification information. The steps to generate, identification information The steps of distributing to the other device controllers through the transmission and transmitting the configuration description information for operating the device by operating the device stored in the other device controller are performed.

1 is a system diagram for explaining the operation of an ID generating unit to which the present invention is applied.

2 is a system diagram for explaining an operation procedure of the ID generating unit to which the present invention is applied.

Fig. 3 is a system diagram for explaining an operation of automatically setting a device controller ID and acquiring a configuration description file CFGi by the ID generation unit to which the present invention is applied.

4 is a system diagram showing a configuration of an information storage system including a device controller in preparation for an ID generating unit to which the present invention is applied.

5 is a block diagram showing the detailed configuration of the device controller in the information storage system prepared for the ID generating unit to which the present invention is applied.

6 is a block diagram showing the configuration of the ID generation unit and the configuration of the device.

Fig. 7 is a block diagram showing the configuration of a device employing an EMIT technology and a field bus interface in an information storage system having an ID generation unit to which the present invention is applied.

8 is a configuration diagram of a field bus table.

9 is a configuration diagram of a variable table included in a configuration description file stored in a device controller in an information storage system having an ID generation unit to which the present invention is applied.

Fig. 10 is a configuration diagram of an association table included in a configuration description file stored in a device controller in an information storage system having an ID generation unit to which the present invention is applied.

11 is a diagram showing software parameters included in the configuration description file stored in the device controller in the information storage system provided with the ID generating unit to which the present invention is applied.

Fig. 12 is a system diagram for explaining an operation of acquiring the configuration description file CFGi from the center server by the device controller having the ID generation unit to which the present invention is applied.

Fig. 13 is a system diagram for explaining an operation of storing and selecting a plurality of configuration description files CFGi in a device controller having an ID generation unit to which the present invention is applied.

14 is a system diagram showing the configuration of an information storage system to which the present invention is applied.

Fig. 15 is a block diagram showing the detailed configuration of a device controller in the information storage system to which the present invention is applied.

Fig. 16 is a system diagram for explaining the operation when the configuration description file of the device controller is updated in the information storage system to which the present invention is applied.

In FIG. 17, (a) shows a state in which a device controller is exchanged, (b) shows a state in which an ID is assigned to the device controller, and (c) shows a configuration description from another device controller to the device controller to which the ID is assigned. This is a diagram illustrating a state in which a file is transmitted.

Fig. 18 is a sequence diagram showing a process until an ID of a device controller is given and an update of the configuration description file is performed in the information storage system to which the present invention is applied.

Fig. 19 is a sequence diagram showing a process until the configuration description file of the device controller is updated and the device is controlled by the device controller in the information storage system to which the present invention is applied.

20 is a system diagram showing the configuration of an information storage system to which the present invention is applied.

21 is a system diagram for explaining the operation when the configuration description file is exchanged in the information storage system to which the present invention is applied.

In FIG. 22, (a) is an explanatory diagram in which the device controller is exchanged, (b) is an explanatory diagram in which an ID is added to the exchanged device controller to broadcast a request, and (c) is a configuration of the exchanged device controller. An explanatory diagram for receiving a response including a description file.

Fig. 23 is a diagram for explaining the number of copies of the configuration description file of each network device in the information storage system to which the present invention is applied.

24 is a system diagram for explaining the type of network device in the information storage system to which the present invention is applied.

Fig. 25 is a block diagram for explaining characteristic operations in the information storage system to which the present invention is applied.

Fig. 26 is a block diagram showing the structure of a device controller in the information storage system to which the present invention is applied.

Fig. 27 is a block diagram showing the detailed configuration of a device controller in the information storage system to which the present invention is applied.

Fig. 28 is a block diagram showing the functional configuration of the information storage system to which the present invention is applied.

Fig. 29 is a block diagram for explaining the contents of signals in the information storage system to which the present invention is applied.

30 is a flowchart showing processing of the distributed shared memory monitoring function in the information storage system to which the present invention is applied.

Fig. 31A is a flowchart showing processing of a shared memory providing function in the information storage system to which the present invention is applied.

Fig. 31B is a flowchart showing processing of a shared memory providing function in the information storage system to which the present invention is applied.

In FIG. 32, (a) is a system diagram showing the use status of the memory of the information storage system, and (b) is a diagram showing the number of copies of the configuration description file of the provider and the requester. .

Fig. 33 is a diagram showing the operation results of the memory status report output function, the distributed shared memory monitoring function, and the shared memory providing function in the information storage system to which the present invention is applied.

In FIG. 34, (a) is a system diagram showing the use state of the memory of the information storage system, and (b) is a diagram showing the number of copies of the configuration description file of the provider and requester.

Fig. 35 is a diagram showing the operation results of the memory status report output function, the distributed shared memory monitoring function, and the shared memory providing function in the information storage system to which the present invention is applied.

In FIG. 36, (a) is a system diagram showing the use state of the memory of the information storage system, and (b) is a diagram showing the number of copies of the configuration description file of the provider and requester.

Fig. 37 is a view showing the operation results of the memory status report output function, the distributed shared memory monitoring function, and the shared memory providing function in the information storage system to which the present invention is applied.

In FIG. 38, (a) is a system diagram showing the use state of the memory of the information storage system, and (b) is a diagram showing the number of copies of the configuration description file of the provider and requester.

Fig. 39 is a diagram showing the operation results of the memory status report output function, the distributed shared memory monitoring function, and the shared memory providing function in the information storage system to which the present invention is applied.

In FIG. 40, (a) is a system diagram showing the use state of the memory of the information storage system, and (b) is a diagram showing the number of copies of the configuration description file of the provider and requester.

Fig. 41 is a diagram showing operation results of the memory status report output function, the distributed shared memory monitoring function, and the shared memory providing function in the information storage system to which the present invention is applied.

In FIG. 42, (a) is a system diagram showing the use state of the memory of the information storage system, and (b) is a diagram showing the number of copies of the configuration description file of the provider and requester.

Fig. 43 is a view for explaining the operation when the network device leaves the information storage system to which the present invention is applied.

Fig. 44 is a flowchart for explaining the operation when the network device leaves the information storage system to which the present invention is applied.

BEST MODE FOR CARRYING OUT THE INVENTION [

EMBODIMENT OF THE INVENTION Hereinafter, embodiment of this invention is described with reference to drawings.

As shown in FIG. 1, the present invention is applied to an ID generating unit 10 in a device controller Di connected to a field bus FB to which a plurality of devices (TU (taminalunits)) are connected.

The device controller Di has an ID generator 10 for identifying a feature of the fieldbus and a feature of the device and generating a device controller ID therein. The ID generator 10 sets the identified information in the device controller ID Si which is a self identifier when identifying the characteristics of the field bus. For example, a device controller ID is generated based on the type and number of field buses and the type and number of devices connected to the field bus.

For example, when an identifier is not assigned to the device controller Di and the device controller Di is newly connected to the field bus, the device controller Di is automatically provided with the device controller ID even if the device controller ID is not assigned manually. Can be set and information (configuration description information) for automatically monitoring and controlling the device group of the fieldbus can be obtained. This eliminates the trouble of adding ID, retrieving configuration technology information, and installation of configuration technology information, which are necessary for the existing manual setting, and thus prevents misconfiguration, shortens setting time, and reduces device cost. Is realized.

When the device controller Di generates the magnetic device controller ID, as shown in FIG. 2, first, the ID generator 10 constructs a software stack (hierarchical structure) inside the device controller Di. Search (step 1, subnetwork identification means). At this time, the ID generating unit 10 preferably searches not only the software stack but also the hardware stack. As a result, the ID generation unit 10 creates a field bus list in which the characteristics of the field bus connected to the device controller Di are arranged, and recognizes that the field buses FBx and FBy are connected. The information of the field buses FBx and FBy is a characteristic of the field buses FBx and FBy, and indicates, for example, the type or number of the field buses FBx and FBy indicating which protocol to control and monitor the device. Information.

Next, the ID generating unit 10 operates the respective FBx interface and the FBy interface in a manner based on the characteristics of the field buses FBx and FBy, and connects the devices connected to the field buses FBx and FBy. (Step 2, device identification means). For this reason, the ID generation unit 10 can recognize that the devices x2, x3, x1, x2, x2 are connected as the device connected to the field bus FBx, and the field bus FBy. As a device connected to, it is possible to recognize that the devices y1, y1, y2, y1 are connected. The information of the device (x, y) is a characteristic of the device (x, y), for example, information indicating the kind (device, actuator, illumination) or the number of devices.

Next, the ID generating unit 10 aggregates the information of the field buses FBx and FBy and the information of the devices x and y obtained in step 2, and the {FBx, FBy, x2, x3, x1, x2, Create topology information called x2, y1, y1, y2, y1} and organize this data as {FBx, FBy, x1, x2, x2, x2, x3, y1, y1, y1, y2} do. Next, the ID generation unit 10 refers to the summarized topology information, obtains the number of fieldbuses and the number of devices, and finds {1: FBx, 1: FBy, 1: x1, 3: x2, 1: x3, 3 Create topology information called: y1, 1: y2}. For this reason, the ID generation unit 10 is connected to the device controller Di one by one of the different field buses FBx and FBy, and one device x1 of the other type is connected to the device controller Di. It can be recognized that three devices x2, one device x3, three devices y1, and one device y2 are connected.

The topology information of {1: FBx, 1: FBy, 1: x1, 3: x2, 1: x3, 3: y1, 1: y2} indicating the number of types of fieldbuses, the number of fieldbuses and devices is given by the device. It becomes a unique device controller ID (Si) in the controller Di. For this reason, the ID generating unit 10 functions as identification information generating means.

In addition, the ID generation unit 10 creates role description information of the device controller Di in order to make the manager of the device controller Di easy to understand the features of the device controller Di. As for this role description information, for example, "the device controller Di is connected to a field bus FBx based on EMIT (Embedded Micro Networking Technology) and a field bus FBy based on LON (Local Operating Network), Three field lights (3: x2) and two air conditioners (2: y1) are connected to these field buses FBx and FBy, and one seal is used as a monitoring object. Sensor (1: x1), one smoke sensor (1: x3) and one interphone (1: y2) are connected ”.

As shown in Fig. 3, the device is controlled by the manufacturer of the device controller Di or the like via the field bus according to the type and number of field buses to which the device controller Di is connected and the type and number of devices. A configuration description file (CFGi) is provided for monitoring. This configuration description file CFGi is a file containing information on environment settings made in order to make the device easier to use in the device controller Di. For example, in the configuration description file CFGi, various items such as individual device settings and device operations are stored. The configuration description file CFGi is created in plural and stored in the file storage device by a combination of the type and number of field buses and the type and number of devices. In addition, the device controller ID acquired from the device controller Di is added to each configuration description file CFGi. Accordingly, the creator of the configuration description file CFGi can determine the ID generation unit 10 of the device controller Di by a combination of the type, number of device buses, and type and number of field buses to which the device controller Di is connected. Knows which device controller ID is to be created, and stores it in the file storage.

Therefore, when the device controller Di acquires the device controller ID Si according to the above process, the device controller Di returns a file transfer request that returns the configuration description file CFGi including the device controller ID Si. Notifies the file storage where the configuration description file (CFGi) is stored.

When the file storage device that stores the configuration description file CFGi is notified of a file transfer request including the device controller ID Si from the device controller Di, the configuration description file CFGi corresponding to the device controller ID Si is notified. ) Is returned to the device controller Di. For this reason, the device controller Di can acquire and install the configuration description file CFGi which describes the process which can be controlled and monitored by the device connected to it.

As described above, according to the ID generation unit 10 to which the present invention is applied, topology information including the characteristics of the subnetwork connected to the device controller Di and the characteristics of the device constituting the subnetwork is obtained. In this way, since the device controller ID can be automatically generated, prevention of missed setting of the device controller ID, reduction in setting time, and reduction in setting cost can be realized. Since the device controller D is a device controller ID related to the role of the device controller D and the like, it is easy to understand as an administrator of the device controller D.

In addition, although said ID generation part 10 acquires the kind and number of a device from the field bus FBx and FBy, it is not limited to this, If it is the information stored in a device, it is the place information of a device. You may create topology information including other information, such as these. In addition, although the ID generation part 10 created the topology information containing the kind of each device, you may create the kind of this device and create the topology information in the role which summarized the some kind of device. This makes it possible to avoid the same device controller ID even when the device controller ID is created from the same field bus configuration.

Next, an information storage system including a plurality of device controllers Di configured as described above will be described. The device controller Di in this information storage system transmits a file transfer request including the device controller ID Si to the other device controller Di by the other device controller Di functioning as a file storage device. will be.

As shown in Fig. 4, the device controller Di is a general-purpose bus, and a plurality of device controllers (A) are provided in a network NW for a plurality of device controllers Di performing peer-to-peer communication. D1 to D4 (hereinafter, collectively referred to simply as "device controller Di") constitute a connected information storage system. The network NW, which is a general-purpose bus, may be, for example, the Internet using IP (lntemet Protocol).

The plurality of device controllers D1 to D4 are each capable of P2P communication, and are capable of passing information between each other. In addition, the detailed structure of each device controller Di is shown in FIG.

Each device controller Di is connected to a subnetwork in which a plurality of devices are connected to a field bus. The device controllers D1 to D4 store the configuration description files CFGi (c1 to c4) obtained by the above process in order to control, monitor, or the like a plurality of devices connected to the fieldbus. In addition, the device controllers D1 to D4 store the configuration description files CFGi of the other device controller Di, respectively, in their distributed shared memories (1-D1, 1-D2, 1-D3, and 1-D4). I remember. This distributed shared memory 1 is provided separately from the storage means for storing its own configuration description file CFGi and functions as a backup storage means for the configuration description file CFGi of another device controller Di.

The device controller Di includes a field bus A in which the device and the device controller Di communicate with each other using a device embedded network technology (EMIT, hereinafter referred to as EMIT technology), and the device and the device controller Di. Field bus B, which communicates with a predetermined multi-transmission method (N-mast method) that realizes transmission and reception of signals as the baseband transmission modulates the pulse width, and a distributed control network method called LON. The field bus C for communication is connected. In addition, the field controller may be connected to the device controller Di not only in the case of using the above-described EMIT technology, the N-mast system, but also in the LON.

In addition, a plurality of devices such as the devices AO to A2, S3 to S7... Are connected to the field bus A, and a seal sensor is included as the device S3. In addition, a plurality of devices such as the devices SO, S1, A1, A3, A4 ... are connected to the field bus B, and include illumination as the device A1. Furthermore, a plurality of devices such as the devices AO to A2, S3 to S5... Are connected to the field bus C, and the device S2 includes a temperature sensor.

The device controller Di includes a P2P communication processor 11 connected to a network NW that performs P2P communication with another device controller Di, a storage controller 12, and the distributed shared memory (1-1). Distributed shared memory 13 corresponding to D1, 1-D2, 1-D3, 1-D4, construction technology information driver 14, variable table 15, application processing unit 16, field The bus monitoring / control unit 17 and the field bus interfaces 18A, 18B, and 18C corresponding to the plurality of field buses A, B, and C connected to the bus are provided.

The field bus interfaces 18A, 18B, and 18C, when the command for acquiring the characteristics of the device connected to each of the field buses A, B, and C from the ID generation unit 10, are input to the field. Send to bus A, B, C. When the response from the device is received, the response is passed to the ID generator 10.

As shown in Fig. 6, the ID generation unit 10 includes a topology information generation unit 10A, a field bus search processing unit 10B, an OS (Operation System) reflection processing unit 10C, and a device access processing unit ( 10D), communication driver 10E, and field bus communication port 10F. The communication driver 10E may be used in combination with the fieldbus communication driver 18a shown in FIG. 5, and the communication driver 10E may be used in combination with the fieldbus interface unit 18b shown in FIG. 5. The ID generating unit 10 shown in FIG. 6 is a specific structural example for performing the operation described with reference to FIG. 2. When generating the magnetic device controller ID by the device controller Di, the OS reflection processing unit 10c of the ID generation unit 10 searches for a software stack (hierarchical configuration) inside the device controller Di. This software stack is composed of a plurality of communication drivers for enabling communication with the field buses A, B, and C because the kind of the fieldbus connected to the device controller Di is assumed in advance. have.

As the software stack of the communication driver, for example, Fig. 6 shows that the software includes N-mas software and EMIT software. The software for N-mas is stored at software address (0x1003), and the software for EMIT is stored at soft address (0x4325). N-mast is a proprietary protocol and is a protocol used in a wiring system for networking all switches with two signal lines of ± 24 V and performing lighting control on a pulse signal. Embedded Micro lntemetworking Technology (EMIT) is a device-integrated network technology, and has a function of simply connecting middleware to a device by connecting it to a network.

Although not shown, of course, the software for communicating with the LON is stored as described above. When such a software stack is retrieved by the OS reflection processing unit 10C, the OS reflection processing unit 10C identifies the correspondence between the N-mast of the driver name and the address (0x1003) of the N-mas software and the driver name EMIT. And the correspondence between the addresses (0x4325) of the EMIT software can be derived.

In the initial stage of manufacturing, the device controller Di stores a plurality of types of communication drivers to correspond to all field buses, but is connected to the field buses A, B, and C and is one of a plurality of types of communication drivers. Alternatively, start a plurality of communication drivers. When the device controller Di is connected to a fieldbus compliant with two N masts and a fieldbus compliant with one EMIT, the communication driver for two N masts and the communication driver for one EMIT are started. It becomes a state. In other words, two N-mas communication drivers are copied and set in different memory addresses, and one EMIT communication driver is copied and set in another memory address. For this reason, the device controller Di forms a hardware stack composed of two N-mask communication drivers and one EMIT communication driver. The hardware stack is retrieved by the OS reflection processing unit 10C. For this reason, the OS reflection processing unit 10C has an N-mas communication driver for the physical address (0x5544), an N-mas communication driver for the physical address (0x5588), and an EMIT for the physical address (0x55BB). You can create hardware configuration information for which a communication driver for your network exists.

The configuration of the communication driver detected by the OS reflection processing unit 10C is the topology information generation as information NM and NM of two N-mast communication drivers and information EM of one N-mast communication driver. It is output to the unit 10A. The information of this communication driver corresponds to the type and number of field buses characteristic of the field bus.

When the device reflection processing unit 10D supplies the type and number of field buses to the topology information generation unit 10A by the OS reflection processing unit 10C, the device access processing unit 10D supplies the maximum number of devices connected to each field bus and each field bus. The range of addresses that the connected device can take is called. In addition, the maximum number of devices and the range of addresses are values standardized by the field bus communication system in advance. The operation of the device access processing unit 10D is activated by the field bus search processing unit 10B.

The field bus search processing unit 10B then controls the device access processing unit 10D to call the device for each address within the range of addresses that the device can take for each field bus. The number of calls of this device is the maximum number of devices that can be connected for each field bus. The device access processing unit 10D calls the device for each address for each field bus. The field bus search processing unit 10B repeatedly operates the device access processing unit 10D until all the addresses are called.

The device access processing unit 10D of the ID generating unit 10 makes a call to a device of a field bus connected to the device controller Di in accordance with the communication method of the field bus. This call is sent to the field bus via the communication driver 10E and the field bus communication port 10F.

The device receives a call signal from the ID generator 10. When the address included in the call signal is its own address, the reflection protocol setting unit 20A of the device activates the reflection processing unit 20B. The reflection processing unit 20B acquires the tag information (device type tag) indicating the device type (type) of the device by searching for the device firmware and confirms that the field bus communication port ( 10F). In addition, the address of the device is stored in this tag information. If there is no device at the address included in the call signal, the device access processing unit 10D detects a timeout error and sends a call signal including the next address to the field bus.

The device access processing unit 10D receives tag information including an address from all devices connected to the field bus. For this reason, the device access processing unit 10D recognizes the number of devices connected to each field bus based on the number of responses of the tag information, and recognizes the individual device types based on the respective tag information. . In addition, the device access processing unit 10D can acquire the address range of the device connected to each field bus.

For example, a device is connected to an N-mast field bus in order of a smoke detector (SD), a detection sensor (PD), and a detection sensor (PD). On the field bus of the mast, a wall switch (WS; Wall Switch), light (L; Light), light (L), wall switch (WS), light (L), wall switch (WS), light (L) The furnace device is connected to the field bus of the EMIT, and a digital camera (DC), a wall switch (WS), an air conditioner (AC) and a dimmer (D; The air conditioner (AC), dimmer (D), and IP telephone (IP) are assumed to be connected. In this case, the tag information (kind information) of the device for each field bus follows the order in which the devices are connected, and is supplied from the device access processing unit 10D to the field bus search processing unit 10B.

The tag information of the called device is supplied from the field bus search processing unit 10B to the device detection unit 10a of the topology information generation unit 10A.

The topology information generation unit 10A includes a device detection unit 10a connected with the field bus search processing unit 10B, a driver detection unit 10b connected with the OS reflection processing unit 10C, an aggregation processing unit 10c, and a classification processing unit. 10d and ID generation processing part 10e.

The tag information (type) of the plurality of devices detected by the device detector 10a and the hardware configuration information indicating the type of field bus detected by the driver detector 10b are collected by the aggregation processor 10c. This aggregation process is a process of listing the types of devices detected by the device detection unit 10a and the types of field buses detected by the OS reflection processing unit 10C. The information collected by the aggregation processing unit 10c is classified by the classification processing unit 10d into the same device type, the same field bus type, and the number of the same device type and the same field bus type are obtained. Become. The information classified by the classification processing unit 10d is topology information in the device controller Di, and becomes the unique device controller ID Si in the device controller Di. As a result, the ID generation unit 10 functions as identification information generating means.

In addition, it is preferable that the ID generation processing unit 10e creates role description information of the device controller Di so that the manager of the device controller Di can understand the characteristics of the device controller Di as described above.

The field bus interfaces 18A, 18B, and 18C shown in FIG. 5 are set to communicate in a manner corresponding to the respective field buses A, B, and C. FIG. For example, the field bus interface 18A employing the EMIT technology and the device connected to the field bus interface 18A are configured as shown in FIG.

The device is provided with a MOS (Micro Object Server) function unit 21 for transmitting control data of various devices, status signals of devices, and the like, between EMIT middlewares. The field bus interface 18A is provided with an OAS (Object Access Server) function unit 31 which performs routing processing, device recognition processing, and the like between EMIT middlewares. The terminal (not shown) of the user who manages the device is provided with an OAL (Object Access Library) function unit (not shown) that outputs control and monitoring requests to the control target device and displays the device status. It is. In addition, in FIG. 7, the case where only the OAS function part 31 is provided in the field bus interface 18A, 18B, 18C is demonstrated, However, OAL function part may be provided.

In the device, the application processing unit 22 and the interface module 23 are connected to the MOS function unit 21. The application processing unit 22 stores, for example, an application code for acquiring a detection value (1 / F value) when functioning as a sensor. The application processing unit 22 maintains the detected value and communicates with the MOS function unit 21.

The interface module 23 performs a process such as a data link layer in the OSI (Open Systems Integrator Connection) reference model. For example, processing in accordance with Ethernet (registered trademark) is performed in the data link layer. The capability of the communication protocol version and the communication speed of the interface module 23 is 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 provided with an object ID 21d by the OAS function unit 31 of the field bus interface 18A to identify that the device is an object in the EMIT.

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

When the device is a sensor, the function 21a becomes a function of outputting a detection value, and the event 21b becomes an event that outputs a detection value, for example, when the detection value reaches a predetermined value, and the variable 21c detects it. The value is it. Such a device generates an event in the event 21b when the detected value reaches a predetermined value, and outputs the detected value of the variable 21c by the function 21a.

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

The OAS function unit 31 is connected to the field bus monitoring / control unit 17 described later, and communicates with the device of the field bus A under the control of the field bus monitoring / control unit 17. The field bus monitoring / control unit 17 supplies a control / monitoring request for such contents when a communication for controlling and monitoring a device with a user and a manager is provided, and returns a response to the control / monitoring request. do.

The communication module 32 communicates with the interface module 23 of the device, and communicates with the communication module 32 of the device in which the other OAS function unit 31 is installed. This communication module 32 performs processing such as a data link layer in the OSI reference model. When the individual devices are composed of various interface modules 23, the communication module 32 communicates with each device or device having other OAS function units 31 under the control of the device access controller 31c. Communication processing in accordance with the device's capabilities such as protocol version and communication speed is performed.

The OAS function unit 31 functions as an EMIT middleware between the processing of the field bus monitoring / control unit 17 and the processing by the communication module 32. The OAS function unit 31 includes a device access server 31a, a 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 through the communication module 32, the field bus monitoring / control unit 17, and the P2P communication processing unit 11 in order to communicate with the client OAL. . The device access server 31a controls the operation of transmitting the control and monitoring request to the device via the device access controller 31c and the communication module 32. For this reason, the device access controller 31c transfers the request from the client to the device, and controls the device.

The device access controller 31c searches the device's service table 21e and the capability table 24 via the communication module 32 to obtain the device's interface definition and service information. For this reason, the device access controller 31c determines which service (function 21a, event 21b, variable 21c) each device has and corresponds to the object ID 21d of each device and the service list. The service information 31b which shows a relationship is created. In addition, the device access controller 31c recognizes what capability (communication protocol version, communication speed) each device has. The service information 31b acquired by the device access controller 31c, when the command for acquiring the feature of the device from the ID generator 10, is generated to the ID generator 10 as information indicating the feature of the device. It may be supplied.

When the event packet of an event is received by the MOS function unit 21 by the communication module 32, the device access controller 31c analyzes the event packet and notifies the device access server 31a. When the device access controller 31c transmits a control / monitoring request from the client to the device, the device access controller 31c refers to the service information 31b for the MOS function unit 21 capable of responding to the control / monitoring request. Recognize it. The device access controller 31c adds the object ID 21d of the transmission destination to the control / monitoring request, and transmits the packet from the communication module 32 to the device in accordance with the capability of the device.

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

The device controller Di having such an OAS function unit 31 is detected by the ID generation unit 10 in accordance with a software stack search process (step 1), and is conformed to the EMIT by the ID generation unit 10. It is detected that one field bus A is connected. After that, when the OAS function unit 31 is given a command for searching for a device connected to the field buses A, B, and C by the ID generation unit 10, the OAS function unit 31 follows the command. By acquiring the service table 21e (tag information) of the device connected to the device, it is possible to generate the device type (feature) as the device controller ID.

The field bus interfaces 18A, 18B, and 18C are configured to include a field bus driver 18a and a field bus interface unit 18b, as shown in FIG.

The field bus driver 18a corresponds to the communication driver 10E shown in FIG. When the field bus driver 18a receives the control data from the field bus monitoring / control unit 17, the field bus driver 18a refers to the configuration description information from the configuration description information driver 14 to determine which device is operated and how. Send a command to the device. In addition, when the field bus interface unit 18b receives a command from the field bus driver 18a, the field bus interface unit 18b converts the command into a signal corresponding to the field buses A, B, and C. To be sent.

In addition, the field bus driver 18a is supplied with a command for searching for a device connected to the field buses A, B, and C in order to generate the device controller ID in the ID generation unit 10, thereby specifying the characteristics of the device. Get the information.

The field bus interface unit 18b corresponds to the field bus communication port 10F shown in FIG. 6. The field bus interface unit 18b receives the monitor data from the field buses A, B, and C when the field bus monitoring / control unit 17 receives monitor data for notifying the device state change and event occurrence from the field buses A, B, and C. It is passed to the field bus driver 18a and sent to the field bus monitoring / control unit 17.

The field bus monitoring / control unit 17 refers to the variable table 15 to control the field buses A, B, and C. FIG. As shown in Fig. 9, the variable table 15 is configured such that a device name, a device state, a variable type, a field bus ID, and an address in a field bus correspond to each field bus A, B, or C. . 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 references the variable table 15 to the field bus A. Control data is sent to the devices B, C).

As shown in FIG. 5, the field bus monitoring / control unit 17 is configured by dividing functions between the field bus monitoring unit 17A and the field bus control unit 17B. The field bus monitoring unit 17A updates the contents of the variable table 15 when receiving the monitor data from the field bus driver 18a. At this time, the field bus 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 the 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 CFGi to determine the field bus and the device to which the control data is sent, and the like. The data is transmitted to the field bus driver 18a.

The application processing unit 16 controls the application processing realized by the device. The application processing unit 16 refers to the variable table and gives a control / monitoring request to the field bus monitoring / control unit 17. For this reason, the device is operated in accordance with the monitoring request and the control request transmitted from the user via the network NW.

In addition, as shown in FIG. 5, the application processing unit 16 includes an application processing unit 16A for transmitting control data to a device, a cooperative table 16B of FIG. 10 to be described later, and its own configuration technology information. Therefore, it may be comprised as the application update part 16C which updates the cooperation table 16B.

The configuration description information driver 14 stores a configuration description file CFGi for controlling and monitoring the field buses A, B, and C connected thereto. As shown in Fig. 5, the configuration description information driver 14 is connected to the storage control section 12 and includes a configuration description file storage section 14a for storing its own configuration description file CFGi. When a plurality of configuration description files CFGi are transmitted from another device controller, the configuration description information driver 14 selects the configuration description files CFGi of the configuration description file storage unit 14a from the information selection unit 12E. Rewrite to the configuration description file (CFGi). In addition, when the new device is connected to the field buses A, B, and C, for example, the configuration description information driver 14 stores the information about the new device by the field bus monitoring unit 17A in the variable table 15. Is added to the device controller ID storage unit 19, and the change information of the field buses A, B, and C is stored in the configuration description file CFGi. This makes it possible to keep the configuration description file CFGi up to date.

The information (configuration description information) included in this configuration description file CFGi includes a field bus table that defines a field bus connected to itself as shown in FIG. 8, a variable table 15 of FIG. 9, and FIG. 10. An association table that defines an association operation performed between the devices as shown in FIG. 11 and a software parameter storing other parameters as shown in FIG. 11 are included.

The field bus table shown in FIG. 8 has field bus IDs (fbO, fb1, fb2, ...) of each of the field buses A, B, and C, and the method adopted by the field buses A, B, and C (EMIT). Field bus information, which defines N mast and ron). This field bus table is read by the field bus monitoring / control unit 17 and is referred to to identify the field buses A, B, and C connected thereto.

The variable table 15 shown in FIG. 9 is comprised as mentioned above, and is referred to by the field bus monitoring / control part 17 and the application processing part 16 in order to specify the state of the device etc. connected to it. This variable table 15 is updated with reference to the configuration description information by the variable table updating unit 15A shown in FIG. 5.

The association table shown in FIG. 10 includes association occurrence event information defining an event of a device that becomes a trigger for starting an association operation, association response device information defining a device that responds when the association occurrence event occurs, The association result information defining the result of the operation of the association response device is associated. This association table is referred to by the application processing unit 16 when an event occurrence is detected by the field bus monitoring / control unit 17 via the field bus interfaces 18A, 18B, and 18C. When the application processing unit 16 determines that an event corresponding to the association table has occurred, the application processing unit 16 operates the association response device to satisfy the association result. In addition, as shown in FIG. 5, this association table may be configured as a part of the function of the application processing unit 16 (partnership table 16B).

In the software parameter shown in FIG. 11, the type of information stored as a parameter, the parameter type information, and the parameter value are stored in association with each other. In this example, the size of the distributed shared memory 13, the capacity of its own configuration description file CFGi, and the number of times of device control are stored as parameters. As the software parameters, parameters used in the field bus interfaces 18A, 18B, and 18C, parameters used in the application processing unit 16, parameters used in the storage control unit 12, and the P2P communication processing unit 11 are used. It also includes parameters to be mentioned.

For example, the size of the distributed shared memory 13 is referred to by the storage control unit 12. The storage control unit 12 determines whether or not the configuration description file CFGi of the other device controller Di can be stored. The storage control unit 12 determines whether or not the self-configuration description file CFGi can be stored in the other device controller Di based on the capacity of the self-configuration description file CFGi.

The storage control unit 12 backs up the self-configuration description file CFGi to the distributed shared memory 13 of the other device controller Di by using the distributed shared memory 1 in the entire network NW. And a process of backing up the configuration description file CFGi of the other device controller Di to the self-distributed shared memory 13. When the storage control section 12 backs up the magnetic configuration description file CFGi to another device controller Di, the storage control section 12 reads the magnetic configuration description file CFGi stored in the configuration description information driver 14, and the P2P communication processing section. (11) to another device controller Di. In addition, the storage control unit 12 receives a backup request from the other device controller Di through the P2P communication processing unit 11, and the configuration description file CFGi of the other device controller Di in the distributed shared memory 13. Save it.

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

When the information requesting unit 12C detects that there is no self-configuration file (CFGi) from the software parameters in the configuration file storage unit 14a, the information requesting unit 12C receives a file transfer request including the device controller ID. Send from). This file transfer request includes the device controller ID generated by the ID generator 10.

In response to the file transfer request being transmitted, when the P2P communication processing unit 11 receives one or a plurality of configuration description files CFGi from another device controller Di, the configuration description file CFGi is received by the information receiving unit 12A. Receive from When the information receiving unit 12A accumulates a plurality of configuration description files CFGi in the configuration description information memory 12D, the information selection unit 12E stores the plurality of configuration description files CFGi stored in the form voted on in the configuration description information memory 12D. Among the configuration description files, a configuration description file (CFGi) that is newest and not modified is selected and made available to the configuration description information driver 14. For this reason, the configuration description information driver 14 keeps the configuration description file CFGi received in the configuration description file storage unit 14a up to date. At this time, the information selecting unit 12E selects the latest configuration description file CFGi with reference to the time stamp added to the configuration description file CFGi. For this reason, the configuration description information driver 14 keeps the configuration description file stored in the configuration description file storage unit 14a up to date. In addition, the storage control part 12 is said, for example, when the structure of the field bus A, B, C changes, or when the device controller Di which stores the old configuration description file CFGi is detected. The configuration description file (CFGi) needs to be updated. 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 CFGi. The information updater 12B then broadcasts from the P2P communication processor 11 including the device controller ID in the file update request for updating its configuration description file CFGi.

In this way, when the configuration of the subnetwork connected to the self is changed, the configuration description file CFGi is updated according to the changed configuration and the configuration description file CFGi of the other device controller is updated. You can remember the description file (CFGi). In addition, the device controller ID newly generated by the ID generation unit 10 is added to the file update request as the configuration of the field buses A, B, and C changes.

Further, when the storage control unit 12 receives the configuration description file CFGi from the other device controller Di with the information receiving unit 12A, the storage control unit 12 distributes the configuration description file CFGi of the other device controller Di. The shared memory 13 is stored. When the storage control unit 12 receives a file transfer request of the device controller Di from another device controller Di, the information controller 12A includes the device controller ID included in the file transfer request. The configuration description file CFGi corresponding thereto is read and transmitted from the P2P communication processing unit 11.

The device controller Di configured as described above is a software stack, and the general purpose bus communication software for realizing the P2P communication processing unit 11 and the field bus interfaces 18A, 18B, and 18C operate to operate the field buses A, B, The field bus communication software for connecting to C), the file management software for acquiring the configuration description file CFGi, and the application software for controlling the devices of the field buses A, B, and C are provided.

By detecting the communication software for the fieldbus, the ID generation unit 10 can detect which characteristics of the fieldbuses A, B, and C are connected to the device controller Di. The field bus interfaces 18A, 18B, and 18C can be controlled to acquire the characteristics of the device connected to B and C). The ID generator 10 generates a device controller ID (Si) based on a combination of the characteristics of the fieldbuses A, B, and C and the device, and stores the device controller ID (Si) in the device controller ID storage unit 19. You can. When the device controller ID Si is set, the device controller Di acquires the self-configuration description file CFGi from another device controller Di by the storage control unit 12, and FIGS. 8 to 11. The configuration description file CFGi including the information shown in the above is stored in the configuration description file storage unit 14a, whereby the control and monitoring of the devices of the field buses A, B, and C can be performed.

In addition, as shown in Fig. 12, the device controller Di has a configuration description file corresponding to the device controller ID Si generated by the combination of the features of all the fieldbuses A, B, and C and the device features. You may be connected to the data server 41 which stored CFGi.

The device controller Di in this system is connected to the data server 41 via a general-purpose line such as the Internet. The device controller Di automatically generates the device controller ID S1 by the ID generation unit 10 and stores the device controller ID S1 in the device controller ID storage unit 19. 41), a file transfer request including the device controller ID S1 is sent.

When the data server 41 receives the file transfer request including the device controller ID S1, the data server 41 reads the configuration description file CFGi corresponding to the device controller ID s1 and returns it to the device controller D1. do. For this reason, the device controller D1 can automatically perform the steps from the setting of the device controller ID to the acquisition of the configuration description file CFGi and the installation of the configuration description file CFGi without incurring an operator's arms.

In addition, the data server 41 may be a center server type that can respond to file transfer requests from the plurality of device controllers D through the Internet network as shown in FIG. It may be a local server type connected to D).

As shown in Fig. 13, a plurality of configuration description files CFG1 (S1), CFG2 (S2), and CFG3 (S3) are stored and shipped at the manufacturing stage of the device controller D in a factory or the like. When the ID is generated, the ID generation unit 10 may select any configuration description file CFGi after automatically setting the device controller ID. For example, when the device controller ID 2 is generated from the type of the field bus FB and the type of the device, a configuration among the plurality of configuration description files CFGi stored in the configuration description information memory 12D in advance. The description file CFG2 is selected and stored in the configuration description file storage unit 14a. For this reason, the selected configuration description file CFG2 is read by the configuration description information driver 14 to the application processing unit 16, the field bus monitoring / control unit 17, and the field bus driver 18a.

As described above, even if the device controller Di is installed in the system shown in Figs. 4 to 13, the ID generation unit 10 provides the characteristics of the subnetwork connected to the device controller Di and the characteristics of the device. The device controller ID can be automatically generated and the configuration description file CFGi can be obtained by using the feature topology information as its own device controller ID, thereby preventing the device controller ID and the configuration description file CFGi from being missed. Therefore, the setting time can be shortened and the setting cost can be reduced. Since the device controller Di is a device controller ID related to the role of the device controller Di and the like, it is easy to understand as an administrator of the device controller D.

Next, 2nd Embodiment which applied this invention is described. In addition, about the same part as said 1st Embodiment, the detailed description is abbreviate | omitted by attaching | subjecting the same code | symbol.

The information storage system according to the second embodiment is characterized by multiplexing the configuration description information stored in each device controller Di into backup storage means of one or a plurality of other device controllers Di.

For example, as shown in Fig. 14, this information storage system is simply referred to as the "device controller Di" in the case of a plurality of device controllers D1 to D4 (hereinafter collectively referred to as a network NW which is a general-purpose bus). .) Is connected. The network NW, which is a general-purpose bus, may be, for example, the Internet using IP (lntemet Protocol). The plurality of device controllers D1 to D4 are each capable of peer-to-peer (P2P) communication, and are capable of passing information between each other.

Each device controller Di has the same configuration as in FIG. 4 described above, and as shown in the detailed configuration of the device controller Di in FIG. 15, the operator's operation panel is replaced with the ID generator 10. The device controller ID is assigned by the operation or the operation of the DIP switch. This device controller ID is stored in the device controller ID storage unit 19. In addition, the device is comprised as FIG.

For example, as shown in FIG. 16, when the configuration description file CFGi of the device controller D4 is replaced by the operator with the latest configuration description file CFGi (4+), the device controller D4 is connected to another device. The controller D1 to D3 broadcasts a file update request including its own device controller ID. As a result, the configuration description file CFGi of the distributed shared memories 1-D1, 1-D2, and 1-D3 of the other device controllers D1 to D3 is changed to the latest configuration description file CFGi (4+). Can be.

As shown in Fig. 17A, when the device controller Di, which has been P2P connected to the device controllers D1 to D3, is exchanged, the device controller ID is not given at the time of the exchange. As shown in Fig. 17B, when the device controller ID (ID: 4) is assigned to the device controller D4 and stored in the device controller ID storage unit 19, the information requesting unit 12C Broadcast a file transfer request containing the device controller ID. For this reason, as shown in Fig. 17C, 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 the device controller ( D4). Here, the device controller D3 cancels the file transfer request from the device controller D4 because the processing load including the current storage control unit 12 is high.

Next, an operation procedure of the information storage system configured as described above and operating as described with reference to FIGS. 16 and 17 will be described with reference to FIGS. 18 and 19. 18 and 19 show the relationship between the user, the configuration requirements of the other device controllers D1 to D3 and the device controller D4 with arrows, and show the operation contents (steps) of the arrow on the left end. It is described.

As shown in FIG. 18, when the device controller ID (= 4) is set (Step ST1) by the operator (user), the device controller first starts the device controller of the device controller ID storage unit 19. As shown in FIG. The ID is changed (step ST2). It goes without saying that the device controller ID may be set automatically by the ID generation unit 10.

Next, the device controller ID storage unit 19 notifies the configuration description information driver 14 that the device controller ID has changed, and the configuration description information driver 14 configures the configuration description file storage unit 14a. The description file CFG4 is reset (step ST3).

Next, the configuration description file CFG4 is reset from the configuration description file storage section 14a to the information requesting section 12C to notify that the configuration description file CFG4 is in an empty state (step ST4). Passes the file transfer request to the P2P communication processing unit 11 (step ST5). This file transfer request includes its own device controller ID (= 4) given in step ST2. 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 ST6).

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

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

Next, from the plurality of configuration description files CFG4 stored in a form voted by the other device controllers D1 to D3 in the configuration description information memory 12D, they are not up to date and deformed. The configuration description file CFG4 is selected in the information selection section 12E (step ST9), passed to the configuration description information driver 14, and the configuration description file storage section 14a by the configuration description information driver 14. The configuration description file CFG4 is stored (steps ST10 and 11).

Next, as shown in FIG. 19, the operation 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 is updated (step ST12), The variable table 15 is updated by the variable table updating unit 15A (step ST13), and the cooperation table 16B is updated by the application processing unit 16 field bus C (step ST14).

According to this operation, the distributed configuration memory CFG4 of the device controller D4 is distributed and stored in the distributed shared memory 13 of one or a plurality of other device controllers D1 to D3. The device controller D4 can be set up only by downloading the description file CFG4, and the device can be easily, lowly costly and shortly without adopting the setting method by the operator's manual work or the setting method for connecting to the server. The controller D4 can be set. In addition, even if there is a bug in any of the configuration description files CFG4, the setting can be made using another configuration description file CFG4.

In addition, when the operations of the field bus controller 17B, the field bus monitor 17A, the field bus driver 18a, and the field bus interface 18b are updated, the field buses A, B, and C are started. When the variable table 15 and the cooperation table 16B are updated (step ST15), the operation of the application processing unit 16 is started (step ST16).

When the field bus interface unit 18b receives sensor information from a temperature sensor, a seal sensor, or the like of the field buses A, B, and C (step ST17), the field bus driver 18a receives The monitor data is created and notified to the field bus monitoring unit 17A, and 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 ST18). . Here, it is assumed that an event based on a sensor value is generated by the MOS function unit 21 of the device, and the sensor value and the event are detected by the field bus 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 ST19), and again the event received in step ST23 from the cooperation table 16B is received. It is stored as an alliance occurrence event of the alliance table 16B, and it is determined whether the alliance response device is set (step ST20). Next, the application processing unit 16 updates the device state of the variable table 15 with the received sensor value, and the device of the variable table 15 corresponding to the cooperation response device determined by the cooperation table 16B. The state is updated (step ST21).

For this reason, when the field bus control unit 17B detects a change in the variable table 15 (step ST22), the field bus driver 18a transmits control data corresponding to the cooperative operation to the field bus driver 18a in accordance with the update contents. The bus driver 18a converts the control data into a command and transmits it from the field bus interface 18b (step ST23).

Next, a third embodiment to which the present invention is applied will be described. In addition, about the same part as said embodiment, the detailed description is abbreviate | omitted by attaching | subjecting the same code | symbol.

The information storage system according to the third embodiment uses the distributed shared memory 1 in the entire system to perform an operation of duplication storing information necessary for a plurality of network devices (for example, the device controller Di). By changing dynamically, it is possible to avoid data loss of information necessary for the network device.

[Example of basic configuration of information storage system]

For example, as shown in FIG. 20, the information storage system includes a plurality of device controllers D1 to D4 in a network NW which is a general-purpose bus. Examples of the network NW which is a general-purpose bus include the Internet using IP (lntemet Protocol). The plurality of device controllers D1 to D4 are each capable of peer-to-peer communication, and mutual information can be transmitted and received.

In the example shown in FIG. 20, the distributed shared memory 1-D1 of the device controller D1 has a memory capacity (3) capable of storing three configuration description files CFGi of another device controller Di. Slot), and the distributed shared memory (1-D2) of the device controller (D2) has a memory capacity (two slots) in which two configuration description files (CFGi) of another device controller (Di) can be stored. The distributed shared memory 1-D3 of the device controller D3 has a memory capacity (3 slots) for storing three configuration description files CFGi of another device controller Di, and the device controller D4. The distributed shared memory 1-D4 has a memory capacity (without the distributed shared memory 1) in which the configuration description file CFGi of the other device controller Di cannot be stored. The configuration description files CFG2, CFG3, CFG4 are stored in the distributed shared memory 1-D1, and the configuration description files CFG1, CFG3 are stored in the distributed shared memory 1-D2. The configuration description files CFG1, CFG2, and cFG4 are stored in the shared memory 1-D3, and the configuration description file CFGi is not stored in the distributed shared memory 1-D4. .

Therefore, this information storage system has a distributed shared memory 1 of different capacity in each device controller Di, so that each device controller Di is from another device controller Di or another network device. In accordance with the request of the present invention, the configuration description file CFGi stored in its distributed shared memory 1 is dynamically changed.

[Basic Operation of Information Storage System]

As shown in Fig. 21, the information storage system updates the distributed shared memory 1 stored in itself as the configuration description file CFGi of the other device controller Di is updated. As shown in Fig. 22, the device controller Di has a function of providing a configuration description file CFGi stored in its distributed shared memory 1 to another device controller Di.

In the information storage system, when the configuration description file CFG4 is updated by the operator and becomes the configuration description file CFG4 +, the device controller D4 stores the configuration description file CFG4 stored in another device controller Di. Broadcast a file update request to the configuration file (CFG4 +) to the network (NW). The device controller D1 and the device controller D3, which store the configuration description file CFG4, are stored in their distributed shared memories 1-D1 and 1-D3 upon receiving a file update request. The configuration description file CFG4 is updated with the configuration description file CFG4 + attached to the file update request. In addition, since the device controller D3 does not store the configuration description file CFG4, the device controller D3 discards the file update request.

In addition, the device controller D4 is hardware-exchanged with the new device controller Di as shown in Fig. 22A by the operator, so as to be the device controller D4 as shown in Fig. 22B. When a device controller ID is added, the device controller D4 broadcasts a file transfer request including the device controller ID to the network NW in order to request its configuration description file CFGi.

As shown in Fig. 22C, the device controller D1, which stores the configuration description file CFG4, receives the file transfer request and stores it in its distributed shared memory 1-D1. The configured configuration description file CFG4 is returned to the device controller D4. For this reason, the device controller D4 can acquire the configuration description file CFG4 for communicating with the terminal device of the field bus. The device controller D3 cancels the file transfer request from the device controller D4 because the processing load including the current memory control unit 12 is high. In addition, since the device controller D3 does not store the configuration description file CFG4, the device controller D3 discards the file transfer request.

In this manner, the information storage system maintains the configuration description file CFGi when the configuration description file CFGi of another device controller Di connected to the network NW is updated or the other device controller Di is exchanged. If not, the configuration description file CFGi owned by the other device controller Di can be provided. Therefore, as described below, even if the memory capacity of each network device is different, the information storage system dynamically changes the storage state of the constituent description file CFGi of the different network devices, and then the respective networks. Maintaining immunity to data loss of the configuration description file (CFGi) of the device.

[Components of Information Memory System]

This information storage system is not only used when the distributed shared memory 1 is used between the device controllers Di connected to the field bus and controlling end devices connected to the field bus as described above, as well as the network NW. The distributed shared memory 1 can also be used among other network devices connected to the network.

As shown in FIG. 23, when there are nine configuration description files CFGi of network devices constituting distributed shared memory 1, c9 through c9, duplication of configuration description files CFGi of each network device. The number is different. This information storage system has a maximum number of copies of three, a network device whose three pieces of configuration file (CFGi) are backed up to another network device, and a minimum number of copies of number of files of its own. Network devices that do not have (CFGi) backed up to other network devices are mixed. In this information storage system, the average value of the configuration description file CFGi is 1.55.

In contrast, the information storage system dynamically changes the use situation of the distributed shared memory 1 between network devices connected to the network NW, and the configuration description file CFGi of all the network devices is transferred to other network devices. Maintain a backed up situation.

As the type of network device in this information storage system, as shown in FIG. 24, a requester Ri for storing its own file using another distributed shared memory 1 and its own distributed sharing. There is a provider Pi that provides the memory 1 to other network devices. Data loss of the configuration description file CFGi is avoided by using the distributed shared memory 1 as the requester Ri and the provider Pi. In the example shown in FIG. 24, the requesters Ra, Rb, Rc, which are network devices not having the distributed shared memory 1, and the provider P1, which provides the distributed shared memory 1 to other network devices, The case where P2, P3, P4, P5) exists is shown. Since the device controller Di has a distributed shared memory 1, it corresponds to the provider Pi, and in the sense of storing its configuration description file CFGi in another device controller Di. This also corresponds to requester Ri.

As shown in Fig. 25, the information storage system outputs a memory status report periodically or randomly by the shared memory provision function of each provider Pi, and the memory status report is requested by the requester Ri. Receive. The requester Ri is empty when there is space in the slot of the distributed shared memory 1 of the provider Pi so that the self-configuration description file CFGi can be backed up to the provider Pi. A slot acquisition request can be sent to the provider Pi to obtain a response from the provider Pi.

[Configuration example of provider Pi]

Next, one structural example of the provider Pi in the information storage system to which the present invention is applied will be described. Moreover, this provider Pi is for controlling and monitoring the terminal device connected to the field bus by connecting a field bus like the device controller Di mentioned above.

As shown in Figs. 26 and 27, the provider Pi is configured almost the same as the device controller Di of Figs. 4 and 5, and the device is configured as shown in Fig. 7. The provider Pi is a type of information stored as a parameter in the software parameters shown in FIG. 11 in order to use the distributed shared memory 1 among other network devices connected to the network NW, The parameter type information and the parameter value are stored in association with each other. In this example, the size of the distributed shared memory 13, the capacity of the self-configuration description file CFGi, and the control count of the terminal device are stored as parameters.

For example, the size of the distributed shared memory 13 is referred to by the storage control unit 12, so that the storage control unit 12 stores the configuration description file CFGi of the requester Ri and another provider Pi. It is determined whether it can be. The storage control unit 12 also determines whether the self-configuration description file CFGi can be stored in the requester Ri or another provider Pi based on the capacity of the self-configuration description file CFGi. . The size of this distributed shared memory 1 may be described not as a byte but as a slot indicating the number of storages of the configuration description file CFGi.

The storage control unit 12 backs up the self-configuration description file CFGi to the distributed shared memory 13 of the other provider Pi by using the distributed shared memory 1 in the entire network NW. And processing for backing up the configuration description file CFGi of the requester Ri and the other provider Pi to its distributed shared memory 13. When the storage control section 12 backs up its configuration description file CFGi to another provider Pi, the storage control section 12 reads its configuration description file CFGi stored in the configuration description information driver 14, The P2P communication processor 11 transmits the data to another provider Pi. In addition, the storage control unit 12 receives the backup request from the requester Ri and the other provider Pi through the P2P communication processing unit 11, and requests the requester Ri and the distributed shared memory 13 to the shared memory 13. Stores a configuration description file (CFGi) of another provider (Pi).

As shown in FIG. 27, the provider Pi is given a device controller ID by an operation of an operator's operation panel, an operation of a dip switch, or the like. This device controller ID is stored in the provider ID storage unit 19.

In addition, when the storage control unit 12 receives the configuration description file CFGi from the requester Ri and the other provider Pi, to the information receiving unit 12A, the requester Ri and the other provider ( The configuration description file CFGi of Pi) is stored in the distributed shared memory 13. In addition, when the storage control unit 12 receives an empty slot acquisition request of the provider Pi from the requester Ri or another provider Pi, the information receiving unit 12A receives the empty information. The configuration description file CFGi corresponding to the device ID included in the slot acquisition request is read and transmitted.

[Function of Information Storage System]

The information storage system including the provider Pi and the requester Ri as described above has a distributed shared memory monitoring function 51 and a memory control function installed in the requester Ri as shown in FIG. And a shared memory providing function 53 provided in the provider Pi.

The distributed shared memory monitoring function 51 is a function provided in each requester Ri, and receives the memory status report S1 broadcasted by the memory status report output function unit 53c of the provider Pi. And an active monitoring unit 51a for monitoring the state of the distributed shared memory 1 and its file backup state.

As shown in Fig. 29, the memory status report s1 includes the device ID of the provider Pi (hereinafter referred to as provider ID) and the distributed shared memory 13 of the provider Pi. The number of reserved slots (the number of storages in the configuration description file CFGi) among all the slots, and slot allocation information indicating to which requester Ri the number of reserved slots are allocated. This memory status report S1 is received by the active monitoring unit 51a.

Upon receiving the memory status report S1, the active monitoring unit 51a creates information indicating the state of the distributed shared memory 1 and information indicating the magnetic file backup state, and sends it to the storage control function 52. Pass it.

The storage control function 52 is information indicating the state of the distributed shared memory 1, and an allocation indicating which requester Ri stores the configuration description file CFGi of each provider Pi. (allocation) Table, table of provider Pi to which it is connected, total number of slots of provider Pi, total number of requesters Ri, total number of providers Pi, configuration technology with the highest number of replicas The shared memory state file 52b including the ID of the requester Ri operating in the file CFGi and the average number of copies of the configuration description file CFGi is stored. In addition, the active monitoring unit 52, as information indicating a self-file backup state, includes the ID of the backup provider Pi, which stores the self-configuration description file CFGi, and the current information storage system as a whole. The number of copies of its own configuration description file CFGi, the desired number of copies required, the number of available memory Pis with space in distributed shared memory 13, and the number of required copies of memory Pi The backup state file 52c including the hit rate divided by the number of n is stored.

The storage control function 52 includes a configuration description information storage unit 52a corresponding to the configuration description file storage unit 14a, a shared memory state file 52b, a backup state file 52c, and a memory state detection function. A unit 52d, an empty slot query function unit 52e, an empty slot acquisition function unit 52f, a copy number warning function unit 52g, and a slot reassignment function unit 52h are provided.

The storage control function 52 includes information indicating the state of the distributed shared memory 1 created by the active monitoring unit 51a of the distributed shared memory monitoring function 51 and information indicating the backup state, and the memory state detecting function unit. When passed to 52d, the shared memory state file 52b and the backup state file 52c are created. This shared memory state file 52b and backup state file 52c can be read from the empty slot query function unit 52e and the empty slot acquisition function unit 52f.

The empty slot query function unit 52e broadcasts an empty slot notification request S2 to the network NW when it wishes to store its configuration description file CFGi in the provider Pi. Receive an empty slot notification response S3 for the empty slot notification request S2. In this empty slot notification request S2, as shown in Fig. 29, its device ID (hereinafter, the device ID of the requester Ri is called a requester ID) and the backup status file 42c. It includes the heat rate stored in.

This empty slot notification request S2 is received by the shared memory providing function 53 installed in the provider Pi. The shared memory providing function 53 is a distributed shared memory 53b corresponding to its own distributed shared memory 13 by the request management function 53a with respect to the received empty slot notification request S2. See, empty slot is searched. The shared memory providing function 53 broadcasts an empty slot notification response S3 including its provider ID to the network NW when there is an empty slot.

When the slot notification response S3 is received by the empty slot query function 52e of the storage control function 52, the empty slot query function 52e is included in the slot notification response S3. The unoccupied provider ID is notified to the empty slot acquisition function unit 52f. The empty slot acquisition function 52f includes a command, a provider ID with an empty slot, a provider list including the provider ID, and a self-configuration description file CFGi, as shown in FIG. An empty slot acquisition request S4 is broadcasted to the network NW.

In addition, the empty slot query function unit 52e notifies the slot reassignment function unit 52h of the slot notification response S3, and the slot reassignment request S5 is performed by the empty slot acquisition function unit 52f. ) To the network (NW). As shown in Fig. 29, this slot reassignment request S5 includes a configuration description file CFGi stored in a slot used by a provider Pi included in a command, a provider list, and the provider list. A requester ID of the requestor, a new (magnetic) requester ID stored in the used slot, and a new (magnetic) configuration description file (CFGi).

The shared memory providing function 53 of the provider Pi receives the empty slot acquisition request S4 by the request management function 53a, and includes the configuration description file included in the empty slot acquisition request S4 ( CFGi) is stored in the distributed shared memory 53b. If the memory state of the distributed shared memory 53b changes in response to receiving the empty slot acquisition request S4 or the slot reassignment request S5, the request management function 53a changes the distributed shared memory ( A memory status report S1 containing the changed slot allocation status is stored in 53b), and is broadcast from the memory status report output function section 53c. For this reason, when the active monitoring unit 51a receives the memory state report S1 indicating that the slot allocation state has changed, the storage control function 52 causes the shared memory state file 52b and the backup state file 52c. Update

In addition, the storage control function 52 is notified of the slot notification response S3 from the empty slot query function unit 52e, so that no self-configuration description file CFGi is duplicated in the information storage system. The copy number warning function unit 52g detects it. If such a configuration description file CFGi is not duplicated, the contents are notified to the active monitoring unit 51a, and the current copy number of the backup status file 52c is updated to "O".

[Process of Information Storage System]

The operation procedures of the distributed shared memory monitoring function 51 and the storage control function 52 in the information storage system having such a function will be described with reference to FIGS. 30 and 31.

The distributed shared memory monitoring function 51 of the requester Ri first performs the processing of steps ST31 to ST38 shown in FIG. 30, so that its own configuration description file CFGi is assigned to another provider Pi. In order to arrange whether or not the degree is duplicated, the shared memory state file 52b and the backup state file 52c are updated, and by the storage control process in the next step ST39, FIGS. 31 (a) and 31 (b). Step ST41 to step ST54 shown in Fig. 2) are performed.

In step ST31 of FIG. 30, the active monitoring unit 51a resets the shared memory state file 52b and the backup state file 52c, and in step ST32, the memory distributed to the network NW. Status report S1 is detected, and it is determined in step ST33 whether the memory status report S1 can be detected. If the memory status report S1 can be detected, the process proceeds to step ST4 to update the allocation table of the shared memory status file 52b. In order to receive the memory status report S1 transmitted reliably every time, this step ST32 and step ST33 are performed by the unit of time twice the predetermined period which transmits the memory status report S1.

In this allocation table, each provider ID and the configuration description file CFGi stored in the provider Pi of the provider ID constitute a certain device (provider Pi or requester Ri). Table indicating whether a file is a description file (CFGi). The active monitoring unit 51a updates the shared memory state file 52b in step ST38, and advances the processing to the storage control process in the storage control function 52 in step ST39.

On the other hand, when the memory status report S1 is not received, the active monitoring unit 51a enters the standby state for a predetermined time in step ST35, and the time for which the memory status report S1 is not received is a predetermined time. If elapsed, the process proceeds to step ST36. This predetermined time is provided at least twice as long as the predetermined interval for transmitting the memory status report S1 in the information storage system.

In step ST36, the active monitoring unit 51a refers to the allocation table included in the shared memory state file 52b, and includes a device table and information including a provider ID and a requester ID constituting the information storage system. The total number of slots, total number of requesters, total number of providers, maximum number of replicas requester (requester ID), and the average number of copies (slot / requester and number of requesters 11) Value), the number of backup providers, the current number of replicas, and the number of memory available providers.

Next, the active monitoring unit 51a updates the backup state file 52c in step ST37 in accordance with the parameter calculated in step ST36, and updates the shared memory state file 52b in step ST38. The process shifts to the storage control process of ST39.

As shown in Fig. 31 (a), the storage control process is first performed by the memory state detection function unit 52d in step ST41, and includes the current self-configuration description file included in the backup state file 52c. It is determined whether or not the number of copies of CFGi) is equal to or greater than the average number of copies included in the shared memory state file 52b. When the number of copies of the self-configuration description file CFGi is equal to or greater than the average number of copies, since the number of copies of the self-configuration description file CFGi is largely unlikely to cause data loss, the process returns to step ST31 in FIG.

On the other hand, when it is determined that the number of copies of the own configuration description file CFGi is not equal to or more than the average number of copies, in step ST42, the memory state detection function unit 52d can use the memory of the backup state file 52c. It is determined whether the number of providers is 0. If it is determined that the number of memory available providers is 0, the processing proceeds to step ST51, and when it is determined that it is not 0, the processing proceeds to step ST43.

In step ST43, the memory state detection function unit 52d subtracts the number of copies of the current self-configuration description file CFGi from the average number of copies and copies the self-configuration description file CFGi in the information storage system. The requested copy number, which is the copy number that needs to be added, is calculated, and the process proceeds to step ST44.

In step ST44, the empty slot query function unit 52e distributes the empty slot notification request S2 to the network NW. At this time, the empty slot query function unit 52e includes, in the empty slot notification request S2, the hit rate obtained by dividing the self request Ri and the required copy number by the number of memory available providers. The empty slot notification request S2 is received by all providers Pi of the information storage system, and the request management function 53a of the shared memory providing function 53 is a self-distributing shared memory. Referring to (53b), when there is an empty slot, an empty slot notification response S3 including its provider ID is broadcasted to the network NW.

In the next step ST45, it is determined whether the empty slot notification response S3 has been received by the empty slot question function unit 52e of the requester Ri, and the empty slot question function unit 52e determines whether the slot is the slot. If notification response S3 could not be received, it is determined in step ST46 of FIG. 31B that there are no empty slots in the information storage system. In addition, when the empty slot query function unit 52e receives the slot notification response S3 and the number of empty slots in the information storage system is larger than zero and smaller than the required copy number, it is shown in FIG. 31 (b). The process proceeds to step ST47, and when the number of empty slots is larger than the required copy number, the process proceeds to step ST48 in Fig. 31B.

When the empty slot query function unit 52e determines that the number of empty slots is larger than zero and smaller than the required copy number, the contents are notified to the empty slot acquisition function unit 52f, and the empty slot query function unit 52e is empty in step ST49. The slot acquiring function unit 52f distributes the empty slot acquiring request S4 to the network NW, and returns the process to step ST41. This empty slot acquisition request (S4) includes a list of provider IDs that have broadcast the number of empty slots by the slot notification response (S3), their provider IDs, and a configuration description file (CFGi). Include. This list of provider IDs contains an empty list of slots.

Therefore, when the empty slot acquisition request S4 is received by the request management function 53a of the shared memory provision function 53 of the provider Pi, the configuration technology included in the empty slot acquisition request S4 is received. The file CFGi is stored in the distributed shared memory 53b. In addition, the shared memory providing function 53 of the provider Pi stores a change in the memory state generated by storing the new configuration description file CFGi in the distributed shared memory 53b. Reflected in the memory status report S1 transmitted by 53c.

In step ST50 after determining that the number of empty slots is larger than the required number of copies in step ST48, the empty slot acquiring function unit 52f includes the number of self-required copies, a list of empty slots, a self-provider ID, The empty slot acquisition request S4 including the configuration description file CFGi is broadcasted to the network NW. As a result, the number of configuration description files CFGi satisfying the required number of copies is copied and stored in the information storage system.

Furthermore, in step ST51 after determining that the number of empty slots is 0 in step ST46, the empty slot query function unit 52e sets the number of copies of the maximum copy count holding requester of the shared memory state file 52b to 1. It is determined whether it is larger than. When the empty slot query function unit 52e determines that the maximum number of copy holding requests is greater than 1, in step ST52, it notifies the slot reassignment function unit 52h of the content. The slot reassignment request S5 is broadcast to the network NW by the empty slot acquisition function unit 52f. The slot reassignment request (S5) includes a list specifying the slots of the provider Pi in which the configuration description file CFGi of the maximum copy number holding requester is duplicated, the ID of the maximum copy number holding requester, A new requester ID, which is a magnetic device ID that newly uses a slot in place of the maximum copy number holding requester, and a self-configuration description file (CFGi).

On the other hand, if the copy number of the maximum copy number holding requester is not greater than 1, in step ST53, the empty slot query function unit 52e determines whether the current copy number of the self-configuration description file CFGi is 0 or not. If it is determined that it is not, the process returns to step ST41, and if the number of copies of the own configuration description file CFGi is zero, the process proceeds to step ST54.

In step ST54, the empty slot query function unit 52e notifies the copy number warning function unit 52g that the copy number of the self-configuration description file CFGi is zero, and the copy number warning function unit 52g The active monitoring unit 51a is notified of a warning message including the contents thereof.

[Operational State Optimization of Information Storage System]

Thus, the operation in the information storage system which dynamically optimizes the memory state of the configuration description file CFGi in the distributed shared memory monitoring function 51, the storage control function 52 and the shared memory providing function 53. This will be described with reference to FIGS. 32 to 42.

For example, as shown in Fig. 32 (a), the information storage system is composed of three requesters Ri and five providers Pi, as shown in Fig. 32 (b). In a state where no configuration description file CFGi is stored in the other distributed shared memory 53b, as shown in FIG. 33, the distributed shared memory monitoring function 51, the storage control function 52, and the shared memory are shared. The memory providing function 53 is operated. That is, the memory status report output function unit 53c of the provider Pi and the requester Ri holds its device IDs Ra, Rb, Rc, P1, P2, P3, P4, and P5. Number of slots (Ra: 0, Rb: 0, Rc: 0, P1: 4, P2: 2, P3: 5, P4: 3, P5: 8), and the number of empty slots (Ra: 0, Rb: 0, The memory status report S1 for notifying Rc: 0, P1: 4, P2: 2, P3: 5, P4: 3, and P5: 8 is delivered. Further, each provider Pi and requester Ri receives the memory status report S1 from another provider Pi and requester Ri in the active monitoring unit 51a, and the total number of slots. [a] is 22 (4 + 2 + 5 + 3 + 8), the total number of requesters is [b] is 8, the total number of providers is [c] is 5, and the maximum number of replicas has no requester [d]. ), Shared memory state file 52b indicating that the average number of copies [e] (min ([a] / [b], [c] -1) is 2 (min (22/8, 5-1) = 2) ), And create a backup state file 52c containing the current number of copies [f], the number of required copies [g] ([e]-[f]), and the number of memory available providers [h]. have.

In this state, the storage control function 52 of the requester Ri calculates the hit rate [g] / [h] and broadcasts an empty slot notification request S2 in response to the slot notification lease. Receive the span S3. By this empty slot notification request S2, the requester Ri receives the slot notification response S3 from the different provider Pi, respectively. Here, the provider P5 cannot receive the slot notification response S3 from any provider Pi even if it broadcasts an empty slot notification request S2, but is again empty at the next opportunity. The slot notification request S2 is broadcast.

The requester Ri, which has received the slot notification response S3, broadcasts a slot acquisition request S4 which is empty in the provider ID included in the slot notification response S3. For this reason, as shown in Fig. 34 (a), the configuration description files CFGi of other providers Pi and requester Ri are stored in the providers P1 to P5, and Fig. 34 (b). As shown in Fig. 1, the number of copies in the information storage system is obtained.

In this state, when the memory status report S1 is delivered from each provider Pi and the requester Ri, as shown in FIG. 35, each provider Pi and the requester Ri are shown. The number of empty slots in the provider Pi is changed by the active monitoring unit 51a, and the slot allocation state, the maximum number of copy holding requests, the average number of copies, the number of copies of the current self, and the number of required copies are updated. At this point in time, the requesters Ri and providers Pi (Rc, P4, P5) whose current copy number is smaller than the average copy number are calculated for the number of memory available providers and the hit rate, respectively. The slot notification request S2 is broadcasted, the empty slot acquisition request S4 is broadcasted again, and the number of copies thereof is increased. Here, the requester Rc cannot receive the slot notification response S3 from any provider Pi even if it broadcasts an empty slot notification request S2, but is again empty at the next opportunity. The slot notification request S2 is broadcast.

For this reason, as shown in FIG. 36 (a), the configuration description files CFGi of other requesters Ri and provider Pi are stored in the providers P1, P3, and P5, and FIG. 36. As shown in (b), the number of copies of the configuration description file CFGi of the provider P4 can be increased by only one, and the number of copies of the configuration description file CFGi of the provider P5 is two. You can only increase it.

In this state, as shown in FIG. 37, in the requester Rc, the current copy number is smaller than the requested copy number, the required copy number, the number of memory available providers, and the hit rate are calculated. The notification request S2 is broadcasted, the slot notification response S3 is returned, and the empty slot acquisition request S4 is broadcasted. For this reason, as shown in FIG. 38 (a), the configuration description file CFGi of the requester Rc is stored in the provider P5, and as shown in FIG. 38 (b), the requester The number of copies of the configuration description file CFGi of (Rc) can be increased by only one.

At this point in time, as shown in FIG. 39, the number of copies of all of the provider Pi and the configuration description file CFGi of the requester Ri is equal to the average number of copies, and the entire information storage system. The distributed shared memory 53b in the system is in an optimized state. Therefore, the requested copy number is "0" in all the providers Pi and requester Ri, and the slot notification request S2 and the empty slot notification request S2 are empty from any provider Pi or requester Ri. The slot acquisition request S4 is not broadcasted.

In this way, the distributed shared memory monitoring function 51, the storage control function 52, and the shared memory providing function 53 are prepared for each provider Pi and requester Ri constituting the information storage system. By performing the processing shown in Figs. 30, 31 (a) and 31 (b), the backups are made with the same number of copies of the configuration description file CFGi of each provider Pi and requester Ri. The possibility of data loss of the configuration description file CFGi of all providers Pi and requester Ri can be reduced.

For example, as shown in Fig. 40 (a), although the requester Rc is connected to the network NW, there is no empty slot in the provider Pi, as shown in Fig. 40 (b). Similarly, when the configuration description file CFGi of the requester Rc is not stored in any of the providers Pi, slots are reassigned in the information storage system. In this case, a warning message is issued from the copy number warning function unit 52g to the active monitoring unit 51a.

In this case, as shown in Fig. 41, since the average copy number is "1", the request copy number becomes "1". The requester Rc broadcasts an empty slot notification request S2, and the slot notification lease. Even if the span S3 can be received, the number of memory available providers becomes "0". Therefore, the requester Rc broadcasts the slot reassignment request S5 by the empty slot acquisition function 52f. At this time, the requester Rc, in the slot reassignment request S5, the provider ID P1, the device ID Ra of the configuration description file CFGi stored in the provider P1, and the self. Include the device ID (Rc) and configuration description file (CFGi).

This slot reassignment request S5 is received from the provider P1, and the provider P1 is the all requester IDs included in the slot reassignment request S5 as shown in Fig. 42 (a). The configuration description file CFGi is deleted, and instead the configuration description file CFGi of the requester Rc is stored. For this reason, as shown in Fig. 42B, the number of copies of the requester Rc configuration description file CFGi can be made equal to the average number of copies of the information storage system.

As described above, according to the information storage system to which the present invention is applied, even if the memory capacity of the provider Pi connected to the network NW is different, the provider Pi and the requester Ri are the average number of copies. You can adjust the number of copies of the configuration description file (CFGi) to meet the requirements. In addition, even if the memory capacity is small, it is not necessary to have a uniform backup capacity in all providers Pi and requester Ri, so that the distributed shared memory 53b of the entire information storage system can be effectively used. You can maintain resistance to

In addition, this information storage system dynamically changes the number of copies so that all providers Pi and requester Ri meet the average number of copies. As another form of dynamically changing the number of copies, the network (NW) It is desirable not to reduce the number of copies of the important configuration description file CFGi. Therefore, all providers Pi and requester Ri set the importance of their configuration description file CFGi and the configuration description file CFGi of other network devices in advance, and the configuration description files of the plurality of network devices. Of course, the CFGi may be backed up so that the number of copies of the configuration description file CFGi of the network device of high importance is higher than the number of copies of the configuration description file CFGi of low importance. Therefore, the configuration description file CFGi, which is important in the network NW, is preferentially maintained as a plurality of network devices, thereby making it possible to increase the tolerance against data loss of the configuration description file CFGi of high importance.

[Operation at the Time of Leaving Provider Pi and Requester Ri in Information Storage System]

Next, the operation of optimizing the distributed shared memory 53b when the provider Pi and the requester Ri are separated from the network NW in the above information storage system will be described.

As shown in Fig. 43 (a), when the requester R connected to the network NW is removed by an operator and is separated from the information storage system, Fig. 43 (a) and Fig. As shown in 28, an exit trigger occurs in the shared memory providing function 53 of the provider P4. This exit trigger includes a device ID (an exit ID) for leaving.

When the provider P4 detects an exit trigger, the provider P4 broadcasts an exit request to the network NW including the device ID and the exit command of the requester R to leave. Here, the provider P1 and the provider P4 store the configuration description file CFGi of the requester R. As shown in FIG. Therefore, the provider P1 and the provider P4 delete the configuration description file CFGi of the requester R as shown in Fig. 43B.

In addition, the leaving provider Pi and the requester Ri broadcast a leaving request including their own device IDs to the network NW when the worker removes them. (Pi) may be notified and the configuration description file CFGi may be deleted by the provider Pi.

In such an information storage system, as shown in FIG. 44, the provider Pi first performs a check operation of the escape trigger by the shared memory providing function 53 in step ST61. The check operation of this escape trigger is performed for each preset period.

In step ST62, it is determined whether the escape trigger is detected. When the exit trigger is detected, the shared memory providing function 53 broadcasts the exit request including the leaving device ID to the network NW. On the other hand, when the departure trigger is not detected, the operation of checking the signal received by the network NW is performed in step ST64, and it is determined whether or not the departure request is received in step ST65. If no escape request is received, the process returns to step ST61, and if an escape request is received, the process proceeds to step ST66.

In step ST66, the provider Pi determines whether or not the configuration description file CFGi of the device ID included in the departure request is stored in its distributed shared memory 53b. If the IDs of the leaving provider Pi and the requester Ri are not stored, the process returns to Step ST61, and if the IDs of the leaving provider Pi and the requester Ri are stored. In step ST67, the configuration description file CFGi of the device ID is deleted, and the processing returns to step ST61.

In this way, when the provider Pi and the requester Ri depart from the network NW, a departure request including the device ID is broadcasted to the network NW, and the configuration description file of the device ID ( Since CFGi is deleted from the provider Pi, another configuration description file CFGi can be stored in the slot where the deleted configuration description file CFGi is stored. Therefore, by increasing the number of copies of the configuration description file CFGi, the immunity to data loss can be further improved. In addition, the distributed shared memory 53b in the information storage system can be used more effectively.

Moreover, said embodiment is an example of this invention. For this reason, this invention is not limited to the said embodiment, Of course other than this embodiment, if it is a range which does not deviate from the technical idea concerning this invention, of course, it can change in various ways according to a design.

In other words, the above-described information storage system has been described with reference to a system consisting of a provider Pi and a requester Ri, and a system consisting only of a device controller Di. The distributed shared memory 1 may be distributedly stored.

According to the information acquisition method of the automatic identification information generating device, the information storage system, and the information storage system according to the present invention, the topology information comprising the characteristics of the subnetwork connected to the device controller and the characteristics of the devices constituting the subnetwork can be obtained. The identification information can be automatically generated as the identification information of the identification information. Therefore, it is possible to prevent delay in setting the identification information, to shorten the setting time, and to reduce the setting cost. In addition, identification information related to the role of the device controller and the like can be provided, and identification information that is easy to understand for an administrator or the like can be created.

According to the information storage system according to the present invention, since the configuration description information stored in the configuration description information storage means of each device controller is stored in the backup storage means of one or a plurality of other device controllers, the multiple description is stored. The device controller can be set simply by downloading the configuration technology information stored in the memory, and the device controller can be set up in a simple, low cost, and short time without adopting a setting method by an operator's manual work or a setting method for connecting to a server. Settings can be made.

According to the information storage system according to the present invention, since the operation setting information stored in the backup storage means is dynamically changed in accordance with a request from another network device, the holding state of the operation setting information of a plurality of network devices can be optimized. In addition, the memory capacity of the entire system can be effectively used even when the memory capacity of the network devices constituting the system is not uniform while maintaining resistance to data loss in the network.

Claims (24)

In a device for automatically generating identification information of a device controller connected to a subnetwork in which a plurality of devices are connected to a field bus, Subnetwork identification means for identifying a characteristic of the subnetwork; Device identification means for identifying a feature of a device included in said subnetwork; And identification information generating means which uses, as its own identification information, topology information consisting of at least one of the characteristics of the subnetwork identified by said subnetwork identification means and the device characteristics identified by said device identification means, The sub-network identification means searches a software stack or a hardware stack stored in the device controller, and identifies the type and number of sub-networks as a feature of the sub-network connected to the device controller. When the type and number of sub-networks are identified by the sub-network identification means, the device identification means accesses a device included in the sub-network according to the communication method of the sub-network, and the device identification means of the device included in the sub-network. Identify the type and number of devices as a feature, And the identification information generating means uses the topology information including the type and number of the identified sub-networks and the type and number of devices as its identification information. delete delete The method of claim 1, The device controller, And a transmitting means connected to the data server storing the configuration description information for the device controller to communicate with the device, and transmitting the identification information generated by the identification information generating means. And the data server returns configuration description information corresponding to the received identification information when the identification information generated by the identification information generating means and received from the transmitting means is received. The method of claim 1, Each device controller Storage means for storing configuration description information for communicating with a device by another device controller; And information transmitting means for returning the configuration description information corresponding to the identification information when receiving the identification information transmitted from the other device controller. The method of claim 4, wherein The identification information generating means transmits its own identification information to the data server, and when the identification information of the user receives the same response as the other identification information, the identification information generating means is different from the transmitted identification information of the owned person and created from the new topology information. Automatic identification information generation device, characterized in that for generating identification information of its own. A device controller which is connected to a subnetwork composed of a plurality of devices, performs at least one of a process of notifying the outside of an event occurring in each of the devices, and a process of notifying each device of a request from the outside to operate the device. With a plurality of, Each device controller Configuration description information storage means for storing configuration description information for communicating with devices of a subnetwork connected to the user; Device control means for referring to the configuration description information and communicating with a device of the subnetwork; Communication means connected to another device controller via a communication line to communicate with the other device controller; Backup storage means for storing the configuration description information transmitted from another device controller and received by the communication means, and functioning as a backup memory of the configuration description information of the other device controller; Storage control means for storing the configuration description information of the device stored in the configuration description information storage means in the backup storage means of the other device controller and storing the configuration description information of the other device controller in the backup storage means of the other device; Subnetwork identification means for identifying a characteristic of the subnetwork; Device identification means for identifying a feature of a device included in said subnetwork; And identification information generating means for making, as its identification information, topology information consisting of at least one of a characteristic of a subnetwork identified by said subnetwork identification means and a characteristic of a device identified by said device identification means, The storage control means transmits the identification information generated by the identification information generating means to the other device controller by the communication means to notify the identification information of the self, and the magnetic construction technology stored in the backup storage means of the other device controller. Information is acquired and stored in the configuration description information storage means. The subnetwork identification means searches a software stack or a hardware stack stored in the device controller to identify the type and number of subnetworks as a feature of the subnetwork connected to the device controller, When the type and number of sub-networks are identified by the sub-network identification means, the device identification means accesses a device included in the sub-network according to the communication method of the sub-network, and the device identification means of the device included in the sub-network. As a feature, identify the type and number of devices, And the identification information generating means uses the topology information including the type and number of the identified subnetwork and the type and number of devices as its identification information. The method of claim 7, wherein The device controller, When newly connected to the communication line, the subnetwork identification means identifies the characteristics of the subnetwork, Perform communication in a manner based on the characteristics of the sub-network identified by said device identification means by said sub-network identification means, Identify features of a device included in the subnetwork, Topological information comprising the characteristics of the subnetwork identified by the identification information generating means as the subnetwork identification means and the characteristics of the device identified by the device identification means, as the identification information thereof, is another device controller by the storage control means. An information storage system, comprising: acquiring constituent description information transmitted from the self and storing the constituent description information in the configuration description information storage means; The method of claim 7, wherein The configuration description information stored in the configuration description information storage means of each device controller, An information storage system, characterized in that multiple storage in the backup storage means of one or a plurality of different device controller. 10. The method of claim 9, The device controller, When the configuration of the subnetwork connected to the user is changed, according to the changed configuration, the configuration description information stored in the configuration description information storage means is updated, and a request for updating the configuration description information is transmitted to another device controller. Information memory system. 10. The method of claim 9, The device controller, When a new connection is made to a communication line, and a given identifier is given, a send request requesting the transmission of its own configuration description information including the identifier is sent to another device controller for further backup. An information storage system, characterized by acquiring configuration technology information stored in a storage means. 10. The method of claim 9, The device controller, When a plurality of constituent description information is received in response to the transmission of a request for transmission of the constituent description information, the newest description information is selected and stored in the configuration description information storage means. Information memory system. 10. The method of claim 9, The device controller, When receiving a transmission request requesting transmission of the configuration description information from another device controller, if there is no processing capability to return the configuration description information at the time when the transmission request is received, transmission of the configuration description information is stopped. Information memory system, characterized in that. The method of claim 7, wherein Some network devices of the plurality of network devices including the device controller have the backup storage means for storing configuration description information transmitted from other network devices and functioning as a backup memory of the configuration description information of the other network device, The storage control means of the network device having the backup storage means dynamically changes the configuration description information stored in the backup storage means in response to a request from another network device received through the communication means. Information memory system, characterized in that. The method of claim 14, The storage control means, And the configuration description information of each network device is stored in the backup storage means so as to average the number of duplications of the configuration description information of the plurality of network devices. The method of claim 14, The storage control means, The importance of the configuration technology information of the own and the configuration technology information of other network devices connected through the communication line is set in advance, and the importance of the configuration technology information of the plurality of network devices is less than the number of copies of the configuration technology information of low importance. An information storage system characterized by storing the configuration technology information in the backup storage means so as to increase the number of copies of the configuration technology information of a high network device. The method according to any one of claims 14 to 16, The network device having the backup storage means, Memory status report output means for notifying another network device of the status of its backup storage means, The storage control means, An information storage system, characterized by storing the configuration description information thereof in a network device having the backup storage means, by referring to the state of the backup storage means notified from the memory status report output means. The method according to any one of claims 14 to 16, The storage control means, It is inquired of a network device having the above backup storage means whether or not its constituent description information can be stored; Sending the configuration technology information to another network device that has responded to the usage status information indicating that the configuration technology information can be stored, and storing the configuration technology information to the other network device, The network device having the backup storage means, An information storage system characterized by returning the memory state of the backup storage means thereof when the other network device inquires whether or not the configuration description information of the other network device can be stored. The method according to any one of claims 14 to 16, The storage control means, When the memory state of the backup storage means is acquired from the network device having the backup storage means, and its own configuration description information is determined to be incapable of storage, the network device having the largest number of copies of the configuration description information is determined. And store its own configuration description information instead of the configuration description information of said network device. The method according to any one of claims 14 to 16, The network device having the backup storage means, When the network device newly participating in the communication line is connected, and it is inquired whether or not the configuration technology information can be stored from the newly joined network device, the memory information of the backup storage means is returned. system. The method according to any one of claims 14 to 16, The network device having the backup storage means, And upon receiving a request for destroying the configuration technology information to escape from the communication line, deleting the configuration technology information of the network device from the backup from the backup storage means. A process in which a subnetwork composed of a plurality of devices is connected to notify the outside of an event occurring in each of the devices, In the information acquisition method of the information storage system which notifies each device of the request from the outside, and has a plurality of device controllers which perform at least one of the processes which operate the said device, and multi-stored the configuration description information for operating a device. In Each device controller Identifying characteristics of the subnetwork connected to the self; Identifying features of a device included in the subnetwork; Generating topology information consisting of at least one of the characteristics of the identified subnetwork and the characteristics of the identified device as its identification information; Distributing the identification information to another device controller via a communication line; Performing the steps of acquiring and storing configuration description information for operating the device by the magnetic device stored in the other device controller; When identifying the subnetwork, the software stack or hardware stack stored in the device controller is searched to identify the type and number of subnetwork as a feature of the subnetwork connected to the device controller, When the type and number of the sub-networks are identified, the type and number of devices are identified as characteristics of the devices included in the sub-networks by accessing the devices included in the sub-networks according to the communication scheme of the sub-networks, And the topology information including the type and number of the identified subnetworks and the type and number of devices as identification information of the sub-network. The method of claim 22, And identifying the characteristics of the subnetwork starts when a new connection is made to the communication line. The method of claim 5, The identification information generating means transmits its identification information to another device controller, and when the identification information thereof receives the same response as that of the other identification information, the identification information generating means is different from the transmitted identification information of the owning party, Automatic identification information generation device, characterized in that for generating the identification information of the self.

Images