WO2007077887A1

WO2007077887A1 - Automatic identifier generation device, information storage system, and information storage system information acquisition method

Info

Publication number: WO2007077887A1
Application number: PCT/JP2006/326108
Authority: WO
Inventors: Laurent Safa
Original assignee: Matsushita Electric Works, Ltd.
Priority date: 2005-12-27
Filing date: 2006-12-27
Publication date: 2007-07-12
Also published as: KR100953015B1; CN101147139A; CN101147139B; KR20070106552A

Abstract

In order to automatically generate an identifier associated with a device controller role or the like, a plurality of devices (x, y) are connected to field busses (FBx, FBy). An ID generation unit (10) in a device controller (D) communicating with the devices (x, y) performs software stack scan for identifying the type of the field buses (FBx, FBy) and performs communication based on the identified sub network type so as to identify the device feature. Then, topology information formed by the feature of field buses (FBx, FBy) and the feature of devices (x, y) are made a local identifier.

Description

Specification

IDENTIFICATION INFORMATION AUTOMATIC GENERATION DEVICE, INFORMATION STORAGE SYSTEM, AND INFORMATION STORAGE SYSTEM INFORMATION OBTAINING METHOD

Technical field

The present invention relates to an automatic identification information generating apparatus, information storage system, and information storage in a communication system that stores multiple pieces of the setting information between device controllers that control and monitor devices according to predetermined setting information. The present invention relates to a system information acquisition method. Background art

Conventionally, it is necessary to connect a device controller to a sub-network that also has a plurality of device capabilities on a general-purpose bus, and to set the device controller to enable control of the sub-network. For example, a technique described in Japanese Patent Application Laid-Open No. 2004-102450 or the like can be cited as a technique for operating a device by backing up a setting file on a server and installing the setting file.

[0003] For example, in a communication system in which a device controller is connected to a complicated subnet network that monitors and controls a large number of devices of 10 to 100, in order to cope with the complexity and enormous amount of setting information, Device controller setting information is managed as a file.

[0004] When constructing a system including a large number of devices, an operator brings the file storing the setting information and the device controller to the installation location, and manually loads the file storing the setting information to the device controller. I was installing. This procedure was performed when an ID was assigned to each device controller, and then setting information corresponding to the ID was searched for and installed.

[0005] As a method of giving an ID to the device controller, a method of inputting a serial number described on a sticker attached to the device controller, or a MAC (for example, stored in an Ethernet (registered trademark) chip, There is a method of using the hardware identifier added to the component of the device controller like the Media Access Control) address as the identifier of the device controller. [0006] In addition, when a device controller is connected to a sub-network that also has multiple device capabilities on the general-purpose bus and the device controller is replaced, it is necessary to reset the device controller to enable control of the sub-network, etc. .

[0007] As a method of resetting the device controller, there is a method of installing the setting of the device controller by a worker's manual work. For example, the worker inserts portable media (CD, floppy (registered trademark) disk, USB (universal serial bus) memory) storing the setting file into the device controller to be reconfigured. This allows the device controller to detect the configuration file it uses and automatically configure it.

[0008] Further, as another method for resetting the device controller, the device controller and a server storing the setting file of the device controller are connected, and the setting file is downloaded from the server to the device controller. As a result, when a device controller is replaced, the device controller can also monitor and control the device by sending a request to search for its own configuration file to the server. As a technique for backing up the setting file to the server in this way, a technique described in JP 2004-102450 A can be cited.

[0009] Furthermore, it has been proposed to solve problems related to data durability in a client-server system by the advancement of an embedded device network that performs plug-and-play and P2P (Peer-to-peer) communication. Yes. The technology for realizing this embedded device network realizes that device data and computer processing programs are distributed over the network. In this embedded device network, in order to maintain the durability of data, it is necessary to protect the integrity of computer processing programs and data even when a part of the system fails.

[0010] As a technique for maintaining the resistance of computer processing programs and data, computer processing programs and data are generally stored in a duplicated manner in a network. By duplicating data, even if a part of the system fails, the data can be recovered after the system is repaired.

As described above, in order to maintain the durability of data, conventionally, information in a network is used. It is possible to use an information backup server that provides services with high reliability and high confidentiality, and a distributed RAID (Redundant Array of Inexpensive Disks) system that distributes data among multiple terminals. ing. In addition, as a technique for backing up data to a server, a technique described in Japanese Patent Application Laid-Open No. 2004-102450 can be given.

[0012] Further, conventionally, there have been proposed a technique for storing duplicate copies of information in the entire system by devices constituting the network and a technique for evenly distributing information on the entire system to all devices. Yes.

However, as described above, the method of adding an ID to the device controller as described above has no relation to the role or purpose regardless of the role or purpose of the device controller in the entire system. There is no ID attached. Therefore, it was necessary to pay close attention to the operator when setting the device controller to operate by adding IDs to multiple device controllers.

[0014] Since the role and characteristics of the device controller in the system and the physical connection relationship are also different, the task of adding an ID to the device controller is complicated and prone to configuration errors! It was a thing.

[0015] Therefore, the method of using the ID written on the sticker pasted on the above device controller as the ID of the device controller has nothing to do with other device controllers, and an ID is added to each device controller. Therefore, it was difficult to set the operation. In addition, when using the IDs of device controller components, it was not possible to visually check after setting the ID, and the reliability of whether the work was properly completed was low.

[0016] In the device controller setting method described above, the portable media storing the setting file may be lost. In that case, the device controller cannot be set. In addition, lost mobile media can be used by malicious third parties. Furthermore, there is a possibility that the setting file stored in the portable media may be damaged and become unreadable, and it is necessary to always prepare a new portable media in preparation for this. It also manages the creation and use of portable media that stores configuration files. Incorrect data may be stored on the portable media due to a setting error by the operator. In addition, it is necessary to provide the device controller with a disk playback device for reading portable media, which increases costs.

[0017] Furthermore, when the device controller downloads the setting file from Sano, it is necessary to provide means for connecting to the server, which increases the cost. Furthermore, the device controller cannot be set when the server cannot be used.

[0018] Further, in the above-described conventional network technology, in a system including an information backup server, connecting the information backup server and the device itself may be a problem of reliability. For example, if the device controller cannot connect to the information backup server, the information backup server cannot respond and the backed up computer processing program and data cannot be used, which may result in data loss.

[0019] Further, in the system using the above-described distributed RAID, since a plurality of terminals are used, the cost for configuring the system, the maintenance cost, and the repair cost are increased. In addition, the power consumption increases as the capacity of the system increases.

[0020] Further, since the technology for storing the information of the entire system in the device by duplicating or distributing it is necessary for all devices constituting the network to have the same capacity of data storage, devices with small memory capacity are Cannot participate in a network that employs this technology, and the tolerance to data loss will be low. Therefore, the technology for storing the information of the entire system in an overlapping or distributed manner in the device is a technology that can be applied only to a high-function device having a high memory capacity, which increases the cost of the entire system.

[0021] Furthermore, the technology for storing the information of the entire system by duplicating the information in the device has a huge amount of duplicate data, and each device needs to be able to store the information of the entire system. For this reason, it is not suitable for a device having a small memory capacity due to the restriction. In a network employing this technology, if the memory capacity of each device is constant, the information of the entire system is simply proportional to the number of devices, and reliable if the number of devices is higher than the memory capacity of each device. Sex disappears.

[0022] Furthermore, the memory capacity is low, such as devices and terminals, the memory capacity is high, devices, etc. Embedded device networks with mixed power are heterogeneous. Most devices have a small memory capacity! In the technology for duplicating the information of the entire system, the amount of data that each device can store is restricted by the device with the smallest memory capacity, and part of the memory capacity range of the device with high memory capacity cannot be used. . Therefore, there is a problem of wasting the memory capacity available for the entire embedded device network.

Therefore, the present invention has been proposed in view of the above-described situation, and an identification information automatic generation apparatus and information storage system that can provide identification information related to the role of a device controller and the like. And an information storage system information acquisition method

In addition, the present invention provides an information storage system capable of setting a device controller in a simple, low-cost and short time without employing a manual setting method by an operator or a setting method for connecting to a server. The purpose is to provide.

[0025] Furthermore, the present invention provides an information storage system that can maintain the tolerance against data loss in a network and can effectively use the memory capacity of the entire system even when the memory capacity of network devices constituting the system is not uniform. The purpose is to do. Disclosure of the invention

[0026] In order to solve the above-described problem, the present invention is an identification information automatic generation device of a device controller that is connected to a subnetwork in which a plurality of devices are connected to a fieldbus and communicates with the device. Sub-network identification means for identifying sub-network characteristics, device identification means for identifying characteristics of devices included in the sub-network, and identification of sub-network characteristics and device identification means identified by the sub-network identification means And identification information generating means for using the topology information that is at least one of the features of the device as its own identification information.

[0027] The information storage system according to the present invention is connected to a subnetwork composed of a plurality of device cards, and processes for notifying an event generated in each device to the outside, and requests from the outside. There are a plurality of device controllers that notify the device and perform at least one of the processes for operating the device. Configuration description information storage means for storing configuration description information to communicate with subnetwork devices connected to itself, device control means for communicating with subnetwork devices with reference to the configuration description information, and other devices A communication means connected to the controller via a communication line to communicate with the other device controller, and configuration description information transmitted from the other device controller and received by the communication means are stored, and the other device The storage device for the knock-up functioning as a knock-up memory for the configuration description information of the controller and the self-configuration description information stored in the configuration description information storage means are stored in the backup storage means of the other device controllers. Record configuration description information of other device controllers in their own backup storage means. Ru and a storage control means for.

[0028] In order to solve the above-described problem, this information storage system includes a sub-network identification unit that identifies a characteristic of a sub-network, a device identification unit that identifies a characteristic of a device included in the sub-network, and a sub-network identification. And an identification information generating means that uses topology information consisting of at least one of the characteristics of the subnet network identified by the means and the characteristics of the device identified by the device identifying means as its own identification information, and the storage control means comprises: The identification information generated by the identification information generation means is transmitted to other device controllers by the communication means to notify the identification information of the self, and the self-configuration description stored in the backup storage means of the other device controller Information is acquired and stored in the configuration description information storage means.

[0029] The information acquisition method of the information storage system according to the present invention includes a process in which a sub-network composed of a plurality of devices is connected, an event that has occurred in each of the devices is notified to the outside, and an external request is received. An information acquisition method for an information storage system comprising a plurality of device controllers for notifying each device and performing at least one of the processing for operating the device, and storing multiple configuration description information for operating the device, Each device controller identifies the characteristics of the subnetwork connected to it, identifies the characteristics of the devices included in the subnetwork, and identifies the characteristics of the identified subnetwork and the identified devices. Topology information consisting of at least one of A step of forming, the identification information, communication A step of distributing to another device controller via a line and a step of acquiring and storing configuration description information for operating the device by operating itself stored in the other device controller are performed.

Brief Description of Drawings

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

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

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

FIG. 4 is a system diagram showing a configuration of an information storage system including a device controller including an ID generation unit to which the present invention is applied.

FIG. 5 is a block diagram showing a detailed configuration of a device controller in an information storage system including an ID generation unit to which the present invention is applied.

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

