JP2008021095A - Cooperation scenario preparation support system, method thereof and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a cooperation scenario preparation support system enabling even a general user having no knowledge in Web or a computer to prepare a cooperation scenario by connecting service elements. <P>SOLUTION: The cooperation scenario preparation support system comprises: a service element database 17 for supporting the preparation of a cooperation scenario for cooperating service elements and storing service element information including the contents of service and input and output information; a service element connection information preparation part 15 for reading out the service element information from the database 17 and writing connection information between the output and input information of service elements which is generated by a user on the basis of the read service element information in a connection information database 18; a scenario preparation part 14 for setting the calling order of service elements; and a scenario sentence generation verification part 19 for reading out connection information corresponding to the combination of the output information and input information of respective continued service elements while referring to the connection information database 18, and inserting the read connection information between the service elements to generate a cooperation scenario. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a cooperation scenario creation support system, method and program for supporting creation of cooperation scenarios widely used by users when executing services by linking element services constituting services distributed on a network.

In recent years, service cooperation technology has attracted attention as one of the technologies for realizing SOA (Service Oriented Architecture). The services linked here define a Web service interface based on technical specifications described in WSDL (Web Services Description Language), a service interface based on UP & P (Universal Plug and Play) specifications, and SOAP (Simple Object Access). Protocol: A function for sending and receiving messages according to an international standardization organization W3C (Technical specifications defined by the World Wide Web Consortium).
A workflow for executing these interface-defined services sequentially or in parallel, that is, a cooperation scenario, is executed in accordance with the description by the scenario execution engine.

Then, the interface-defined service that the scenario execution engine refers to and calls based on the cooperation scenario is referred to as an element service in the following description.
Generally, BPEL (Business Process Execution Language) or the like is used as a workflow description language for describing a complex workflow using a Web service.
Since the scenario execution engine executes a workflow based on the description by BPEL, it is also called a BPEL engine.

  In addition to a system using BPEL, a system having a function of discovering an intermediary service and synthesizing the element service including the intermediary service when the interface matching between the scenario execution engine and the element service cannot be achieved. (For example, refer to Patent Document 1), and a system (for example, refer to Patent Document 2) that enables dynamic adaptation to other service elements having equivalent functions in the same area where element services are provided.

By using these systems, it is possible to use a cooperation scenario combining element services.
However, in order to create a cooperation scenario, knowledge of Web services such as element service interface information and service element description method is required, and a programming ability to describe a flow between element services in the cooperation scenario is required. For this reason, it is difficult and difficult for a general user to create a program that describes a flow between element services in a cooperation scenario.

In addition, there is a system (for example, see Patent Document 3) that makes the processing related to the interface information (input / output parameters) of the element service more efficient using a parameter form, but the necessity of describing a cooperation scenario still remains. .
JP 2005-071052 A JP-A-2005-250844 Japanese Patent Laying-Open No. 2005-332122

In recent years, it is becoming popular to create new services by combining various services by users themselves.
At present, users who create the above services have relatively knowledge of computers and Web services, but other ordinary users can link multiple element services in succession and execute them as complex processes. It does not have the ability to create scenarios (cooperation services) by itself.
The present invention has been made in view of such circumstances, and even a general user who does not have knowledge about Web services, computers, etc., can select element services one by one and connect them freely and cooperate with each other. It is an object of the present invention to provide a cooperative scenario creation support system, method and program capable of creating a scenario.

  The cooperation scenario creation support system of the present invention is a cooperation scenario creation support system that supports creation of a cooperation scenario used when operating a plurality of element services that can be used via a network in cooperation with each other, Element service database storing element service information including service contents, input information and output information of each element service, and first and second specified by the user (for example, knowledge user 3 in the embodiment) from the element service database The element service information of the element service is read out, and based on these, between the output information of the first element service and the input information of the second element service generated by the user (for example, the knowledge user 3 in the embodiment) Element service connection information that performs the data flow of the element service connection information database Element service connection information creation unit to be written, and element services selected sequentially according to the cooperation scenario flow diagram displayed on the screen by the user (for example, knowledge user 3 and general user 4 in the embodiment) A scenario creation unit for setting the order, and element service connection information corresponding to a combination of output information and input information of each successive element service according to the calling order of the element services created by the scenario creation unit, the element service A scenario sentence generation verification unit corresponding to generating a linkage scenario by interleaving between element services and referring to the connection information database.

  The cooperation scenario creation support system of the present invention further includes a cooperation scenario database that stores the cooperation scenario generated by the scenario sentence generation verification unit, and the scenario preparation unit includes users (for example, the knowledge user 3 and the general user in the embodiment). The already generated cooperation scenario selected by the user 4) is read from the cooperation scenario database, and the order in which the already generated cooperation scenario is partially edited according to the cooperation scenario flow diagram displayed on the screen is changed. The element service call order is set.

  In the cooperation scenario creation support system of the present invention, the element service connection information creation unit compares the parameter name of the output information of the first element service with the parameter name of the input information of the second element service, The data flow is associated with the output information of the second element service and the input information of the second element service.

  In the cooperation scenario creation support system according to the present invention, the element service connection information creation unit includes meta information related to output information of the first element service and meta information related to input information of the second element service. The data flow is compared between the output information of the first element service and the input information of the second element service by comparing the information.

  The cooperation scenario creation support system of the present invention further includes a scenario execution engine that sequentially executes element services according to the cooperation scenario, and the scenario sentence generation verification unit causes the scenario execution engine to execute the created cooperation scenario. The service quality is confirmed by verifying the execution result of each element service.

  The cooperation scenario creation support method of the present invention is a cooperation scenario creation in a cooperation scenario creation support system that supports creation of a cooperation scenario used when operating a plurality of element services that can be used via a network in cooperation with each other. A storage method for storing element service information including service contents, input information, and output information of each element service in the element service database, and an element service connection information creation unit from the element service database to a user (for example, a support method) , The element service information of the first and second element services designated by the knowledge user 3) in the embodiment is read, and the user between the output information of the first element service and the input information of the second element service ( For example, the data flow generated by the knowledge user 3) in the embodiment is changed to the element service link. Element service connection information creation process to be written to the information database, and the scenario creation unit selects the element services sequentially selected by the user (for example, knowledge user 3 and general user 4 in the embodiment) according to the cooperative scenario flow diagram displayed on the screen. The scenario creation process for setting the calling order of the element services in the selected order, and the scenario statement generation / verification unit according to the calling order of the element services created by the scenario creation unit, output information and input of each successive element service It includes a scenario sentence generation process corresponding to generating a linkage scenario by reading element service connection information corresponding to a combination of information with reference to the element service connection information database.

  The cooperation scenario creation support method of the present invention includes a process of storing a cooperation scenario generated by a scenario sentence generation / verification unit and a cooperation scenario database, and the scenario creation unit includes users (for example, knowledge user 3 and general user in the embodiment). 4) The already generated cooperation scenario selected in 4) is read from the cooperation scenario database, and according to the cooperation scenario flow diagram displayed on the screen, the order in which the already generated cooperation scenario is partially edited and changed, And a process of setting as a calling sequence of element services.

