JP5846084B2 - Message sequence generation method and message sequence generation apparatus - Google Patents

Description

  The present invention relates to a message sequence generation method and a message sequence generation apparatus for generating a message sequence diagram describing a specification of a communication protocol.

  In a monitoring control system or the like, communication protocol specifications are often described in message sequence diagrams. In addition to normal processing, a method for generating an executable program by describing processing when an error occurs in a message sequence diagram has been proposed.

  In general, in the communication protocol, there are more processes when an error occurs than when it is normal. Therefore, a method for efficiently creating a message sequence diagram when an error occurs is required.

  Patent Document 1 is characterized in that a message sequence to which processing at the time of error occurrence is added is generated from a normal sequence representing a sequence at the time of normality and a rule that describes a condition in which an error can occur and its processing. A message sequence generator has been proposed.

  Patent Document 2 proposes a software development support apparatus that generates an overall specification by adding and synthesizing an abnormal specification to a normal specification given as an input.

JP-A-6-152701 JP 2006-85668 A

  However, in the method disclosed in Patent Document 1, when there are many types of messages and the number of states, the number of rules to be described increases, and a message sequence diagram describing an abnormal specification cannot be generated efficiently. There was a problem.

  Further, the method disclosed in Patent Document 2 does not disclose means for adding / combining an abnormal specification to a message sequence diagram representing a normal specification. For this reason, there is a problem that a message sequence diagram to which an abnormal specification is added cannot be generated.

  The present invention has been made to solve the above problems, and an object of the present invention is to provide a message sequence generation method and a message sequence generation apparatus capable of efficiently generating a message sequence with error processing added. And

  A message sequence generation method according to the present invention involves (a) a step of preparing message sequence information indicating normal processing of a communication protocol using a message sequence diagram for data processing, and (b) mode switching of an instance. A step of preparing an event-causal relationship model in which events and events requiring error processing are described together with a causal relationship for data processing, (c) device / configuration control information including mode information of the instance, and device / configuration Storing a current value of control information in a database; (d) setting an action to be performed when the event occurs for a specific event in the event causality model; and (e) message sequence information A step of associating each element with each event and generating element / event correspondence information; and (f) element A step of storing the event correspondence information in the storage device; and (g) acquiring each action corresponding to each element and the action set for the event caused by the event from the element / event correspondence information, and processing the error. And (h) generating message sequence information in the current mode state of the system targeted by the message sequence information, each step being executed by computer data processing. And

  In addition, the message sequence generation device according to the present invention has a causal relationship with respect to message sequence information indicating normal processing of a communication protocol using a message sequence diagram, an event accompanied by mode switching of an instance, and an event that requires error processing. For a specific event in the event-causal relationship model, a database that stores the event-causal relationship model described together with the device / configuration control information including the mode information of the instance, and the current value of the device / configuration control information. A setting means for setting an action to be performed when an error occurs, each element of message sequence information and each event are associated with each other, correspondence information generating means for generating element / event correspondence information, and element / event correspondence information are stored Each event and event corresponding to each element from the storage means and the element / event correspondence information. The action set for each event caused by the event is acquired, and the message sequence information in the current mode state of the system targeted by the message sequence information is generated by adding to each element as error processing. And an information generating means.

  According to the message sequence generation method and the message sequence generation device according to the present invention, a system targeted by message sequence information in error processing including a case where system switching is involved while considering a causal relationship between events by an event causal relationship model. Since error processing in the current mode state can be added, an error processing addition message sequence diagram can be efficiently generated.

It is a block diagram which shows the structure of the message sequence production | generation apparatus 41 by Embodiment 1 of this invention. It is a hardware block diagram by Embodiment 1 of this invention. It is a figure which shows the example of the message sequence information 31 by Embodiment 1 of this invention. It is a figure which shows the example of the event causal relationship model 33 by Embodiment 1 of this invention. It is a figure which shows the example of apparatus and structure control information DB200 by Embodiment 1 of this invention. It is a figure which shows the example of the apparatus and structure control information present value information 201 by Embodiment 1 of this invention. It is a flowchart which shows operation | movement of the element and event corresponding | compatible information generation means 35 by Embodiment 1 of this invention. It is a flowchart which shows operation | movement of the element and event corresponding | compatible information generation means 35 by Embodiment 1 of this invention. It is a flowchart which shows operation | movement of the element and event corresponding | compatible information generation means 35 by Embodiment 1 of this invention. It is a flowchart which shows operation | movement of the element and event corresponding | compatible information generation means 35 by Embodiment 1 of this invention. It is a flowchart which shows operation | movement of the element and event corresponding | compatible information generation means 35 by Embodiment 1 of this invention. It is a flowchart which shows operation | movement of the error process addition means 37 by Embodiment 1 of this invention. It is a flowchart which shows operation | movement of the error process addition means 37 by Embodiment 1 of this invention. It is a figure which shows the example of the information of the error processing by Embodiment 1 of this invention. It is a flowchart which shows operation | movement of the error process addition means 37 by Embodiment 1 of this invention. It is a flowchart which shows operation | movement of the error process addition means 37 by Embodiment 1 of this invention. It is a flowchart which shows operation | movement of the error process addition means 37 by Embodiment 1 of this invention. It is a flowchart which shows operation | movement of the error process addition means 37 by Embodiment 1 of this invention. It is a flowchart which shows operation | movement of the error process addition means 37 by Embodiment 1 of this invention. It is a figure which shows the example of input of Embodiment 1 of this invention. It is a figure which shows the example of the action setting process of the element and event corresponding | compatible information generation means 35 by Embodiment 1 of this invention. It is a figure which shows the example of the element and event correlation of the element and event corresponding information generation means 35 by Embodiment 1 of this invention. It is an example of the error process addition message sequence information 40 by Embodiment 1 of this invention. It is an example of the error process addition message sequence information 40 by Embodiment 1 of this invention. It is a figure which shows the example of the element definition information by Embodiment 1 of this invention. It is a figure which shows the example of the event definition information by Embodiment 1 of this invention. It is a figure which shows the example of the element and event corresponding | compatible definition information by Embodiment 1 of this invention. It is a figure which shows the example of the action / phenomenon correspondence definition information by Embodiment 1 of this invention. It is a block diagram which shows the structure of the message sequence production | generation apparatus 44 by Embodiment 2 of this invention. It is an example of the instance abstraction event causal relationship model by Embodiment 2 of this invention. It is a flowchart which shows operation | movement of the instance abstraction event causal relationship model realization means by Embodiment 2 of this invention. It is an example of the event causal relationship model by Embodiment 2 of this invention.