[FIG. 7] FIG. 7 shows an EMI in an information storage system including an ID generation unit to which the present invention is applied.

2 is a block diagram showing a configuration of a device adopting T technology and a fieldbus interface. FIG.

FIG. 8 is a configuration diagram of a fieldbus table.

FIG. 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 including an ID generation unit to which the present invention is applied.

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

FIG. 11 is a diagram showing software parameters included in a configuration description file stored in a device controller in an information storage system including an ID generation unit to which the present invention is applied.

[FIG. 12] FIG. 12 is a system diagram for explaining the operation of acquiring the configuration description file CFGi from the center Sano by the device controller having the ID generation unit to which the present invention is applied. is there.

[FIG. 13] FIG. 13 is a system diagram illustrating 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.

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

FIG. 15 is a block diagram showing a detailed configuration of a device controller in an 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.

[Figure 17] In Figure 17, (a) shows how the device controller is replaced, (b) shows how the device controller is given an ID, and (c) shows the device controller that is given the ID. FIG. 10 is a diagram showing how a configuration description file is transmitted from another device controller.

FIG. 18 is a sequence diagram showing processing from when a device controller ID is given to updating a configuration description file in an information storage system to which the present invention is applied.

FIG. 19 is a sequence diagram showing processing from when the device controller configuration description file is updated until the device is controlled by the device controller in the information storage system to which the present invention is applied.

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

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

[FIG. 22] In FIG. 22, (a) is an explanatory diagram in which a device controller is exchanged, (b) is an explanatory diagram in which an ID is added to the exchanged device controller and a request is broadcast, (c ) Is an explanatory diagram in which the replaced device controller receives a response including a configuration 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.

FIG. 24 is a system diagram for explaining the types of network devices 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 a configuration of a device controller in the information storage system to which the present invention is applied.

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

FIG. 28 is a block diagram showing a functional configuration in an information storage system to which the present invention is applied.

FIG. 29 is a block diagram illustrating the contents of signals in the information storage system to which the present invention is applied.

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

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

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

[FIG. 32] 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 pronoida and requester.

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

