WO2017145309A1

WO2017145309A1 - Computer and state transition information generation method

Info

Publication number: WO2017145309A1
Application number: PCT/JP2016/055518
Authority: WO
Inventors: 衣津美水谷; 侑中田; 木下　雅文; 芳樹松浦; 辰彦宮田
Original assignee: 株式会社日立製作所
Priority date: 2016-02-24
Filing date: 2016-02-24
Publication date: 2017-08-31

Abstract

A computer for generating state transition information indicating transitions in the operating state of a device, said computer comprising a state transition information generation unit for generating the state transition information, wherein the state transition information generation unit: acquires operating information including a plurality of messages indicating the operating state of a target device; divides the operating information to generate a plurality of sets of scenario information, each representing a scenario corresponding to one state transition pattern of the target device; and integrates the plurality of sets of scenario information together, thereby generating the state transition information, which indicates all state transitions of the target device.

Description

Computer and method for generating state transition information

The present invention relates to a computer that generates state transition information indicating a state transition of a device, and a state transition information generation method.

In the IoT (Internet of Things) era where all devices are connected for communication, there are an increasing number of cases where various devices are connected to a network for analysis and management. As the trend of IoT, “Industrie 4.0” advocated by Germany and “Industrial Internet Consortium (IIC)”, an American promotion organization, are attracting attention. According to these, it is predicted that information and sensor data of various devices will be collected and analyzed in real time via a network and used for operation and maintenance.

The following processing is performed for management based on collection and analysis of device information and sensor data. First, a device equipped with a sensor for observing data to be collected (for example, temperature, pressure, vibration, etc. for an industrial device) continuously transmits data. Next, a processing server that performs collection and analysis receives data transmitted from the apparatus, performs preprocessing such as conversion processing, and then performs analysis. By performing these series of processes, for example, it is possible to observe an abnormal value of the sensor and perform preventive maintenance such as replacement of parts before the apparatus is damaged.

Here, when sensor data is collected and analyzed in real time and used for operation and maintenance, it is necessary to be able to identify the state of the target device from the outside. For example, it is necessary to specify whether the target device is stopped or not, what kind of processing is being performed during operation, and the like. In order to solve this, a state transition of the apparatus is necessary. As a technique for generating state transition information indicating a state transition of a device, for example, a method as disclosed in Patent Document 1 is known.

Patent Document 1 states that “the message sequence diagram storage unit A1 stores all message sequence diagrams to be converted, and the process designating unit A2 designates a process to be converted on the message sequence diagram. The state transition information conversion unit A3 extracts event sequences on all message sequence diagrams of the process specified by the process specification unit A2 from the message sequence diagram stored in the message sequence diagram storage unit A1, and converts them into state transition information. The state transition information reduction unit A5 deletes the duplicate transition information in the state transition information stored in the state transition diagram storage unit A4, and stores the state transition information in the state transition diagram storage unit A4. It will be reduced. "

JP-A-11-134180

When generating state transition information, it is necessary to define the state of the device and specify the transition between the states of the device. In order to define the state of the device, information describing the specification or design of the device is required in advance.

However, there are cases where information as described above does not necessarily exist. For example, for a product purchased from the outside, a specification or design document may not be released.

In the prior art as described in Patent Document 1, it is necessary to prepare a specification or design document of the apparatus in advance. Therefore, when the above-described information does not exist, the state transition information of the device cannot be generated by the conventional technique.

It is an object of the present invention to provide a computer and a method for efficiently generating state transition information of a device even when the device state cannot be defined because there is no device specification or design document. .

A typical example of the invention disclosed in the present application is as follows. That is, a computer that generates state transition information indicating a transition of an operating state of a device, the computer being a processor, a memory connected to the processor, and an interface connected to the processor and connected to an external device A state transition information generation unit configured to generate the state transition information, wherein the state transition information generation unit acquires operation information including a plurality of messages indicating an operation state of the target device, and the target device A plurality of scenario information is generated by dividing the operation information for each scenario corresponding to a single state transition pattern, and all the state transitions of the target device are obtained by integrating the plurality of scenario information. The state transition information shown is generated.

According to the present invention, it is possible to efficiently generate device state transition information even when there is no device specification or design document. Problems, configurations, and effects other than those described above will become apparent from the following description of embodiments.

It is a block diagram explaining an example of a structure of the computer system of Example 1. FIG. 1 is a block diagram illustrating an example of a configuration of a device according to a first embodiment. FIG. 3 is a block diagram illustrating an example of a configuration of a data store server according to the first embodiment. It is a block diagram explaining an example of a structure of the state transition production | generation server of Example 1. FIG. It is a block diagram explaining an example of a structure of the analysis server of Example 1. FIG. 6 is a diagram illustrating an example of an event log according to the first embodiment. It is a figure explaining an example of the reference | standard message definition information of Example 1. FIG. It is a figure explaining an example of the scenario information of Example 1. FIG. It is a figure explaining an example of the scenario information of Example 1. FIG. 3 is a graph showing a concept of a scenario of Example 1. 3 is a graph showing a concept of a scenario of Example 1. It is a figure explaining an example of the scenario integration information of Example 1. FIG. It is a figure explaining an example of the scenario integration information of Example 1. FIG. It is a sequence diagram explaining the flow of a process of the computer system in the case of producing | generating the state transition information of Example 1. FIG. FIG. 6 is a diagram illustrating an example of a GUI operated when generating state transition information according to the first embodiment. FIG. 6 is a diagram illustrating an example of a CUI operated when generating state transition information according to the first embodiment. It is a flowchart explaining an example of the state transition information generation process which the state transition generation server of Example 1 performs. It is a figure explaining an example of the state transition information of Example 1. FIG. It is a flowchart explaining an example of the scenario integration process which the state transition production | generation server of Example 1 performs. It is a flowchart explaining an example of the state integration process which the state transition production | generation server of Example 1 performs. It is a flowchart explaining an example of the state integration process which the state transition production | generation server of Example 1 performs. It is a figure explaining the production | generation process of the state transition information of Example 1. FIG. It is a figure explaining the production | generation process of the state transition information of Example 1. FIG. It is a figure explaining the production | generation process of the state transition information of Example 1. FIG. It is a figure explaining the example of a display of the state transition information display column of Example 1. FIG. It is a figure explaining the example of a display of the state transition information display column of Example 1. FIG. It is a sequence diagram which shows the flow of a production | generation processing flow in the computer system at the time of the production | generation of the state transition information of Example 2. FIG. It is a flowchart explaining an example of the state transition information generation process which the state transition generation server of Example 2 performs. It is a flowchart explaining an example of the state integration process which the state transition production | generation server of Example 2 performs.

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

FIG. 1 is a block diagram illustrating an example of the configuration of a computer system according to the first embodiment.

The computer system according to the first embodiment includes a plurality of devices 101, a data store server 102, a state transition generation server 103, and an analysis server 104. The plurality of devices 101, the data store server 102, the state transition generation server 103, and the analysis server 104 are connected to each other via a network 105.

The network 105 may be a LAN (Local Area Network), a WAN (Wide Area Network), or the like. Note that the present invention is not limited to the type of the network 105. Further, the present invention is not limited to the connection form between each device and the network 105, and may be wireless or wired.

The device 101 is a device for which the state transition information 426 (see FIG. 4) is to be generated. Note that the present invention is not limited to the type of the apparatus 101. For example, equipment in a certain factory, sensors, and the like correspond to the apparatus 101.

The data store server 102 manages the data store. In this embodiment, the event log 321 (see FIG. 3) is stored in the data store. The event log 321 includes a plurality of messages indicating operating states of the plurality of apparatuses 101. In FIG. 1, the number of data store servers 102 is one, but a plurality of data store servers 102 may exist. In this case, a data store is configured by integrating storage areas of a plurality of data store servers 102.

The state transition generation server 103 generates state transition information 426 (see FIG. 4) of the apparatus 101 using a plurality of messages acquired from the event log 321 or the apparatus 101.

The analysis server 104 executes an analysis process using the state transition information 426 generated by the state transition generation server 103. Note that the present invention is not limited to the processing content of the analysis processing.

FIG. 2 is a block diagram illustrating an example of the configuration of the apparatus 101 according to the first embodiment.

The apparatus 101 includes a processor 201, a volatile memory 202, a nonvolatile memory 203, a network I / F 204, and an input / output I / F 205, and the respective components are connected to each other via an internal communication line such as a bus.

The processor 201 executes a program stored in the volatile memory 202. The function of the apparatus 101 is realized by the processor 201 executing a program stored in the volatile memory 202. In the following description, when a process is described mainly with a program, it indicates that the processor 201 is executing the program.

The volatile memory 202 stores a program executed by the processor 201, and includes a storage area for temporarily storing data necessary for executing the program. The nonvolatile memory 203 includes a storage area for permanently storing data. The programs and storage areas stored in the volatile memory 202 and the nonvolatile memory 203 will be described later.

The network I / F 204 is an interface for connecting to other devices via the network 105. The input / output I / F 205 is an interface for connecting to an input / output device. The input / output device includes, for example, a display, a touch panel, a keyboard, and a mouse.