<A. Embodiment 1>
<A-1. Configuration>
FIG. 1 is a block diagram showing a configuration of a message sequence generation device 41 according to Embodiment 1 of the present invention.

  As shown in FIG. 1, the message sequence generating device 41 is an element / event correspondence information generating means for acquiring each element described in the message sequence information 31 and each event described in the event causal relation model 33. 35.

  Here, the message sequence information 31 indicates the communication protocol specifications using a message sequence diagram. The event-causal relationship model 33 describes a plurality of events including events that require error processing together with their causal relationships. The device / configuration control information DB (database) 200 describes device information, mode state combination information, and mode state transition information included in the target system of the message sequence information 31. The device / configuration control information current value information 201 describes information on the current value of an item that is changed during operation of the target system among items included in the device / configuration control information DB 200.

  The element / phenomenon correspondence information generating unit 35 receives an action from the action input unit 34 and an event from the element / phenomenon input unit 36.

  The message sequence generation device 41 is generated from a certain event among the element / event correspondence information storage unit 38 to which the element / event correspondence information is input from the element / event correspondence information generation unit 35 and the event causal relationship model 33. Error processing deriving means 39 for deriving error processing, device / configuration control information current value acquiring means 202 for acquiring the current value of the device / configuration control information from the device / configuration control information current value information 201, and element / event correspondence information And error processing adding means 37 for adding the error processing information to the message sequence information 31. The message sequence information 31 to which error processing has been added becomes error processing addition message sequence information 40.

  Further, the message sequence generation device 41 includes correspondence result output means 32 that outputs element / event correspondence information.

  Here, the elements in the message sequence information 31 indicate all operations, states, their results, and processes indicated in the message sequence information, such as message transmission / reception and internal actions. It is also assumed that an element is between two consecutive elements. For example, when there is message sequence information in which an instance sends a message and the status is “message sending”, “message sending” and “status (message sending)” are also elements, and “message sending” element It is assumed that the element during “state (message transmission)” is also an element. This means that although an instance has sent a message, the result before entering the “state (message send)” can be treated as an element.

  The action input from the action input unit 34 is a predetermined process executed when each event in the event causal relationship model 33 occurs.

  FIG. 2 shows a hardware configuration when the message sequence generation device 41 is actually operated. In FIG. 2, the PC 1 is provided as the message sequence generation device 41 in FIG. Note that the message sequence generation device 41 may include not only a PC but also a general computer, for example.

  The PC 1 includes a CPU 2 that performs computation, a storage device 3 that can store information, an input device 4 that provides input to the PC such as a mouse and a keyboard, and an output device that can perform output such as a display. 5 is included.

  The element / event correspondence information generating means 35, the element / event correspondence information storage means 38, the error processing derivation means 39, the error processing addition means 37, and the device / configuration control information current value acquisition means 202 in FIG. And is executed on the CPU 2.

  Further, the action input unit 34, the element / event input unit 36, and the error processing addition unit 37 obtain input from the user by the input device 4. The correspondence result output means 32 outputs the element / event correspondence information by the output device 5. Further, the error processing additional message sequence information 40 is output by the output device 5.

  FIG. 3 is a diagram illustrating an example of the message sequence information 31 of FIG. In the message sequence information 31, the time axis is represented vertically, and time flows from top to bottom.

  In the message sequence information, the system, apparatus, and functions in the system that are the main body of message transmission / reception are called instances. An instance includes an instance start symbol 61, an instance name 62, a lifeline 63, and an instance end symbol 64.

  The name of the instance is indicated by the instance name 62. The start position and end position of the instance are indicated by an instance start symbol 61 and an instance end symbol 64, respectively.

  The instance start symbol 61 and the instance end symbol 64 are connected by a lifeline 63 to indicate the lifetime of the instance. Message exchange between instances is indicated by message symbol 65. The message has a defined direction and can identify the source and destination of the message. The message type and name are indicated by a message name 66.

  The timer is indicated by a timer symbol 67, and the name and period are indicated by timer information 68. Timer reset is indicated by timer reset symbol 300, and timer firing is indicated by timer firing symbol 301. Stopping the timer is indicated by a timer stop symbol 302. The state of the instance is indicated by a status symbol 69, and the internal action of the instance that does not involve sending and receiving messages is indicated by an internal action symbol 70.

  The positional relationship between the instance name 62, the message name 66, and the timer information 68 may be in any place as long as the relationship between the instance start symbol 61, the message symbol 65, and the timer symbol can be recognized. Further, the object end symbol 64 may be omitted.

  The message sequence information 31 in the present invention is not limited to that shown in FIG. 3, but is a message sequence diagram defined by UML (Unified Modeling Language), ITU-T (International Telecommunication Union Telecommunication Standardization Sector) Recommendation Z . Message Sequence Chart (MSC) by 120 may be used.

  FIG. 4 illustrates the event-causal relationship model 33 of FIG. 1 using an FT (Fault Tree) diagram as an example.

  The event causal relationship model 33 is a representation of a causal relationship between a top event 81 representing an abnormal event such as error processing and an event that generates them using a logical symbol, for example, on a tree structure. Note that the method of indicating the causal relationship between events is not limited to a method using logical symbols.

  The top event 81 is arranged at the top of the figure. Factors related to the occurrence of the top event 81 are arranged on the tree structure using the logical product 82 and the logical sum 83. Events connected by logical symbols are referred to as intermediate events 84, and events that cannot be further resolved are referred to as basic events 85.

  5A to 5C are examples of the device / configuration control information DB 200. FIG. The device / configuration control information DB 200 includes device information, mode state combination information, and mode state transition information.

  The device information shown in FIG. 5A stores what devices are included in the target system, what name, class, and IP address are specified, and the priority at the time of system switching. In the class, an instance name in the message sequence information is specified.

  The system switching priority is used when there are a plurality of standby systems with respect to the regular system in a multiple system of triple system or more. When a failure occurs in the active system and transitions to the standby system, and one standby system transitions to the regular system, which system is transitioned from the plurality of standby systems to the regular system is determined using the priority. In this example, it is assumed that a priority with a small number is preferentially transitioned to the regular system.

  The mode state combination information shown in FIG. 5B specifies combinations of operation modes of the respective systems when the target system has a redundant configuration. In this example, it is indicated that both the server 1 and the server 2 are in the normal mode or the standby mode, and the combination of the maintenance mode and the standby mode is not possible. Further, it is shown that a combination of the normal mode and the standby mode or the normal mode and the maintenance mode is possible.

  The mode state transition information illustrated in FIG. 5C is information indicating state transitions between the normal mode, the standby mode, and the maintenance mode.

  FIG. 6 is an example of the device / configuration control information current value information 201 of FIG. The device / configuration control information current value information 201 includes items that are changed during execution of the target system among the information included in the device / configuration control information DB 200. In this example, the IP address and the operation mode state are included in the device / configuration control information current value information as items to be changed during execution of the target system. The current IP address of the server 1 is 192.168.0.3, indicating that the operation mode state is normal. Further, the current IP address of the server 2 is 192.168.0.4, and the operation mode state is standby. It is assumed that the device / configuration control information current value information 200 is updated each time the state of the device being executed is changed.

