JP2010146050A - Distributed system and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To surely notify a function block in the periphery of a composite function block of the generation of abnormality while maintaining the secrecy of the internal structure of the composite function block. <P>SOLUTION: The distributed system includes: a composite function block management part 25 for managing the state of a function block 31; a configuring function block list 61 in which the configuring block of the composite function block is shown; and a disclosed cooperative interface list 71 in which the disclosed cooperative interface of the composite function block is shown. The composite function block management part 25 specifies, when the abnormality of the function block 31 is detected in equipment 10m in which the composite function block management part 25 itself is arranged, a composite program component whose abnormality has been generated on the basis of the configuring function block list 61, and makes an operation request for abnormality generation to the disclosed interface of the composite function block whose abnormality has been generated on the basis of the disclosed cooperative interface list 71. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a distributed system including a distributed environment in which program parts are arranged in a plurality of devices, and a construction support apparatus for supporting the construction of the distributed environment, and a program for adding an extended function to the distributed system About.

  There is a distributed system in which a plurality of program parts are centrally operated by arranging a plurality of program parts in a controller or the like of a plurality of apparatuses connected via a network and operating the program parts in cooperation with each other. Such a system, for example, controls the operation of various drive devices (for example, a heater drive switch, a valve drive device for adjusting a flow rate, a robot arm drive device, etc.) in a factory production facility, and various measuring devices (for example, It is used to obtain operation information from a thermometer, hygrometer, pressure gauge, etc.).

  In the process of building such a distributed system, for example, a software developer creates and provides highly reusable program parts as function blocks, and the system builder combines the provided function blocks according to the system. In addition, the overall design of the distributed system is made by setting the operation parameters of each functional block.

  Other software developers create and provide composite function blocks (composite program parts) that combine existing function blocks to realize complex functions, while system builders use these composite function blocks together. The entire design of the distributed system may be performed (for example, Patent Document 1).