The cooperation scenario creation support program of the present invention is a program for causing a computer to function as the cooperation scenario creation support system described above.
The recording medium of the present invention is a computer-readable recording medium that records the cooperation scenario creation support program.

As described above, according to the present invention, even a general user who does not have knowledge about Web services, computers, etc., creates service scenarios by selecting service elements one by one and connecting them freely. It will be possible.
That is, according to the present invention, by realizing an environment in which a wide variety of users can easily create a linked service, the general user can experience the fun of creating a linked service and further create a linked service. Therefore, there is a possibility that a convenient linkage service for many users will be created.

As the number of cooperation services increases, a method for managing a plurality of cooperation services used by the user himself / herself is necessary. Considering the above reasons, a system that realizes the following three points is considered desirable.
That is, as an effect of the present invention,
First, a wide range of users can create collaborative services.
Secondly, it is possible to manage the services used by the user.
Third, the cooperation service created by the user can be reused by other users.

Hereinafter, a cooperation scenario creation support system according to an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a conceptual diagram showing the configuration of the cooperation scenario creation support system of the embodiment. FIG. 2 is a block diagram illustrating a functional configuration example of the cooperation scenario creation support system according to the embodiment.
As shown in FIG. 1, the element service 200 a constituting the element service group 200 can be used via the network I. Here, the service element 200a is an entity (also referred to as an entity) that can handle a target in a computer environment, and includes a process or data that can be used on the network I.
For example, provision of weather information and stock price information by a web service using a technology used between systems connected via the web such as the Internet communication network, and enterprise application integration between companies are realized. In addition, programs that provide various services over the network using JXTA, a general-purpose peer-to-peer (P2P) platform, are distributed over the network.

  Other examples of the service element 200a include components realized by EJB (enterprise Java (registered trademark) Beans) constituting Web services, contents such as video that can be accessed via the network, and network I. Computer environmental resources such as connected printers and displays, CPU resources indicating how much the computer is operating, network bandwidth indicating how much network is being used, and multiple services for realizing services on the network There are service templates that describe the order in which elements are provided. Also, software that runs on a server that is always connected is not the only service component. For example, software that operates on a portable terminal capable of a limited number of communications with other physically close users is also a service element. The network I is composed of the public including the Internet and a dedicated information communication network.

  The scenario execution engine 2 inputs the output information from the service providing apparatus that provides the Nth (N is a natural number) element service according to the order described in the cooperation scenario that is the workflow of the element service. Then, the process of transmitting as the input information of the service providing apparatus that executes the service element (N + 1) described in the cooperation scenario is repeated. Here, the scenario execution engine 2 is a core module of the platform, and after reading the cooperation scenario, checks the validity with an XML parser and executes the cooperation scenario. Also, when applied in an event-driven system, it is possible to execute the corresponding linkage scenario according to the event, and wait for execution when delegating the processing to the upper application process during execution.