<A-2. Operation>
FIG. 7 is a flowchart showing the operation of the element / event correspondence information generating means 35 of FIG. In step ST201, the element / event correspondence information generation unit 35 acquires the message sequence information 31 and the event causal relationship model 33.

  Next, in step ST202, action setting processing for setting an action (processing) at the time of occurrence of the event is performed on the event in the event causal relationship model 33.

  Next, in step ST203, element / event correspondence information generation processing for associating the elements in the message sequence information 31 with the events in the event causal relationship model 33 is performed. When the process is finished, the operation is finished.

<A-2-1. Action settings>
FIG. 8 is a flowchart showing the operation (action setting process for each event) of step ST202 of the element / phenomenon correspondence information generating means 35 of FIG.

  In step ST210, the element / phenomenon correspondence information generating unit 35 sequentially receives events from the element / phenomenon input unit 36. Here, an event is an event in the event causal relationship model 33, an element that specifies an element in the message sequence information 31, and an end of the specification.

  In the event, the user can arbitrarily associate the event and the element. However, the correspondence with “events” that can occur in any “element” in the message sequence diagram regardless of the communication protocol, such as hardware failure, is “element definition information”, “event definition information”, “element / event” It is also possible to automatically associate all “elements” in the message sequence diagram using “correspondence definition information”.

  In addition, “events” that can occur when receiving any message, such as parity test violations, can be received using “element definition information”, “event definition information”, and “element / event correspondence definition information”. It is also possible to automatically associate all “elements”.

  Furthermore, it is possible to automatically associate “elements” for receiving messages of a specific group, “internal actions” of a specific group, and “events”. It is also possible to associate elements with events using past history.

  Here, “element definition information” is information indicating a group to which each element belongs. For example, the element “selection message reception” is included in the group “message” and is included in the “selection control message” (see FIG. 25).

  “Event definition information” is information indicating a group to which each event belongs. For example, the event “LAN both system abnormality” is included in the groups “failure” and “communication disconnection”, and the event “parity test violation” is included in the group “message fraud” (see FIG. 26).

  In the “element / event correspondence definition information”, “event” and a plurality of corresponding elements can be designated (see FIG. 27).

  For example, the event “abnormality of both LAN systems” can occur at any time regardless of the communication protocol, and is therefore associated with all elements in the message sequence information. Therefore, “All (element)” is designated as the corresponding element of “event definition information”. This means that the event “abnormality of both LAN systems” is associated with all elements. For the corresponding element, specify a specific element name or a group of request definition information.

  For example, the event “parity test violation” can occur when all messages are received, so the corresponding elements are all “message received” elements. Here, the logical expression is obtained by connecting corresponding elements such as S1∩S2 and the like with logical symbols, and fine specification is possible.

  The element / event correspondence information generation unit 35 acquires an event and its corresponding element (1 to n) from the event definition information. Subsequently, the elements corresponding to the corresponding elements 1 to n are acquired from the element definition information. Among the acquired elements, an element that matches the one evaluated by the logical expression is searched from the message sequence information, and the element and the event can be associated with each other.

  Then, in step ST211, an event determination is performed. If it is an end event, the operation is terminated, and if it is not an end event, the process proceeds to step ST212.

  In step ST212, the event in the event causal relationship model 33 designated by the event received in step ST210 is stored, and the process proceeds to step ST213.

  In step ST213, the action set in the event stored in step ST212 input by the action input means 34 is stored, and the process proceeds to step ST214.

  In step ST214, the action stored in step ST213 is set in the event stored in step ST212, and the process proceeds to step ST210. The events are sequentially received, and actions are set for the events designated by the respective events. When setting of the actions is completed for all the events (that is, when the end event is reached), the operation is ended.

  Note that an event and an action can be arbitrarily associated by the user.

  Here, in order to efficiently associate one “action” with a plurality of “events”, the above “event definition information” and “action / phenomenon correspondence definition information” can be used.

  Here, the “action / phenomenon correspondence definition information” is information indicating which “phenomenon” each “action” is associated with. As shown in FIG. 28, a group of “events” associated with each “event” is described. As with “element / event correspondence definition information”, logical expressions can also be used.

  The element / phenomenon correspondence information generating unit 35 obtains each “phenomenon” information from “phenomenon definition information”, and obtains correspondence information between actions and phenomena from “action / phenomenon correspondence definition information”.

  Subsequently, an “event” corresponding to each “action” is searched from the event causal relationship model 33 and automatically associated. When multiple actions are set for one event, the action set by the user can be prioritized. Further, when there are a plurality of automatically set actions, the user can be notified. The action set earlier (or later) may be given priority.