It is assumed that the composite functional block is created by a software developer and provided to a system builder. In this case, in order to protect the know-how of the software developer, the internal structure of the composite function block is concealed from the system builder. It is only an interface for linking with a functional block.
JP 2006-350580 A

  Next, the problem will be described with reference to some specific configuration examples of the distributed system. FIG. 2 shows an example of an application configuration that constitutes a part of the distributed system. This application configuration is to acquire field data from a measuring instrument and store it in a database. The field data acquisition function block 31G and a composite function block 301A for converting the field data into an appropriate data format by arithmetic processing and outputting them. And functional blocks 31A and 31B for writing the transferred data to the database.

  The composite function block 301A includes an arithmetic function block 31F for arithmetically processing field data, a buffer function block 31E for buffering the arithmetically processed data, and periodically taking out the buffered data, converting it into a predetermined format, and outputting it. A data conversion function block 31C for converting the buffer value into data update event information and outputting it when the buffered value is updated. Only the data reception interface 32f of the calculation function block 31F and the data transmission interfaces 33c and 33d of the data conversion function blocks 31C and 31D are disclosed to the system builder in order to cooperate with the external function blocks 31A, 31B and 31G. ing.

  Since the composite function block needs to hide the internal structure as described above, the following problems occur.

  For example, when an unexpected abnormality occurs in the internal functional blocks that make up a composite functional block, even though it is a composite functional block, the individual internal functional blocks actually only behave according to their specifications. Depending on the combination of functional blocks, abnormal operation may not be transmitted around the abnormal functional block, and normal operation may continue in the surrounding functional blocks. In this case, since the information on the occurrence of the abnormality is not transmitted to the external function block that operates in cooperation with the composite function block, the problem arises that the abnormal operation continues throughout the distributed system without being distinguished from the normal operation. .

  For example, when the arithmetic function block 31F abnormally stops in the application configuration of FIG. 2, the value of the buffer function block 31E is not updated, but the two data conversion function blocks 31C and 31D are not affected by the occurrence of the abnormality. One functional block 31C continues to transmit the same unupdated data, and the other functional block 31D does not transmit a data update event. Such an operation is continued without being distinguished from a normal operation.

  In addition, in order to solve the above problems, when an abnormality occurs in the internal function blocks that make up the composite function block, the error contents are propagated through the internal function blocks and transmitted to the external function block. It is possible to add functions. For example, the error contents generated in the arithmetic function block 31F in FIG. 2 are propagated to the function blocks 31E to 31D and recognized by the external function blocks 31A and 31B.

  However, in such a method, when the error content is specific to the functional block, the internal configuration of the composite functional block is estimated by the system builder or the like based on the error content propagated to the external functional block. The problem of end up arises. Such a situation contradicts the fact that the internal structure of the composite functional block is concealed in order to protect the know-how of the software developer.

  In addition, in order to solve the problems as described above, when an abnormality occurs in the internal functional blocks constituting the composite functional block, life cycle control is performed on each functional block constituting the composite functional block, It is also possible to add a function such as stopping each function block. Specifically, when it is detected that an abnormality has occurred in the arithmetic function block 31F in FIG. 2, the other function blocks 31E to 31C are stopped.

  However, with such a method, for example, when a function block around the composite function block has a processing function for occurrence of an abnormality, there is a problem that this processing function is not exhibited. For example, when the data writing function block 31A in FIG. 2 has a rollback function for deleting a series of received data from the database when a data reception error occurs, the function block of the composite function block 301A is used in the life cycle control. Since 31E is normally stopped, the external data writing function block 31A cannot detect a data reception error and cannot shift to the rollback process.

  Also, in the above paragraph, we presented a method to add two types of extended functions (function to propagate the occurrence of abnormality and function to perform life cycle control when an abnormality occurs) to the composite function block. However, there is a problem that it is difficult to add such an extended function.

  This is because, in the controller of the device where the functional block is arranged, which functional block constitutes the composite functional block, and which functional block is the other individual functional block is not normally distinguishable. . Therefore, in order to add the extended function as described above, the creator of the composite function block has only to add a program configuration that realizes the extended function in the composite function block, and such a composite is not considered. It is difficult to add such an extended function to the function block from the outside.

  In addition, when the above-mentioned extended functions are provided in the basic software (also called framework) that performs process management and memory management for each functional block, the functional blocks that make up the composite functional block on the basic software And other individual functional blocks cannot be distinguished from each other, so that an extended function is uniformly added to both of these functional blocks. Therefore, it is difficult to add a specific function only to the composite function block.

  In a distributed system in which composite function blocks and individual function blocks are distributed and executed, when an unexpected abnormality occurs in any of the function blocks constituting the composite function block, the present invention This is to ensure that the occurrence of an abnormality can be reliably transmitted to the functional blocks around the composite functional block while maintaining the confidentiality of the internal structure.

  In order to achieve the above object, the invention according to claim 1 is a distributed environment in which each program component constituting a composite program component and each program component are distributed and arranged in a plurality of devices, and the distributed environment In a distributed system including a construction support apparatus that performs construction support, a composite part management unit that performs state management and operation control of the composite program part disposed in the device, and the composite program part disposed in the device A configuration information list indicating information of the configured program parts, and a list creation means for creating the configuration information list from composite program definition information provided in the construction support device, the composite part management unit, An error was detected in the program component in the device where the device is located If any of the composite program parts is included in the composite program part based on the configuration information list, the composite program part belongs to the composite program part and is included in the composite program part. It is characterized in that an operation for generating an abnormality is performed by specifying an open interface that exchanges data with program parts other than the parts.

  According to a second aspect of the present invention, in the distributed system according to the first aspect, the configuration information list includes a composite component list in which information for identifying each program component constituting the composite program component is registered, And an open interface list in which information for identifying each open interface belonging to a composite program part is registered, and the list creation means includes the composite part list and the open interface list for each composite program part. It is the structure which makes and.

  According to a third aspect of the present invention, in the distributed system according to the second aspect, the composite part management unit searches for a composite program part including a program part detected as abnormal based on the composite part list, and the composite part A specific function for specifying a program part; and an operation request function for performing an operation for generating an abnormality by designating the open interface belonging to the composite program part specified by the specific function based on the open interface list It is characterized by having.

  According to a fourth aspect of the present invention, in the distributed system according to the first aspect, the configuration information list includes arrangement information indicating in which device each of the open interfaces belonging to the composite program part is arranged, The composite component management unit communicates with another composite component management unit arranged in another device via a communication network, and an open interface belonging to a composite program component determined to be abnormal based on the arrangement information Using the communication function based on the arrangement information when it is determined by the determination function that it is arranged in another device. Operation request transmission function for transmitting an operation request to the composite component management unit of the other device, and When receiving the operation request from the JIT component management unit, it is characterized by comprising an operation request proxy function of the open interface of the composite program part in accordance with the operation request to perform the operation of the abnormality occurrence.

  According to a fifth aspect of the present invention, there is provided a function for causing a computer that supports construction of a distributed environment to read composite program definition information in which composite program component configuration information is represented, and the composite program component from the composite program definition information. And a function for creating a configuration information list that includes identification information of each program part that constitutes the system, and identification information of each open interface that belongs to the composite program part and exchanges data with other program parts It is.

  The invention according to claim 6 is a program executed by a computer for controlling a plurality of devices that realizes a distributed environment by arranging program components, and the program computer in the device has an abnormality in the program components in the device. Is detected, the composite program part including the program part in which the abnormality has occurred is searched from the composite program part configuration information list stored in the storage unit of the control computer, and the composite program part is identified. A specific function to be performed, and a composite program part configuration information list stored in the storage unit of the control computer, the program parts and data belonging to the composite program part specified by the specific function and other than the composite program part Interacting It specifies the release interface, a program for realizing the operation request function to perform the operation for abnormal to the open interface.

  According to the present invention, the list creation means creates the composite function block configuration information list while maintaining the concealment of the internal structure of the composite function block. The composite function block in which an abnormality has occurred is identified using the configuration information list, and an operation for generating an abnormality is performed on the public interface. Therefore, the occurrence of an abnormality can be reliably transmitted to the function blocks around the composite function block while the concealment of the internal structure of the composite function block is maintained.

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