Here, programs and storage areas stored in the volatile memory 202 and the nonvolatile memory 203 will be described.

The volatile memory 202 stores a program for realizing the control unit 212 and the volatile storage unit 210.

The control unit 212 is composed of a plurality of program modules and performs various controls of the apparatus. Specifically, the control unit 212 includes a device control unit 221 and a message output unit 222.

The device control unit 221 controls the entire device 101. Note that the present invention is not limited to the control content performed by the device control unit 221. The message output unit 222 controls output of a message indicating the operating state of the apparatus 101. Note that the function of the message output unit 222 may be included in the device control unit 221.

The message output unit 222 may output a message to the data store server 102 each time a message is generated, or may output a plurality of messages to the data store server 102 when a predetermined number of messages are accumulated. Good. At this time, the message output unit 222 may directly output a message to the data store server 102 via the data relay application.

Further, the message output unit 222 may provide an API for receiving a message output request. For example, when a message output request is received from the state transition generation server 103 via the API, the message output unit 222 outputs a predetermined number of messages to the state transition generation server 103. Further, the state transition generation server 103 outputs an API via the data store server 102 using an application that acquires the message via the API to the message output unit 222 and stores the acquired message in the data store server 102. A message may be obtained.

The volatile storage unit 210 controls data reading processing and writing processing for the volatile memory 202. In the present embodiment, the volatile storage unit 210 manages data managed by the device control unit 221 and messages output by the message output unit 222.

The nonvolatile memory 203 stores a program for realizing the nonvolatile storage unit 211.

The nonvolatile storage unit 211 controls data read processing and write processing with respect to the nonvolatile memory 203. For example, an important message is stored in the nonvolatile memory 203.

Note that the device 101 may not include the nonvolatile memory 203. Further, the apparatus 101 may not include the input / output I / F 205.

FIG. 3 is a block diagram illustrating an example of the configuration of the data store server 102 according to the first embodiment.

The data store server 102 includes a processor 301, a volatile memory 302, a nonvolatile memory 303, a network I / F 304, and an input / output I / F 305, and the respective components are connected to each other via an internal communication line such as a bus.

The processor 301, the volatile memory 302, the nonvolatile memory 303, the network I / F 304, and the input / output I / F 305 of this embodiment are the processor 201, the volatile memory 202, the nonvolatile memory 203, the network I / F 204, and the input / output I / F 305. This is the same as the output I / F 205.

The volatile memory 302 stores a program for realizing the volatile storage unit 310 and the data store management unit 312.

The data store management unit 312 manages a data store configured using the storage area of the volatile memory 302.

The volatile storage unit 310 controls data reading processing and writing processing for the volatile memory 302 in cooperation with the data store management unit 312. In this embodiment, the volatile storage unit 310 manages the event log 321 and a plurality of analysis data 322. The event log 321 includes a plurality of messages from a plurality of devices 101. The analysis data 322 includes the result of the analysis process executed by the analysis server 104. For example, the analysis data 322 includes the results of analysis processing for one device 101.

The nonvolatile memory 303 stores a program for realizing the nonvolatile storage unit 311. The nonvolatile storage unit 311 is the same as the nonvolatile storage unit 211.

Note that the data store may be configured using a storage area of the nonvolatile memory 303. In this case, the data store management unit 312 controls data reading processing and writing processing with respect to the nonvolatile memory 303 in cooperation with the nonvolatile storage unit 311.

FIG. 4 is a block diagram illustrating an example of the configuration of the state transition generation server 103 according to the first embodiment.

The state transition generation server 103 includes a processor 401, a volatile memory 402, a nonvolatile memory 403, a network I / F 404, and an input / output I / F 405, and the respective components are connected to each other via an internal communication line such as a bus. .

The processor 401, the volatile memory 402, the nonvolatile memory 403, the network I / F 404, and the input / output I / F 405 of the present embodiment are the processor 201, the volatile memory 202, the nonvolatile memory 203, the network I / F 204, and the input / output I / F 405. This is the same as the output I / F 205.

The volatile memory 402 stores a program for realizing the volatile storage unit 410 and the state transition generation application 412.

The state transition generation application 412 includes a plurality of program modules, and generates state transition information for each of the plurality of apparatuses 101. Specifically, the state transition generation application 412 includes an input / output unit 421, a message acquisition unit 422, and a state transition information generation unit 423.

The input / output unit 421 controls input of various data when generating state transition information, output of state transition information, and the like. The input / output unit 421 uses the state transition information 426 to generate display information for displaying a GUI or the like. The message acquisition unit 422 acquires operation information including a message indicating the operation state of the target apparatus 101. The message acquisition unit 422 may acquire operation information from the event log 321 managed by the data store server 102, or may acquire operation information via an API provided by the device 101.

The state transition information generation unit 423 generates state transition information 426 indicating the state transition of the apparatus 101 using the operation information acquired by the message acquisition unit 422.

The volatile storage unit 410 controls data read processing and write processing with respect to the volatile memory 402. In this embodiment, the volatile storage unit 410 manages scenario information 424 and scenario integration information 425.

Scenario information 424 is information for managing a scenario. The scenario integration information 425 is information generated by integrating a plurality of scenario information 424. In this embodiment, the state transition information 426 of one device 101 is generated by integrating all scenarios of one device 101.

The non-volatile storage unit 411 controls a data reading process and a writing process with respect to the non-volatile memory 403. The nonvolatile storage unit 411 manages the state transition information 426 and the reference message definition information 427.

The state transition information 426 is information generated by the state transition information generation unit 423. One state transition information 426 is information indicating the state transition of one device 101. In this embodiment, a plurality of state transition information 426 having different reference messages or different state integration states may be generated for one apparatus 101. Note that the state transition information 426 may be stored in the volatile storage unit 410.

The reference message definition information 427 stores reference message information used when generating a plurality of scenarios from operation information including a plurality of messages. Here, the scenario indicates one state transition pattern of one device 101.

The state transition of the device 101 has a plurality of patterns. Therefore, when a plurality of messages are analyzed as they are when the state transition information 426 is generated, the processing becomes very complicated. Therefore, in this embodiment, the state transition information generation unit 423 divides operation information including a plurality of messages into a plurality of scenarios, and integrates the scenarios by comparing them. As a result, state transition information 426 covering all state transitions of one device 101 is generated.

In the following description, when “store data in the volatile storage unit 410” is described, a data storage request is output to the volatile storage unit 410, and the volatile storage unit 410 is stored in the storage area of the volatile memory 402. Indicates that data is to be stored. In addition, when “store data in the nonvolatile storage unit 411” is described, a data storage request is output to the nonvolatile storage unit 411, and the nonvolatile storage unit 411 stores the data in the storage area of the nonvolatile memory 403. Indicates to do.

FIG. 5 is a block diagram illustrating an example of the configuration of the analysis server 104 according to the first embodiment.

The analysis server 104 includes a processor 501, a volatile memory 502, a nonvolatile memory 503, a network I / F 504, and an input / output I / F 505, and each component is connected to each other via an internal communication line such as a bus.

The processor 501, the volatile memory 502, the nonvolatile memory 503, the network I / F 504, and the input / output I / F 505 of this embodiment are the processor 201, the volatile memory 202, the nonvolatile memory 203, the network I / F 204, and the input / output I / F 505. This is the same as the output I / F 205.

The volatile memory 502 stores programs for realizing the volatile storage unit 510, the message reception application 512, and the analysis application 513.

The message receiving application 512 is an application that provides a function for receiving a message, and includes a message receiving unit 521.

The message receiving unit 521 receives a message from the device 101 or the data store server 102. For example, the message receiving unit 521 receives a real-time message from the device 101 via an API provided by the device 101.

The analysis application 513 is an application that provides a function for performing various types of analysis, and includes an input / output unit 522, a state transition analysis unit 523, and a display information generation unit 524.

The input / output unit 522 controls input of various data during execution of analysis processing, output of results of analysis processing, and the like. The state transition analysis unit 523 executes an analysis process using the message and the state transition information 525. Note that the present invention is not limited to the contents of the analysis process. The display information generation unit 524 generates display information for displaying the result of the analysis processing and the like.

The volatile storage unit 510 controls data reading processing and writing processing for the volatile memory 502. In this embodiment, the volatile storage unit 510 manages received messages, display information, and the like.

The non-volatile storage unit 511 controls data reading processing and writing processing for the non-volatile memory 503. The nonvolatile storage unit 511 manages the state transition information 525. The state transition information 525 is the same as the state transition information 426 generated by the state transition generation server 103.

In this embodiment, the state transition generation server 103 outputs the state transition information 426 generated to the analysis server 104, and the state transition information 426 received by the analysis server 104 is managed as the state transition information 525. The state transition generation server 103 may transmit the generated state transition information 426 to the data store server 102. In this case, the analysis server 104 acquires the state transition information 426 from the data store server 102 and manages it as state transition information 525 in the nonvolatile storage unit 511.

FIG. 6 is a diagram illustrating an example of the event log 321 according to the first embodiment.

The event log 321 includes a plurality of messages including a date, an identifier of the device 101, and a message content indicating the state of the device 101.