[FIG. 34] In FIG. 34, (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 pronoida and requester.

FIG. 35 is a diagram showing operation results of a memory status report output function, a distributed shared memory monitoring function, and a shared memory providing function in the information storage system to which the present invention is applied. [FIG. 36] In FIG. 36, (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 pronoida and requester.

FIG. 37 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.

[FIG. 38] In FIG. 38, (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 pronoida and requester.

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

[FIG. 40] In FIG. 40, (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 pronoida and requester.

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

[FIG. 42] In FIG. 42, (a) is a system diagram showing the usage 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 pronoida and requester.

FIG. 43 is a diagram for explaining an operation when a network device is detached in the information storage system to which the present invention is applied.

FIG. 44 is a flowchart for explaining an operation when a network device is detached in an information storage system to which the present invention is applied.

BEST MODE FOR CARRYING OUT THE INVENTION

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

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

[0033] The device controller Di includes an ID generation unit 10 that internally identifies the characteristics of the fieldbus and the characteristics of the device and generates a device controller ID. This ID generation unit 10 is characterized in that, when the characteristics of the fieldbus are identified, the identified information is set in the device controller ID (Si) that is its own identifier. For example, based on the type and number of fieldbuses, the type and number of devices connected to the fieldbus To generate a device controller ID.

[0034] For example, when an identifier is given to the device controller Di and the device controller Di is newly connected to the field bus in a state, the device controller Di does not have to be given a device controller ID manually by an operator. The device controller ID can be automatically set, and information (configuration description information) for automatically monitoring and controlling fieldbus devices can be acquired. This eliminates the need for ID addition work, configuration description information search work, configuration description information installation work, etc., which was necessary for existing manual settings, prevents setting mistakes, and reduces setup time. Shortening, reduction of equipment cost, etc. are realized.

[0035] As shown in Fig. 2, when the device controller Di generates its own device controller ID, first, the ID generator 10 searches the software stack (hierarchical configuration) inside the device controller Di. (Procedure 1, sub-network identification means). At this time, it is desirable that the ID generation unit 10 searches not only the software stack but also the hardware stack. As a result, the ID generation unit 10 creates a fieldbus list that lists the characteristics of the fieldbus V connected to the device controller Di, and recognizes that the fieldbus FBx and FBy are connected. . This fieldbus FBx, FBy information is a feature of the fieldbus FBx, FBy, for example, information indicating the type or number of fieldbus FBx, FBy that indicates what protocol is used to control and monitor the device It is.

[0036] Next, the ID generation unit 10 operates each FBx interface and FBy interface by a method compliant with the characteristics of the fieldbus FBx and FBy, and selects a device connected to the fieldbus FBx and FBy. Search (step 2, device identification means). As a result, the ID generation unit 10 can recognize that the devices x2, x3, xl, x2, and x2 are connected as the devices connected to the fieldbus FBx, and the devices connected to the fieldbus FBy. As can be seen, the devices yl, yl, y2, yl are connected. The information on the devices X and y is the characteristics of the devices X and y, and is information indicating the type (sensor, activator, illumination) or the number of devices, for example.

[0037] Next, the ID generation unit 10 aggregates the fieldbus FBx, FBy information acquired in step 2 and the device X, y '| blueprint, and generates {FBx, FBy, x2, x3 , xl, x2, x2, yl, yl, y2, yl} and Create the so-called porology information and organize this data as {FBx, FBy, xl, x2, x2, x2, x3, yl, yl, yl, y2}. Next, the ID generation unit 10 refers to the organized topology information to obtain the number of fieldbuses and the number of devices, and {l: FBx, l: FBy, l: xl, 3: χ2, 1: χ3 , 3: yl, 1: y2} topology information. As a result, the ID generation unit 10 is connected to the device controller Di by one different type of fieldbus FBx, FBy, and the device controller Di has one different type of device xl, three devices x2, and a device It can be recognized that one x3, three devices yl, and one device y2 are connected.

[0038] Indicates the number of types of fieldbuses, the number of fieldbuses and devices {1: FBx, l: FBy, l: xl, 3: χ2, 1: χ3, 3: yl, 1: y2} topology information Is a unique device controller ID (Si) for the device controller Di. Thereby, the ID generation unit 10 functions as identification information generation means.

[0039] Further, the ID generation unit 10 creates role description information of the device controller Di so that the administrator of the device controller Di can easily distribute the features of the device controller Di. The role description information is, for example, “Device controller Di is connected to field bus FBx compliant with EMIT (Embedded Microworking Technology) and field bus FBy compliant with LON (Local Operating Network). The buses FB X and FBy are connected with three lights (3: x2) and two air conditioners (2: yl) as control targets, and one human sensor (1: xl) as a monitoring target. And one smoke sensor (1: x3) and one intercom (1: y2) are connected!

[0040] As shown in FIG. 3, a device controller Di manufacturer or the like controls a device via the fieldbus according to the type and number of fieldbuses to which the device controller Di is connected and the type and number of devices. · A configuration file CFGi necessary for monitoring is prepared. This configuration description file CFGi is a file that contains information on environment settings made to make the device easier to use for the device controller Di. For example, the configuration description file CFGi stores various items such as individual device settings and device operation. This configuration file CFGi contains the fieldbus type, number and device type, A plurality of numbers are created and stored in the file storage device in combination with the number. Each configuration description file CFGi has a device controller ID acquired by the device controller Di. Therefore, the creator of the configuration description file CFGi determines what kind of device the ID generator 10 of the device controller Di uses depending on the type of fieldbus to which the device controller Di is connected, the number of devices and the type of device, and the number of devices. It knows whether the controller ID is created and stores it in the file storage device.

[0041] Therefore, when the device controller Di acquires the device controller ID (Si) by performing the above-described processing, the device controller Di sends a file transfer request for returning the configuration description file CFGi including the device controller ID (Si). Then, notify the file storage device where the configuration description file CFGi is stored.

[0042] The file storage device storing the configuration description file CFGi, when a file transfer request including the device controller ID (Si) is notified from the device controller Di, the configuration description file CFGi corresponding to the device controller ID (Si). Is read back and sent back to the device controller Di. As a result, the device controller Di can acquire and install the configuration description file CFGi that describes the processes that can be controlled and monitored by the device connected to itself.

[0043] As described above, according to the ID generation unit 10 to which the present invention is applied, the topology information including the characteristics of the subnetwork connected to the device controller Di and the characteristics of the devices constituting the subnetwork. Since the device controller ID can be automatically generated with the device controller ID set as its own device controller, it is possible to prevent setting errors of the device controller ID, shorten the setting time, and reduce the setting cost. Further, 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 for the administrator of the device controller D to share.

[0044] It should be noted that the ID generation unit 10 described above is not limited to the fieldbus FBx, FBy force, and the like, which is a device that acquires the type and number of devices. The topology information may be created including other information such as device location information. The ID generation unit 10 creates topology information including the types of individual devices. Topology information may be created by creating a device type from the role of collecting device types. This prevents the device controller IDs from becoming the same even when the device controller ID is created with the same fieldbus configuration capabilities.

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 sends a file transfer request including the device controller ID (Si) to the other device controller Di when the other device controller Di functions as a file storage device. .

As shown in FIG. 4, this device controller Di is a general-purpose bus that performs P2P (Peer-to-peer) communication, and is connected to a network NW for a plurality of device controllers Di. An information storage system to which D4 (hereinafter collectively referred to simply as “device controller Di”) is connected is configured. Examples of the network NW that is a general-purpose bus include the Internet using IP (Internet Protocol). Each of the device controllers D1 to D4 can perform P2P communication, and can exchange information with each other. The detailed configuration of each device controller Di is shown in Fig. 5.

[0047] Each device controller Di is connected to a subnetwork in which a plurality of devices are connected to a fieldbus. The device controllers D1 to D4 store configuration description files CFGi (C1 to C4) obtained by the above-described processing in order to control and monitor a plurality of devices connected to the fieldbus. The device controllers D1 to D4 store the configuration description file CFGi of the other device controller Di in their own distributed shared memory 1—D1, 1-D2, 1-D3, 1—D4. Yes. 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.

[0048] The device controller Di uses a device embedded network technology (EMIT, hereinafter referred to as EM IT technology) to communicate with the device and the device controller Di. Fieldbus B, which communicates with a predetermined multiplex transmission method (Enumast method) that realizes transmission and reception of signals by performing baseband transmission that modulates the pulse width between the device bus A and the device controller Di, and LON It is connected to Fieldbus C, which communicates using a distributed control network system. Note that the device controller Di can be connected to the fieldbus by any method, not only when using the EMIT technology, enumast method, and LON described above.

[0049] It should be noted that a plurality of devices such as devices A0 to A2, S3 to S7,... Are connected to the field bus A, and a human sensor is included as the device S3. In the field bus B, a plurality of devices such as devices SO, Sl, Al, A3, Α4,... Are connected, and the device A1 includes illumination. Further, a plurality of devices such as devices AO to A2 and S3 to S5 ′... Are connected to the field bus C, and a temperature sensor is included as the device S2.

[0050] The device controller Di includes a P2P communication processing unit 11 connected to a network NW that performs P2P communication with other device controllers Di, a storage control unit 12, and the above distributed shared memory 1 -Dl, 1 -D2 , 1 -D3, 1— Distributed shared memory 13 equivalent to D4, configuration information driver 14, variable table 15, application processing unit 16, and fieldbus monitoring 'control unit 17 are connected to itself. And field node interfaces 18A, 18B, and 18C corresponding to a plurality of field buses A, B, and C.

[0051] When the field bus interface 18A, 18B, 18C is given a command from the ID generation unit 10 to obtain the characteristics of the devices connected to the field buses A, B, C, the field bus interface 18A, 18B, 18C Send to bus A, B, C. When a response from the device is received, the response is passed to the ID generation unit 10.

[0052] As shown in FIG. 6, the ID generation unit 10 communicates with a topology information generation unit 10A, a fieldbus search processing unit 10B, an OS (Operation System) reflection processing unit 10C, and a device access processing unit 10D. A driver 10E and a fieldbus communication port 10F are provided. The communication driver 10E may be shared with the fieldbus communication driver 18a shown in FIG. 5, and the communication driver 10E may be shared with the fieldbus interface unit 18b shown in FIG. The ID generation unit 10 illustrated in FIG. 6 is a specific configuration example that performs the operation described with reference to FIG. When the device controller Di generates its own device controller ID, the OS reflection processing unit 10C of the ID generation unit 10 searches the software stack (hierarchical configuration) inside the device controller Di. This software stack is composed of a plurality of communication drivers that enable communication on the field buses A, B, and C because the type of field bus connected to the device controller Di is assumed in advance. Yes.

[0054] As a communication driver software stack, for example, FIG. 6 shows a software driver that includes enumast software and EMIT software. Enmast software is stored in the software address (0 X 1003), and EMIT software is stored in the software address (0 X 4

325). Enmast is a proprietary protocol that is used in a wiring system in which all switches are networked with two ± 24V signal lines, and lighting control is performed using a NOR signal. EMIT (Embedded Micro Internetworking Technology) is a device-embedded network technology that has the ability to easily incorporate middleware into devices and connect to the network.

[0055] It should be noted that although shown in the figure, the software for communicating with the LON is stored as described above! When such a software stack is searched by the OS reflection processing unit 10C, the OS reflection processing unit 10C reads the correspondence between the driver name enumast and the address of the enumast software (0 X 1003), and the driver name EM Derivation of correspondence between IT and EMIT software address (0 X 4325)

[0056] In the initial stage of manufacturing, the device controller Di is connected to the power field bus A, B, C, in which a plurality of types of communication drivers are stored to support any field bus. Start one or more communication drivers from multiple types of communication drivers. If the device controller Di is connected to two Enumast-compliant fieldbuses and one EMIT-compliant fieldbus, two Enumast communication drivers, one EMIT communication driver, Will be activated. In other words, two enum communication drivers are copied to different memory addresses and various settings are made, and one EMIT communication driver is copied to different memory addresses. Various settings will be made. As a result, the device controller Di forms a hardware stack composed of two communication drivers for enumast and one communication driver for EMIT. This hardware stack is searched by the OS reflection processing unit 10C. As a result, the OS reflection processing unit 10C sets the communication address for the enumast to the physical address (0 X 5544), the communication address for the enumast to the physical address (0 X 5588), and EMIT to the physical address (0 X 55BB). Can create hardware configuration information that has a communication driver for the system.

[0057] The configuration of the communication driver detected by the OS reflection processing unit 10C consists of two enumast communication driver information (NM, NM) and one enumast communication driver information (EM ) Is output to the topology information generation unit 10A. This communication driver information corresponds to the type and number of fieldbuses that are the characteristics of the fieldbus described above.

[0058] When the type and number of field buses are supplied to the topology information generation unit 10A by the OS reflection processing unit 10C, the device access processing unit 10D is connected to each field bus, and the maximum number of devices and A range of addresses that can be taken by the device connected to the fieldbus is called. Note that the maximum number of devices and the address range are values specified in advance by the fieldbus communication method. The operation of the device access processing unit 10D is activated by the fieldbus search processing unit 10B.

[0059] Then, the fieldbus search processing unit 10B controls the device access processing unit 10D to call the device for each address within the range of addresses that the device takes for each fieldbus. The number of calls to this device is the maximum number of devices that can be connected per fieldbus. The device access processing unit 10D calls a device for each address for each fieldbus. The fieldbus search processing unit 10B operates the device access processing unit 10D repeatedly until a call is made for all addresses.

[0060] The device access processing unit 10D of the ID generation unit 10 calls the fieldbus device connected to the device controller Di according to the communication method of the fieldbus. This call is sent to the fieldbus via the communication driver 10E and the fieldbus communication port 10F.

The device receives a call signal from the ID generation unit 10. Included in call signal If the address to be received is its own address, the reflection protocol implementation unit 20A of the device activates the reflection processing unit 20B. The reflection processing unit 20B obtains tag information (device type tag) indicating its own device type (kind) by searching for device firmware, and returns it to the fieldbus communication port 10F via the reflection protocol implementation unit 20A. . The tag information stores the device address. If there is no device with 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 fieldbus.

[0062] The device access processing unit 10D receives tag information including addresses from all devices connected to the fieldbus. As a result, the device access processing unit 10D recognizes the number of devices connected to each fieldbus based on the number of tag information replies, and determines the type of each device based on each tag information. recognize. The device access processing unit 10D can obtain the address range of the device connected to each fieldbus.

[0063] For example, the Enumast fieldbus is connected to devices in the order of smoke detector (SD), human detection sensor (PD), human detection sensor (PD), and others. The enumast field bus consists of a wall switch (WS; Wall Switch), lighting (L; Light), lighting (L), wall switching (WS), lighting (L), wall switching (WS), lighting (L). The devices are connected in order, and the EMIT fieldbus has a digital camera (DC), wall switch (WS), air conditioner (AC), dimmer (D) ), Air conditioner (AC), dimmer (D), IP phone (IP) are connected! In this case, the device tag information (type information) for each fieldbus is supplied to the device access processing unit 10D force fieldbus search processing unit 10B in the order in which the devices are connected.

[0064] The tag information of the called device is supplied from the fieldbus search processing unit 10B to the device detection unit 10a of the topology information generation unit 10A.

[0065] The topology information generation unit 10A aggregates a device detection unit 10a connected to the fieldbus search processing unit 10B and a driver detection unit 10b connected to the OS reflection processing unit 10C. A processing unit 10c, a classification processing unit 10d, and an ID generation processing unit 10e are provided.

[0066] Tag information (type) of a plurality of devices detected by the device detection unit 10a and nodeware configuration information indicating the type of fieldbus detected by the driver detection unit 10b are aggregated by the aggregation processing unit 10c. The This aggregation process is a process of listing the type of device detected by the device detection unit 10a and the type of fieldbus detected by the OS reflection processing unit 10C. The information aggregated by the aggregation processing unit 10c is classified into the same device type and the same fieldbus type by the classification processing unit 1 Od, and the number of the same device types is the same. The number of fieldbus types is determined. The information classified by the classification processing unit 10d is topology information for the device controller Di and is a unique device controller ID (Si) for the device controller Di. Thereby, the ID generation unit 10 functions as identification information generation means.

[0067] It should be noted that the ID generation processing unit 10e creates the role description information of the device controller Di in order to make it easier for the administrator of the device controller Di to share the features of the device controller Di as described above. Desire ヽ.

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

[0069] Each device is equipped with a MOS (Micro Object Server) function unit 21 that transmits and receives control data of various devices between EMIT middleware and device status signals. The field bus interface 18A is provided with an OAS (Object Access Server) function unit 31 that performs routing processing between EMIT middleware, device recognition processing, and the like. OAL (Object Access Library) function unit (not shown) that outputs a control / monitoring request to the device to be controlled and displays the status of the device on the user terminal (not shown) that manages the device Has been implemented. In FIG. 7, the case where only the OAS function unit 31 is mounted on the fieldbus interface 18A, 18B, 18C will be described. However, the OAL function unit may be mounted. In the device, an MOS processor 21 is connected to an application processor 22 and an interface module 23.

For example, when the application processing unit 22 functions as a sensor, an application code for obtaining a detection value (IZF value) is stored. The application processing unit 22 holds the detection value and passes it to the MOS function unit 21.

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

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

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

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

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

The OAS function unit 31 is connected to a fieldbus monitoring / control unit 17 described later, and communicates with the device of the fieldbus A according to the control of the fieldbus monitoring / control unit 17. Fieldbus monitoring and control unit 17 controls and monitors devices with users and administrators If communication is desired, a control / monitoring request to that effect is supplied and a response to the control's monitoring request is returned.

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

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

[0080] In order to communicate with the client (OAL), the device access server 3 la sends a request from the client via the communication module 32, the fieldbus monitoring and control unit 17, and the P2P communication processing unit 11. Receive. Then, the device access server 3 la controls the operation of transmitting the control “monitoring request” to the device via the device access controller 3 lc and the communication module 32. As a result, the device access controller 31 c transmits a request from the client to the device and controls the device.

The device access controller 31c searches the device service table 21e and the capability table 24 via the communication module 32 in order to obtain the device interface definition and service information. As a result, the device access controller 31c determines what service each device has (function 21a, event 21b, variable 21c), and indicates the correspondence between the object ID 21d of each device and the service list. Create 3 lb service information. Further, the device access controller 31c recognizes what capabilities (communication protocol version, communication speed) each device has. The service information 31b acquired by the device access controller 31c is information indicating the characteristics of the device when a command for acquiring the characteristics of the device is generated from the ID generation unit 10. May be supplied to the ID generation unit 10.

When the MOS function unit 21 receives an event packet of an event at the communication module 32, the device access controller 31c analyzes the event packet and notifies the device access server 31a. In addition, the device access controller 31c recognizes the MOS function unit 21 that can respond to the monitoring request by referring to the service information 3 lb when sending a monitoring request to the device. . Then, the device access controller 31c adds the transmission destination object ID 21d to the control 'monitoring request, and causes the communication module 32 to transmit a bucket to the device according to the capability of the device.

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

[0084] The device controller Di having such an OAS function unit 31 is detected by the ID generation unit 10 by the software stack search process (step 1), and the ID generation unit 10 sets the field bus A in compliance with EM IT. It is detected that it is connected. After that, when a command for searching for devices connected to the field buses A, B, and C is given by the ID generation unit 10 to the OAS function unit 31, the devices connected to the field bus A according to the commands are sent. By obtaining the service table 21e (tag information), the device type (feature) can be generated as the device controller ID.

[0085] As shown in FIG. 5, the fieldbus interfaces 18A, 18B, 18C are configured to include a fieldbus driver 18a and a fieldbus interface unit 18b.

The fieldbus driver 18a corresponds to the communication driver 10E shown in FIG. When the field bus driver 18a receives the control data from the fieldbus 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 to be operated and how. Send a command to the device. In addition, Upon receiving a command from the fieldbus driver 18a, the first bus interface unit 18b converts the command into a signal corresponding to the fieldbus A, B, C and sends it to the fieldbus A, B, C.

[0087] Further, the fieldbus driver 18a is supplied with a command for searching for a device connected to the fieldbus A, B, or C in order to generate a device controller ID in the ID generation unit 10, and identifies a feature of the device. Get information to do.

[0088] The fieldbus interface unit 18b is connected to the fieldbus communication port 1 shown in FIG.

Corresponds to OF. The fieldbus interface unit 18b provides the fieldbus monitoring data to notify the fieldbus monitoring and control unit 17 of device status change and event occurrence.

When the A, B, and C forces are also received, the monitor data is transferred to the fieldbus driver 18a and sent to the fieldbus monitoring and control unit 17.

[0089] The fieldbus monitoring and control unit 17 refers to the variable table 15 and refers to the fieldbus A,

Controls B and C. As shown in FIG. 9, the variable table 15 is configured by associating device names, device states, variable types, field bus IDs, and addresses within the field bus for each of the field buses A, B, and C. . Then, the fieldbus monitoring / control unit 17 monitors the devices of fieldbus A, B, C, updates the contents of variable table 15, and refers to variable table 15 for fieldbus A, B, C. Send control data to the device.

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

[0091] The application processing unit 16 controls application processing realized by the device. . The application processing unit 16 refers to the variable table and gives a control / monitoring request to the fieldbus monitoring / control unit 17. As a result, the device is operated according to the monitoring request and control request transmitted from the user through the network NW.

Further, as shown in FIG. 5, the application processing unit 16 includes an application processing unit 16A for sending control data to the device, a linkage table 16B in FIG. 10 described later, and a linkage table according to its own configuration description information. It can be configured as an application update unit 16C that updates 16B.

The configuration description information driver 14 stores a configuration description file CFGi for controlling and monitoring the fieldbuses A, B, and C connected thereto. As shown in FIG. 5, the configuration description information driver 14 is connected to the storage control unit 12 and includes a configuration description file storage unit 14a for storing its own configuration description file CFGi. The configuration description information driver 14 receives the configuration description file CFGi in the configuration description file storage unit 14a as the configuration description file CFGi selected by the information selection unit 12E when other device controller capabilities are transmitted with multiple configuration description files CFGi. Rewrite to In addition, the configuration description information driver 14 indicates that, for example, when a new device is connected to the field bus A, B, C, the information about the new device is added to the variable table 15 by the fieldbus monitoring unit 17A. Is notified from the device controller ID storage unit 19, and the change information of the fieldbus A, B, C is stored in the configuration description file CFGi. As a result, the configuration description file CFGi can always be kept up-to-date.

[0094] The information (configuration description information) included in the configuration description file CFGi includes a fieldbus table that defines the fieldbus connected to itself as shown in FIG. 8, the variable table 15 in FIG. This includes a linkage table that defines linkage operations between devices as shown in Fig. 10, and software parameters that store other parameters as shown in Fig. 11.

[0095] The fieldbus table shown in FIG. 8 is the fieldbus ID of each fieldbus A, B, C (fbO, fbl, fb2,...) And the method used by the fieldbus A, B, C. Fieldbus information defining (EMI T, Enumast, Ron) is associated. This field bus table is read by the fieldbus monitoring 'control unit 17 and connected to itself. Referenced to identify the designated fieldbus A, B, C.

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

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

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

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 the configuration description file CFGi of another device controller Di can be stored. Based on the capacity of its own configuration description file CFGi, the storage controller 12 determines whether or not its own configuration description file CFGi can be stored in another device controller Di.

[0100] The storage controller 12 uses the distributed shared memory 1 in the entire network NW, The process of backing up its own configuration description file CFGi in the distributed shared memory 13 of the other device controller Di and the process of backing up the configuration description file CFGi of the other device controller Di in its own distributed shared memory 13 are performed. When the storage controller 12 backs up its own configuration description file CFGi to another device controller Di, the storage control unit 12 reads out its own configuration description file CFGi stored in the configuration description information driver 14 and receives other configuration descriptions from the P2P communication processing unit 11. Send to device controller Di. Further, the storage control unit 12 accepts a backup request from another device controller Di via the P2P communication processing unit 11 and stores the configuration description file CFGi of the other device controller Di in the distributed shared memory 13.

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

[0102] When the information request unit 12C detects from the software parameters in the configuration description file storage unit 14a that it does not have its own configuration description file CFGi, it sends a file transfer request including the device controller ID to the P2P communication processing unit 11 To send from. This file transfer request includes the device controller ID generated by the ID generation unit 10.

[0103] When one or more configuration description files CFGi are received by the P2P communication processing unit 11 from another device controller Di in response to the transmission of this file transfer request, the configuration description file CFGi is received by the information receiving unit 12A. Receive at. 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 a plurality of configuration description files stored in a voted form in the configuration description information memory 12D. The configuration description file CFGi, which is the latest and not corrupted, is selected from the files, and can be used by the configuration description information driver 14. Accordingly, the configuration description information driver 14 updates the configuration description file CFGi stored in the configuration description file storage unit 14a. At this time, the information selection unit 12E selects the latest configuration description file CFGi with reference to the time stamp added to the configuration description file CFGi. As a result, the configuration description information driver 14 updates the configuration description file stored in the configuration description file storage unit 14a. [0104] Further, the storage control unit 12, for example, when the configuration of the fieldbus A, B, C is changed or when the device controller Di that stores the configuration description file CFGi is detected, The configuration description file CFGi needs to be updated. At this time, the storage control unit 12 also detects 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. Then, the information update unit 12B includes the device controller ID in the file update request for updating its own configuration description file CFGi and broadcasts it from the P2P communication processing unit 11.

[0105] In this way, when the configuration of the subnetwork connected to itself changes, the configuration description file CFGi is updated according to the changed configuration, and the configuration description file of another device controller is updated. Since CFGi is updated, the latest configuration description file CFGi can always be stored. The device controller ID newly generated by the ID generation unit 10 is added to the file update request according to the change in the configuration of the field buses A, B, and C.

Furthermore, when the configuration description file CFGi is received from the other device controller Di by the information receiving unit 12A, the storage control unit 12 stores the configuration description file CFGi of the other device controller Di in the distributed shared memory 13. Remember. In addition, when the storage controller 12 receives a file transfer request for the device controller Di from another device controller Di, the storage controller 12 corresponds to the device controller ID included in the file transfer request by the information receiver 12A. The configuration description file CFGi to be read is read out and sent from the P2P communication processing unit 11.

[0107] The device controller Di configured as described above has a general purpose bus communication software for realizing the P2P communication processing unit 11 and a fieldbus interface 18A, 18B, 18C as a software stack. Fieldbus communication software for connecting to buses A, B, and C, file management software for obtaining configuration description file CFGi, and application software for controlling devices in fieldbus A, B, and C And are implemented.

[0108] The ID generation unit 10 detects the characteristics of the fieldbus A, B, and C connected to the device controller Di by detecting the fieldbus communication software. You can control the fieldbus interface 18 A, 18B, 18C to get the characteristics of the devices connected to the fieldbus A, B, C. Then, the ID generation unit 10 can generate a device controller ID (Si) based on the combination of the characteristics of the field buses A, B, and C and the device characteristics and store the device controller ID (Si) in the device controller ID storage unit 19. . Then, when the device controller ID (Si) is set, the device controller Di obtains its own configuration description file CFGi from the other device controller D by the storage control unit 12, and FIG. 8 to FIG. The configuration description file CFGi including the information shown in 11 can be stored in the configuration description file storage unit 14a to control and monitor the devices of the fieldbus A, B, and C.

In addition, as shown in FIG. 12, the device controller Di is a configuration description file corresponding to a device controller ID (Si) generated by a combination of all fieldbus A, B, and C features and device features. It may be connected to the data server 41 that stores CFGi.

The device controller Di in this system is connected to the data server 41 via a general-purpose line such as the Internet. Then, when the device controller Di automatically generates the device controller ID (S1) by the ID generation unit 10 and stores it in the device controller ID storage unit 19, the P2P communication processing unit 11 sends the device controller ID to the data server 41. Send a file transfer request that includes the controller ID (SI).

[0111] Upon receiving a file transfer request including the device controller ID (S1), the data server reads the configuration description file CFGi corresponding to the device controller ID (S1) and returns it to the device controller D1. . As a result, the device controller D 1 automatically performs the process of acquiring the configuration description file CFGi and installing the configuration description file CFGi without the effort of the operator. Can do.

[0112] The data server 41 may be a center server type that can respond to file transfer requests from a plurality of device controllers D via the Internet network as shown in FIG. It may be a local server type connected to. [0113] Furthermore, as shown in FIG. 13, a plurality of configuration description files CFGl (Sl), CFG2 (S2), and CFG3 (S3) were stored and shipped at the manufacturing stage of device controller D in a factory or the like. In this case, 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 ID2 is generated from the type of fieldbus FB and the device type, the configuration description file CFG2 is selected from the multiple configuration description files CFGi stored in advance in the configuration description information memory 12D. And stored in the configuration description file storage unit 14a. As a result, the selected configuration description file CFG2 is read by the configuration description information driver 14 into the application processing unit 16, the fieldbus monitoring / control unit 17, and the fieldbus driver 18a.

[0114] As described above, even if the device controller Di is installed in the system as shown in FIG. 4 to FIG. 13, the feature of the subnetwork connected to the device controller Di by including the ID generation unit 10 Since the device controller ID is automatically generated and the configuration description file CFGi can be obtained by using the topology information that is the device characteristic and its own device controller ID, the device controller ID and the configuration description file CFGi Prevention of setting mistakes, shortening of setting time, and reduction of setting cost can be realized. Further, since the device controller Di is a device controller ID related to the role of the device controller Di, it is easy for the administrator of the device controller D to share.

[0115] Next, a second embodiment to which the present invention is applied will be described. Note that parts similar to those of the first embodiment described above are denoted by the same reference numerals, and detailed description thereof is omitted.

[0116] The information storage system according to the second embodiment is characterized in that the configuration description information stored in each device controller Di is multiplexed and stored in the knock-up storage means of one or more other device controllers Di. It is what.

For example, as shown in FIG. 14, this information storage system includes a plurality of device controllers D1 to D4 (hereinafter collectively referred to as “device controller Di”) in a network NW that is a general-purpose bus. Is connected. An example of a network NW that is a general-purpose bus is the Internet using IP (Internet Protocol). Multiple devices Each of the controllers D1 to D4 can perform peer-to-peer (P2P) communication, and can exchange information with each other.

Each device controller Di is configured in the same manner as in FIG. 4 described above. As shown in FIG. 15, the detailed configuration of the device controller Di is replaced with an operator operation panel instead of the ID generation unit 10. Device controller ID is given by the operation to, the operation to the dip switch. This device controller ID is stored in the device controller ID storage unit 19. The device is configured in the same way as in FIG.

For example, as shown in FIG. 16, when the configuration description file CFGi of the device controller D4 is replaced with the latest configuration description file CFGi (4 +) by the manufacturer, the device controller D4 is replaced with another device controller D1. Broadcasts a file update request containing its device controller ID to ~ D3. As a result, the configuration description file CFGi of the distributed shared memory l—Dl, 1 -D2, 1—D3 of the other device controllers D1 to D3 can be changed to the latest configuration description file CFGi (4 +).

[0120] Also, as shown in Fig. 17 (a), when the device controller Di that was P2P connected to the device controllers D1 to D3 is replaced, the device controller ID is not given at the time of replacement. . As shown in FIG. 17 (b), when the device controller ID (ID: 4) is given to the device controller D4 and stored in the device controller ID storage unit 19, the information request unit 12C Broadcast a file transfer request that includes the ID. As a result, as shown in FIG. 17 (c), among the device controllers D1 to D3, the configuration description file corresponding to the device controller ID (4) is transmitted from the device controllers Dl and D2, and the device controller Can be received by D4. Here, the device controller D3 cancels the file transfer request from the device controller D4 because the processing load including the storage controller 12 is high.

Next, the 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 and other device controllers D1 to D3 and the configuration requirements of the device controller D4 with arrows, and the operation contents (steps) of the arrows are shown at the left end. It is described. As shown in FIG. 18, the device controller first stores the device controller ID when the device controller ID (= 4) is set by the operator (user) operation (step ST1). The device controller ID of section 19 is changed (step ST2). Of course, the device controller ID may be automatically set by the ID generation unit 10.

[0123] Next, the device controller ID storage unit 19 notifies the configuration description information driver 14 that the device controller ID has been changed, and the configuration description information driver 14 stores the configuration description file in the configuration description file storage unit 14a. Reset CFG4 (step ST3).

[0124] Next, the configuration description file storage unit 14a notifies the information requesting unit 12C that the configuration description file CF G4 has been reset and is empty (step ST4), and the information requesting unit 12C The file transfer request is passed 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 also received by the information requesting unit 12C into a predetermined packet and broadcasts it to the other device controllers D1 to D3 (step ST6).

[0125] Upon receiving the file transfer request, the device controllers D1 to D3 return the plurality of configuration description files by returning the configuration description file CFG4 corresponding to the device controller ID (= 4) included in the file transfer request. 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 a plurality of 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). .

[0127] Next, the configuration description file CFG4 that has been updated and corrupted from the plurality of configuration description files CFG4 stored in the form voted by the other device controllers D1 to D3 in the configuration description information memory 12D. Is selected by the information selection unit 12E (step ST9), passed to the configuration description information driver 14, and the configuration description information driver 14 stores the configuration description file CFG4 in the configuration description file storage unit 14a (steps ST10 and ST11). Next, as shown in FIG. 19, the operations of the fieldbus control unit 17B, the fieldbus monitoring unit 17A, the fieldbus driver 18a, and the fieldbus interface unit 18b are updated (step ST12), and the variable table is updated. The variable table 15 is updated by the unit 15A (step ST13), and the linkage table 16B is updated by the application processing unit 16 fieldbus C (step ST14).

[0129] According to such an operation, the configuration description file CFG4 of the device controller D4 is distributed and stored in the distributed shared memory 13 of one or more other device controllers D1 to D3. The device controller D4 can be set simply by downloading the stored configuration description file CFG4, and it is easy and low-cost without adopting a manual setting method or setting method to connect to the server. Device controller D4 can be set in a short time. Even if there is a bug in one configuration description file CFG4, it can be set using another configuration description file CFG4.

[0130] When the operations of the fieldbus control unit 17B, the fieldbus monitoring unit 17A, the fieldbus driver 18a, and the fieldbus interface unit 18b are updated, the fieldbuses A, B, and C are started to operate (step ST15 ) When the variable table 15 and the linkage table 16B are updated, the operation of the application processing unit 16 is started (step ST16).

[0131] When the fieldbus interface 18b receives the sensor information of the temperature sensors of the fieldbus A, B, and C (step ST17), the fieldbus driver 18a creates monitor data. Then, the fieldbus monitoring unit 17A notifies the fieldbus monitoring unit 17A, and the fieldbus 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 the sensor value is generated by the MOS function unit 21 of the device, and the sensor value and the event are detected by the fieldbus monitoring unit 17A (OAS function unit 31).

[0132] 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 the event received in step ST23 is the linkage table 16B force. It is stored as an occurrence event, and it is determined whether a cooperative 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. Newly, the device status of the variable table 15 corresponding to the cooperation response device determined by the cooperation table 16B is updated (step ST21).

Thus, when the fieldbus control unit 17B detects a change in the variable table 15,

(Step ST22), control data corresponding to the cooperative operation is transmitted to the fieldbus driver 18a according to the updated contents, and the fieldbus driver 18a converts the control data into a command and transmits it from the fieldbus interface unit 18b ( Step ST23).

Next, a third embodiment to which the present invention is applied will be described. Note that parts similar to those in the above-described embodiment are denoted by the same reference numerals, and detailed description thereof is omitted.

[0135] The information storage system according to the third embodiment stores the information necessary for a plurality of network devices (for example, device controller Di) by using the distributed shared memory 1 in the entire system. It is characterized by avoiding data loss of information necessary for network devices by dynamically changing the operation.

[Basic configuration example 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 that is a general-purpose bus. Examples of the network NW that is a general-purpose bus include the Internet using IP (Internet Protocol). Each of the plurality of device controllers D1 to D4 is capable of P2P (Peer-to-peer) communication, and can exchange information with each other.

In the example shown in FIG. 20, the distributed shared memory 1—D1 of the device controller D1 has a memory capacity (3 slots) that can store three configuration description files CFGi of other device controllers Di. The distributed shared memory 1—D2 of the device controller D2 has a memory capacity (2 slots) that can store two configuration description files CFGi of other device controllers Di. Type shared memory 1—D3 has a memory capacity (3 slots) that can store three configuration description files CFGi of other device controller Di, and distributed shared memory 1—D4 of device controller D4 Device controller Di configuration description file CFGi cannot be stored in memory capacity (distributed shared memory 1 There is no state. Distributed shared memory 1—D1 stores configuration description files CFG2, CFG3, CFG4, distributed shared memory 1—D2 stores configuration description files CFG1, CFG3, and distributed shared memory 1—D3 The configuration description files CFGI, CFG 2 and CFG4 are stored, and the configuration description file CFGi is stored in the distributed shared memory 1—D4.

Therefore, this information storage system has a distributed shared memory 1 with different capacities in each device controller Di, and each device controller Di has other device controller Di and other network equipment capabilities. The configuration description file CFGi stored in its own distributed shared memory 1 is dynamically changed according to the request.

[0139] [Basic operation of information storage system]

As shown in FIG. 21, this information storage system updates the distributed shared memory 1 stored in the memory device itself in response to the update of the configuration description file CFGi of another device controller Di. As shown in FIG. 4, the other device controller Di has a function of providing a configuration description file CFGi stored in its own distributed shared memory 1.

[0140] In the information storage system, for example, when the configuration description file CFG4 is updated by the operator to become the configuration description file CFG4 +, the device controller D4 is stored in the other device controller Di. A file update request to update CFG4 to the configuration file CF G4 + is broadcast to the network NW. When the device controller Dl and device controller D3 storing the configuration description file CFG4 receive the file update request, the configuration description files stored in their own distributed shared memory 1—D1, 1—D3 Update CFG4 to the configuration description file CFG4 + attached to the file update request. In addition, the device controller D3 stores the configuration description file CFG4 and discards the file update request.

[0141] The device controller D4 is replaced with a new device controller Di by an operator as shown in Fig. 22 (a), and the device controller D4 is changed as shown in Fig. 22 (b). When the 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 own configuration description file CFGi. [0142] Then, as shown in FIG. 22 (c), when the device controller D1 stores the configuration description file CFG4 and receives the file transfer request, it stores it in its own distributed shared memory 1-D1. Return the configured configuration file CFG4 to the device controller D4. As a result, the device controller D4 can obtain the configuration description file CFG4 for communicating with the terminal device of the fieldbus. 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. In addition, the device controller D3 stores the configuration description file CFG4 and discards the file transfer request.

[0143] In this way, the information storage system is configured such that when the configuration description file CFGi of another device controller Di connected to the network NW is updated, or when another device controller Di is replaced, the configuration description file CFGi If this is the case, the configuration description file CFGi that the other device controller Di owns can be provided. Therefore, this information storage system dynamically changes the storage state of the configuration description file CFGi of each other network device even when the memory capacity of each network device is different as described below. The configuration description file CFGi of each network device retains tolerance against data loss.

[0144] [Components of information storage system]

Such an information storage system is not only used when the distributed shared memory 1 is used in the device controller D コントローラ connected to the field bus and controlling the end device connected to the field bus, as described above. The distributed shared memory 1 can be used between other network devices connected to the network NW.

[0145] As shown in Fig. 23, when there are nine configuration description files CFGi of C1 to C9 of the network devices that make up the distributed shared memory 1, the number of copies of the configuration description file CFGi of each network device Will be different. In this information storage system, the maximum number of replicas is 3, the network configuration device CFGi is backed up to 3 other network devices, and the minimum number of replicas is 0. Configuration description file C FGi is backed up by another network device, and there are some network devices mixed together. In this information storage system, the average value of the configuration description file CFGi is 1.5. 5

[0146] In contrast, the information storage system dynamically changes the usage status of the distributed shared memory 1 between network devices connected to the network NW, and the configuration description file CFGi for all network devices is different. The status backed up to other network devices is retained.

[0147] As shown in Fig. 24, the types of network devices in this information storage system include a requester Ri that uses other distributed shared memory 1 to store its own file, and its own distributed shared memory. There is a provider Pi that provides 1 to other network devices. Then, the requester Ri and the provider Pi use the distributed shared memory 1 to avoid data loss of the configuration description file CFGi. In the example shown in FIG. 24, requesters Ra, Rb, Rc, which are network devices that do not have the distributed shared memory 1, and providers PI, P2, P3, P4, P5 that provide the distributed shared memory 1 to other network devices. The case where and exist. The device controller Di described above corresponds to the provider Pi because it has the distributed shared memory 1, and also corresponds to the requester Ri in the sense that its own configuration description file CFGi is stored in another device controller Di. .

[0148] As shown in Fig. 25, the information storage system outputs a memory status report periodically or randomly by the shared memory providing function of each provider Pi, and receives the memory status report by the requester Ri. . The requester Ri sends a free slot acquisition request to the pronoida Pi when there is a free space in the distributed shared memory 1 slot of the provider Pi and it wants to back up its configuration file CFGi to the provider Pi. Response from provider P can be obtained.

[0149] [Configuration example of provider Pi]

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

[0150] As shown in FIG. 26 and FIG. 27, the provider Pi is the device controller of FIG. 4 and FIG.

The device is configured in the same manner as Di, and the device is configured in the same manner as in FIG. [0151] This provider Pi uses the distributed shared memory 1 among other network devices connected to the network NW, so the types of information stored as parameters in the software parameters shown in Fig. 11 , Parameter type information, and parameter values 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 the terminal device is controlled are stored as parameters.

[0152] For example, the size of the distributed shared memory 13 is referred to by the storage control unit 12, and the storage control unit 12 determines whether or not the requester Ri and the configuration description file CFGi of another provider Pi can be stored. . Further, the storage control unit 12 determines whether or not the configuration description file CFGi can be stored in the requester Ri and another provider Pi based on the capacity of the configuration description file CFGi. Note that the size of the distributed shared memory 1 may be described in slots representing the number of configuration description files CFGi that can be stored, not in units of bytes.

[0153] The storage control unit 12 uses the distributed shared memory 1 in the entire network NW to perform a process of backing up its own configuration description file CFGi in the distributed shared memory 13 of another provider Pi, and a requester. Ri and other provider Pi configuration description file CFGi is backed up to its own distributed shared memory 13. When the storage controller 12 backs up its own configuration description file CFGi to another provider Pi, the storage control unit 12 reads out its own configuration description file CFGi stored in the configuration description information driver 14 and receives it from the P2P communication processing unit 11 To be sent to the provider Pi. In addition, the storage control unit 12 receives a backup request from the requester Ri and another provider Pi via the P2P communication processing unit 11, and stores the requester Ri and the configuration description file CFGi of the other provider Pi in the distributed shared memory 13. To do.

Further, as shown in FIG. 27, the provider Pi is given a device controller ID by an operation on the operator's operation panel or an operation on the date switch. This device controller ID is stored in the provider ID storage unit 19.

[0155] Furthermore, when the storage controller 12 receives the configuration description file CF Gi from the requester Ri and another provider Pi at the information reception unit 12A, the storage controller 12 distributes the configuration description file CFGi of the requester Ri and other provider Pi. Store in the shared memory 13. In addition, the storage control unit 12 When receiving a free slot acquisition request for the provider Pi from Questa Ri, another provider! ^, The information receiving unit 12A sends the configuration description file CFGi corresponding to the device ID included in the free slot acquisition request. Read and send.

[0156] [Function of information storage system]

As shown in FIG. 28, the information storage system including the pronoida Pi and the requester Ri as described above is installed in the provider Pi with the distributed shared memory monitoring function 51 and the storage control function 52 implemented in the requester Ri. And a shared memory providing function 53.

[0157] The distributed shared memory monitoring function 51 is a function provided in each requester Ri. The distributed shared memory monitoring function 51 receives the memory status report S1 broadcast by the memory status report output function unit 53c of the provider Pi, and distributes the shared shared memory. It has an active monitoring unit 51a that monitors the state of the memory 1 and its own file backup state.

[0158] As shown in FIG. 29, the memory status report S1 includes the device ID of the provider Pi (hereinafter referred to as the provider ID) and the possession slot among all the slots of the distributed shared memory 13 of the provider Pi. Number (stored in the configuration description file CFGi) and slot allocation information indicating for which requestor Ri the allocated slot number is allocated. This memory status report S1 is received by the active monitoring unit 5 la.

[0159] Upon receipt of the memory status report S1, the active monitoring unit 51a creates information indicating the status of the distributed shared memory 1 and information indicating its own file backup status, and passes it to the storage control function 52 .

[0160] The storage control function 52 is an allocation table indicating which requester Ri's configuration description file CFGi is stored as information indicating the state of the distributed shared memory 1, and the provider to which the self is connected. Pi table, total number of provider Pi slots, total number of requester Ri, total number of provider Pis, configuration file C with the highest number of replicas, including the ID of the requester Ri that runs on FGi, and the average number of replicas of the configuration file CFGi Memory status file 52b is stored. In addition, the active monitoring unit 52 uses the ID of the knock-up provider Pi that stores its own configuration description file CFGi as information indicating its own file backup status, and its configuration description file in the entire current information storage system. Number of CFGi replicas, desired number of required replicas, distributed shared memory 13 free memory It stores a backup status file 52c that includes the number of provider Pis available and the hit rate that is the number of requested replicas divided by the number of provider Pis that can be stored.

[0161] 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 knock-up state file 52c, a memory state detection function unit 52d, and an empty slot. A question function unit 52e, an empty slot acquisition function unit 52f, a duplicate number warning function unit 52g, and a slot reassignment function unit 52h are provided.

[0162] The storage control function 52 includes a memory state detection function unit that includes information indicating the state of the distributed shared memory 1 and information indicating the backup state created by the active monitoring unit 51a of the distributed shared memory monitoring function 51. When passed to 52d, it creates a shared memory state file 52b and a backup state file 52c. The shared memory status file 52b and the backup status file 52c can be read from the empty slot inquiry function unit 52e and the empty slot acquisition function unit 52f.

[0163] The empty slot inquiry function unit 52e broadcasts the empty slot notification request S2 to the network NW when it wants to store its configuration description file CFGi in the provider Pi, and notifies the empty slot notification request S2 of the empty slot notification request S2. Response S3 is received. In this free slot notification request S2, as shown in FIG. 29, its own device ID (hereinafter, the device ID of the requester Ri is called the requester ID) and the hit stored in the knockup status file 42c! Including rates.

[0164] This free slot notification request S2 is received by the shared memory providing function 53 installed in the provider Pi. In response to the received empty slot notification request S2, the shared memory providing function 53 searches the empty slot by referring to the distributed shared memory 53b corresponding to its own distributed shared memory 13 by the request management function unit 53a. When there is an empty slot, the shared memory providing function 53 broadcasts an empty slot notification response S3 including its provider ID to the network NW.

[0165] When this slot notification response S3 is received by the empty slot question function unit 52e of the storage control function 52, the empty slot question function unit 52e sends the provider ID included in the slot notification response S3 to the empty slot acquisition function unit 52f. Notify As shown in FIG. 29, the empty slot acquisition function unit 52 f includes a command, a provider ID having an empty slot, and the corresponding provider I Broadcast the empty slot acquisition request S4 including the provider list including D and its own configuration description file CFGi to the network NW.

[0166] Further, the empty slot inquiry function unit 52e notifies the slot reassignment function unit 52h of the slot notification response S3, and the empty slot acquisition function unit 52f broadcasts the slot reassignment request S5 to the network NW. As shown in Fig. 29, this slot reassignment request S5 is stored in the command, provider list, requester ID of the configuration description file CFGi stored in the slot used by the provider Pi included in the provider list, and the slot used. New (self) requester ID and new (self) configuration description file CFGi.

[0167] When the shared memory providing function 53 of the provider Pi receives the free slot acquisition request S4 by the request management function 53a, the configuration description file CFGi included in the free slot acquisition request S4 is stored in the distributed shared memory 53b. . In addition, when the memory state of the distributed shared memory 53b changes due to reception of the free slot acquisition request S4 or the slot reallocation request S5, the request management function 53a stores the changed slot in the distributed shared memory 53b. The memory status report S1 including the lot allocation status is created and broadcast from the memory status report output function unit 53c. Accordingly, when the active monitoring unit 51a receives the memory status report S1 indicating that the slot allocation status has changed, the storage control function 52 updates the shared memory status file 52b and the backup status file 52c. Let

[0168] In addition, the storage control function 52 is notified of the slot notification response S3 from the empty slot question function unit 52e, and its own configuration description file CFGi is duplicated in the information storage system. Is detected by the copy number warning function 52g. When such a configuration description file CFGi is not replicated, this is notified to the active monitoring unit 51a, and the current number of replicas of the backup status file 52c is updated to “0”.

[0169] [Processing procedure of information storage system]

The operation procedure 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. FIG.

[0170] The distributed shared memory monitoring function 51 of the requester Ri first performs the processing of step ST31 to step ST38 shown in FIG. 30, and its configuration description file CFGi is transferred to another provider. In order to sort out how much it is replicated in the Pi, the shared memory state file 52b and the knock-up state file 52c are updated, and the storage control processing in the next step ST39 shows the results shown in FIGS. 31A and 31B. The processing from step ST41 to step ST54 is 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, detects the memory state report S1 distributed from the network NW. In step ST33, it is determined whether or not the memory status report S1 has been detected. If the memory status report S1 is detected, the process proceeds to step ST4, and the allocation table of the shared memory status file 52b is updated. Steps ST32 and ST33 are performed in units of time twice as long as a predetermined period for transmitting the memory status report S1 in order to reliably receive the memory status report S1 transmitted every time.

[0172] This allocation table shows the configuration description file CFG の of each device ID (provider Pi, requester Ri) stored in each provider ID and the provider description ID CFGi. It is a table. In step ST38, the active monitoring unit 5la updates the shared memory state file 52b, and proceeds to the storage control process in the storage control function 52 in step ST39.

[0173] On the other hand, when the memory status report S1 has not been received, the active monitoring unit 51a waits for a predetermined time in step ST35, and the time when the memory status report S1 has not been received has passed the predetermined time. If so, proceed 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.

[0174] In step ST36, the active monitoring unit 51a refers to the allocation table included in the shared memory state file 52b, and compares the device table including the provider ID and the requester ID constituting the information storage system, and the total information storage system. Number of slots, total number of requesters, total number of providers, maximum number of replicas possessing requester (requester ID), average number of replicas (the smaller of slot number / requester number and requester number 1), number of backup providers, current replication Number, the number of available memory providers.

[0175] Next, the active monitoring unit 51a performs knocking according to the parameters calculated in step ST36. The up state file 52c is updated in step ST37, and the shared memory state file 52b is updated in step ST38, and the process proceeds to the storage control process in step ST39.

As shown in FIG. 31A, in the storage control process, first, in step ST41, the memory state detection function unit 52d determines that the number of copies of the current configuration description file CFGi included in the knock-up state file 52c is It is determined whether or not the average number of replicas included in the shared memory status file 52b is exceeded. If the number of copies of its own configuration description file CFGi is equal to or greater than the average number of copies, the number of copies of its own configuration description file CFGi is large.

Therefore, the process returns to step ST31 in FIG.

[0177] On the other hand, if it is determined that the number of replicas of the configuration description file CFGi is not equal to or greater than the average number of replicas, the memory status detection function unit 52d uses the memory of the knock-up status file 52c in step ST42. Determine if the number of possible providers is 0. If it is determined that the memory available pronoida power is ^, the process proceeds to step ST51, and if it is not 0, the process proceeds to step ST43.

[0178] In step ST43, the memory state detection function unit 52d needs to add the own configuration description file CFGi in the information storage system by subtracting the number of copies of the current configuration description file CFGi from the average number of replicas. The requested number of replicas that is a certain number of replicas is calculated and the process proceeds to step ST44.

[0179] In step ST44, the empty slot inquiry function unit 52e distributes the empty slot notification request S2 to the network NW. At this time, the empty slot interrogation function unit 52e includes, in the empty slot notification request S2, its own requester Ri and the hit rate obtained by dividing the number of requested replicas by the number of available memory providers. The free slot notification request S2 is received by all provider Pis of the information storage system, and the request management function 53a of the shared memory providing function 53 has a free slot with reference to its own distributed shared memory 53b. In this case, an empty slot notification response S3 including its own provider ID is broadcast to the network NW.

[0180] In the next step ST45, it is determined whether the empty slot question response unit 52e of the requester Ri has received the empty slot notification response S3, and the empty slot question response unit 52e has failed to receive the slot notification response S3. In step ST46 of Figure 31B. It is determined that there is no empty slot in the information storage system. Also, the empty slot inquiry function unit 52e receives the slot notification response S3, and if it is larger than the number of empty slots SO of the information storage system and smaller than the requested number of replicas, the process proceeds to step ST47 in FIG. 31B. If the number of empty slots is larger than the requested number of replicas, the process proceeds to step ST48 in FIG. 31B.

[0181] When the empty slot inquiry function unit 52e determines that the number of empty slots is greater than the requested number of copies, it is notified to the empty slot acquisition function unit 52f, and in step ST49, The empty slot acquisition function unit 52f distributes the empty slot acquisition 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 broadcasted by the slot notification response S3 indicating that there is an empty slot number, its own provider ID, and the configuration description file CFG i. This list of provider IDs includes a list of free slots.

[0182] Thus, when the free slot acquisition request S4 is received by the request management function 53a of the shared memory providing function 53 of the provider Pi, the configuration description file CFGi included in the free slot acquisition request S4 is distributed to the distributed shared memory 53b. To store. In addition, Pronoida Pi's shared memory provision function 53 sends the memory state report output function unit 53c to the memory state change that occurs when the new configuration description file CFGi is stored in the distributed shared memory 53b. Memory status report to be reflected in SI.

[0183] Further, in step ST50 after determining that the number of empty slots is larger than the requested replica number in step ST48, the empty slot acquisition function unit 52f determines its own requested replica number, the list of empty slots, and its provider ID. And an empty slot acquisition request S4 including the configuration description file CFGi is broadcast to the network NW. As a result, a number of configuration description files CFGi that satisfy the required number of replicas are replicated and stored in the information storage system.

[0184] Further, in step ST51 after determining that the number of empty slots is 0 in step ST46, the empty slot inquiry function unit 52e determines that the number of replicas of the requester holding the maximum number of replicas of the shared memory state file 52b is 1 It is determined whether or not there are more. When the empty slot interrogation function unit 52e determines that the number of replicas of the requester with the maximum number of replicas is greater than one, In step ST52, the slot reassignment function unit 52h is notified of this, and the slot reassignment request unit 52f broadcasts the slot reassignment request S5 to the network NW. In this slot reassignment request S5, the configuration description file CFGi of the maximum replication count requester is duplicated, and the list specifying the provider Pi slot, the ID of the maximum replication count requester, and the maximum replication count requester Instead, it includes a new requester ID, which is its own device ID that newly uses the slot, and its own configuration description file CF Gi.

[0185] On the other hand, if the number of replicas of the requester having the maximum number of replicas is not greater than 1, in step ST53, the empty slot interrogation function unit 52e determines whether the current configuration number of the configuration description file CFGi is SO. If not, the process returns to step ST41, and if the copy description power SO of its configuration description file CFGi is SO, the process proceeds to step ST54.

[0186] In step ST54, the empty slot question function unit 52e notifies the copy number warning function unit 52g that the copy count of its own configuration description file CFGi is 0, and the copy number warning function unit 52g Is sent to the active monitoring unit 51a.

[0187] [Memory state optimization operation of information storage system]

In this way, the operations in the information storage system that 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 are shown in FIGS. The description will be given with reference.

For example, as shown in FIG. 32 (a), the information storage system is composed of three requester Ris and five provider Pis, and any configuration description file as shown in FIG. 32 (b). When CFGi is not 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 providing function 53 operate. That is, the memory status report output function unit 53c of the provider Pi and the requester Ri has its own device ID (Ra, Rb, Rc, PI, P2, P3, P4, P5) and the number of slots (Ra: 0, Rb: 0, Rc: 0, Pl: 4, P2: 2, P3: 5, P4: 3, P5: 8) and the number of empty slots (Ra: 0, Rb: 0, Rc: 0, Pl: 4, P2: 2, P3: 5, P4: 3, P5: 8) are delivered, and the memory status report SI is delivered. [0189] Each provider Pi and requester Ri receives the memory status report S1 from the other provider Pi and requester at the active monitoring unit 51a, and the total number of slots [a] is 22 (4 + 2 + 5 + 3 + 8), the total number of requesters [b] is 8, the total number of providers [c] is 5, the maximum number of replica holders [d] is not present, the average number of replicas [6]

, [c] — Creates a shared memory state file 52b indicating that 1) is 2 (min (22Z8, 5— 1) = 2), the current number of replicas [f], the number of requested replicas [g] ( [e] — [f]), creating backup state file 52c containing number of available providers [h].

[0190] In such a state, the memory control function 52 of the requester Ri calculates the hit rate ([g] Z [h]) and responds to the slot notification response S3 according to the broadcast of the empty slot notification request S2. Receive. With this free slot notification request S2, the requester Ri becomes a different provider! Receive slot notification response S3 from ^. Here, provider P5 has not received slot notification response S3 from any provider P even if it broadcasts empty slot notification request S2, but broadcasts empty slot notification request S2 again at the next opportunity. become.

[0191] The requester Ri that has received the slot notification response S3 broadcasts an empty slot acquisition request S4 to the provider ID included in the slot notification response S3. As a result, as shown in FIG. 34 (a), the provider P1 to P5 store the configuration description file CFGi of the other provider Pi and requester Ri, and the information storage as shown in FIG. 34 (b). This is the number of replicas in the system.

[0192] When the memory status report SI is also delivered to each provider Pi and requester R in this state, as shown in Fig. 35, the active monitoring unit 51a of each provider Pi and requester Ri performs the provider. The number of free slots in the Pi changes, and the slot allocation status, requester with maximum replica count, average replica count, current self replica count, and requested replica count are updated. At this point, requester Ri and provider Pi (Rc, P4, P5), which have a current number of replicas less than the average number of replicas, calculate the number of available memory providers and the hit rate, respectively, and free slot notification request S2 Is broadcasted, and an empty slot acquisition request S4 is broadcasted to increase the number of replicas. Here, even if requester Rc broadcasts empty slot notification request S2, slot notification from any provider! ^ Although the response S3 has not been received, the empty slot notification request S2 is broadcast again at the next opportunity.

As a result, as shown in FIG. 36 (a), the configuration description file CFGi of the other requester Ri and provider Pi is stored in the providers PI, P3, and P5. As shown, the number of replicas of configuration description file CFGi for provider P4 can be increased by one, and the number of replicas of configuration description file CFGi for provider P5 can be increased by two.

In such a state, as shown in FIG. 37, the requester Rc calculates the number of requested replicas, the number of providers that can use memory, and the hit rate, which are smaller than the number of requested replicas, and free space is available. The slot notification request S2 is broadcasted, a response of the slot notification response S3 is received, and an empty slot acquisition request S4 is broadcast. As a result, the requester Rc configuration description file CFGi is stored in the provider P5 as shown in Fig. 38 (a), and the requester Rc configuration description file CFGi is stored in the requester Rc as shown in Fig. 38 (b). You can increase the number of copies by one.

[0195] At this point, as shown in Figure 39, the number of replicas of the configuration description file CFGi of all providers Pi and requester Ri is the same as the average number of replicas, and distributed shared memory 53b in the entire information storage system is optimal. It becomes the state that became. Therefore, the number of requested replications is “0” in all pronoida Pis and requesters Ri, and neither provider Pi nor requester R is in a state in which the empty slot notification request S2 and the empty slot acquisition request S4 are not broadcast.

In this way, each provider Pi and requester Ri configuring the information storage system is provided with the distributed shared memory monitoring function 51, the storage control function 52, and the shared memory providing function 53, as shown in FIG. 30, FIG. 31A, FIG. By executing the processing shown in 31B, backup is performed with the same number of copies of the configuration description file CFGi of each provider Pi and requester Ri, and data loss of the configuration description file CFGi of all provider Pis and requester Ri is possible. Can be reduced.

Further, for example, as shown in FIG. 40 (a), the requester Rc is connected to the network NW. The provider Pi has an empty slot. As shown in FIG. 40 (b), the configuration of the requester Rc If the description file CFGi is stored in any provider Pi, in this case, the slot is reassigned in the information storage system. In this case, the copy number warning A warning message is issued from the functional unit 52g to the active monitoring unit 51a.

In this case, as shown in FIG. 41, the requester Rc broadcasts an empty slot notification request S2 by broadcasting the empty slot notification request S2 because the average number of replicas is “1”, and the slot notification response is broadcast. Even if S3 can be received, the number of providers that can use memory becomes “0”. Therefore, the requester Rc broadcasts the slot reallocation request S5 by the empty slot acquisition function unit 52f. At this time, the requester Rc, in the slot reassignment request S5, configures the provider ID (P1), the device ID (Ra) of the configuration description file CFGi stored in the provider P1, and its own device ID (Rc). Include the description file CFGi.

[0199] This slot reassignment request S5 is received by the provider P1, and the provider P1

As shown in (a), the configuration description file CFGi of the previous requester ID included in the slot reassignment request S5 is deleted, and the configuration description file CFGi of the requester Rc is stored instead. As a result, as shown in FIG. 42 (b), the number of replicas of the configuration description file CFGi of the requester Rc can be made equal to the average number of replicas of the information storage system.

[0200] Thus, according to the information storage system to which the present invention is applied, even when the memory capacity of the provider Pi connected to the network NW is different, all the provider Pis and the requester Ri have an average number of replicas. The number of copies of the configuration file CFGi can be adjusted to satisfy In addition, even if the memory capacity is small, it is not necessary for all provider Pis and requestor Ris to have a uniform backup capacity. Therefore, the distributed shared memory 53b of the entire information storage system can be used effectively, and it can withstand data loss. Can be held.

[0201] In addition, this information storage system dynamically changes the number of replicas so that all provider Pis and requester Ri satisfy the average number of replicas. However, the information storage system has other forms that dynamically change the number of replicas. Therefore, it is desirable not to reduce the number of copies of configuration description file CFGi, which are important for network NW! Therefore, all provider Pis and requesters Ri must set the importance of their own configuration description file CFGi and the configuration description file CFGi of other network devices in advance. Of course, backup may be performed so that the number of copies of the network device configuration description file CFGi is higher than the number of copies of the configuration description file CFGi, which is less important. As a result, the configuration description file CFGi important for the network NW is preferentially duplicated. It can be retained by a large number of network devices, and can be highly resistant to data loss in the configuration description file CFGi.

[0202] [Operation when provider Pi and requester Ri leave information storage system]

Next, in the information storage system described above, the operation for optimizing the distributed shared memory 53b when the network NW power is also removed from the provider Pi and the requester Ri will be described.

[0203] As shown in Fig. 43 (a), when the requester R force operator connected to the network NW is removed by the operator and the information storage system power is released, Fig. 43 (a) and Fig. 28 As shown in Fig. 5, a withdrawal trigger occurs in the shared memory providing function 53 of provider P4. This leave trigger includes the device ID to leave (leave ID).

[0204] When provider P4 detects a withdrawal trigger, provider P4 broadcasts a withdrawal request including the device ID of the requester R to leave and a withdrawal command to the network NW. Here, the provider P1 and the provider P4 store the requester R configuration description file CFGi. Therefore, provider P1 and provider P4 delete the requester R configuration description file CFGi as shown in Figure 43 (b).

[0205] In addition, the provider Pi and requester Ri to leave, broadcast to the network NW a removal request including its own device ID, and notify the provider Pi that it will leave when the worker removes it. The configuration description file C FGi may be deleted by the provider Pi.

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

[0207] In step ST62, it is determined whether or not the force at which the separation trigger is detected. When a leaving trigger is detected, the shared memory providing function 53 broadcasts a leaving request including the device ID to leave to the network NW. On the other hand, when the exit trigger is detected, the signal received from the network NW is checked in step ST64, and it is determined whether or not the exit request is received in step ST65. If no exit request is received, return to step ST61 and receive the exit request. If so, the process proceeds to step ST66.

[0208] At step ST66, the provider Pi determines whether or not the device ID configuration description file CFGi included in the withdrawal request is stored in its own distributed shared memory 53b. If the ID of the leaving provider Pi and requester Ri is not stored, the process returns to step ST61. If the ID of the leaving provider Pi and requester Ri is stored, in step ST67, the device Delete ID configuration description file CFGi and return to step ST61.

[0209] When the provider Pi and requester Ri leave the network NW in this way, a leave request including the device ID is broadcast to the network NW, and the device ID configuration description file CFGi is deleted from the provider Pi. Therefore, another configuration description file CFGi can be stored in the slot in which the deleted configuration description file CFGi is stored. Therefore, the number of copies of the configuration description file CFGi can be increased to further improve the tolerance of data loss. In addition, the distributed shared memory 53b in the information storage system can be used more effectively.

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

[0211] That is, the information storage system described above is a distributed sharing of files and data stored in devices such as the force sensor described in the system consisting only of the provider Pi, the requester R, and the device controller Di. The memory 1 may be distributed and stored.

Industrial applicability

[0212] According to the automatic identification information generation apparatus, information storage system, and information acquisition method of the information storage system according to the present invention, the characteristics of the sub-network connected to the device controller and the characteristics of the devices constituting the sub-network Since the identification information can be automatically generated using the topology information consisting of the identification information as its own identification information, it is possible to prevent mistakes in setting the identification information, shorten the setting time, and reduce the setting cost. Also, device control port It is possible to give identification information related to the role of the administrator, and to create identification information that is easy to understand for the administrator.

[0213] According to the information storage system of the present invention, the configuration description information stored in the configuration description information storage means of each device controller is multiplexed to the backup storage means of one or more other device controllers. The device controller can be set simply by downloading the multiplexed and stored configuration description information, and a manual setting method for workers and a setting method for connecting to a server are used. The device controller can be set up easily, at low cost and in a short time.

[0214] According to the information storage system of the present invention, the operation setting information to be stored in the backup storage means is dynamically changed according to the demands of other network devices. The setting information retention state can be optimized, and the tolerance to data loss in the network can be maintained, and the memory capacity of the entire system can be used effectively even if the memory capacity of the network devices constituting the system is not uniform. it can.

Claims

The scope of the claims

[1] An apparatus for automatically generating identification information of a device controller that is connected to a sub-network in which a plurality of devices are connected to a fieldbus and communicates with the device, and that identifies the characteristics of the sub-network Means,

Device identification means for identifying the characteristics of devices included in the subnetwork, and at least one of the characteristics of the subnetwork identified by the subnetwork identification means and the characteristics of the devices identified by the device identification means An identification information generating means that uses the topology information as its own identification information;

An identification information automatic generation apparatus comprising:

[2] The subnetwork identification means searches the software stack or hardware stack stored in the device controller, and determines the type or number of subnetworks as the characteristics of the subnetwork connected to the device controller. Identify at least one,

The identification information generating means uses topology information including at least one of the type and number of subnetworks identified by the subnetwork identifying means as its identification information.

The identification information automatic generation device according to claim 1, wherein:

[3] The device identification means identifies at least one of the type or number of devices as a feature of the device included in the subnetwork identified by the subnetwork identification means,

2. The identification information automatic generation apparatus according to claim 1, wherein the identification information generation unit uses, as its own identification information, topology information including at least one of the type and number of devices identified by the device identification unit. .

[4] The device controller is further connected to a data server storing configuration description information for the device controller to communicate with the device, and further includes a transmission unit that transmits the identification information generated by the identification information generation unit,

When the data server receives the identification information generated by the identification information generation means and transmitted from the transmission means, the configuration description information corresponding to the received identification information To reply

The identification information automatic generation device according to any one of claims 1 to 3, wherein the identification information automatic generation device according to any one of claims 1 to 3 is characterized.

[5] Each device controller

Storage means for storing configuration description information for other device controllers to communicate with the device;

An information transmission means for returning configuration description information corresponding to the identification information when the identification information transmitted from another device controller is received;

The identification information automatic generation device according to any one of claims 1 to 3, further comprising:

[6] The identification information generating means transmits its own identification information to another device controller or data server, and when it receives a response that its own identification information is the same as the other identification information. Unlike the self-identification information that was created, the self-identification information created from the new topology information must be generated.

6. The identification information automatic generation device according to claim 4 or 5, wherein:

[7] Sub-networks consisting of multiple device groups are connected, processing to notify the event generated by each device to the outside, and notification of external requests to each device to operate the device Multiple device controllers that perform at least one of

Each device controller

Configuration description information storage means for storing configuration description information for communicating with devices of the subnetwork connected to the network;

Referring to the configuration description information, device control means for communicating with the devices of the sub-network;

A communication means connected to another device controller via a communication line and communicating with the other device controller;

Stores the configuration description information transmitted from another device controller card and received by the communication means, and functions as a backup memory for the configuration description information of the other device controller. Effective backup storage means,

A storage for storing the configuration description information stored in the configuration description information storage means in the backup storage means of another device controller, and storing the configuration description information of other device controllers in the backup storage means of itself. Control means; subnetwork identification means for identifying characteristics of the subnetwork;

Device identification means for identifying the characteristics of devices included in the subnetwork, and at least one of the characteristics of the subnetwork identified by the subnetwork identification means and the characteristics of the devices identified by the device identification means An identification information generating means for using the topology information as its own identification information,

The storage control means transmits the identification information generated by the identification information generation means to another device controller by the communication means to notify its own identification information, and to the backup storage means of the other device controller. Acquiring stored self configuration description information and storing it in the configuration description information storage means

An information storage system.

[8] When the device controller is newly connected to a communication line, the device controller identifies the characteristics of the subnetwork by the subnet identification means, and the sub-network identification means identified by the subnetwork identification means by the device identification means. Communicate using a method that conforms to the characteristics of the network, and identify the characteristics of the devices included in the subnetwork.

The storage control means uses, as its own identification information, topology information comprising the characteristics of the subnetwork identified by the subnetwork identification means by the identification information generating means and the characteristics of the devices identified by the device identification means. To acquire its own configuration description information transmitted from another device controller and store it in the configuration description information storage means.

The information storage system according to claim 7.

[9] The configuration description information stored in the configuration description information storage unit of each device controller is stored in multiple in the knock-up storage unit of one or more other device controllers. Information storage system.

[10] The configuration of the subnetwork connected to the device controller has changed The configuration description information stored in the configuration description information storage unit is updated according to the changed configuration, and a request for updating the configuration description information is transmitted to another device controller. Information storage system described in 1.

[11] When the device controller is newly connected to a communication line and given its own identifier, it sends a transmission request for requesting transmission of its own configuration description information including the own identifier to another device controller. 10. The information storage system according to claim 9, wherein the configuration description information transmitted to the device controller and stored in the other knock-up storage means is acquired.

[12] When the device controller receives a plurality of pieces of configuration description information in response to transmission of a transmission request for requesting transmission of its own configuration description information, the device controller selects the newest configuration description information, The information storage system according to claim 9, wherein the information is stored in the configuration description information storage means.

[13] When the device controller receives a transmission request for requesting transmission of configuration description information by other device controller capabilities, the device controller does not have the processing capability to return the configuration description information at the time of receiving the transmission request. 10. The information storage system according to claim 9, wherein transmission of configuration description information is stopped in this case.

[14] Some network devices of the plurality of network devices including the device controller store configuration description information transmitted from other network devices, and store the configuration description information of the other network devices. The backup storage means functioning as a backup memory,

The storage control means of the network device having the backup storage means dynamically stores the configuration description information to be stored in the backup storage means in accordance with the request for the other network equipment power received via the communication means. The information storage system according to claim 7, wherein the information storage system is changed.

[15] The storage control means causes the backup storage means to store the configuration description information of each network device so as to average the number of copies of the configuration description information of the plurality of network devices. Item 15. The information storage system according to item 14.

[16] The storage control means is connected via its own configuration description information and the communication line. The importance of the configuration description information of other network devices is preset, and the network device is more important than the number of copies of the configuration description information of the plurality of network devices that is less important. 15. The information storage system according to claim 14, wherein the configuration description information is stored in the backup storage means so as to increase the number of copies of the configuration description information.

[17] The network device having the backup storage means has a memory status report output means for notifying other network devices of the status of its backup storage means, and the storage control means outputs the memory status report 17. The means according to any one of claims 14 to 16, wherein the configuration description information is stored in the network device having the backup storage means with reference to the notified state of the backup storage means. An information storage system according to claim 1.

[18] The storage control means includes:

Inquires of the network device having the backup storage means whether or not its own configuration description information can be stored, and another network that has responded to the usage status information indicating that its configuration description information can be stored Sends its own configuration description information to the device, stores its own configuration description information in the other network device,

When the network device having the backup storage means inquires from another network device whether or not the configuration description information of the other network device can be stored, the memory state of its own knock-up storage means To reply

The information storage system according to any one of claims 14 to 16, characterized by:

[19] The storage control means acquires the memory state of the backup storage means from the network device having the backup storage means, and determines that its configuration description information cannot be stored. Any one of claims 14 to 17, wherein the number of copies of the description information is determined so that the network device is determined and the configuration description information of the network device is stored instead of the configuration description information of the network device. An information storage system according to claim 1.

[20] A network device having the backup storage means is newly added to the communication line. When the participating network device is connected and the configuration information of the new network device is inquired about whether it can be stored, the memory information of its own backup storage means is returned. Item 17. The information storage system according to any one of Items 14 to 16.

[21] When the network device having the backup storage means receives a request to discard the configuration description information in order to leave the communication line, the backup storage means power is also deleted from the configuration description information of the disconnected network device. The information storage system according to any one of claims 14 to 16, wherein:

[22] Subnetwork consisting of multiple device groups is connected, processing to notify the event that occurred on each device to the outside, and notification of external request to each device to operate the device An information storage method for an information storage system comprising a plurality of device controllers that perform at least one of processing to be performed and multiple storages of configuration description information for operating a device,

Each device controller

Identifying the characteristics of the subnetwork connected to it;

Identifying the characteristics of the devices included in the sub-network, and generating topology information having at least one of the characteristics of the identified sub-network and the characteristics of the identified devices as self-identification information A step of distributing the identification information to another device controller via a communication line; and acquiring and storing configuration description information for operating the device by operating itself stored in the other device controller Steps to do

The information acquisition method of the information storage system characterized by performing.

23. The information acquisition method for an information storage system according to claim 22, wherein the step of identifying the characteristics of the subnetwork starts when a new connection is made to a communication line.