[First Embodiment]
FIG. 3 is a configuration diagram illustrating the entire distributed system according to the embodiment of this invention.

  In the distributed system of this embodiment, a plurality of devices 10a to 10z (for example, production facility devices) are connected to the communication network 90, and further, the function block 31 and the composite function block 301 are arranged in the plurality of devices 10a to 10z. It will be. Although omitted in FIG. 1, as shown in the devices 10 a and 10 b, any one of a plurality of types of functional blocks 31 and a plurality of types of composite functional blocks 301 is arranged in all the devices 10 a to 10 z. It is what has been. The plurality of functional blocks 31 and the composite functional block 301 operate in cooperation with each other, whereby the operation of the plurality of devices 10a to 10z is comprehensively controlled or the information is collectively acquired from the plurality of devices 10a to 10z. Can be done.

  Furthermore, in the embodiment of the present invention, the system construction computer 100 is provided that supplies the configuration information list of the composite function block 301 to the devices 10a to 10z via the communication server 80 and the communication network 90 when the distributed system is constructed. .

  The functional block 31 and the composite functional block 301 are software executed by the CPU (central processing unit) of the device, and are unitized so that specific functions are realized. Each functional block 31 or each composite functional block 301 operates in cooperation with another functional block 31 or composite functional block 301 while exchanging data with each other. Data exchange is performed via the cooperative interfaces 32 and 33 included in each functional block 31.

  The cooperation interfaces 32 and 33 are software interfaces. In the same device, the cooperation interfaces 32 and 33 transmit and receive data via a memory, and the plurality of devices 10a to 10z have a cooperation interface. 32 and 33 transmit and receive data via the communication network 90.

  The cooperation interfaces 32 and 33 hold, for example, a connection refusal, a service provision refusal, and a service provable state in advance, and are in a service provable state during normal operation. Here, connection rejection refers to a state in which no connection is established, and service provision rejection refers to a state in which a connection is established, but denies data exchange at the application level, and service provision is possible. It is in a state where it is possible to exchange.

  The composite function block 301 is created by a software vendor or the like by combining the existing function blocks 31 in order to realize useful functions, and is provided to the system builder of the distributed system. Each internal functional block 31 constituting the composite functional block 301 performs a behavior in accordance with the existing specifications of each functional block 31, and does not perform an operation specific to the composite functional block 301. The internal structure of the composite function block 301 is hidden from the system builder in order to protect the know-how of the software vendor. The system builder can be set by the system builder with the overall functions of the composite function block 301. Only the specifications and the like of the public operation interfaces (open interfaces) 32 and 33 that are opened for exchanging data with the external operation block and the external function block are disclosed.

  Although not shown, each device 10a to 10z has a CPU (Central Processing Unit) that executes a program, a storage device that stores program modules and control data, a memory that provides a memory space for the CPU, and the like. A controller (control computer) 20 is provided. Then, when the CPU executes a predetermined program module, a plurality of functional blocks 31 are generated as instances in the memory space, and these functional blocks 31 operate by software.

  The system construction computer 100 includes a CPU that executes a program, a storage device that stores application programs and control data, a memory that provides a working memory space for the CPU, a display device that displays and outputs information to an operator, An input device for inputting an operation command is provided, and a software function for supporting the construction of a distributed system is realized by the above application program.

  The distributed system construction support function 110 mainly includes a distributed system design function 111 that performs overall design of the distributed system, and program modules for realizing predetermined function blocks 31 and composite function blocks 301 in the respective devices 10a to 10z. A module transfer function 112 for transferring setting data and a composite function block information creation function 113 for creating a configuration information list of each composite function block 301 and transferring it to the devices 10a to 10z are included.

  The system construction computer 100 includes definition information indicating the operation content and specification information of each function block 31, composite function indicating the internal structure of the composite function block 301, operation parameters of the internal function block 31, and the like. Block definition information 121 (FIG. 4) is read in advance, and the definition information is used to support the construction of a distributed system.

  In the distributed system design function 111, the operator determines the hardware configuration and network configuration of the plurality of devices 10a to 10z constituting the distributed system, and the function block 31 and the composite function block 301 arranged in each device 10a to 10z. By selecting, determining the connection mode of each functional block 31 or each composite functional block 301, or setting the operation parameters of each functional block 31 or each composite functional block 301, the entire distributed system is configured on the computer. Design support.

  In this distributed system design function 111, the operator can handle the composite function block 301 in the same manner as one function block 31, connect it to other function blocks 31, and determine the arrangement thereof. In the system construction computer 100, one composite function block 301 is recognized as a plurality of function blocks 31 constituting the composite function block 301 based on pre-read composite function block definition information 121 (FIG. 4). Processing is in progress.

  The module transfer function 112 transfers program modules and setting data for realizing the function blocks 31 and composite function blocks 301 that are arranged and designed to the devices 10a to 10z after the design of the distributed system is completed. It is. Each of the devices 10a to 10z executes the transferred program module, so that the functional block 31 and the composite functional block 301 that are arranged and operated operate on the controller 20 of the device.

  FIG. 4 is a functional block diagram showing a configuration related to the composite functional block information creation function in the system construction computer. FIG. 5 is a chart showing an example of composite function block definition information.

  The composite function block information creation function 113 reads the composite function block definition information 121 indicating the internal structure of the composite function block 301 and creates a configuration information list of the composite function block 301. The configuration information list includes a configuration function block list 61 in which configuration function block IDs for identifying each function block 31 constituting the composite function block 301 are registered, and belongs to the composite function block 301 and is open to the outside. It is composed of a public cooperation interface list 71 in which public cooperation interface IDs that enable designation of the cooperation interfaces 32 and 33 are registered. The specific contents of each of the lists 61 and 71 are shown in Tables 1 and 2 below.

  The composite function block definition information 121 is for the software developer who created the composite function block 301 to clarify the internal structure of the composite function block 301 to the distributed system construction support function 110 of the system construction computer 100. For example, it is provided in a format in which the contents are not read out by an operator, and is read into the computer 100 for system construction.

  As shown in FIG. 5, the composite function block definition information 121 indicates information on the constituent function blocks 31 indicating the function blocks 31 configuring the composite function block 301 and the cooperation interfaces 32 and 33 provided in the function blocks 31. Information, public setting information indicating whether the linkage interfaces 32 and 33 are open to the outside, internal linkage destination information indicating a linkage destination between internal function blocks, and the like are described.

  Then, the constituent function block list 61 and the public cooperation interface list 71 created by the composite function block information creation function 113 are transferred to the devices 10a to 10z where the corresponding composite function block 301 is arranged, and the devices 10a to 10a are arranged. It is stored in a 10z storage device or memory. For example, the module transfer function 112 described above transfers the program module and setting data together.

  Note that the configuration function block ID and the public cooperation interface ID registered in the configuration information list (61, 71) are the function blocks 31 on the system construction computer 100 when the layout design of the function block 31 is completed. Or identification information given to each of the linkage interfaces 32 and 33. When the function blocks 31 are actually instantiated on the controllers 20 of the devices 10a to 10z, the identification information is associated with the instances of the function blocks 31 and the cooperation interfaces 32 and 33. With these identification information, it is possible to identify each functional block 31 and each instance of each linkage interface 32, 33 on the controller 20 of the devices 10a to 10z.

  In addition, since the above-described component function block list 61 and the public cooperation interface list 71 are generated inside the system construction computer 100 and transferred to the devices 10a to 10z, they are read by the operator of the system construction computer 100. These lists 61 and 71 do not cause the confidentiality of the internal structure of the composite function block 301 to be countered.

  An application program that realizes the distributed system design function 111, the module transfer function 112, and the composite function block information creation function 113 described above can be read by the system construction computer 100, for example, a portable storage medium such as an optical disk, a flash It can be stored in a non-volatile memory such as a memory, a ROM (Read Only Memory), or the like. In addition, a form in which such a program is downloaded to the system construction computer 100 via a communication line using a carrier wave as a medium may be applied.

  FIG. 1 is a functional block diagram showing a functional configuration generated on the controller of one device constituting the distributed system of the first embodiment. Next, the functional configuration of one device 10m will be described, but each of the devices 10a to 10z has the same functional configuration.

  As shown in FIG. 1, on the controller 20 of the device 10 m, individual functional blocks 31 (including functional blocks that are components of the composite functional block 301) arranged on the device 10 m, and each functional block 31. The function block state acquisition unit 26 that acquires the state parameter of the function block and the cooperation interface operation unit 27 that can operate the cooperation interfaces 32 and 33 of each function block 31 from the outside of the function block 31 are constructed as software executed by the CPU. Has been.

  Further, on the controller 20 of the device 10m in which the composite function block 301 is arranged, as shown in FIG. 1, for each function block 31 constituting the composite function block 301, state monitoring and operation control at the time of occurrence of an abnormality are performed. A composite function block management unit 25 is constructed as software executed by the CPU. In addition, the component function block list 61 and the public cooperation interface list 71 transferred from the system construction computer 100 are made readable by the composite function block management unit 25.

  Although illustration is omitted, basic software (also referred to as a framework) for performing process management and memory management of each functional block 31 is operating on the controller 20 of the device. A plurality of functional blocks can be operated in parallel by the CPU. Since the basic software performs process management of each functional block 31, it is possible to acquire the operating state of each functional block 31 via this basic software, and the cooperation interface 32, Since 33 is a configuration for exchanging data via an interface function provided by the basic software, it is also possible to directly operate the cooperation interfaces 32 and 33 of each functional block 31 from the basic software side.

  The functional block status acquisition unit 26 acquires status parameters of each functional block 31 via the basic software. When there is a change in the value of the state parameter of the function block 31, a function block state change notification code to be described later is created, and this notification code is sent to the composite function block management unit 25 as a state change event. Yes. The value of the state parameter that can be acquired by the functional block state acquisition unit 26 includes values indicating the normal operation, state transition, abnormal stop, abnormal end, abnormal load, etc. of the functional block 31.

  The functional block state acquisition unit 26 operates by receiving a state management start request from the management computer of the distributed system via the communication network 90 when starting the operation of the distributed system, or It is configured to operate simultaneously with the start of the 10 m basic software.

  The cooperation interface operation unit 27 causes the cooperation interfaces 32 and 33 designated from the outside of the function block 31 to perform a specific operation via the basic software. Specifically, in response to a cooperation operation request to be described later from the composite function block management unit 25, the designated public cooperation interfaces 32 and 33 are caused to execute the operation contents when an abnormality occurs.

  One composite function block management unit 25 is provided as one of the basic software service applications in the controller 20 of the device 10m in which the composite function block 301 is arranged. The operation of the composite function block management unit 25 will be described in detail later.

  The service application program that realizes the composite function block management unit 25 is stored in a storage medium readable by the controller 20 of the device 10m, for example, and is incorporated so as to be executable by the CPU of the device 10m. As the storage medium, for example, a portable storage medium such as an optical disk, a nonvolatile memory such as a flash memory, a ROM (Read Only Memory), or the like can be applied. Alternatively, the application program may be transferred via a communication line using a carrier wave as a medium and incorporated in the device 10m.

  The component function block list 61 and the public cooperation interface list 71 are created by the composite function block information creation function 113 of the system construction computer 100 as described above, and transferred to the device 10m where the composite function block 301 is arranged. It is. The component function block list 61 and the public cooperation interface list 71 are generated one by one for one composite function block 301, and a plurality of composite function blocks 301 are arranged in one device 10m. Corresponding to the plurality of composite function blocks 301, a plurality of component function block lists 61 and a plurality of public cooperation interface lists 71 are stored.

  As shown in Table 1, the configuration function block list 61 includes a plurality of configuration function block IDs (identification information) that can identify all the function blocks 31 constituting one composite function block 301. It is.

  For example, when the functional block configuration shown in FIG. 2 is arranged in one device 10m, as shown in Table 1, one constituent functional block list 61 is generated in correspondence with the composite functional block 301A. Registered are the calculation function block 31F, the data buffer function block 31E, and the identification information “fb001” to “fb004” of the two data conversion function blocks 31C and 31D constituting the composite function block 301A. These pieces of identification information “fb001” to “fb004” are information that can identify actual functional blocks that are instantiated on the controller 20 of the device 10m.

  As shown in Table 2, the public cooperation interface list 71 includes all of the cooperation interfaces 32 open to an external function block among the plurality of cooperation interfaces 32 and 33 belonging to one composite function block 301. , 33 can be specified, and a public cooperation interface ID (identification information) is registered.

  For example, when the functional block configuration of FIG. 2 is arranged in a device, as shown in Table 2, one public cooperative interface list 71 corresponding to the composite functional block 301A is generated, and this list 71 includes Are registered three pieces of identification information “ch001” to “ch003” that can respectively designate a plurality of public cooperation interfaces 33c, 33d, and 32f that belong to the composite function block 301A and are open to the outside. The identification information “ch001” to “ch003” is information that can specify the actual linkage interfaces 32 and 33 that are instantiated on the device 10m.

  Next, the operation at the time of operation of the distributed system will be described.

  When all the functional blocks 31 are activated in the distributed system, each functional block 31 operates according to individual specifications and operational settings, and a plurality of functional blocks 31 connected to each other via the linkage interfaces 32 and 33. Data is exchanged with each other. As a result, the plurality of functional blocks 31 cooperate to operate the distributed system in an integrated manner.

  In addition, on each of the devices 10a to 10z, in parallel with the operation of the function block 31, the composite function block management unit 25, the function block state acquisition unit 26, and the cooperation interface operation unit 27 also operate. The functional block state acquisition unit 26 receives the above-described state management start instruction, or automatically starts operation when the devices 10a to 10z are activated, whereby each functional block 31 arranged in the devices 10a to 10z. Start monitoring the status of

  FIG. 6 is a flowchart showing the procedure of the state management process of the composite function block 301 executed by the function block state acquisition unit 26 and the composite function block management unit 25. Next, an operation example for one device 10m will be described, but the same operation is performed for the other devices 10a to 10z.

  When the operation starts, the functional block state acquisition unit 26 acquires a state parameter from each functional block 31 arranged in the device 10m at a predetermined cycle (step S1), and changes to the state value every time the state parameter is acquired. It is determined whether or not there is any (step S2). If there is no change, the process waits until the next cycle as it is, and repeats acquisition of periodic state parameters.

  On the other hand, if it is determined in step S2 that the state parameter value has changed, the functional block state acquisition unit 26 creates, for example, a function block state change notification code as shown in Table 3, This notification is sent to the composite function block management unit 25 (step S3). This function block state change notification is, for example, data to which the function block ID corresponding to the changed function block 31 and the state parameter value after the change are added.

  The composite function block management unit 25 always waits for a state change notification from the function block state acquisition unit 26. When receiving the state change notification, first, the composite function block management unit 25 extracts the function block ID included in the state change notification. It is searched whether the function block ID is included in one or a plurality of component function block lists 61 (specific function: step S4). Here, if this function block ID is not found in the list, a state change has occurred in the function blocks 31 other than the composite function block 301. Therefore, the composite function block management unit 25 performs processing related to this state change notification. End and wait until the next state change notification.

  On the other hand, when the above function block ID is found in the constituent function block list 61, it can be specified that a state change has occurred inside the composite function block 301 arranged in the device 10m, so that composite function block management is possible. The unit 25 proceeds to the next step S5, and confirms the state of the functional block 31 from the value of the state parameter included in this state change notification. That is, it is determined whether or not an abnormality has occurred (step S5). For example, if the value of the state parameter indicates a value indicating normal operation or state transition, it is determined that the value is normal, while the value indicating the abnormal stop or abnormal end of the function block 31 or the processing of the function block 31 If the load is a value indicating an abnormal value, it is determined that an abnormality has occurred.

  The cause of the occurrence of such an abnormality within the composite function block 301 is, for example, when an abnormality occurs in the function block 31 that constitutes the composite function block 301, between the function blocks 31 that constitute the composite function block 301. When an abnormality occurs in the coordinated operation, the functional block 31 constituting the composite function block 301 or the coordinated operation between these functional blocks 31 cannot operate normally due to a hardware failure in the device 10m. And so on.

  If it is determined that an abnormality has occurred, the composite function block management unit 25 next reads the public cooperation interface list 71 associated with the component function block list 61 found in step S4, and all the functions described therein are read. The public cooperation interface ID is designated as the identification information of the operation target (step S6). That is, as a result, all the linked interfaces 32 and 33 that belong to the composite function block 301 in which an abnormality has occurred and are open to the outside are designated as operation targets.

  Subsequently, for example, the composite function block management unit 25 creates a code for a cooperation operation request as shown in Table 4 and sends this code to the cooperation interface operation unit 27 (step S7). The operation request function is configured by the processing in steps S6 and S7. This cooperation operation request is, for example, a code to which the cooperation interface ID specified in step S6 and an operation parameter indicating the operation content are added. In this embodiment, the operation content of the cooperation operation request applies cooperation interruption as an operation for generating an abnormality.

  When the above-described cooperation operation request is sent to the cooperation interface operation unit 27, the cooperation interface operation unit 27 extracts the operation target cooperation interface ID from the code of the cooperation operation request, and the cooperation interfaces 32 and 33 specified by the identification information. A request for an operation for shutting off the link is made to.

  When an operation request for cooperative blocking is made to the public cooperative interfaces 32 and 33, the public cooperative interfaces 32 and 33 perform the cooperative blocking operation and enter the service provision refusal state described above. As a result, information on the occurrence of abnormality is transmitted to the external function block 31 connected to the composite function block 301. For example, if a cooperation blocking operation is performed during cooperation between the composite function block 301 and the external function block 31, an error message indicating disconnection is sent from the cooperation interface to the external function block 31. Further, when a new cooperation request is generated from the external function block 31 to the composite function block 301, the cooperation is rejected at the application level, and an error message indicating the cooperation rejection from the cooperation interface is displayed in the external function block 31. Will be sent to.

  Since the external function block 31 can recognize that an abnormality has occurred in the composite function block 301 based on such an error message, by setting the error message to be subjected to predetermined error processing, It is possible to avoid a problem that a useless operation or an incorrect operation is continued indefinitely because the occurrence of an abnormality cannot be recognized.

  For example, when an abnormality occurs in the arithmetic function block 31F in the application configuration example of FIG. 2, the composite function block management unit 25 sets the cooperation interfaces 33c, 33d, and 32f that are open to the outside as cooperation blocking. As a result, an error message indicating disconnection or cooperation refusal is sent to the external function blocks 31A, 31B, and 31G, so that the on-site data acquisition function block 31G stops data transmission to the composite function block 301A. The data writing function block 31A can stop writing data to the database. In addition, the data writing function block 31B can cancel an event waiting state and prevent unintentional data storage and useless operations.

  As described above, according to the distributed system of this embodiment, in the distributed system in which the composite function block 301 and the individual function blocks 31 are distributed and operated in cooperation with each other in the plurality of devices 10a to 10z, When an abnormality occurs inside the block 301, the occurrence of the abnormality is communicated to the other function block 31 that performs the cooperative operation with the composite function block 301 while maintaining the confidentiality of the internal structure of the composite function block 301. Can do.

  In addition, according to the distributed system of this embodiment, the composite function block management unit 25 is provided on the controller 20 of the device, so that the occurrence of abnormality of the composite function block 301 is monitored from the outside of the composite function block 301 and Since the operation control is performed, it is possible to cope with the occurrence of an abnormality as described above without adding a special function to the composite function block 301 itself.

  Also, the composite function block management unit 25 identifies the composite function block 301 in which an abnormality has occurred and performs the operation when the abnormality occurs based on the constituent function block list 61 and the public cooperation interface list 71. , 33, the composite function block management unit 25 can be made common to all the devices 10a to 10z. Then, by making the configuration function block list 61 and the public cooperation interface list 71 the contents in accordance with the arrangement of the composite function block 301, the state management of the composite function block 301 corresponding to each device 10a to 10z can be performed. it can.

  In addition, this invention is not restricted to said embodiment, A various deformation | transformation is possible. For example, as the configuration information list of the composite function block 301, one example of generating the configuration function block list 61 and the public cooperation interface list 71 for each composite function block has been shown. If all the public cooperation interface IDs of the composite function block 301 including the function block 31 can be specified, it is not necessary to generate the lists 61 and 71 separately for each composite function block 301. The information list (61, 71) can be changed as appropriate, for example, by including other data items.

  In the above embodiment, an example is shown in which such functions are realized via basic software in order to acquire the state parameters of each functional block 31 and to operate the linkage interfaces 32 and 33 from the outside. However, the present invention is not particularly limited to such a method, and various methods can be applied as long as similar functions are realized.

  In addition, the configuration information list (61, 71) of the composite function block 301 is generated by the system construction computer 100 and transferred to the devices 10a to 10z. For example, the basic software of each device 10a to 10z is shown. Such a list creation function may be provided. For example, when an instance of the composite function block 301 is generated on the controller 20 of the devices 10a to 10z, the basic software of the devices 10a to 10z is configured to generate the configuration function block list 61 and the public cooperation interface list 71. .

  Moreover, although the cooperation interruption | blocking of the public cooperation interfaces 32 and 33 was illustrated as operation | movement at the time of abnormality generation of the composite function block 301, as long as it is operation | movement which can transmit abnormality generation to the exterior, you may apply another operation | movement.

  In addition, the details shown in the embodiment, such as the processing contents of the distributed system construction support function 110 and the control procedure of the state management processing by the composite function block management unit 25, can be changed as appropriate without departing from the spirit of the invention.