The top message shown in FIG. 6 is “13:15” with the date and time “December 14, 2015”, the identifier of the device 101 is “X0123931”, and the message content is “ Indicates “power on”.

When the data store management unit 312 receives the message, the data store management unit 312 updates the event log 321 by adding data in the format shown in FIG.

FIG. 7 is a diagram illustrating an example of the reference message definition information 427 according to the first embodiment.

The reference message definition information 427 is information set in advance by a computer system administrator or a user who uses the apparatus 101, and includes a plurality of entries including a device ID 701 and a reference message 702.

The device ID 701 is an identifier of the device 101. The reference message 702 is the content of a message used when generating a scenario.

8A and 8B are diagrams illustrating an example of the scenario information 424 according to the first embodiment. 9A and 9B are graphs showing the concept of the scenario of the first embodiment.

The scenario information 424 is given the identifier of the apparatus 101 and the scenario identifier. FIG. 8A shows scenario information 424 in which the identifier of the device 101 is “device 1” and the scenario identifier is “scenario 1”. FIG. 8B shows scenario information 424 in which the identifier of the device 101 is “device 1” and the scenario identifier is “scenario 2”.

Scenario information 424 includes a plurality of entries including a status ID 801, a connection destination status ID 802, and an output message 803. One entry corresponds to one state (node).

Status ID 801 is an identifier of a node indicating a status. The connection destination state ID 802 is an identifier of a node whose time series is one after the node corresponding to the state ID 801. In the case of the node corresponding to the end of the scenario, there is no node after the node, so the connection destination state ID 802 is blank. The output message 803 is the content of a message that is output when the state corresponding to the state ID 801 transits to the state corresponding to the connection destination state ID 802.

The scenario information 424 shown in FIG. 8A corresponds to the scenario shown in FIG. 9A. The scenario information 424 shown in FIG. 8B corresponds to the scenario shown in FIG. 9B. As shown in FIGS. 9A and 9B, each node is defined as a state, and a message is associated with an edge connecting each state.

10A and 10B are diagrams illustrating an example of the scenario integration information 425 according to the first embodiment. FIG. 10A shows scenario integration information 425 used when executing the scenario integration processing. FIG. 10B shows scenario integration information 425 used when executing the state integration processing.

The identifier of the apparatus 101 is given to the scenario integration information 425. The scenario integrated information 425 illustrated in FIG. 10A includes a plurality of entries including an integrated state ID 1001, a connection destination integrated state ID 1002, an output message 1003, a distance (starting end) 1004, and a distance (ending) 1005. One entry corresponds to one state (node).

The integration state ID 1001, the connection destination integration state ID 1002, and the output message 1003 are the same as the state ID 801, the connection destination state ID 802, and the output message 803. However, the integrated state ID 1001 and the connection destination integrated state ID 1002 store the identifiers of the states after the scenarios are integrated. In the following description, the state after the scenario is integrated is also referred to as an integrated state.

Distance (starting point) 1004 is a distance (hop count) from the starting state of the state included in the scenario before integration. The distance (termination) 1005 is the distance (number of hops) from the termination state of the state included in the scenario before integration. The distance (starting edge) 1004 and the distance (ending edge) 1005 are used when integrating scenarios.

For example, since the state “S1_St1” in FIG. 9A is the start point state, the distance from the start end state is “0”, and the distance from the end state is “6”. In the state “S1_St4” in FIG. 9A, the distance from the start end state is “3”, and the distance from the end end state is “3”.

The scenario integration information 425 illustrated in FIG. 10B includes a plurality of entries including an integration state ID 1001, a connection destination integration state ID 1002, and an output message 1003. One entry corresponds to one state (node).

When a plurality of nodes are integrated, as many rows as the number of nodes connected to each node to be integrated are generated in the connection destination integration state ID 1002 of one entry. Also, as many lines as the number of nodes connected to the node are generated in the output message 1003 of the entry.

For example, an entry whose integrated state ID 1001 is “St2” indicates that two nodes included in different scenarios are integrated nodes.

On the other hand, when a plurality of integration states are integrated into one integration state in the state integration process, the output message 1003 has one line, and a plurality of messages are stored in one line.

For example, an entry whose integration state ID 1001 is “St3” indicates that the integration node is an integration node obtained by integrating a plurality of integration nodes.

FIG. 11 is a sequence diagram for explaining the processing flow of the computer system when the state transition information 426 of the first embodiment is generated. FIG. 12 is a diagram illustrating an example of a GUI (Graphical User Interface) operated when generating the state transition information 426 according to the first embodiment. FIG. 13 is a diagram illustrating an example of a CUI (Character User Interface) operated when generating the state transition information 426 according to the first embodiment.

FIG. 11 illustrates an example in which the state transition information 426 is generated using the event log 321 stored in the data store server 102.

First, the input / output unit 421 of the state transition generation server 103 displays a display screen 1200 as shown in FIG. 12 or a display screen 1300 as shown in FIG. Here, each of the

display screens

1200 and 1300 will be described.

The display screen 1200 shows an example of a GUI, and includes a setting information input field 1210, a START button 1220, a display switching selection field 1230, and a state transition information display field 1240.

The setting information input column 1210 is a column for inputting various parameters used for generating the state transition information 426. The setting information input field 1210 includes a definition information input field 1211, a reference button 1212, a target device ID input field 1213, a state number input field 1214, and a period input field 1215.

The definition information input field 1211 is an input field for designating reference message definition information 427 to be referred to. In the definition information input field 1211, a path name or a file name in which the reference message definition information 427 is stored is input.

The reference button 1212 is a button for determining reference to the reference message definition information 427 set in the definition information input field 1211. When the reference button 1212 is operated, the state transition generation server 103 executes state transition information generation processing using the reference message definition information 427.

The target device ID input column 1213 is a column for inputting the identifier of the device 101 that generates the state transition information 426. In the example shown in FIG. 12, the target device ID input field 1213 is displayed as a pull-down input field.

The state number input column 1214 is an input column for setting the maximum number of states included in the state transition information 426. The period input field 1215 is an input field for designating a period for acquiring a message. The state transition information generation unit 423 holds the maximum value of the state input in the state number input field 1214 and the like as granularity information, and also holds the period input in the period input field 1215 and the like as period information.

The START button 1220 is an operation button for instructing generation of the state transition information 426 based on the value set in the setting information input field 1210. In this embodiment, the user sets a value in at least the target device ID input field 1213 and operates the START button 1220. In the definition information input field 1211, the state number input field 1214, and the period input field 1215, values are not necessarily input.

The state transition information display column 1240 is a column for displaying the state transition information 426 generated by the state transition generation server 103. When a plurality of state transition information 426 exists, the plurality of state transition information 426 is displayed in a tab format as shown in FIG. In the state transition information display field 1240, various parameters used when the state transition information 426 is generated may be displayed together. In the state transition information display field 1240 of FIG. 12, the state transition information 426 is displayed in a graph format. A reference message is displayed in the state transition information display field 1240 in FIG.

The display switching selection column 1230 is a selection column for changing the display format of the state transition information 426 displayed in the state transition information display column 1240. The display switching selection field 1230 in FIG. 12 includes radio buttons for switching the state color and the state alignment method in the state transition information 426 in the graph format.

The OK button 1250 is an operation button for determining the state transition information 426 stored in the nonvolatile storage unit 411 from among the plurality of state transition information 426. When the user operates a predetermined tab and operates an OK button 1250, state transition information 426 corresponding to the tab is stored in the nonvolatile storage unit 411.

The display screen 1300 shows an example of a CUI.

The line 1301 corresponds to a command instructing generation of the state transition information 426. The command includes various parameters used when the state transition information 426 is generated. In FIG. 13, the date and time, the reference message definition information 427, the identifier of the apparatus 101, and the granularity information are included.

Line 1302 shows the generated state transition information 426. In FIG. 13, three pieces of state transition information 426 are displayed.

The line 1303 corresponds to a command for selecting the state transition information 426 stored in the nonvolatile storage unit 411. FIG. 13 shows that the state transition information 426 of “pattern03” is selected.

The input / output unit 421 receives various types of information via the display screen 1200 or the display screen 1300 (step S1101). When receiving the process start instruction, the input / output unit 421 issues a process start request to the state transition information generation unit 423 (step S1102). For example, the input / output unit 421 issues a process start request to the state transition information generation unit 423 when the START button 1220 is operated.

When the state transition information generation unit 423 receives the processing start request, the state transition information generation unit 423 issues a read request for the reference message definition information 427 to the nonvolatile storage unit 411 (step S1103).

The non-volatile storage unit 411 outputs the reference message definition information 427 designated by the user to the state transition information generation unit 423 when receiving the read request (step S1104). The state transition information generation unit 423 temporarily stores the received reference message definition information 427 in the volatile storage unit 410.

Note that if the user does not specify the reference message definition information 427, the processing in step S1103 and step S1104 is omitted.

The state transition information generation unit 423 transmits a message acquisition request to the data store management unit 312 of the data store server 102 via the message acquisition unit 422 (step S1105). The message acquisition request includes at least the identifier of the target device 101. When the user specifies a period of a message to be acquired in the period input field 1215 of the display screen 1200, the message acquisition request includes information on the period.