<A-2-2. Generating element / event correspondence information>
FIG. 9 is a flowchart showing the operation (element / event correspondence information generation processing) of step ST203 of the element / event correspondence information generation means 35 of FIG.

  In step ST220, the element / event correspondence information generating unit 35 acquires the message sequence information 31 and the event causal relationship model 33, and proceeds to step ST221.

  In step ST221, events are sequentially acquired from the element / phenomenon input means 36, and the process proceeds to step ST222. The event acquired here is acquired independently of the event received in step ST210.

  In step ST222, an event is determined. If the event is for an element in the message sequence information 31, the process proceeds to step ST223. If the event is for an event in the event causality model 33, the process proceeds to step ST224. finish.

  In step ST223, element designation processing is performed. In step ST224, an event designation process is performed. Details will be described later.

  FIG. 10 is a flowchart showing the operation (element specifying process) of step ST223 of the element / event correspondence information generating means 35 of FIG.

  In step ST260, the element / phenomenon correspondence information generating unit 35 stores the element designated as the event in step ST221, and proceeds to step ST261.

  In step ST261, an event is acquired from the element / phenomenon input means 36, and the process proceeds to step ST262. The event acquired here is the same event as the event acquired in step ST221.

  In step ST262, an event is determined. If the event is for an element of the message sequence information 31, the process proceeds to step ST265, and if the event is for an event of the event causality model 33, the process proceeds to step ST263.

  In step ST263, the event specified in the event acquired in step ST261 is associated with the element stored in step ST260, and the process proceeds to step ST264.

  In step ST264, the element / event correspondence information associated in step ST263 is stored in the element / event correspondence information storage means 38 (storage device 3), and the operation is terminated.

  In step ST265, the element stored in step ST260 is discarded, the element specified in step ST261 is stored, and the process proceeds again to step ST261.

  FIG. 11 is a flowchart showing the operation (event designation process) of step ST224 of the element / event correspondence information generation means 35 of FIG.

  In step ST280, the element / phenomenon correspondence information generating unit 35 stores the phenomenon designated as the event in step ST221, and proceeds to step ST281.

  In step ST281, an event is acquired from the element / phenomenon input means 36, and the process proceeds to step ST282. The event acquired here is the same event as the event acquired in step ST221.

  In step ST282, event determination is performed, and in the case of an event for an event in the event causality model 33, the process proceeds to step ST285, and in the case of an event for an element of the message sequence information 31, the process proceeds to step ST283.

  In step ST283, the element specified in the event acquired in step ST281 and the event stored in step ST280 are associated and stored, and the process proceeds to step ST284.

  In step ST284, the element / event correspondence information associated in step ST283 is stored in the element / event correspondence information storage unit 38 (storage device 3), and the operation is terminated.

  In step ST285, the event stored in step ST280 is discarded, the event specified in step ST281 is stored, and the process proceeds to step ST281 again.

<A-2-3. Add error handling>
FIG. 12 is a flowchart showing the operation of the error processing adding means 37 of FIG.

  The error process addition means 37 acquires the message sequence information 31 in step ST300, and proceeds to step ST301.

  Next, in step ST301, one element / event correspondence information is acquired from the element / event correspondence information storage unit 38, that is, information of an event corresponding to one element is obtained, and the process proceeds to step ST302.

  In step ST302, it is determined whether or not the element / event correspondence information corresponding to one element has been acquired. If it can be acquired, the process proceeds to step ST303, and if it cannot be acquired, the operation ends.

  In step ST303, the state of each instance related to one element acquired in step ST301 is acquired from the message sequence information 31 acquired in step ST300, and the process proceeds to step ST304.

  In step ST304, the state of each instance acquired in step ST303 and the element / event correspondence information of one element acquired in step ST301 are passed to the error processing deriving means 39.

  On the other hand, in step ST305, error processing information corresponding to one element acquired in step ST301 is acquired from the error processing deriving means 39, and the process proceeds to step ST306.

  In step ST306, an error processing additional message sequence information generation process is performed, and the process proceeds to step ST301. Details will be described later.

  FIG. 13 is a flowchart showing the operation (error processing addition message sequence information generation processing) of step ST306 of the error processing addition means 37 in FIG.

  In step ST400, the error processing adding unit 37 sets the message sequence information 31 until one element acquired in step ST301 is generated as work target message sequence information, and proceeds to step ST401.

  In step ST401, information on occurrence of a corresponding event of one element acquired in step ST301 is added to the work target message sequence information, and the process proceeds to step ST402.

  In step ST402, error processing information resulting from the event corresponding to one element acquired in step ST301 is extracted from the error processing deriving unit 39, and the process proceeds to step ST403.

  In step ST403, it is determined whether or not error processing information has been extracted. If it has been extracted, the process proceeds to step ST404. If it cannot be extracted, the process proceeds to step ST409.

  In step ST404, it is determined whether the configuration control condition is set in the error processing information acquired in step ST402. When the configuration control condition is set, the process proceeds to step ST405. If not set, the process proceeds to step ST406.

  In step ST405, the device / configuration control information is added to the work target message sequence information acquired in step ST400, and the process proceeds to step ST406. Details will be described later.

  In step ST406, the execution condition and configuration control condition of the action included in the error processing information acquired in step ST402 are checked, and the process proceeds to step ST407.

  In step ST407, it is determined whether the action execution condition and the configuration control condition acquired in step ST406 are satisfied. If the execution condition is satisfied, the process proceeds to step ST408. If not satisfied, the process proceeds to step ST409.

  In step ST408, the action of ST402 is added to the work target message sequence information, and the process proceeds to step ST402.

  In step ST409, the work target message sequence information to which the corresponding error processing is added is output to the output device 5 as the error processing addition message sequence information 40.

  FIG. 14 shows an example of error processing information. The error processing information is numbered in the order of execution, and the event name corresponding to the error processing, the action set for the event, the execution condition, and the condition of the configuration control when the event occurs are associated. ing.

  In this example, the event name “system switching” and the action “action 1” are associated, the execution condition in this case is not set, the configuration control condition is “usual mode is regular” and “partner mode is spare”. It shows that there is.

  FIG. 15 is a flowchart showing the operation (device / configuration control information addition process) of step ST405 of the error process addition means 37 in FIG.

  In step ST420, whether to generate only message sequence information in the current state of the target system or to output all combinations is designated from the input device. Then, it progresses to step ST421.

  In step ST421, event determination is performed. If an instruction to output only message sequence information in the current state is given, the process proceeds to step ST422. If a command to output all combinations is given, the process proceeds to step ST423.

  In step ST422, a device / configuration control information addition message sequence generation process in the current state is performed, and the process ends. Details will be described later.

  In step ST423, a device / configuration control information all combination addition message sequence generation process for generating a message sequence to which the device / configuration control information in all combinations is added is performed, and the process ends. Details will be described later.

  FIG. 16 is a flowchart showing the operation of step ST422 of the error processing addition means 37 in FIG. 15 (device / configuration control information addition message sequence generation processing in the current state).

  In step ST430, an instance that is a system switching target is acquired from the device / configuration control information DB 200, and the process proceeds to step ST431.

  In step ST431, the current state of the instance to be system-switched is acquired from the device / configuration control information current value acquisition unit, and the process proceeds to step ST432.

  In step ST432, a device / configuration control information current value information addition message sequence information generation process is performed, and the process ends. Details will be described later.

  FIG. 17 is a flowchart showing the operation (device / configuration control information current value information addition message sequence information generation processing) of step ST432 of the error processing addition means 37 in FIG.

  In step ST450, the instance acquired in step ST430 is added to the work target message sequence information in step ST401, and the process proceeds to step ST451.

  In step ST451, the current mode state of each instance acquired in step ST431 is added to the message sequence information to which the system switching target instance acquired in step ST450 is added, and the process ends.

  FIG. 18 is a flowchart showing the operation of step ST423 of the error processing addition means 37 in FIG. 15 (device / configuration control information all combination addition processing).

  In step ST470, an instance that is a system switching target is acquired from the device / configuration control information DB 200, and the process proceeds to step ST471.

  In step ST471, the instance acquired in step ST470 is added to the work target message sequence information in step ST401, and the process proceeds to step ST472.

  In step ST472, all combinations of mode states that can be taken by each instance of the target system are acquired from the device / configuration control information DB 200, and the process proceeds to step ST473.

  In step ST473, a copy of the work target message sequence information is created for the combination of mode states acquired in step ST472, and the process proceeds to step ST474.

  In step ST474, the mode state of each instance of the message sequence information in step ST473 is added so as to satisfy all combinations of possible mode states acquired in step ST472, and the process ends.