The cooperation scenario creation support system 1 according to the present embodiment supports each process in the creation process when the knowledge user 3 and the general user 4 create a cooperation scenario executed by the scenario execution engine 2.
Here, the knowledge user 3 is a user who has some knowledge and skills related to the Web service, and is defined to be distinguished from a general user who only uses the Web service.
Further, as shown in FIG. 2, the cooperation scenario creation support apparatus 1 includes a scenario database 10, a user login unit 11, a selection unit 12, a scenario management / execution instruction unit 13, a scenario creation unit 14, and an element service connection information creation unit. 15, a search unit 16, an element service database 17, an element service connection information database 18, and a scenario sentence generation verification unit 19.

The scenario management / execution instructing unit 13, the scenario creating unit 14, and the element service connection information creating unit 15 can be used from the terminal of the general user 4 and the terminal of the knowledge user 3 via the network I.
The user login device 11 authenticates the user by comparing the password and ID (identification information) input by the knowledge user 3 or the general user 4 with the password and ID registered in advance, and the result of the authentication is registered. When it is detected that the user is a registered user, each support process in the subsequent scenario creation is executed. When it is detected that the user is not registered, the connection with the terminal is disconnected without performing the subsequent support process.

After the authentication, the selection unit 12 uses the selection information input from the terminal of the general user 4 or the terminal of the knowledge user 3 in the support process of the cooperation scenario creation support apparatus 1, the scenario management / execution instruction unit 13, the scenario creation unit 14 or the element service connection information creation unit 15 is selected.
The scenario management / execution instructing unit 13 performs a process of executing and stopping the cooperation scenario created by each user with respect to the scenario execution engine 2 connected via the network I.

  The element service connection information creating unit 15 determines the correspondence between the output information of the first element service at the first stage and the input information of the second element service at the second stage in the element services to be processed continuously. It is detected by comparing metadata such as tag information related to the type, parameter name, and parameter. Here, the data type includes class type, interface type, array type, value type, enumeration type, type parameter, generic type definition, and open construction generic type or closed construction generic type. Metadata is additional information added to resources for computer processing, and it is desirable to use a vocabulary in which a vocabulary language and a target word are shared.

In addition, the element service connection information creation unit 15 generates element service connection information for converting the format of the output information into the format of the input information in the associated output information and input information, that is, the element service connection information database in advance. The template read out from the template table set to 18 in correspondence with the combination of the format of the output information and the input information is used as element service connection information for performing the data format conversion process, and is associated with each element service combination. The service connection information database 18 is stored.
Alternatively, the knowledge user 3 associates output information and input information of each element service, and sets element service connection information for converting the format of the data between the output information and the input information. It may be generated by using an editor function, and may be stored in the element service connection information database 18 corresponding to each combination of element services.

The element service connection information may include a description that prescribes a process (method) in which the preceding element service (for example, element service A) calls the latter element service (for example, element service B).
That is, the element service connection information creation unit 15 includes the element service call method in the element service connection information and stores it in the element service connection information database 18 as meta information of each element service.
Here, the calling method of the element service is a calling instruction in a different cooperation scenario depending on whether the element service has only an input, only an output, or both an input and an output. The description process is required.
In addition, in the element service invocation method, is it necessary to describe the repetition structure such as the while statement and the judgment processing such as the if-then-else statement in the scenario statement in the linkage scenario as the characteristics of the element service? Contains information on whether or not.

The scenario creation unit 14 lists all the element services selected by each user in the order of the element services selected from the list of element services displayed on the display screen by the search unit 15, and element service connection information corresponding to the combination of element services. Is read from the element service connection information database 18 via the search unit 15.
The scenario sentence generation verification unit 19 generates a cooperation scenario by continuously describing element services and element service connection information corresponding to the combination of each element service, and the Web service executes the processing according to the cooperation scenario. If there is no problem, the cooperative scenario is stored in the scenario database 10 in association with the identification information.

Hereinafter, the operation of the cooperation scenario creation support system 1 according to the present embodiment will be described with reference to FIGS. FIG. 3 is a flowchart showing an operation example of the cooperation scenario creation support system 1 according to the present embodiment.
As described in FIG. 1, each element service of the element service group 200 can be used by each terminal of the knowledge user 3 and the general user 4 via the network I. Then, the scenario execution engine 2 executes each element service in the described order corresponding to the cooperation scenario for linking the element services described above. Similarly, the scenario management / execution instructing unit 13, the scenario creating unit 14, and the element service connection information creating unit 15 can be used from the terminals of the knowledge user 3 and general users via the network I.

The knowledge user 3 or the general user 4 accesses the cooperation scenario creation support system 1 via the network I with each terminal, and inputs a user name (ID) and a password.
As a result, the user login unit 11 sequentially compares a combination of a plurality of user names and passwords registered therein and a combination of the input user name and password, and detects the presence or absence of a matching combination. When a matching combination is detected, the user authentication is performed and the user's terminal is notified that the login is successful, and the user's terminal is set in the login state to the cooperation scenario creation support system 1. The process to proceed to step S102 (step S101).