The data store management unit 312 reads the message of the target device 101 from the event log 321 and transmits operation information including the read message to the state transition generation server 103 (step S1106). The state transition information generation unit 423 acquires the operation information transmitted from the data store server 102 via the message acquisition unit 422. The state transition information generation unit 423 temporarily stores the acquired operation information in the volatile storage unit 410.

The state transition information generation unit 423 executes state transition information generation processing after the operation information including a plurality of messages is acquired (step S1107). Details of the state transition information generation processing will be described with reference to FIG. As a result of the state transition information generation process, one or more state transition information 426 is generated. At this time, the generated state transition information 426 is temporarily stored in the volatile storage unit 410.

The state transition information generation unit 423 outputs one or more state transition information 426 generated in the input / output unit 421 (step S1108). The input / output unit 421 displays the generated state transition information 426 in the state transition information display field 1240. The user refers to the state transition information 426 displayed on the display screen 1200 or the display screen 1300, and selects the state transition information 426 to be stored in the nonvolatile storage unit 411.

When the state transition information 426 is selected by the user (step S1109), the input / output unit 421 issues a storage request for the selected state transition information 426 to the state transition information generation unit 423 (step S1110).

When the state transition information generation unit 423 receives a storage request, the state transition information generation unit 423 outputs the selected state transition information 426 to the nonvolatile storage unit 411 (step S1111).

The nonvolatile storage unit 411 stores the state transition information 426 and then responds to the state transition information generation unit 423 (step S1112).

FIG. 14 is a flowchart illustrating an example of state transition information generation processing executed by the state transition generation server 103 according to the first embodiment. FIG. 15 is a diagram illustrating an example of the state transition information 426 according to the first embodiment.

FIG. 14 describes a state transition information generation process when the reference message definition information 427 is not used.

The state transition information generation unit 423 generates a list of reference messages based on the operation information of the target device 101 (step S1401).

Specifically, the state transition information generation unit 423 analyzes the contents of a plurality of messages included in the operation information, and generates a list of reference messages based on the appearance frequency. For example, the state transition information generation unit 423 generates a list of reference messages by extracting messages that appear above a predetermined threshold and sorting the extracted messages in order of frequency. Note that the state transition information generation unit 423 may extract a low-frequency message as a reference message.

Next, the state transition information generation unit 423 starts a loop process for the reference message (step S1402).

Specifically, the state transition information generation unit 423 selects one reference message from the list of reference messages. For example, the state transition information generation unit 423 selects the reference messages in descending order of frequency. Note that the state transition information generation unit 423 may select the reference messages in ascending order of frequency.

Next, the state transition information generation unit 423 generates scenario information 424 based on the operation information of the target device 101 and the selected reference message (step S1403). Specifically, the following processing is executed.

The state transition information generation unit 423 sorts the plurality of messages included in the operation information in chronological order, and divides the operation information into a plurality of message groups based on the reference message. In this embodiment, the reference message is handled as the last message included in the scenario. That is, the state transition information generation unit 423 divides a plurality of messages included between a certain message and a reference message as one message group. One divided message group corresponds to one scenario. The state transition information generation unit 423 assigns an identifier (scenario identifier) to each of the divided message groups.

Note that the operation information dividing method based on the reference message is not limited to the method described above. For example, the reference message may be treated as the first message included in the scenario. In this case, the state transition information generation unit 423 divides a plurality of messages included between the reference message and the message immediately before the next reference message as one scenario.

The state transition information generation unit 423 selects one scenario. The state transition information generation unit 423 generates empty scenario information 424 and assigns the identifier of the target device 101 and the scenario identifier to the scenario information 424.

The state transition information generation unit 423 calculates the number of messages included in one scenario. The state transition information generation unit 423 generates nodes as many as the number of messages, and defines the nodes as one state. That is, the state transition information generation unit 423 generates entries for the number of messages in the scenario information 424, and sets an identifier in the state ID 801 of each entry.

The state transition information generation unit 423 generates an edge connecting nodes. For example, the state transition information generation unit 423 generates an edge between the node having the identifier “St1” and the node having the identifier “St2”. The state transition information generation unit 423 registers edge information in the scenario information 424. That is, the state transition information generation unit 423 sets the identifier of the connection destination node in the connection destination state ID 802 of the entry corresponding to each node. Thereby, the edge and the direction of the edge are set.

Note that since there is no node to be connected to the terminal node, the connection destination state ID 802 of the entry corresponding to the node is blank.

The state transition information generation unit 423 associates one message with the edge. That is, the state transition information generation unit 423 sets the content of one message in the output message 803 of one entry. For each edge, the contents of the message are set in the output message 803 so that the order of the edges corresponds to the time series of the messages.

For example, the edge connecting the first node and the second node is associated with the content of the first message in time series. In the following description, a message input to a certain node (state) is described as an input message, and a message output from a certain node (state) is described as an output message.

Through the above processing, the state transition information generation unit 423 sets values for all entries. Note that the connection destination state ID 802 of the entry corresponding to the terminal node remains blank.

The state transition information generation unit 423 executes the above-described processing for all scenarios. As a result, scenario information 424 for all scenarios is generated. The above is the description of the process in step S1403.

Next, the state transition information generation unit 423 executes a scenario integration process for integrating the states of a plurality of scenarios (step S1404). Scenario integration information 425 is generated from a plurality of scenario information 424 by scenario integration processing. Details of the scenario integration processing will be described with reference to FIG.

Next, the state transition information generation unit 423 determines whether or not the integrated state included in the scenario integration information 425 needs to be integrated (step S1405). Specifically, the following processing is executed.

The state transition information generation unit 423 determines whether information specifying the number of states is input. For example, the state transition information generation unit 423 determines whether or not the granularity information is held.

When it is determined that the granularity information is not held, the state transition information generation unit 423 determines that it is not necessary to integrate the integrated state included in the scenario integration information 425.

When it is determined that the granularity information is held, the state transition information generation unit 423 determines whether or not the number of integrated states included in the scenario integration information 425 is smaller than the value included in the granularity information.

When the number of integration states included in the scenario integration information 425 is smaller than the value included in the granularity information, the state transition information generation unit 423 determines that it is not necessary to integrate the integration states included in the scenario integration information 425.

If the number of integration states included in the scenario integration information 425 is equal to or greater than the value included in the granularity information, the state transition information generation unit 423 determines that the integration states included in the scenario integration information 425 need to be integrated. The above is the description of the processing in step S1405.

If it is determined that it is not necessary to integrate the integration state included in the scenario integration information 425, the state transition information generation unit 423 proceeds to step S1407.

When it is determined that the integration state included in the scenario integration information 425 needs to be integrated, the state transition information generation unit 423 executes state integration processing for integrating the integration state included in the scenario integration information 425 ( Step S1406). With the state integration process, the granularity of the state transition information 426 can be adjusted. Details of the state integration processing will be described with reference to FIG.

If step S1405 is NO or after the state integration process is executed, the state transition information generation unit 423 generates a state transition from the terminal state to the starting state (step S1407).

Specifically, the state transition information generation unit 423 sets the identifier of the integrated state at the start end in the connection destination integrated state ID 1002 of the entry corresponding to the integrated state at the end of the scenario integrated information 425.

The process in step S1407 is a process for generating state transition information 426 corresponding to an analysis process such as the time for transition from the terminal integrated state to the starting integrated state, the behavior of the apparatus 101, and the like. Therefore, the process of step S1407 is not necessarily executed. In this case, the presence or absence of the process in step S1407 may be designated based on the user's selection.

Next, the state transition information generation unit 423 determines whether or not the number of generated scenario integration information 425 is equal to or greater than a predetermined threshold (step S1408). In this embodiment, it is assumed that the number of scenario integration information 425 to be generated is set in the state transition generation server 103 in advance. The threshold value may be updated as appropriate by the user.

When it is determined that the number of generated scenario integration information 425 is equal to or greater than a predetermined threshold, the state transition information generation unit 423 exits the loop and ends the state transition information generation process.

When it is determined that the number of generated scenario integration information 425 is smaller than a predetermined threshold, the state transition information generation unit 423 determines whether or not processing has been completed for all reference messages (step S1409).

If it is determined that the processing has not been completed for all the reference messages, the state transition information generation unit 423 returns to step S1402 and executes the same processing.

If it is determined that the processing has been completed for all the reference messages, or if step S1408 is YES, the state transition information generation unit 423 generates state transition information 426 based on the scenario integration information 425 (step S1410). Thereafter, the state transition information generation unit 423 ends the state transition information generation process.

Specifically, the state transition information generation unit 423 generates the state transition information 426 by converting the scenario integration information 425 into a predetermined data format. For example, the state transition information generation unit 423 generates state transition information 426 in a JSON (Java Script Object Notification) format as shown in FIG.

Note that the state transition information generation unit 423 may generate the scenario integration information 425 as the state transition information 426 as it is.