[Second Embodiment]
In FIG. 7, the block diagram showing the function structure constructed | assembled by the apparatus of 2nd Embodiment is shown.

  The distributed system of the second embodiment shows a configuration that can cope with a case where one composite functional block 301 is arranged across a plurality of devices 10a to 10z. The distributed system of the second embodiment includes the same configuration as that of the first embodiment, and the description of the same configuration as that of the first embodiment is omitted.

  In the distributed system of the second embodiment, since one composite function block 301 may be arranged across a plurality of devices 10a to 10z, the component function block list 61B created by the composite function block information creation function 113 is sometimes obtained. And an extension of the public cooperation interface list 71B is applied.

  In the configuration function block list 61B, as shown in Table 5, in addition to the configuration function block ID, the network address (for example, IP address) of the device in which each function block 31 is arranged is added to the list item. Thereby, it becomes possible to specify in which device 10a-10z each functional block 31 is arranged.

  As shown in Table 6, in the public cooperation interface list 71B, in addition to each public cooperation interface ID, identification information (affiliated function block ID) of the function block 31 to which each public cooperation interface 32, 33 belongs is added to the list item. ing. Thereby, it is possible to specify which function block 31 each public cooperation interface 32, 33 belongs to, and each function block 31 is arranged in any device 10a to 10z from the network address of the constituent function block list 61B. Therefore, it is possible to specify in which device 10a to 10z each public cooperation interface 32, 33 is arranged from these pieces of information.

  The constituent function block list 61B and the public cooperation interface list 71B are duplicated by the number of devices in which the corresponding composite function block 301 is distributed and these plural devices (for example, two devices 10x and 10y). Are respectively transferred and stored.

  Also in the second embodiment, as shown in FIG. 7, the controller 20 of each device 10 x, 10 y belongs to the functional block 31 constituting the composite functional block 301, individual functional blocks, and each functional block 31. The linkage interfaces 32 and 33 are generated by being instantiated. Further, in the devices 10x and 10y in which the composite function block 301 is arranged, the configuration function block list 61B and the public cooperation interface list 71B corresponding to the composite function block 301 are stored, and further, the composite function block management unit 25B, The function block state acquisition unit 26 and the cooperation interface operation unit 27 are operated.

  In the composite function block management unit 25B of the second embodiment, in addition to the configuration of the composite function block management unit 25 of the first embodiment, the composite function block management unit 25B of the other devices 10a to 10z via the communication network 90 is included. And an operation request transmission / reception function (communication function) for transmitting and receiving cooperative operation requests.

  In the distributed system of the second embodiment, an abnormality occurs between the plurality of devices 10x and 10y in which the composite function block 301 is distributed and the hardware configuration of the devices 10x and 10y and the controller 20 itself. It is equipped with a high-level error check function that checks whether there is any problem.

  As a specific example of the upper level abnormality confirmation function, a configuration in which confirmation messages for regularly confirming the operation state of the devices are exchanged between a plurality of devices 10x and 10y in which one composite function block 301 is distributed and arranged. Is applicable. For example, the composite function block management unit 25B of the device 10x acquires the network address of the other device 10y in which the same composite function block 301 is distributed from the component function block list 61B, and periodically receives the device 10y. Exchange confirmation messages to confirm the operational status. When the basic software itself stops abnormally due to an abnormality in the hardware of the device 10y or an abnormality in the controller 20, the confirmation message is not responded, thereby determining that an abnormality has occurred in the device 10y to be confirmed. can do.

  Next, the operation of the state management process of the composite function block 301 according to the second embodiment will be described.

  FIG. 8 shows a flowchart of the state management process of the composite function block 301 executed by the composite function block management unit 25B and the function block state acquisition unit 26 of the second embodiment.

  In the state management process of the second embodiment, as shown in FIG. 8, the occurrence of an abnormality in the composite function block 301 is monitored by two processing flows. The monitoring process of occurrence of abnormality in steps S1 to S5 is monitoring by the functional block state acquisition unit 26 as in the first embodiment. In the second embodiment, furthermore, by exchanging confirmation messages by the above-described upper level abnormality confirmation function, it is monitored whether an abnormality has occurred in another device 10x in which a part of the composite function block 301 is arranged. Yes.

  When the abnormality of the other device 10x is detected by exchanging the confirmation message, the composite function block management unit 25B includes the configuration function including the network address of the device 10x detected as abnormal from all the configuration function block lists 61B. The block list 61B is searched (step S11), and it is determined that the composite function block 301 corresponding to the component function block list 61B is abnormal (step S12).

  Similarly to the first embodiment, when an abnormality occurs in the composite function block 301 arranged in its own device and the abnormality is detected by the function block state acquisition unit 26, the component function block list 61B is searched. (Steps S1 to S5), the composite function block 301 in which an abnormality has occurred is specified.

  When the composite function block 301 in which an abnormality has occurred is identified, the composite function block management unit 25B then reads the public cooperation interface list 71B associated with the constituent function block list 61B of the composite function block 301, and The cooperation interfaces 32 and 33 to be operated are specified (step S13).

  Next, the composite function block management unit 25B creates a code for a cooperative operation request for the cooperative interfaces 32 and 33 to be operated (step S14). In the second embodiment, since the cooperation interfaces 32 and 33 to be operated may be arranged in other devices 10x, the code of the cooperation operation request is as shown in Table 7 as the operation target cooperation interface ID and In addition to the code of the operation content, the network address of the devices 10x and 10y where the corresponding link interfaces 32 and 33 are arranged is added. A code for such a cooperation operation request is created for all the public cooperation interfaces 32 and 33 belonging to the target composite function block 301.

  When such a code for a cooperative operation request is created, it is determined for each cooperative operation request whether the network address is local (own device) or remote (other device) (discriminating function: step S15). If it is local, this cooperation operation request is sent to the cooperation interface operation unit 27 of its own device 10y (step S16). Thereby, the public cooperation interfaces 32 and 33 of the own device are operated to cut off the cooperation.

  On the other hand, if it is remote, the composite function block management unit 25B sends a cooperation operation request to the composite function block management unit 25B of the other device 10x indicated by the network address of the cooperation operation request via the communication network 90. Transmit (operation request transmission function: step S17).

  The composite function block management unit 25B of each device 10x, 10y is in a state of always waiting to receive a cooperative operation request by interrupt processing or the like, and receives a cooperative operation request when it is sent (step S21). Then, when a cooperative operation request is received from another device 10y, it is sent to the cooperative interface operation unit 27 of its own device 10x (operation request proxy function: step S22). As a result, the public collaboration interfaces 32 and 33 of the device 10x are blocked from cooperation.

  As described above, according to the distributed system of the second embodiment, even when one composite functional block 301 is distributed and arranged in a plurality of devices 10x and 10y, any one of the composite functional blocks 301 is configured. When an abnormality occurs in the function block 31, all of the public cooperation interfaces 32 and 33 belonging to the composite function block 301 are blocked, and the occurrence of the abnormality can be transmitted around the composite function block 301. .

  In addition, even if a higher level error that causes the basic software to stop due to a hardware error or a controller 20 error occurs in other devices 10x and 10y in which the composite function block 301 is distributed, the confirmation This abnormality can be detected by checking the message. Then, it is determined that the composite function block 301 partially arranged in the devices 10x and 10y cannot operate normally, and the public cooperation interfaces 32 and 33 belonging to the composite function block 301 are set to be blocked. Thus, it is possible to convey the occurrence of an abnormality around the composite function block 301. As a result, it is possible to avoid a problem that a useless operation or an incorrect operation is continued without being distinguished from a normal operation.

  In the second embodiment, the network address is added to the configuration function block list 61B and the configuration function block ID is added to the public cooperation interface list 71B. However, the network address is added to the public cooperation interface list 71B. You may do it. In the second embodiment, since the information that identifies the location address of each functional block 31 is added to the configuration function block list 61B, the configuration function block list 61B and the public cooperation interface list 71B are particularly supported. It is not necessary to store only in the devices 10x and 10y in which the composite function block 301 is arranged. For example, all the component function block lists 61B and the public cooperation interface list 71B may be stored in all the devices 10a to 10z. good.

  In addition, the details shown in the embodiment, such as the contents of the cooperation operation request and the processing procedure of the state management process by the composite function block, can be appropriately changed without departing from the spirit of the invention.