<A-2-4. Error processing derivation>
FIG. 19 is a flowchart showing the operation of the error process deriving means 39 in FIG.

  In step ST351, the error processing deriving unit 39 stores the event designated by the error processing adding unit 37, that is, the event corresponding to one element of the work target message sequence information as the work target event, and proceeds to step ST352.

  In step ST352, the action of the work target event and its execution condition are acquired from the element / phenomenon correspondence information storage means 38, and the process proceeds to step ST353.

  In step ST353, it is determined whether or not they can be acquired. If they can be acquired, the process proceeds to step ST354, and if they cannot be acquired, the process proceeds to step ST355.

  In step ST354, the action of the work target event and its execution condition are stored, and the process proceeds to step ST355.

  In step ST355, it is checked whether or not a higher-order event of the work target event exists. If it exists, the process proceeds to step ST356, and if it does not exist, the process proceeds to step ST360.

  In step ST356, the conditions under which the existing upper event occurs are checked (acquired), and the process proceeds to step ST357.

  In step ST357, it is determined whether or not the condition for causing the higher-level event is related to system switching. If so, the process proceeds to step ST359. When not related, it progresses to step ST358.

  In step ST358, it is checked whether or not an upper event occurs. If it occurs, the process proceeds to step ST359, and if not, the process proceeds to step ST360.

  In step ST359, the upper event is set as a work target event, and the process proceeds to step ST352.

  In step ST360, the stored action of the work target event and its execution condition are passed to the error process adding means 37 as error process information, and the process ends.