FIG. 14 illustrates the state transition information generation processing when the reference message definition information 427 is not used. Here, the state transition information generation processing when the reference message definition information 427 is used will be described. When the reference message definition information 427 is used, since the reference message is uniquely determined, the processing in step S1401, the processing in step S1408, and the reference message loop processing are not executed. Other processing is the same.

FIG. 16 is a flowchart illustrating an example of a scenario integration process executed by the state transition generation server 103 according to the first embodiment.

The state transition information generation unit 423 selects one scenario from a plurality of scenarios (step S1601). Furthermore, the state transition information generation unit 423 generates scenario integration information 425 based on the scenario information 424 of the selected scenario (step S1602).

Specifically, the state transition information generation unit 423 copies the contents of the scenario information 424 of the selected scenario to the empty scenario integration information 425. At this time, the state transition information generation unit 423 assigns an integrated state identifier to each state, and sets the integrated state identifier in the integrated state ID 1001 and the connection destination integrated state ID 1002. In addition, the state transition information generation unit 423 calculates the distance from the start state and the distance from the end state for each state, and calculates the distances calculated as the distance (start end) 1004 and the distance (end) 1005. Set.

Next, the state transition information generation unit 423 starts a scenario loop process (step S1603).

Specifically, the state transition information generation unit 423 selects one scenario that is not integrated. Hereinafter, the scenario selected in step S1603 is also referred to as a selected scenario.

Next, the state transition information generation unit 423 starts a loop process of the selected scenario state (step S1604).

Specifically, the state transition information generation unit 423 selects one state entry from the scenario information 424 of the selected scenario. In the following description, the state selected in step S1604 is also referred to as a selected state. At this time, the state transition information generation unit 423 calculates the distance from the start state and the distance from the end state for the selected state.

Next, based on the scenario information 424 and scenario integration information 425 of the selected scenario, the state transition information generation unit 423 determines whether there is an integrated state that is the same as the selected state (step S1605). Specifically, the following processing is executed.

The state transition information generation unit 423 refers to the scenario information 424 of the selected scenario and identifies the input message and output message of the selected state. The state transition information generation unit 423 refers to the scenario integration information 425 and searches for an integrated state where the input message matches the specified input message and the output message matches the specified output message.

When there is no integrated state that satisfies the above-described conditions, the state transition information generation unit 423 determines that there is no integrated state having the same state as the selected state.