It is the functional block diagram which showed the function structure implement | achieved on the controller of an apparatus. It is a functional block diagram which shows an example of a part of application structure arrange | positioned at an apparatus. It is a block diagram which shows the whole distributed system of embodiment of this invention. It is a functional block diagram showing the structure regarding a composite functional block information creation function. It is a chart showing an example of composite functional block definition information. It is the flowchart which showed the process sequence of the management process of a composite function block. It is a functional block diagram which shows the function structure implement | achieved on the controller of the apparatus of 2nd Embodiment. It is a flowchart which shows the process sequence of the management process of the composite function block in 2nd Embodiment.

Explanation of symbols

10a-10z Equipment 25 Composite Function Block Management Unit (Composite Parts Management Unit)
26 Function Block Status Acquisition Unit 27 Cooperation Interface Operation Unit 31 Function Block (Program Parts)
31A, 31B Data writing function block 31C Data conversion function block 31D Event type data conversion function block 31E Data buffer function block 31F Arithmetic function block 31G Field data acquisition function block 32, 33 Cooperation interface 33c, 33d, 33f Public cooperation interface (open) interface)
301, 301A Composite function block (composite program part)
61 Configuration function block list (composite parts list, configuration information list)
71 Public linkage interface list (open interface list, configuration information list)
DESCRIPTION OF SYMBOLS 90 Communication network 100 System construction computer 110 Distributed system construction support function 111 Distributed system design function 112 Module transfer function 113 Composite function block information creation function 115 Composite function block information creation unit 121 Composite function block definition information 25B Composite function block management unit 61B Configuration function block list 71B Public linkage interface list