<A-3. Example of operation>
An operation example of the first embodiment will be described with reference to FIGS. 20, 21, 22, 23, 24, and 25.

  FIG. 20 shows an input example in Embodiment 1 of the present invention. In the message sequence information example of FIG. 20A, there are three instances of message sequence information: a host system, a monitoring control server, and a monitoring control terminal device.

  In response to the selection request from the host system, the monitoring control server transmits the selection request to the monitoring control terminal device. The monitoring control terminal device transits to the “selection complete” state and transmits a selection reply (OK) to the monitoring control server. The monitoring control server transits to the “selection completed” state, and transmits a selection reply (OK) to the higher system. When the host system receives the selection reply (OK), the host system transits to the “selection complete” state. The message transmission side manages the reply from the message reception side using a timer. If a reply is not returned for a certain period, the timer fires. On the other hand, when the reply is returned, the timer is reset.

  Similarly, upon receiving a control request from the host system, the monitoring control server transmits a control request to the monitoring terminal device. When the monitoring terminal device receives the control request, the monitoring terminal device transits to a “control completed” state, and transmits a control reply (OK) to the monitoring control server. When receiving the control reply (OK), the monitoring control server changes the state to “control completed” and transmits the control reply (OK) to the host system. The host system receives it and changes the state to “control completed”.

  In the example of the event causal relationship model in FIG. 20B, the top event representing an abnormal event such as error processing is selective return. Selective return occurs only when selection is in progress due to a control request reception data error or a selection return request or system switching. Further, the control request reception data abnormality occurs due to a parity test violation or an illegal data error. In addition, system switching occurs due to the occurrence of a serious failure when the operation mode of the own instance is normal and the operation mode of the partner system is standby. A serious failure occurs due to the disconnection of both local LAN systems or a power failure.

  FIG. 21 is an example of the action setting process (see step ST202) of the element / phenomenon correspondence information generating means 35 in the first embodiment of the present invention. Assume that selective return, system switching, and occurrence of a serious failure are specified in the event.

  The following action 1 is set for selective return which is a top event.

  Action 1 is that the monitoring control server whose mode state is normal transmits a selection return request to the monitoring control terminal device and receives a selection return reply for the selection return request, so that the normal monitoring control server changes the state to “none”. Transition to “Select”. Subsequently, the regular monitoring control server transmits a selective return reply to the host system, and the host system receives the selective return reply and transitions the state to “no selection”.

  The following action 2 is set for system switching which is an intermediate event.

  Action 2 indicates that the timer t3 operating in the monitoring control server is reset and the timer t4 operating in the host system is reset.

  Action 3 indicates that the element “serious failure” occurs in the monitoring control server.

  FIG. 22 is an example of the element / event correspondence information generation process of the element / event correspondence information generation means 35 in the first embodiment of the present invention.

  The element in the message sequence information 31 after the monitoring control server starts the timer t4 is associated with the “serious failure occurrence” event in the event causal relationship model 33.

  An operation example of the error processing adding unit 37 and the error processing deriving unit 39 in the first embodiment of the present invention will be described.

  First, in step ST301, the error processing adding means 37 acquires one element / event correspondence information from the element / event correspondence information storage means 38, that is, information on an event corresponding to one element. In this example, the monitoring control server acquires correspondence information between the elements after starting the timer t4 and the “serious failure occurrence” event (see FIG. 22).

  In step ST303, the state of each instance related to one element acquired in step ST302 is acquired from the message sequence information 31 acquired in step ST300. In this example, the statuses of the host system, the monitoring control server, and the monitoring terminal device are “selection complete”.

  In step ST304, the state of each instance acquired in step ST303 and the element / event correspondence information of one element acquired in step ST301 are passed to the error processing deriving means 39.

  On the other hand, the error process deriving unit 39 stores an event designated by the error process adding unit 37 in step ST351, that is, an event corresponding to one element of the work target message sequence information as a work target event. In this example, since the monitoring control server has acquired the element / event correspondence information of the element after starting the timer t3 and the “major fault occurrence” event, the work target event becomes the “major fault occurrence” event. .

  In step ST352, the action of the work target event and its execution condition are acquired from the element / phenomenon correspondence information storage means 38. In this example, action 3 shown in FIG. 21 is set. Execution conditions are not set.

  In step ST354, the action and execution condition of the work target event are stored, and in step ST355, it is checked whether there is a higher event of the work target event. In this example, since the intermediate event “system switching” exists as a higher-level event, the process proceeds to step ST356.

  In step ST356, the conditions under which a higher-level event occurs are checked, and the process proceeds to step ST357. In this example, system switching occurs when the mode state of the own system is normal and the mode state of the partner system is standby.

  In step ST357, it is determined whether or not the condition for causing the higher-level event is related to system switching. Since this example relates to system switching, the process proceeds to step ST359.

  In step ST359, the higher-level event “system switching” is set as a work target event, and the process proceeds to ST352.

  In step ST <b> 352, the work target event is “system switching”, and the action is action 2. The execution condition for action 2 is not set. Through ST353 and step ST354, action 2 of the work target event “system switching” is acquired, and the process proceeds to step ST355. In step ST355, it is checked whether there is an upper event of the work target event “system switch”. In this example, since selection return exists as an upper event, the process proceeds to step ST356.

  In step ST356, a condition for causing selective return, which is a higher-order event, is checked, and the process proceeds to step ST357. The condition for the return of selection is when system switching occurs during selection. In this example, since the state of the monitoring control server is being selected, selection return occurs.

  In step ST357, it is determined whether or not the condition for causing the upper event is related to system switching. Since there is no relationship in this example, the process proceeds to step ST358. In step ST358, it is determined whether an upper event occurs. In this example, selection return, which is a higher-order event, occurs, so the process proceeds to step ST359.

  In step ST359, selection return which is a higher-order event is set as a work target event, and the process proceeds to step ST352.

  In step ST352, the action and execution condition for selective return that is a work target event are acquired, and the process proceeds to step ST353. In this example, the action for selection return is action 1. Execution conditions are not set.

  It progresses to step ST355 through step ST353 and step ST354. In step ST355, it is determined whether there is an upper event of the work target event. In this example, since there is no upper event of selective return, the process proceeds to step ST360.

  In step ST360, the stored action of the event and the execution condition are passed to the error processing adding unit 37 as error processing. In this example, action 3 set for an event and actions 2 and 1 caused by the event are stored.

  Further, in step ST401, the error processing adding unit 37 adds information on occurrence of the corresponding event to the work target message sequence information until one element acquired in step ST301 occurs. In this example, information on the occurrence of the event “serious failure” is added as an element after the monitoring control server starts the timer t3.

  Subsequently, in step ST402, the error process stored by the error process deriving unit 39 is taken out. Specifically, the action set for the event and the action caused by the event are extracted in the stored order.

  In this example, first, action 3 is extracted, and the process proceeds to step ST404. In step ST404, it is determined whether a configuration control condition is set in the error process. Since it is not set in action 3, the process proceeds to step ST406. In this example, since the execution condition of action 3 is not set, the process proceeds to step ST408.

  In step ST408, the action of step ST402 is added to the work target message sequence information, and the process proceeds to step ST402. In this example, action 3 in which a serious failure has occurred in the monitoring control server is added.

  In step ST402, action 2 is taken out and the process proceeds to step ST404.

  In step ST404, it is determined whether a configuration control condition is set. In action 2, since the configuration control condition is set, the process proceeds to the device / configuration control information addition processing in step ST405.

  In the detailed flowchart of step ST405, it is designated in step ST420 whether to generate only message sequence information or output all combinations in the current state of the target system.

  If all combinations are output, the process proceeds to step ST423.

  In the detailed flowchart of step ST423, in step ST470, an instance that is a system switching target is acquired from the device / configuration control information DB, and the process proceeds to ST471. In this example, it is a monitoring control server.

  In step ST471, the instance acquired in step ST470 is added to the work target message sequence information in step ST401, and the process proceeds to step ST472. In this example, supervisory control is added, and the conventional supervisory control server is designated as supervisory control server 1 and the added supervisory control server is designated as supervisory control server 2 from the device / configuration control information DB.

  In step ST472, all combinations of possible mode states are acquired from the device / configuration control information DB, and the process proceeds to step ST473. In this example, there are four patterns: (server 1, server 2) = (normal, standby), (normal, maintenance), (standby, normal), (maintenance, standby).

  In step ST473, the work target message sequence information copy is created for the combination of the mode states acquired in step ST472, and the process proceeds to step ST474. In this example, four work target message sequence information copies are created.

  In step ST474, the mode state of each instance of the message sequence information in step ST473 is added so as to satisfy all combinations of possible mode states acquired in step ST472, and the process proceeds to step ST406. In this example, the mode states that can be taken by the server 1 and the server 2 acquired in step ST472 are added to the respective copies.

  In step ST406, action 2 is added to the work target message sequence information in step ST408. At this time, action 2 is added to each copy created in step ST473 for a copy that satisfies the configuration control condition. For unsatisfied copies, the process proceeds to step ST409.

  Similarly, action 1 is taken out and action 1 is added to the copy of step ST473 to which action 2 is added.

  FIG. 23 shows error processing additional message sequence information 40 when the monitoring control server 1 is in the normal mode and the monitoring control server 2 is in the standby mode. On the other hand, FIG. 24 shows error processing additional message sequence information 40 when the monitoring control server 1 is in the normal mode and the monitoring control server 2 is in the maintenance mode.

  In FIG. 23, system switching occurs, and an action for selective return, which is an upper event of system switching, is added. On the other hand, in FIG. 24, since system switching does not occur, the action of selective return that is the higher-order event is not added.

  In step ST420, when only the current information of the device / configuration control information is generated, the process proceeds to ST422.

  In step ST430, which is a detailed flowchart of step ST422, an instance that is a system switching target is acquired from the device / configuration control information DB, and the process proceeds to step ST431. In this example, it is a monitoring control server.

  In step ST431, the current state of the instance to be system-switched is acquired from the device / configuration control information current value acquisition unit, and the process proceeds to step ST432.

  In step ST450, which is a detailed flowchart of step ST432, the instance acquired in step ST430 is added to the work target message sequence information in step ST401, and the process proceeds to step ST451. In this example, a monitoring control server is added.

  In step ST451, the current mode state of each instance acquired in ST431 is added to the message sequence to which the system switching target instance acquired in step ST450 is added. In this example, FIG. 24 shows error processing additional message sequence information 40 when the mode states of the monitoring control server 1 and the monitoring control server 2 are normal and maintenance, respectively. Error processing additional message sequence information 40 in a mode state other than the current state is not generated.

  With the above-described configuration, the device / configuration control information current value acquisition unit acquires the current value of the device status from the device / configuration control current value information, and an error processing additional message sequence in the current operation state of the multiplex system Generate information only. Thereby, it is possible to suppress error processing additional message sequence information that does not occur from the current operating state of the multiplex system.