Next, the selection unit 12 selects a knowledge user 3 or a general user 4 (hereinafter referred to simply as a user when referring to both) from a display screen by using a GUI (Graphical User Interface) according to an instruction displayed on the screen. Then, the process is shifted to the processing corresponding to the cooperation scenario creation support function of the cooperation scenario creation support system 1 (step S102).
That is, when the user selects a support process performed by any of the scenarios in the scenario creation unit 14, the scenario management / execution instruction unit 13 or the element service connection information creation unit 15, the selection unit 12 performs the process of the selected unit. Start up.
Hereinafter, operations when the element service connection information creation unit 15, the scenario creation unit 14, and the scenario management / execution instruction unit 13 are activated will be described.

<When the element service connection information creation unit 15 is activated>
In step S102, when the user (mainly knowledge user 3) selects the support process of the element service connection information creation unit 15 and the selection unit 12 activates the element service connection information creation unit 15, as shown below, the element Element service connection information for controlling data consistency of input / output information between services is generated. Further, the processing after step S131 and the functions of the element service connection information creation unit 15 are functions mainly used by users who have some knowledge and skills related to Web services (hereinafter referred to as general users 4 and referred to as knowledge users 3). It is.

The element service connection information creation unit 15 creates element service connection information and stores the creation result in the element service connection information database 18 corresponding to the combination of element services.
Here, the element service connection information database 18 stores a plurality of element service connection information shown in FIG. 4 corresponding to combinations of element services.
The element service connection information creation unit 15 displays a screen for creating element service connection information on the display screen of the terminal of the knowledge user 3 and stores each element service of the element service group 200 stored in the element service database 17. The functions, operations, input information, output information, and the like are associated with each other and displayed as a list on the display screen of the knowledge user 3 terminal (step S131).

Next, the knowledge user 3 selects the element service A and the element service B shown in FIG. 4 from the element services displayed on the display screen (step S132).
That is, when the element service A as the element service of the preceding stage and the element service B as the element service of the succeeding stage are selected, the element service connection information creating unit 15 formats the data (data) of the element service A and the element service B. Based on the format, element service connection information is created as a data flow for matching the data format from the output information of the element service A to the input information of the element service B. This element service connection information is composed of input / output parameter change processing corresponding to each combination of output information and input information in the combination of element service A and element service B.

  The element service corresponds to a Web service defined by OWL (Ontology Web Language) -S or WSDL, a UPnP (Universal Plug and Play) service, or an element service in Japanese Patent Laid-Open No. 2005-250844. It has the above inputs and zero or more outputs. The element service in Japanese Patent Laid-Open No. 2005-250844 provides functions and resources in a network environment such as the Internet communication network, and a method used from the remote (terminal) side can be acquired on the network. Each function and resource can be called remotely and used according to the method used.

  Here, UPnP is a technical specification for connecting devices such as personal computers, peripheral devices, AV devices, telephones, and home appliances in the home via a network and providing functions to each other. More than 20 companies such as Intel, 3Com, AT & T, Dell Computer, etc. It is based on the technology that is standard on the Internet, and aims to function without complicated operations and setting work simply by connecting to a network. As a network infrastructure, in addition to Ethernet (registered trademark), which is most widely used for personal computer LANs, standards for home LAN such as HomePNA and HomeRF are also supported.

The following is an example of element service in Japanese Patent Laid-Open No. 2005-250844.
First, a web service, a DCOM component, such as a translation web service, an authentication web service, an airline ticket reservation web service, a product order web service, a weather information web service, a location information provision web service, “Windows (registered trademark) Media Player”, There are element services realized from EJB.

In addition, devices that can be used remotely such as a display, speakers, sensors, washing machines, toasters, touch panels, electric fans, monitor cameras, and televisions connected to the remote side can be elemental services. Similarly, computer resources that can be used remotely such as a CPU processing capacity providing service and a disk storage service are also service elements.
In addition, network access capability that can be used remotely such as broadband Internet access service for in-house LAN and broadband wireless Internet access service to connect to ad hoc networks in various regions is also an element service.
Remotely available agents operating on the network, such as schedule adjustment agents and travel arrangement agents, are also element services.

Each element service described above inputs zero or more pieces of input information, performs a specific application process, and outputs zero or more pieces of output information.
Some element services provide a plurality of processes such as operations, methods, and primitive processes. Input and output may be defined for each process. Although effective, in the present embodiment, such a concept is omitted for the sake of simplicity.

As shown in FIG. 4, for example, the element service A has an input I_A1, an input I_A2, an output O_A3, and an output O_A4, and the element service B has an input I_B1, an input I_B2, an output O_B3, and an output O_B4.
The knowledge user 3 refers to the displayed input information and output information that the output O_A3 corresponds to the input I_B1 and the output O_A4 corresponds to the input I_B2 according to the screen guidance displayed on the display screen of the terminal. If this is detected, the correspondence relationship of this combination is input to the element service connection information creation unit 15, and the correspondence between the output and input of the previous and subsequent stages is instructed (step S133).

  At this time, the element service connection information creation unit 15 selects the output type of the element service A and the input type of the element service B in the input information and output information of the element service before and after the continuous description in the description statement of the cooperation scenario. Similarity, input parameters and output parameter names, similarity information indicating how much similarity is obtained by referring to and comparing metadata such as tag information related to input parameters and output parameters Or whether the output O_A3 corresponds to the input I_B1 and the output O_A4 corresponds to the input I_B2 when it is higher than the similarity threshold set by the user. Can also be displayed (recommended) on the display screen.