When there is an integrated state that satisfies the above-described conditions, the state transition information generation unit 423 determines that the distance (starting edge) 1004 of the integrated state is the same as the distance from the starting state of the selected state, or the distance of the integrated state ( It is determined whether or not (end) 1005 is the same as the distance from the selected end state.

If the conditions described above are not satisfied, the state transition information generation unit 423 determines that there is no integrated state that is the same as the selected state. When the conditions described above are satisfied, the state transition information generation unit 423 determines that an integrated state having the same state as the selected state exists.

When the status is integrated based on the rules described above, the input message and output message of the integrated status are all the same. Therefore, even when there are a plurality of input messages and output messages in an integrated state, the above-described determination criteria may be applied to a combination of one input message and output message.

In addition, if the state is integrated based only on the input message and the output message, an incorrect state transition may be generated. Therefore, by integrating the states in which the input message and the output message are the same and the distance from the start end is the same or the distance from the end is the same, the risk of generating an illegal state transition is reduced. be able to. The above is the description of the processing in step S1605.

If it is determined that an integrated state having the same state as the selected state exists, the state transition information generating unit 423 integrates the selected state into the integrated state having the same state (step S1606). Thereafter, the state transition information generation unit 423 proceeds to step S1608. In step S1606, the following processing is executed.

The state transition information generation unit 423 adds one row to the connection destination integrated state ID 1002 of the entry corresponding to the searched integrated state, and sets the value of the connection destination state ID 802 of the entry corresponding to the selected state to the added row. Set. The state transition information generation unit 423 adds one line to the output message 1003 of the entry, and sets the value of the output message 803 of the entry corresponding to the selected state in the added line.

Furthermore, the state transition information generation unit 423 refers to each entry and searches for a row in which the value of the state ID 801 of the entry corresponding to the selected state is set in the connection destination integrated state ID 1002. The state transition information generation unit 423 sets the identifier of the integrated state in which the selected state is integrated in the connection destination integrated state ID 1002 of the searched row. The above is the description of the processing in step S1606.

When it is determined that there is no integrated state having the same state as the selected state, the state transition information generating unit 423 registers the selected state in the scenario integrated information 425 as a new integrated state (step S1607). Thereafter, the state transition information generation unit 423 proceeds to step S1608. In step S1607, the following processing is executed.

The state transition information generation unit 423 gives an integrated state identifier to the selected state. The state transition information generation unit 423 adds a new entry to the scenario integration information 425, and sets the identifier assigned to the selected state in the integration state ID 1001 of the added entry.

The state transition information generation unit 423 sets the value of the connection destination state ID 802 of the entry corresponding to the selected state in the connection destination integrated state ID 1002 of the added entry. The state transition information generation unit 423 sets the value of the output message 803 of the entry corresponding to the selected state in the output message 1003 of the added entry.

The state transition information generation unit 423 refers to each entry and searches for a row in which the value of the state ID 801 of the entry corresponding to the selected state is set in the connection destination integrated state ID 1002. The state transition information generation unit 423 sets the identifier assigned to the selected state in the connection destination integrated state ID 1002 of the searched row. The above is the description of the processing in step S1607.

After the processing of step S1606 or step S1607 is executed, the state transition information generation unit 423 determines whether or not processing has been completed for all states included in the selected scenario (step S1608).

If it is determined that the processing has not been completed for all states included in the selected scenario, the state transition information generation unit 423 returns to step S1604 and executes the same processing.

If it is determined that the processing has been completed for all states included in the selected scenario, the state transition information generation unit 423 determines whether the processing has been completed for all scenarios (step S1609).

If it is determined that the processing has not been completed for all scenarios, the state transition information generation unit 423 returns to Step S1603 and executes the same processing.

If it is determined that the processing has been completed for all scenarios, the state transition information generation unit 423 ends the scenario integration processing. Through the above processing, the scenario integrated information 425 shown in FIG. 10A is generated from the scenario information 424 shown in FIGS. 8A and 8B. Note that the state transition information generation unit 423 deletes the distance (start end) 1004 and the distance (end end) 1005 from the scenario integration information 425 before starting the state integration processing.

In the scenario integration process shown in FIG. 16, the state transition information generation unit 423 compares the two scenarios and integrates the two scenario information 424, but the present invention is not limited to this. For example, the state transition information generation unit 423 may integrate a plurality of scenarios by selecting a target integrated state from one scenario and searching for an integrated state having the same state as the selected integrated state.

FIGS. 17A and 17B are flowcharts for explaining an example of the state integration process executed by the state transition generation server 103 according to the first embodiment.

The state transition information generation unit 423 generates a list of integrated states based on the analysis result of the operation information of the target device 101 (step S1701). Specifically, the following processing is executed.

The state transition information generation unit 423 generates an empty integrated state list. The state transition information generation unit 423 analyzes the contents of a plurality of messages included in the operation information, and generates a message list by sorting the messages included in the message group based on the appearance frequency. It is assumed that the message list includes a plurality of entries including message contents and appearance frequency.

The state transition information generation unit 423 selects one entry in order from the entry on the message list. The state transition information generation unit 423 extracts the entry in the integrated state in which the output message 1003 of the scenario integration information 425 matches the content of the message of the selected entry.

The state transition information generation unit 423 registers an entry in which the integrated state ID 1001 of the extracted entry and the appearance frequency of the message are associated with each other in the integrated state list.

The state transition information generation unit 423 executes the same processing for all messages included in the message list. As a result, a list of integrated states is generated so as to correspond to the appearance frequency of messages. The above is the description of the processing in step S1701.

Next, the state transition information generation unit 423 starts an integrated state loop process (step S1702). Specifically, the following processing is executed.

The state transition information generation unit 423 selects one integrated state from the integrated state list. At this time, the state transition information generation unit 423 refers to the integration state ID 1001 of the scenario integration information 425 and determines whether or not an entry corresponding to the selected integration state exists in the scenario integration information 425.

When the entry corresponding to the selected integration state does not exist in the scenario integration information 425, the state transition information generation unit 423 selects another integration state from the integration state list. This is because when there is no entry corresponding to the selected integration state in the scenario integration information 425, the integration state has already been integrated with another integration state. In the following description, the integrated state selected in step S1702 is also referred to as a selected integrated state. The above is the description of the processing in step S1702.

Next, the state transition information generation unit 423 refers to the list of integrated states and determines whether or not there is an integrated state whose appearance frequency is the same as the appearance frequency of the selected integrated state (step S1703).

Specifically, the state transition information generation unit 423 refers to the entry of the selected integrated state in the integrated state list, and searches for an integrated state entry whose appearance frequency is the same as the appearance frequency of the selected integrated state. In the following description, an integrated state having the same appearance frequency is also described as a specific integrated state.

If it is determined that the specific integration state does not exist, the state transition information generation unit 423 determines whether the selected integration state is a single connection state based on the scenario integration information 425 (step S1704). Here, the single connection state is a state in which the number of integrated states connected via the input message is “1” and the number of integrated states connected via the output message is “1”. Indicates. Specifically, the following processing is executed.

The state transition information generation unit 423 refers to the scenario integration information 425 and determines whether or not the selected integration state is a terminal integration state.

When the selected integrated state is the terminal integrated state, the state transition information generation unit 423 determines that the selected integrated state is not a single connection state. This is because when the selected integrated state is the terminal integrated state, there is no integrated state whose time series is behind the terminal integrated state.

If the selected integrated state is not the terminal integrated state, it is determined whether the number of identifiers set in the connection destination integrated state ID 1002 of the selected integrated state entry is one.

When a plurality of identifiers are set in the connection destination integrated state ID 1002 of the entry of the selected integrated state, the state transition information generating unit 423 determines that the selected integrated state is not a single connection state.

When one identifier is set in the connection destination integration state ID 1002 of the entry of the selected integration state, the state transition information generation unit 423 has one entry in which the identifier of the selection integration state is stored in the connection destination integration state ID 1002. It is determined whether or not.

When there are a plurality of entries in which the identifier of the selected integrated state is stored in the connection destination integrated state ID 1002, the state transition information generation unit 423 determines that the selected integrated state is not a single connection state.

When there is one entry in which the identifier of the selected integrated state is stored in the connection destination integrated state ID 1002, the state transition information generation unit 423 determines that the selected integrated state is a single connection state. The above is the description of the process in step S1704.

If it is determined that the selected integration state is not a single connection state, the state transition information generation unit 423 proceeds to step S1712.

When it is determined that the selected integration state is a single connection state, the state transition information generation unit 423 starts a loop process of the related integration state (step S1705). Here, the related integration state indicates an integration state in which the time series is subsequent to the selected integration state, or an integration state in which the time series is in front and has a connection relationship with the selected integration state. Whether the time series is the previous integrated state or the time series is the subsequent integrated state is determined as a related integrated state based on the user's selection. Specifically, the following processing is executed.

The state transition information generation unit 423 refers to the scenario integration information 425 and searches for a connected state from the selected integrated state via an output message. The searched state becomes the related integrated state. The state transition information generation unit 423 generates a list of related integrated states. The state transition information generation unit 423 selects one entry from the list.

Note that the list of related integration states includes a plurality of entries including identifiers of related integration states. The entries in the list are sorted in the order of transition from the selected integrated state. That is, the list includes entries in order of generation, such as the order of the integration state directly connected to the selected integration state (first integration state) and the integration state directly connected to the first integration state (second integration state). Stored.

Next, the state transition information generation unit 423 determines whether or not the related integration state is a single connection state (step S1706). Note that the process of step S1706 is the same as the process of step S1704.

If it is determined that the related integration state is a single connection state, the state transition information generation unit 423 integrates the related integration state into the selected integration state (step S1707). Thereafter, the state transition information generation unit 423 proceeds to step S1709. Specifically, the following processing is executed.

The state transition information generation unit 423 acquires the connection destination integrated state ID 1002 and the value of the output message 1003 from the related integrated state entry.

The state transition information generation unit 423 sets the value of the connection destination integrated state ID 1002 acquired in the connection destination integrated state ID 1002 of the entry corresponding to the selected integration state. Further, the state transition information generation unit 423 adds the value of the acquired output message 1003 to the output message 1003 of the entry corresponding to the selected integration state.

That is, the connection destination integrated state ID 1002 is updated to the identifier of the integrated state connected to the related integrated state, and the output message of the related integrated state is added to the output message 1003. The above is the description of step S1707.

When it is determined that the related integration state is not a single connection state, the state transition information generation unit 423 determines whether or not the selected integration state has been integrated with the related integration state at least once (step S1708).

Specifically, the state transition information generation unit 423 determines whether or not the number of messages set in the output message 1003 of the entry corresponding to the selected integration state is “2” or more. If the number of messages set in the output message 1003 is “2” or more, it indicates that the selected integration state has been integrated with the related integration state at least once.

If it is determined that the selected integrated state is not integrated with the related integrated state, the state transition information generation unit 423 proceeds to step S1712.

When it is determined that the selected integrated state has been integrated with the related integrated state at least once, the state transition information generation unit 423 exits the related integrated state loop and proceeds to step S1710.

After the processing in step S1707, the state transition information generation unit 423 determines whether the processing has been completed for all related integration states (step S1709).

If it is determined that processing has not been completed for all related integration states, the state transition information generation unit 423 returns to step S1705 and executes similar processing.

If it is determined that the processing has been completed for all the related integration states, the state transition information generation unit 423 proceeds to step S1710.

In step S1710, the state transition information generation unit 423 determines whether or not the number of integrated states included in the scenario integration information 425 is smaller than a predetermined threshold (step S1710).

Specifically, the state transition information generation unit 423 determines whether the number of integrated states included in the scenario integrated information 425 is smaller than a value included in the granularity information.

If the number of integrated states included in the scenario integration information 425 is equal to or greater than a predetermined threshold, the state transition information generation unit 423 proceeds to step S1712.

When it is determined that the number of integrated states included in the scenario integration information 425 is smaller than a predetermined threshold, the state transition information generation unit 423 outputs the scenario transition information 425 to be converted into the state transition information 426 to the volatile storage unit 410. (Step S1711). Thereafter, the state transition information generation unit 423 ends the state integration process. For example, it is conceivable to add a flag indicating the conversion target to the scenario integration information 425.

In step S1712, the state transition information generation unit 423 determines whether or not the processing has been completed for all integrated states included in the integrated state list (step S1712).

When it is determined that the processing has not been completed for all the integration states included in the integration state list, the state transition information generation unit 423 returns to step S1702 and executes the same processing.

When it is determined that the processing has been completed for all the integration states included in the integration state list, the state transition information generation unit 423 ends the state integration processing.

When it is determined in step S1703 that the specific integration state exists, the state transition information generation unit 423 starts the loop processing of the specific integration state (step S1721). Specifically, the following processing is executed.

The state transition information generation unit 423 registers the selected integrated state and the searched integrated state in the specific integrated state list. The list of specific integration states includes a plurality of entries including integration state identifiers. The state transition information generation unit 423 selects one specific integrated state from the list of specific integrated states.

The state transition information generation unit 423 refers to the integration state ID 1001 of the scenario integration information 425 to determine whether an entry corresponding to the selected specific integration state exists in the scenario integration information 425.

When no entry corresponding to the selected specific integration state exists in the scenario integration information 425, the state transition information generation unit 423 selects another specific integration state from the list of specific integration states. The above is the description of the process in step S1721.

Next, based on the scenario integration information 425, the state transition information generation unit 423 determines whether the selected specific integration state is a single connection state (step S1722). The process in step S1722 is the same as the process in step S1704.

If it is determined that the selected specific integration state is not a single connection state, the state transition information generation unit 423 proceeds to step S1730.

When it is determined that the selected specific integration state is a single connection state, the state transition information generation unit 423 starts a loop process of the related integration state (step S1723). In steps S1723 to S1727, processing is executed for the related integration state of the selected specific integration state. The related integration state search method is the same as that in step S1705.

In step S 1723, the state transition information generation unit 423 generates a copy of the scenario integration information 425, and integrates the integration state using the copied scenario integration information 425. This is because in the loop processing in the specific integration state, a plurality of scenario integration information 425 having different integration states to be integrated is output.

Next, the state transition information generation unit 423 determines whether or not the related integration state is a single connection state (step S1724). Note that the process of step S1724 is the same process as step S1706.

When it is determined that the related integration state is a single connection state, the state transition information generation unit 423 integrates the related integration state into the specific integration state (step S1725). Thereafter, the state transition information generation unit 423 proceeds to step S1727.

The process of step S1725 is the same process as the process of step S1707. Further, the process of step S1727 is the same process as the process of step S1709.

When it is determined that the related integration state is not a single connection state, the state transition information generation unit 423 determines whether or not the specific integration state has been integrated with the related integration state at least once (step S1726). The process of step S1726 is the same process as the process of step S1708.

If it is determined that the specific integration state is not integrated with the related integration state, the state transition information generation unit 423 proceeds to step S1730. When it is determined that the specific integration state has been integrated with the related integration state at least once, the state transition information generation unit 423 proceeds to step S1728.

In step S1728, the state transition information generation unit 423 determines whether or not the number of integrated states included in the scenario integration information 425 is smaller than a predetermined threshold (step S1728). The process of step S1728 is the same process as the process of step S1710.

When it is determined that the number of integrated states included in the scenario integration information 425 is smaller than a predetermined threshold, the state transition information generation unit 423 outputs the scenario transition information 425 to be converted into the state transition information 426 to the volatile storage unit 410. (Step S1729). Thereafter, the state transition information generation unit 423 proceeds to step S1730. The process of step S1729 is the same process as the process of step S1711.

In step S1730, the state transition information generation unit 423 determines whether or not the processing has been completed for all the specific integration states included in the specific integration state list (step S1730).

When it is determined that the processing has not been completed for all the specific integration states included in the list of specific integration states, the state transition information generation unit 423 returns to step S1721 and executes the same processing.

When it is determined that processing has been completed for all the specific integration states included in the list of specific integration states, the state transition information generation unit 423 determines whether one or more scenario integration information 425 has been output (step S1731).

When it is determined that one or more scenario integration information 425 has not been output, the state transition information generation unit 423 performs integration for all the specific integration states (step S1732). Thereafter, the state transition information generation unit 423 proceeds to step S1710.

Specifically, the state transition information generation unit 423 updates the scenario integration information 425 by executing the processing from step S1723 to step S1727 for each specific integration state. Note that the state transition information generation unit 423 may generate one scenario integration information 425 by merging a plurality of scenario integration information 425 that is the processing result of each specific integration state.

When it is determined that one or more scenario integration information 425 has been output, the state transition information generation unit 423 ends the state integration processing. The state transition information generation unit 423 can change the granularity of the state transition information 426 by integrating the states included in the scenario integration information 425 based on the granularity information.

Here, the process of generating the state transition information 426 will be described with reference to FIGS. 18A, 18B, and 18C. 18A, 18B, and 18C are diagrams illustrating a process of generating the state transition information 426 according to the first embodiment.

Here, it is assumed that the scenario integration process and the state integration process are performed on the scenario as shown in FIGS. 8A and 8B. It is assumed that “7” is set in the state number input field 1214.

As a result of the scenario integration process, “S1_St1” and “S2_St1” are integrated, “S1_St2” and “S2_St2” are integrated, “S1_St6” and “S2_St6” are integrated, and “S1_St7” And “S2_St7” are integrated. Therefore, after the scenario integration process is executed, the scenario integration information 425 is in a state as shown in FIG. 18A.

As a result of executing the state integration process, “St4” and “St5” are integrated into “St3”, and “St9” and “St10” are integrated into “St8”. Therefore, after the state integration process is executed, the scenario integration information 425 is in a state as shown in FIG. 18B. Note that FIG. 10B corresponds to the scenario integration information 425 shown in FIG. 18B.

In Step S1407, when the transition from the terminal integrated state to the starting integrated state is generated, the scenario integrated information 425 becomes a state as shown in FIG. 18C.

As a result of the above processing, state transition information 426 as shown in FIG. 18C is generated.

19A and 19B are diagrams for explaining display examples of the state transition information display field 1240 according to the first embodiment.

When the display switching selection field 1230 is operated, the display method of the state transition information 426 in the state transition information display field 1240 is changed. Here, it is assumed that state transition information 426 as shown in FIG. 12 is displayed in the state transition information display field 1240 before the display switching selection field 1230 is operated.

When the “colored” radio button in the display switching selection field 1230 is operated, the input / output unit 421, as shown in FIG. 19A, state transition information in which the same color is given to the integrated state where the input message is the same. 426 is displayed. In FIG. 19A, the difference in the representation of the node frame is represented as a difference in color.

When the “Arranged” radio button in the display switching selection field 1230 is operated, the input / output unit 421 displays state transition information 426 in which the input messages are aligned in the same integrated state on the same line. When the “colored” and “aligned” radio buttons are operated, state transition information 426 as shown in FIG. 19B is displayed in the state transition information display field 1240.

As described above, the state transition generation server 103 can generate the state transition information 426 indicating the state transition of the device 101 using the message acquired from the device 101.

Thus, even if there is no manual of the device 101 and the state of the device 101 cannot be defined, the state transition information 426 of the device 101 can be generated. Further, the state transition generation server 103 can generate state transition information 426 with various granularities regardless of whether or not there is knowledge about the device 101. Therefore, even if a manual or the like of the apparatus 101 exists, the state transition information 426 having a granularity adapted to the analysis processing desired to be executed by the analysis server 104 can be generated.

In Example 1, the state transition generation server 103 generates a plurality of state transition information 426 for one device 101 and stores the state transition information 426 selected by the user in the nonvolatile storage unit 411. In the second embodiment, the state transition generation server 103 generates one state transition information 426 for one device 101, and stores the generated state transition information 426 in the nonvolatile storage unit 411.

Hereinafter, the second embodiment will be described focusing on the differences from the first embodiment.

Since the configuration of the computer system according to the second embodiment is the same as the configuration of the computer system according to the first embodiment, description thereof is omitted. The configurations of the device 101, the data store server 102, the state transition generation server 103, and the analysis server 104 of the second embodiment are the same as the configurations of the respective devices of the first embodiment, and thus description thereof is omitted.

In the second embodiment, the processing at the time of generating the state transition information 426 is partially different from the processing in the first embodiment.

FIG. 20 is a sequence diagram illustrating the flow of processing for generating the processing flow in the computer system when the state transition information 426 according to the second embodiment is generated.

The process flow from step S2001 to step S2007 is the same as the process flow from step S1101 to step S1107. Specifically, the processing flow is as follows.

The input / output unit 421 receives various types of information via a program execution command from the display screen 1200 or the display screen 1300 or another application (step S2001). When receiving the process start instruction, the input / output unit 421 issues a process start request to the state transition information generation unit 423 (step S2002).

When the state transition information generation unit 423 receives the processing start request, the state transition information generation unit 423 issues a read request for the reference message definition information 427 to the nonvolatile storage unit 411 (step S2003).

The non-volatile storage unit 411 outputs the reference message definition information 427 designated by the user to the state transition information generation unit 423 when receiving the read request (step S2004). The state transition information generation unit 423 temporarily stores the received reference message definition information 427 in the volatile storage unit 410.

The state transition information generation unit 423 transmits a message acquisition request to the data store management unit 312 of the data store server 102 via the message acquisition unit 422 (step S2005).

The data store management unit 312 reads the message of the target device 101 from the event log 321 and transmits operation information including the read message to the state transition generation server 103 (step S2006).

The state transition information generation unit 423 executes the state transition information generation process after obtaining the operation information (step S2007).

In the second embodiment, since one state transition information 426 is generated for one device 101, the user does not need to select. Therefore, after the state transition information generation process ends, the state transition information generation unit 423 outputs the generated state transition information 426 to the nonvolatile storage unit 411 (step S2008).

After storing the state transition information 426, the nonvolatile storage unit 411 responds to the state transition information generation unit 423 (step S2009).

When the state transition information generation unit 423 receives a response from the nonvolatile storage unit 411, the state transition information generation unit 423 outputs a completion notification to the input / output unit 421 (step S2010).

FIG. 21 is a flowchart illustrating an example of state transition information generation processing executed by the state transition generation server 103 according to the second embodiment.

FIG. 21 illustrates a state transition information generation process when the reference message definition information 427 is not used.

The state transition information generation unit 423 determines a reference message based on the message group of the target device 101 (step S2101).

Specifically, the state transition information generation unit 423 analyzes the content of the message and generates a list of reference messages based on the appearance frequency. The state transition information generation unit 423 selects one message having the highest appearance frequency or the lowest appearance frequency.

Next, the state transition information generation unit 423 generates scenario information 424 based on the operation information of the target device 101 and the determined reference message (step S2102). The process of step S2102 is the same as the process of step S1403.

Next, the state transition information generation unit 423 executes a scenario integration process for integrating the states of a plurality of scenarios (step S2103). The state transition information generation unit 423 determines whether or not the states included in the state transition information 426 need to be integrated (step S2104). The process in step S2104 is the same as the process in step S1405.

If it is determined that it is not necessary to integrate the states included in the state transition information 426, the state transition information generation unit 423 proceeds to step S2106.

When it is determined that the states included in the state transition information 426 need to be integrated, the state transition information generation unit 423 executes a state integration process for integrating the states included in the scenario integration information 425 (step S2105). ). The process in step S2105 is the same as the process in step S1405.