<A-4. Effect>
According to the message sequence generation method according to the first exemplary embodiment of the present invention, (a) a step of preparing message sequence information indicating normal processing of a communication protocol using a message sequence diagram for data processing; ) A step of preparing an event causal relationship model in which an event accompanied by mode switching of an instance and an event requiring error processing are described together with a causal relationship for data processing; and (c) a device / configuration including mode information of the instance Storing the control information and the current value of the device / configuration control information in the database; and (d) setting an action to be performed when the event occurs for a specific event in the event causal relationship model; (E) Corresponding each element of the message sequence information and each event to generate element / event correspondence information A process, (f) a step of storing element / event correspondence information in a storage device, and (g) each element corresponding to each element and an event caused by the event are set from the element / event correspondence information. And (h) generating message sequence information in the current mode state of the system targeted by the message sequence information, and performing data processing by a computer. Since each process is executed, error processing including cases involving system switching can be added while considering the causal relationship between events by the event causal relationship model, so that an error processing additional message sequence diagram is efficiently generated. be able to.

Also,
According to the message sequence generation device according to the first exemplary embodiment of the present invention, (message sequence information indicating normal processing of a communication protocol using a message sequence diagram, an event accompanied by instance mode switching, and error processing are required. An event-causal relationship model described with a causal relationship with a particular event, a database storing device / configuration control information including instance mode information, and the current value of the device / configuration control information, and a specific event-causal relationship model A setting means for setting an action to be performed when an event occurs for an event, each element of message sequence information, each event is associated with each other, correspondence information generating means for generating element / event correspondence information, and an element・ Storage means for storing event response information and element / event response information Acquiring each action event and the action set for the event caused by the event, adding to each element as error processing, and message in the current mode state of the system targeted by the message sequence information Since there is an information generation means that generates sequence information, error processing including cases involving system switching can be added while considering the causal relationship between events using the event causal relationship model, so error processing can be added efficiently A message sequence diagram can be generated.

  In addition, error processing in the current mode state of the system targeted by the message sequence information can be added in error processing including cases involving system switching while considering the causal relationship between events by the event causal relationship model. Thus, it is possible to efficiently generate an error processing additional message sequence diagram.

<B. Second Embodiment>
<B-1. Configuration>
FIG. 29 is a block diagram showing a configuration of the message sequence generation device 44 according to the embodiment of the present invention. Among the constituent elements of the block diagram, except for the instance abstraction event causal relationship model 303 and the instance abstraction event causal relationship model specifying means, the configuration is the same as that of the first embodiment, and detailed description thereof will be omitted.

  FIG. 30 shows an example of an instance abstraction event causal model. In the event-causal relationship model 33 of the first embodiment, it is necessary to describe the system switching condition using specific information on each instance. In the example of the event-causal relationship model 33 in FIG. 20, it is necessary to describe the conditions for system switching by specifically using the instances of the own system and other systems.

  In FIG. 30, an instance of another system in the system switching occurrence condition is abstracted and described as “other system X”.

  The instance abstraction event-causal model can easily describe system switching conditions related to a multi-system with a triple structure or higher.

  FIG. 31 is a flowchart showing the operation of the instance abstraction event-causal model realization means. In step ST500, one event of the instance abstraction event causal relationship model is acquired, and the process proceeds to step ST501.

  In step ST501, it is determined whether the event of step ST500 has been acquired. If it can be obtained, the process proceeds to step ST502. If not acquired, the process proceeds to ST507.

  In step ST502, it is determined whether the event in step ST500 is an event related to the abstraction instance. If so, the process proceeds to step ST503. If not, the process proceeds to step ST500. Whether or not the event is related to the abstract instance is determined by whether or not the instance of the event in which the mode state is described is a specific instance name.

  In step ST503, the mode state of each instance is acquired from the device / configuration control information current value acquisition unit, and the process proceeds to step ST504. In this example, the mode state of the server 1 is normal, and the mode state of the server 2 is standby (see FIG. 6).

  In step ST504, the system switching priority is acquired from the device / configuration control information DB, and the process proceeds to step ST505. In this example, the system switching priority of the server 1 is 1, and the system switching priority of the server 2 is 2.

  In step ST505, an instance that replaces the abstraction instance is searched, and the process proceeds to step ST506. In this example, since the server 2 is the only monitoring control server that is currently a standby system, the server 2 is acquired. If there are multiple standby systems, the standby system with the highest system switching priority is acquired.

  In step ST506, the abstraction instance acquired in step ST500 is replaced with the instance acquired in step ST505, and the process proceeds to step ST500. In this example, the other system X is replaced by the server 2.

  In step ST507, the event causal relationship model in which the abstract instance is replaced with a specific instance is passed to the error processing deriving unit.

  FIG. 32 is an example of an event causal relationship model generated according to the second embodiment of the present invention. In the instantiation abstract event causality model, the event “other system X: standby mode” is replaced with “monitoring control server 2: standby mode”, and the current instance of the target system replaces the abstract instance with an appropriate concrete instance. Has been.

<B-4. Effect>
According to the message sequence generation method of the second embodiment of the present invention, (a) preparing message sequence information for normal processing of a communication protocol using a message sequence diagram for data processing; and (b) A step of preparing an event-causal relation model describing together with a causal relation between an event accompanied by mode switching of the instance and an event requiring error processing, and (c) device / configuration control including mode information of the instance Storing the information and the current value of the device / configuration control information in a database; (d) setting an action to be performed when the event occurs for a specific event in the event causality model; e) A step of associating each element of message sequence information with each event to generate element / event correspondence information (F) storing element / event correspondence information in the storage device; and (g) actions set for each event corresponding to each element and an event caused by the event from the element / event correspondence information. And (h) generating message sequence information in the current mode state of the system targeted by the message sequence information; (i) device / configuration control information; , A process to generate an event causal relationship model describing the mode switching occurrence conditions of the instance from the current value of the device / configuration control information and the event causal relationship model, so that system switching related to a specific instance occurs An event-causal relationship model describing conditions can be generated.

  In addition, according to the message sequence generation device of the second exemplary embodiment of the present invention, message sequence information indicating normal processing of the communication protocol using the message sequence diagram, an event accompanied by instance mode switching, and error processing are required. An event-causal relationship model described with a causal relationship with a particular event, a database storing device / configuration control information including instance mode information, and the current value of the device / configuration control information, and a specific event-causal relationship model A setting means for setting an action to be performed when an event occurs for an event, each element of message sequence information, each event is associated with each other, correspondence information generating means for generating element / event correspondence information, and an element・ Storage means for storing event response information and element / event response information Acquisition means, an action set for each event that occurs due to the event, and an addition means for adding to each element as error processing, and a message sequence in the current mode state of the system targeted by the message sequence information Information generation means for generating information, model generation for generating an event causal relationship model describing the mode switching occurrence condition of the instance from the device / configuration control information, the current value of the device / configuration control information, and the event causal relationship model Therefore, it is possible to generate an event-causal relationship model describing a system switching occurrence condition related to a specific instance.

  In addition, error processing in the current mode state of the system targeted by the message sequence information can be added in error processing including cases involving system switching while considering the causal relationship between events by the event causal relationship model. Thus, it is possible to efficiently generate an error processing additional message sequence diagram.

  1 PC, 2 CPU, 3 storage device, 4 input device, 5 output device, 31,400 message sequence information, 32 correspondence result output means, 33 event causal relationship model, 34 action input means, 35 element / event correspondence information generation means 36, element / event input means, 37, 42 error processing addition means, 38 element / event correspondence information storage means, 39, 45 error processing derivation means, 40 error processing addition message sequence information, 41, 44 message sequence generation device, 61 Instance start symbol, 62 Instance name, 63 Lifeline, 64 Instance end symbol, 65 Message symbol, 66 Message name, 67 Timer symbol, 68 Timer information, 69 Status symbol, 70 Internal action symbol, 81 Top event, 82 Logical product, 83 logic Sum, 84 Intermediate event, 85 Basic event, 300 Timer reset symbol, 301 Timer firing symbol, 302 Timer stop symbol, 303 Instance abstract event causal relationship model, 304 Instance abstract event causal relationship model realization means.