For example, when the output O_A3 is an address and the input I_B1 is longitude / latitude information, the element service connection information creation unit 15 can input the contents (data) of the output O_A3 in the same format as the input I_B1. It is detected by comparing the data formats of the output information and the input information.
Then, the element service connection information creation unit 15 converts, for example, address (or building or place name) data into latitude / longitude information data between the output O_A3 and the input I_B1. Since it is necessary to mediate (interpolate) A3_B1, whether or not this mediation is necessary is described in the element service connection information (step S133).

This input / output parameter conversion processing includes processing such as converting names to gender, and the difference between data and units of output information to be output and input information to be input, and differences in data representation formats. This is a process of converting the data format of the output information in accordance with the data format.
Further, this input / output parameter conversion processing may be previously set in the element service connection information database 18 for each combination of element services, or the knowledge user 3 may output information and input information for each combination of element services. It may be created while confirming the corresponding relationship.

Here, the necessity of mediating the input / output parameter conversion processing A3_B1 is determined by the element service connection information creation unit 15 analyzing input information, output information, and data, or an input displayed by the knowledge user 11 The element service connection information creating unit 15 may be actively instructed by comparing the information and the output information.
In addition, in the element service connection information, it is described that it is necessary to output to the display screen of the user terminal as additional information of the element service A and the element service B, for example, when the element service B is executed. Is done.
Similarly, the output O_A4 is associated with the input I_B2 through the input / output parameter conversion process A4_B2. That is, the element service connection information creating unit 15 needs to mediate the input / output parameter conversion process A4_B2 between the output O_A4 and the input I_B2, and therefore describes the necessity of this mediation in the element service connection information. To do.

As described above, the element service connection information inserted between the element service A and the element service B is expressed as a data input / output parameter conversion process of the element service A and the element service B as shown in FIG. .
Here, as in the collaboration scenario ST1 shown in FIG. 5A, from the element service A to the element service B, from the element service B to the element service C, from the element service C to the element service D, and from the element service B to the element service D. Element service connection information is also expressed in the same manner.
Then, the element service connection information creation unit 15 stores the element service connection information in the element service connection information database 18 (step S134).
In addition, when inserting the element service, the element service connection information creating unit 15 reads information on the method of calling the element service from the element service connection information database 18 corresponding to each element service, and the knowledge user 3 To be displayed on the terminal. Thereby, the knowledge user 3 can describe easily the process which calls an element service with respect to element service connection information.

<When scenario creation unit 14 is activated>
In step S102, when the user (knowledge user 3 or general user 4) selects the support process of the scenario creation unit 14 and the selection unit 12 activates the scenario creation unit 14, the scenario creation unit 14 is displayed as shown below. Is a functional unit that creates a cooperation scenario using the information of the element service connection information. Unlike the element service connection information creation unit 15, not only the knowledge user 3, but also a general user 4 who has no knowledge or skill about the Web service can use the function unit.

The scenario creation unit 14 displays a screen (step S122) that supports creation of a cooperation scenario on the display screen of the logged-in user's terminal (step S121).
Here, the scenario creation unit 14 starts the search unit 16, reads out available element services from the element service database 17, and displays them together with the function display in the GUI flow diagram (cooperation scenario flow diagram).
In addition, the scenario creation unit 14 uses the element service described in the GUI flow diagram for the user to use in the cooperation scenario according to the cooperation scenario creation procedure (the GUI flow diagram) displayed on the display screen of the terminal. Are sequentially selected in the order of element service A (S41) → element service B (S42) → element service C (S43) → element service D (S43), as shown in FIG. The reading of the element service of the cooperation scenario ST1 is finished (step S122).

As described above, in step S122, the general user 4 calls the element service A first after starting the creation of the cooperation scenario as shown in FIG. 6 according to the screen guidance of the terminal displayed by the scenario creation unit 14. The scenario creating unit 14 is instructed by selecting the element service A in the GUI flow diagram.
As a result, the scenario creation unit 14 reads the element service A selected by the user from the element service database 17.

  Here, the scenario creation unit 14 accesses the search unit 16 as needed to read the element service from the element service database 17. However, the scenario creation unit 14 knows what element services the general user 3 can use, and displays the element services that cannot be used on the GUI flow diagram. Without making it visible to the general user 3. For example, the scenario creation unit 14 may select a usable element service based on the passwords of the knowledge user 3 and the general user 4. Element services that cannot be used by the general user 3 include element services for which element service connection information is not set in a combination of element services.