When step S2105 is NO or after the state integration process is executed, the state transition information generation unit 423 generates a state transition from the terminal state to the starting state (step S2106). The process in step S2106 is the same as the process in step S1407.

Next, the state transition information generation unit 423 generates state transition information 426 based on the generated scenario integration information 425 (step S2107). Thereafter, the state transition information generation unit 423 ends the state transition information generation process. The process in step S2107 is the same as the process in step S1410.

In the second embodiment, the reference message loop processing may also be executed. In this case, the state transition information generation unit 423 generates one state transition information 426 for one reference message, and stores the generated state transition information 426 in the nonvolatile storage unit 411.

Since the scenario integration process of the second embodiment is the same as the scenario integration process of the first embodiment, description thereof is omitted.

FIG. 22 is a flowchart illustrating an example of a state integration process executed by the state transition generation server 103 according to the second embodiment.

The state transition information generation unit 423 generates a list of integrated states based on the operation information of the target device 101 (step S2201). The state transition information generation unit 423 starts a loop process for the integrated state (step S2202). The process of step S2201 is the same as the process of step S1701. Further, the process of step S2202 is the same as the process of step S1702.

Next, based on the scenario integration information 425, the state transition information generation unit 423 determines whether or not the selected integration state is a single connection state (step S2203). The process in step S2203 is the same as the process in step S1704.

If it is determined that the selected integration state is not a single connection state, the state transition information generation unit 423 proceeds to step S2211.