Claims (6)

In a distributed system including a distributed environment in which each program part constituting a composite program part and individual program parts are distributed and arranged in a plurality of devices, and a construction support device that supports construction of the distributed environment,
A composite part management unit that performs state management and operation control of the composite program part arranged in the device;
A configuration information list in which information of program parts that are arranged in the device and constitute the composite program part is shown;
List creation means for creating the configuration information list from composite program definition information provided in the construction support device;
With
The composite part management unit
When an abnormality is detected in a program part in the device in which it is located, it is determined based on the configuration information list whether the program part in which the abnormality is detected is included in any composite program part. A distributed system that specifies an open interface that belongs to the composite program part and exchanges data with a program part other than the composite program part, and performs an operation for generating an abnormality. . The configuration information list is
A composite part list in which information for identifying each program part constituting the composite program part is registered;
An open interface list in which information for identifying each open interface belonging to the composite program part is registered;
Including
2. The distributed system according to claim 1, wherein the list creation means is configured to create the composite part list and the open interface list for each composite program part. The composite part management unit
Based on the composite part list, search for a composite program part including a program part detected as abnormal, and a specific function for specifying the composite program part,
Based on the open interface list, an operation request function for specifying the open interface belonging to the composite program part specified by the specific function and performing an operation for generating an abnormality,
The distributed system according to claim 2, further comprising: The configuration information list is
Including arrangement information indicating in which device each of the open interfaces belonging to the composite program part is arranged;
The composite part management unit
A communication function for communicating with another composite component management unit arranged in another device via a communication network;
A determination function for determining whether any of the open interfaces belonging to the composite program part determined to be abnormal based on the arrangement information is arranged in another device,
An operation request transmission function for transmitting an operation request to the composite part management unit of the other device using the communication function based on the arrangement information when it is determined by the determination function that the device is disposed in another device; ,
When the operation request is received from the composite component management unit of another device, an operation request proxy function that causes the release interface of the composite program component corresponding to the operation request to perform an operation for occurrence of an abnormality,
The distributed system according to claim 1, further comprising: A computer that supports the construction of a distributed environment
A function for reading composite program definition information in which composite program part configuration information is represented;
Configuration including identification information of each program part constituting the composite program part and identification information of each open interface belonging to the composite program part and exchanging data with other program parts from the composite program definition information The ability to create information lists;
A program that realizes A program that is executed by a computer for controlling a plurality of devices that realize a distributed environment by arranging program parts,
In the computer for controlling the device,
When an abnormality is detected in the program part in the device, the composite program part including the program part in which the abnormality has occurred is retrieved from the composite program part configuration information list stored in the storage unit of the control computer. A specific function for identifying the composite program part,
From the composite program part configuration information list stored in the storage unit of the control computer, data is exchanged with a program part belonging to the composite program part specified by the specific function and other than the composite program part. An operation request function that designates an open interface and causes the open interface to perform an action for occurrence of an abnormality,
A program that realizes

Images