Next, as shown in FIG. 6, the user calls the element service B next to the element service A according to the screen guidance of the scenario creation unit 14, and selects the element service B from the GUI flow diagram. The creation unit 14 is instructed.
As described above, the scenario creation unit 14 provides a GUI flow chart that visually supports creation of a cooperation scenario by GUI (Graphical user interface) in an Internet browser, a stand-alone program, or the like in screen guidance displayed on a user terminal. It is shown.

The GUI flow diagram may be based on BPMN (Business Process Modeling Notation) or UML (Unified Modeling Language), but the information related to parameter conversion processing described in the element service connection information and the element service A Additional information (meta information, etc.) used by a knowledgeable user such as knowledge user 3 possessed by the element service B is difficult information for the general user 4 and is therefore a normal screen unless otherwise specified. Not shown above (not visible).
An instruction to call the element service A or the element service B by the general user 4 selecting in the GUI flow diagram requires command input such as mouse click, drag, drop on the GUI flow diagram on the display screen of the terminal. It is possible to do so with a user interface that does not.

  That is, the general user 3 simply outputs an instruction to call the element service A and then call the element service B to the scenario creation unit 14 after the start of the creation of the cooperation scenario. As shown, an order setting process for creating a cooperation scenario and reading of element services from the element service database 17 are performed. Therefore, it is sufficient for the general user 4 to select an element service in the GUI flow diagram on the terminal display screen and instruct the scenario creation unit 14 to create a cooperation scenario.

As shown in FIG. 5A, when the user creates a collaboration scenario ST1 composed of the element services A, B, C, and D, thereafter, similarly, as shown in FIG. The element service C, the element service D after the element service C are selected in the GUI flow diagram, and the scenario creation unit indicates that the selection of the element service in the cooperation scenario ST1 is completed with the element service D in the GUI flow diagram on the display screen. 14 (S123).
That is, when the user clicks a button indicating that the element service selection process has ended in the GUI flow diagram on the display screen of the terminal, a selection end signal indicating that the element service selection has ended is sent to the scenario creation unit 14. Are output (sent).

As described above, after the general user 4 notifies the scenario creation unit 14 that the creation of the collaboration scenario ST1 has been completed, the scenario creation unit 14 notifies the scenario sentence generation verification unit 19 of the collaboration scenario. A control signal for instructing the generation process is output.
As a result, the scenario sentence generation verification unit 19 automatically generates a scenario sentence (description of the cooperation scenario) having the configuration (element service arrangement) of the cooperation scenario ST1 (S124).
Here, the scenario sentence generation verification unit 19 follows the arrangement order of the element services shown in FIG. 6 and provides element services corresponding to each input information and output information for each combination of the element services in the former stage and the element services in the latter stage. The link information is read from the element service link information database 18 and is correlated as shown in FIG. 4 and inserted between the preceding and following element services.

The scenario sentence generation verification unit 19 uses the information related to the subsequent element service invocation method stored corresponding to each element service in the element service connection information database 18 as the element service invocation method required in the cooperation scenario. Generate the corresponding scenario syntax.
For example, the scenario sentence generation verification unit 19 determines whether the element service has only an input, only an output, or both an input and an output, and the element service call instruction in the cooperation scenario. Select and describe.
Alternatively, the scenario sentence generation verification unit 19 performs, as an element service invocation method, a repetitive structure such as a while sentence or a determination process such as an if-then-else sentence according to the processing characteristics of each element service. Append (or describe) with the call instruction.

  The description format of the scenario sentence in the cooperation scenario described above can be based on the business flow description language BPEL or a service template (Service Template) described in JP-A-2005-250844, for example. Based on this service template, an element service is searched at a requested time point, and the obtained element service is combined to provide service as a cooperation scenario. Therefore, in the ubiquitous environment, detailed interface information of the element service is never known in advance. In the ubiquitous environment, when an element service is discovered in the requesting environment, the specific method name, parameter name, and data type name of the discovered element service are known for the first time. Therefore, unlike BPEL, individual element services are not specified in advance, and method names, parameter names, data type names, etc. are described abstractly in the service template.

In the following, a method of abstracting element services in the service template and performing service composition based on the service template will be described with a specific example.
First, the service template describes the categories of element services to be combined on the assumption that the element services are classified into categories. Do not describe names that depend on individual element services.
The parameters are also described with the standard parameters defined on the assumption that standard parameter names are defined in units such as categories. In service composition in the ubiquitous environment, each element service is called with a standard parameter name, so mapping to each parameter name for each element service is required. Therefore, the service template is described as shown in FIG.
In such a program like a high-level programming language, a method for describing a service template by paying attention to the category of the element service, the calling order of the element service, and the setting of the value of the calling parameter when calling, It is called an operation-oriented description.

  In the above description, the general user 4 indicates that the scenario creating unit 14 is instructed only to call the element service A and then call the element service B. In this step S124, the scenario creation unit 14 refers to the element service connection information via the search unit 104, and parameters as shown in FIG. 4 that are actually necessary for connecting the element service B after the element service A. A scenario sentence including conversion processing is generated.

  Next, the scenario sentence generation verification unit 19 includes the scenario sentence in the generated linkage scenario included in the scenario sentence, and refers to the quality information included in the element service used as processing, or other linkage Refer to the quality management information on the element service managed by the scenario creation support system, or refer to the quality management information of the log file by temporarily executing the scenario statement of the generated linkage scenario by the scenario execution engine 2. Thus, it is verified whether or not the scenario sentence actually functions effectively, and further, the quality of service (QoS) of the scenario sentence is verified (step S125).