Claims (4)

(A) preparing message sequence information indicating normal processing of a communication protocol using a message sequence diagram for data processing;
(B) preparing an event-causal relationship model describing, together with a cause-and-effect relationship, an event accompanied by mode switching of an instance and an event requiring error processing for data processing;
(C) storing device / configuration control information including mode information of the instance and a current value of the device / configuration control information in a database;
(D) setting an action to be performed when the event occurs for the specific event in the event-causal relationship model;
(E) associating each element of the message sequence information with each event to generate element / event correspondence information;
(F) storing the element / event correspondence information in a storage device;
(G) From the element / phenomenon correspondence information, acquire the action corresponding to each element and the action set for the event caused by the event, and add it to each element as error processing Process,
(H) generating the message sequence information in a current mode state of a system targeted by the message sequence information,
A method for generating a message sequence, wherein the steps are executed by data processing by a computer. (I) including a step of generating an event causal relationship model describing a mode switching occurrence condition of the instance from the device / configuration control information, a current value of the device / configuration control information, and the event causal relationship model. The message sequence generation method according to claim 1, wherein: Message sequence information indicating normal processing of the communication protocol using the message sequence diagram;
An event-causal relationship model that describes events that involve mode switching of instances and events that require error handling, along with causal relationships;
A database that stores device / configuration control information including mode information of the instance, and a current value of the device / configuration control information;
Setting means for setting an action to be performed when the event occurs with respect to the specific event in the event-causal relationship model;
Correspondence information generating means for associating each element of the message sequence information with each event and generating element / event correspondence information;
Storage means for storing the element / event correspondence information;
Adding means for acquiring each of the events corresponding to each of the elements and the action set for the event caused by the event from the element / event correspondence information, and adding the action to each element as error processing; ,
A message sequence generation device comprising: information generation means for generating the message sequence information in a current mode state of a system targeted by the message sequence information. Model generation means for generating an event causal relationship model describing a mode switching occurrence condition of the instance from the device / configuration control information, the current value of the device / configuration control information, and the event causal relationship model The message sequence generation device according to claim 3, wherein

Images