When it is determined that the selected integration state is a single connection state, the state transition information generation unit 423 starts a loop process of the related integration state (step S2204). The process in step S2204 is the same as the process in step S1705.

Next, the state transition information generation unit 423 determines whether or not the related integration state is a single connection state (step S2205). The process in step S2205 is the same as the process in step S1706.

When it is determined that the related integrated state is a single connection state, the state transition information generation unit 423 integrates the related integrated state into the selected integrated state (step S2206). Thereafter, the state transition information generation unit 423 proceeds to step S2208. The process in step S2206 is the same as the process in step S1707.

When it is determined that the related integration state is not a single connection state, the state transition information generation unit 423 determines whether or not the selected integration state is integrated with another integration state at least once (step S2207). The process in step S2207 is the same as the process in step S1708.

If it is determined that the selected integration state is not integrated with the related integration state, the state transition information generation unit 423 proceeds to step S2211.

When it is determined that the selected integrated state has been integrated with the related integrated state at least once, the state transition information generation unit 423 exits the related integrated state loop and proceeds to step S2209.

After the process of step S2206, the state transition information generation unit 423 determines whether or not the process has been completed for all related integration states (step S2208). The process in step S2208 is the same as the process in step S1709.

If it is determined that the processing has not been completed for all the related integration states, the state transition information generation unit 423 returns to step S2204 and executes the same processing.

If it is determined that the processing has been completed for all related integration states, the state transition information generation unit 423 proceeds to step S2209.

In step S2209, the state transition information generation unit 423 determines whether or not the number of integrated states included in the scenario integration information 425 is smaller than a predetermined threshold (step S2209). The process in step S2209 is the same as the process in step S1710.

If the number of integrated states included in the scenario integration information 425 is equal to or greater than a predetermined threshold, the state transition information generation unit 423 proceeds to step S2211.

When it is determined that the number of integrated states included in the scenario integration information 425 is smaller than a predetermined threshold, the state transition information generation unit 423 outputs the scenario transition information 425 to be converted into the state transition information 426 to the volatile storage unit 410. (Step S2210). Thereafter, the state transition information generation unit 423 ends the state integration process. The process in step S2210 is the same as the process in step S1711.

In step S2211, the state transition information generation unit 423 determines whether or not processing has been completed for all integrated states included in the integrated state list (step S2211). The process of step S2211 is the same as the process of step S1712.

If it is determined that processing has not been completed for all integration states included in the integration state list, the state transition information generation unit 423 returns to step S2202 and executes similar processing.

In the second embodiment, the number of state transition information 426 generated is one, but is not limited to this. By setting the number of state transition information 426 to be generated in advance, the state transition generation server 103 can generate the set number of state transition information 426.

According to the second embodiment, the state transition generation server 103 can generate the state transition information 426 indicating the state transition of the device 101 using the message acquired from the device 101.

Moreover, since the state transition information 426 of the apparatus 101 is automatically generated, it is possible to reduce a user's operation burden and the like.

In addition, this invention is not limited to the above-mentioned Example, Various modifications are included. Further, for example, the above-described embodiments are described in detail for easy understanding of the present invention, and are not necessarily limited to those provided with all the described configurations. Further, a part of the configuration of each embodiment can be added to, deleted from, or replaced with another configuration.

In addition, each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit. The present invention can also be realized by software program codes that implement the functions of the embodiments. In this case, a storage medium in which the program code is recorded is provided to the computer, and a processor included in the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code itself and the storage medium storing it constitute the present invention. Examples of storage media for supplying such program codes include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs (Solid State Drives), optical disks, magneto-optical disks, CD-Rs, magnetic tapes, A non-volatile memory card, ROM, or the like is used.

Further, the program code for realizing the functions described in this embodiment can be implemented by a wide range of programs or script languages such as assembler, C / C ++, Perl, Shell, PHP, Java, and the like.

Furthermore, by distributing the program code of the software that realizes the functions of the embodiments via a network, the program code is stored in a storage means such as a hard disk or memory of a computer or a storage medium such as a CD-RW or CD-R. A processor included in the computer may read and execute the program code stored in the storage unit or the storage medium.

In the above-described embodiments, the control lines and information lines indicate those that are considered necessary for the explanation, and do not necessarily indicate all the control lines and information lines on the product. All the components may be connected to each other.

Claims

A computer that generates state transition information indicating the transition of the operating state of the device,
The calculator is
A processor, a memory connected to the processor, and an interface connected to the processor and connected to an external device;
A state transition information generating unit for generating the state transition information;
The state transition information generation unit
Obtain operational information including multiple messages indicating the operational status of the target device,
Generating a plurality of scenario information by dividing the operation information for each scenario corresponding to one state transition pattern of the target device,
A computer that generates the state transition information indicating all state transitions of the target device by integrating the plurality of scenario information.
The computer according to claim 1,
The state transition information generation unit
Determining a reference message as a reference for dividing the operation information;
Based on the reference message, the operation information is divided into the plurality of scenarios,
Generating one node for one message included in the scenario, and defining the plurality of nodes as the state of the device;
Generating an edge connecting the plurality of nodes, associating the message output from the node with the plurality of edges,
Generating the scenario information including a plurality of entries associated with the identifier of the node, the identifier of the node to which the node is connected, and the message output from the node;
Among the plurality of nodes included in each of the plurality of scenario information, the plurality of scenario information is integrated by integrating a plurality of nodes in which the input message and the output message are the same. Generate scenario integration information,
The computer that generates the state transition information based on the scenario integration information.
The computer according to claim 2,
The state transition information generation unit
With reference to the scenario integration information, a single connected node connected to one of the nodes via an input message and connected to one of the nodes via an output message is searched.
The computer is characterized in that the state transition information is generated by integrating the plurality of single-connected nodes.
The computer according to claim 3, wherein
The state transition information generation unit
Holds granularity information indicating the granularity of the state transition information,
A computer that adjusts the number of the single connected nodes to be integrated based on the granularity information.
A computer according to claim 2 or claim 3, wherein
The state transition information generation unit
Analyzing the operational information,
The computer, wherein the reference message is determined based on the appearance frequency of the message.
A computer according to claim 2 or claim 3, wherein
The state transition information generation unit
After the scenario integration information is generated, the state transition information including the state transition from the termination node to the start node is generated by generating an edge from the termination node to the start node included in the scenario integration information A computer characterized by
A computer according to claim 2 or claim 3, wherein
A computer comprising: an input / output unit that generates display information for presenting the state transition information to a user.
A method for generating state transition information of a computer that generates state transition information indicating a transition of an operating state of a device,
The calculator is
A processor, a memory connected to the processor, and an interface connected to the processor and connected to an external device;
The method for generating the state transition information is as follows:
A first step in which the processor acquires operation information including a plurality of messages indicating an operation state of a target device, and stores the operation information in the memory;
The processor generates a plurality of scenario information by dividing the operation information for each scenario corresponding to one state transition pattern of the target device, and stores the plurality of scenario information in the memory And the steps
A third step in which the processor generates the state transition information indicating all the state transitions of the target device by integrating the plurality of scenario information, and stores the state transition information in the memory; A state transition information generation method characterized by comprising:
The state transition information generation method according to claim 8,
The second step includes
A fourth step in which the processor determines a reference message as a reference for dividing the operation information;
A fifth step in which the processor divides the operation information into the plurality of scenarios based on the reference message;
A sixth step in which the processor generates one node for one message included in the scenario and defines the plurality of nodes as the state of the device;
A seventh step in which the processor generates an edge connecting the plurality of nodes, and associates the message output from the node with the plurality of edges;
An eighth step in which the processor generates the scenario information including a plurality of entries associated with an identifier of the node, an identifier of the node to which the node is connected, and the message output from the node; Including
The third step includes
The processor integrates a plurality of nodes having the same input message and a plurality of output messages out of the plurality of nodes included in each of the plurality of scenario information. Generating scenario integration information integrated with
And a step of generating the state transition information based on the scenario integration information. The method for generating state transition information.
The method for generating state transition information according to claim 9,
The third step includes
The processor refers to the scenario integration information, and searches for a single connected node connected to one of the nodes via an input message and connected to one of the nodes via an output message. And the steps
And a tenth step in which the processor generates the state transition information by integrating the plurality of single-connected nodes.
The state transition information generation method according to claim 10,
The computer holds granularity information indicating the granularity of the state transition information,
The tenth step includes a step in which the processor adjusts the number of the single connected nodes to be integrated based on the granularity information.
A method for generating state transition information according to claim 9 or claim 10, wherein:
The fourth step includes
The processor analyzing the operation information;
And a step of determining the reference message based on the frequency of appearance of the message.
A method for generating state transition information according to claim 9 or claim 10, wherein:
In the third step, after the scenario integration information is generated, the processor generates an edge from the end node to the start node included in the scenario integration information, thereby causing the end node to the start node. A step of generating the state transition information including the state transition information including the step of generating the state transition information.
A method for generating state transition information according to claim 9 or claim 10, wherein:
A method for generating state transition information, wherein the processor includes a step of generating display information for presenting the state transition information to a user.