And the scenario sentence production | generation verification part 19 memorize | stores the scenario sentence of the verified cooperation scenario in the scenario database 10 as mentioned above (S126).
The scenario creation unit 14 can access the scenario database 10, and when the general user 4 creates a cooperation scenario in step S122, the cooperation created by another user (for example, the knowledge user 3). Display the scenario on the display screen.
As a result, the user refers to the cooperation scenario displayed on the display screen, and edits (reuses) the cooperation scenario partially as a template. For example, the type of element service in the cooperation scenario You can create your own new collaboration scenario by changing the calling order and so on.

<When scenario management / execution instruction unit 13 is activated>
When the user (knowledge user 3 or general user 4) selects the support process of the scenario management / execution instruction unit 13 in step S102 and the selection unit 12 activates the scenario management / execution instruction unit 13, as shown below. In addition, the scenario management / execution instructing unit 13 is a functional unit that instructs the scenario execution engine 2 to execute the cooperation scenario instructed by the user (controls execution start and execution stop). Similar to the scenario service creation unit 14, unlike the element service connection information creation unit 15, not only the knowledge user 3 but also a general user 4 who does not have any knowledge or skill about the Web service can use the function unit.

As described above, when the selection unit 12 selects to proceed to the process of the scenario management / execution instruction unit 13 in step S102, the scenario management / execution instruction unit 13 is activated, and the general user 3 starts the cooperation scenario. The GUI used when executing the service execution instruction and execution status management is displayed on the display screen of the user terminal (step S111).
Next, for example, the general user 10 instructs the scenario management / execution instructing unit 13 to execute the cooperation scenario ST1 created in the scenario creating unit 14 according to the screen guidance, using the GUI of the terminal.

Thereby, the scenario management / execution instructing unit 13 transmits the input identification information of the cooperation scenario and the control information indicating that the cooperation scenario is executed to the scenario execution engine 2 via the network I.
When the control information is input, the scenario execution engine 2 accesses the scenario database 10, reads out the cooperation scenario corresponding to the input identification information from the scenario database 10, and reads the scenario sentence of the read cooperation scenario ST1. Refer to and start execution of the cooperation scenario according to the scenario sentence (step S112).

Further, the scenario management / execution instructing unit 13 executes the scenario execution when a control signal for confirming the operation state of the cooperation scenario ST1 after the execution instruction is given from the user, for example, the general user 4 via the GUI of the terminal. A control signal for requesting to access the engine 2 and to transmit information on the operation status is transmitted.
As a result, when the control signal is input, the scenario execution engine 2 detects the operation status of the cooperation scenario ST1 being executed from the log file and transmits the operation status information to the scenario management / execution instruction unit 13. .
Then, the scenario management / execution instruction unit 13 transmits the operation status information input from the scenario execution engine 3 to the user's terminal, and displays the operation status on the display screen by using the GUI.
As described above, the general user 4 can confirm whether or not the cooperation scenario ST1 is operating after the execution instruction by the display screen of the terminal.

When the scenario management / execution instruction unit 13 receives a control signal for requesting execution stop of the cooperation scenario ST1 instructed to execute from a user, for example, a general user 4 via the GUI of the terminal, the scenario execution engine 2 Is output, and a control signal for stopping execution of the cooperation scenario ST1 is output.
At this time, when the scenario execution engine 2 inputs the control signal, the scenario execution engine 2 stops the execution of the cooperation scenario ST1 and notifies the scenario management / execution instruction unit 13 that the cooperation scenario ST1 has been stopped.

Then, the scenario management / execution instructing unit 13 transmits the execution stop information input from the scenario execution engine 3 to the user's terminal, and displays the operation status on the display screen using the GUI.
As described above, the general user 4 instructs the scenario management / execution instructing unit 13 to stop the operating cooperation scenario ST1 according to the screen guidance in the GUI of the display screen on the display screen of the terminal. The execution of the cooperation scenario ST1 in the scenario execution engine 2 can be stopped.

In the above, the cooperation scenario creation support system 1 shown in FIGS. 1 and 2 has been described with respect to the form that supports creation of the cooperation scenario ST1 in which the element services shown in FIG. 5A are described in series.
However, as a configuration form of a similar cooperation scenario, there is also a cooperation scenario in which the element service C and the element service D are called in parallel as the subsequent stage of the element service B, as in the cooperation scenario ST2 shown in FIG. It can be created in the mechanism of the cooperation scenario creation support system 1 according to the present embodiment described above.

  The functions of the user login unit 11, the selection unit 12, the scenario management / execution monitoring unit 13, the scenario creation unit 14, the element service connection information creation unit 15, the search unit 16, and the scenario sentence generation verification unit 19 in FIG. The program for supporting the cooperation scenario creation may be performed by recording a program for recording on a computer-readable recording medium, causing the computer system to read and execute the program recorded on the recording medium. Here, the “computer system” includes an OS and hardware such as peripheral devices. The “computer system” includes a WWW system having a homepage providing environment (or display environment). The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Further, the “computer-readable recording medium” refers to a volatile memory (RAM) in a computer system that becomes a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. In addition, those holding programs for a certain period of time are also included.

  The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the “transmission medium” for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, and what is called a difference file (difference program) may be sufficient.

It is a conceptual diagram which shows the structure of the cooperation scenario creation assistance system 1 of one Embodiment of this invention. It is a block diagram which shows the structural example of the cooperation scenario creation assistance system 1 by this embodiment in FIG. It is a flowchart which shows the operation example of the cooperation scenario creation assistance system in FIG. It is a conceptual diagram which shows the concept of the element service connection information which performs the data conversion between each element service in this embodiment. It is a conceptual diagram which shows the structural example of a cooperation scenario. It is a conceptual diagram showing how to create a collaboration scenario by sequentially selecting element services

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Cooperation scenario creation support system 2 ... Scenario execution engine 3 ... Knowledge user 4 ... General user 10 ... Scenario database 11 ... User login part 12 ... Selection part 13 ... Scenario management and execution instruction part 14 ... Scenario creation part 15 ... Element service Linked information creation unit 16 ... Search unit 17 ... Element service database 18 ... Element service link information database 19 ... Scenario sentence generation verification unit 200 ... Element service group 200a ... Element service

Claims (9)

A collaborative scenario creation support system that supports creation of a collaborative scenario used when operating a plurality of element services that can be used via a network in cooperation with each other,
An element service database for storing element service information including service contents, input information and output information of each element service;
The element service information of the first and second element services designated by the user is read from the element service database, and the output information of the first element service and the second element service generated by the user based on these are read. Element service connection information creation unit for writing element service connection information for data flow between input information to the element service connection information database;
A scenario creation unit that sets the element service call order in the selected order for the element services selected in accordance with the linkage scenario flow diagram displayed on the screen by the user;
The element service connection information corresponding to the combination of the output information and input information of each successive element service is read with reference to the element service connection information database in accordance with the calling order of the element services generated by the scenario generation unit. And a scenario sentence generation and verification unit that generates a linkage scenario by interposing between element services. It further has a cooperation scenario database that stores the cooperation scenarios generated by the scenario sentence generation verification unit,
The scenario creation unit
Read the already generated cooperation scenario selected by the user from the cooperation scenario database,
2. The cooperation scenario creation according to claim 1, wherein an order changed by partially editing the already-created cooperation scenario is set as an element service calling order according to the cooperation scenario flow diagram displayed on the screen. Support system.   The element service connection information creation unit compares the parameter name of the output information of the first element service with the parameter name of the input information of the second element service, and compares the output information of the first element service with the second information The linkage scenario creation support system according to claim 1 or 2, wherein the data flow is associated with the input information of the element service.   The element service connection information creation unit compares the meta information related to the output information of the first element service with the meta information related to the input information of the second element service, and the first element The linkage scenario creation support system according to claim 1 or 2, wherein the data flow is correlated between the output information of the service and the input information of the second element service. A scenario execution engine for sequentially executing element services according to the linkage scenario;
5. The scenario sentence generation verification unit causes the scenario execution engine to execute the created cooperation scenario, verifies the execution result of each element service, and confirms the service quality. The cooperation scenario creation support system described in any one. A collaborative scenario creation support method in a collaborative scenario creation support system that supports creation of a collaborative scenario used when operating a plurality of element services that can be used via a network in cooperation with each other,
A storage process for storing element service information including service contents, input information and output information of each element service in the element service database;
The element service connection information creation unit reads the element service information of the first and second element services designated by the user from the element service database, and outputs the output information of the first element service and the input information of the second element service. Element service connection information creation process for writing the data flow generated by the user to the element service connection information database,
Scenario creation process in which the scenario creation unit sets the calling order of the element services in the selected order for the element services selected by the user according to the linked scenario flow diagram displayed on the screen;
The scenario sentence generation verification unit uses the element service connection information corresponding to the combination of the output information and the input information of each successive element service in accordance with the calling order of the element services created by the scenario creation unit. A collaborative scenario creation support method comprising: a scenario sentence generation process corresponding to generating a collaborative scenario by reading with reference to a database. The process of storing the linkage scenario generated by the scenario sentence generation verification unit, and the linkage scenario database;
The scenario creation unit reads an already generated cooperation scenario selected by the user from the cooperation scenario database, and partially edits the already generated cooperation scenario according to the cooperation scenario flow diagram displayed on the screen. The linked scenario creating method according to claim 6, further comprising: setting the changed order as a calling order of element services.   A cooperation scenario creation support program for causing a computer to function as the cooperation scenario creation support system according to any one of claims 1 to 5. A computer-readable recording medium on which the program according to claim 8 is recorded.

Images