JP2009294863A - Event service distribution system, event service distribution device, and event service distribution method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an event service distribution system that detects a cooperative scenario which is a target of execution, on the basis of event information included in notification received from a requester so as to execute the cooperative scenario, an event service distribution device, and to provide an event service distribution method. <P>SOLUTION: In a network service platform 2, an event/service distribution part 10 stores event notification from a requester 11 and address information of a service composition part 3, which is for executing a cooperative scenario which is a target of execution corresponding to the event notification, in association with each other, and the event/service distribution part transmits the event notification to an address of the service composition part 3 corresponding to the event notification, on the basis of the event notification received from the requester 11 so as to allow the service composition part 3 to execute the cooperative scenario. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to an event service distribution system, an event service distribution device, and an event service distribution method in a system that executes a cooperation scenario (cooperation service) for linking element services provided by servers distributed on a network.

  In recent years, as one of the technologies for realizing SOA (Service-Oriented Architecture), service cooperation technology that links a plurality of Web services (element services, service components) has been attracting attention. For example, an interface based on a technical specification published by W3C (World Wide Web Consortium) which is an international standardization organization, for example, a Web interface based on a WSDL (Web Services Description Language) specification, UPnP (Universal Plug and play), etc. By defining a service interface based on the above specifications in advance and sending and receiving messages using SOAP (Simple Object Access protocol), it becomes possible to link various element services.

In this cooperation, the interface-defined element service is executed by the cooperation scenario execution engine sequentially or in parallel based on the workflow (cooperation scenario, cooperation scenario). Hereinafter, the element service referred to (called) in the cooperation scenario will be described as a service component.
For example, BPEL (Business Process Execution Language) is widely used as a language for describing a cooperation scenario combining service components. The cooperation scenario based on the BPEL description is executed by a BPEL engine (cooperation scenario execution engine) that is a service composition device or software. In the cooperation scenario arranged (deployed) in the BPEL engine, a web interface is defined based on WSDL, and the web scenario is provided as a service component by itself.

Normally, a BPEL engine is deployed with a plurality of cooperation scenarios in which a Web interface is defined in a WSDL document. This WSDL document is information indicating the definition of a Web interface described based on the WSDL specification. Also, the WSDL document describes the endpoint address information of the corresponding cooperation scenario. According to the client / server model, the client sends a SOAP message to the BPEL engine with the endpoint address as the destination, The cooperation scenario is executed (invoked).
Hereinafter, a configuration (software, device, client, etc.) that outputs a request for executing a cooperation scenario or a signal that triggers execution is referred to as a “requester”.

In addition to BPEL, when the interface matching between the cooperation scenario execution engine and the service component cannot be established, a service component that mediates these interfaces is discovered, and a system for synthesizing the service including this is realized. There is a technology (for example, Patent Literature 1) and a system technology that enables dynamic adaptation to other service components having equivalent functions in the same area (for example, Patent Literature 2).
As described above, the cooperation scenario is executed when the BPEL engine receives an execution request or the like by the SOAP protocol from a requester on the network. For example, when the requester detects (detects) some event, it transmits a cooperation scenario execution request including information related to this event.

  Also, when executing different linkage scenarios for each event, the service component execution order is described in the task, and all event occurrence conditions such as “event A reception” and “predetermined time” are described in this task as events. Keep it. There is a technology in which a server that manages the occurrence of an event executes a collaboration scenario by performing task activation management by referring to activation conditions when an event occurs.

Also, as the service execution method, input information is fixedly set for each task. When this task is started, this information is distributed to the service components using a predetermined method, and information such as parameters must be input when the service is executed. A method for realizing a cooperative service including the service component is proposed.
There is also a method for realizing task execution by setting input information for each service component in advance, receiving input information from outside at the time of task activation, and distributing the received information to each service component.

By the way, generally, when a requester detects some event (such as an alarm occurrence), the requester executes a linked scenario deployed on the linked scenario execution engine. On the other hand, the cooperation scenario execution engine provides execution of a deployed cooperation scenario to a large number of unspecified requesters as a Web service. For this reason, it is necessary to have a configuration for determining and selecting which linkage scenario is executed when which event is triggered.However, if the linkage scenario execution engine decides the linkage scenario in advance, There is a problem that the combination of services cannot be determined. As a result, the requester individually has a functional configuration and software for selecting and determining a cooperation scenario to be executed for each event.
JP-A-2005-71052 JP-A-2005-250844

  However, a memory that stores information on the cooperation scenario to be executed for each event, a configuration for determining for each event which execution scenario execution request is to be transmitted, and a request that conforms to the interface defined in the execution request destination The provision of a requester with a configuration for generating a signal has a problem that the configuration of the requester becomes complicated and the amount of processing increases. Also, in preparation for changes in the interface and service contents at the request signal destination, it is necessary to always check the changes, and if there is a change, it is necessary to perform setting change processing on the requester side again, which is not convenient for the user. There is a problem.

  The present invention has been made in consideration of such circumstances, and has been made to solve the above problem. The purpose of the present invention is to provide event information included in the received notification when the network service platform receives the event notification from the requester. It is an object of the present invention to provide an event service distribution system, an event service distribution device, and an event service distribution method that can detect and execute a cooperation scenario that is an execution target.

  In order to solve the above problem, the present invention provides an event service distribution system for a cooperation scenario storage device that stores a cooperation scenario in which a service execution procedure is described, and an endpoint that is an address for executing the cooperation scenario. A network service providing system including a service composition device that executes the cooperation scenario in response to a scenario execution request, an event service distribution device, a requester device that transmits an event notification when an event is detected, and a service component that provides the service Are connected via a network, and the event service distribution device of the network service providing system executes an event notification received from the requester device and an execution target cooperation scenario corresponding to the event notification. Event routing table storage means for storing end point information, which is information indicating a response, and event notification received from the requester device as a search key, and the endpoint information of the cooperation scenario from the event routing table storage means. An event service distribution system comprising: distribution means for reading and transmitting the cooperation scenario execution request to the endpoint.

  In addition, the event service distribution system of the present invention further includes a user terminal device connected to a network, and the user terminal device executes an event notification transmitted from the requester device and a cooperation scenario executed based on the event notification. The event service distribution device transmits an event notification sent from the requester device based on the registration request received from the user terminal device, and the event notification. Table updating means for writing the end point information of the cooperation scenario to be executed based on the event routing table storage means.

  The event service distribution system of the present invention further includes a registry device connected to a network and a user terminal device connected to the network, and the registry device includes endpoint information of the requester device, and the requester device. Is stored in association with the event notification information transmitted by the user terminal device, and the user terminal device generates a registration request for requesting registration with the endpoint information of the cooperation scenario executed based on the event notification transmitted from the requester device. The event service distribution device transmits, based on the registration request received from the user terminal device, from the registry device, an event notification from the requester device, and endpoint information which is address information of the requester device. Read the event Notification and, characterized in that the end-point information of the cooperative scenarios for performing based on the event notification includes a table updating means for writing said event routing table storing means.

  Further, the present invention executes a cooperation scenario storage device that stores a cooperation scenario in which a service execution procedure is described, and the cooperation scenario in response to a scenario execution request addressed to an endpoint that is an address for executing the cooperation scenario. Network service providing system including a service composition device, an event service distribution device, a requester device that transmits an event notification when an event is detected, and a service component that provides the service are connected via a network. The event service distribution device according to claim 1, wherein an event notification received from the requester device is associated with endpoint information, which is information indicating an address for executing a cooperation scenario to be executed corresponding to the event notification. The event routing table storage means for storing and the event notification received from the requester device are used as search keys to read the endpoint information of the linkage scenario from the event routing table storage means, and the linkage scenario execution request is addressed to the endpoint. An event service distribution device comprising distribution means for transmitting to the event service.

  Further, the present invention executes a cooperation scenario storage device that stores a cooperation scenario in which a service execution procedure is described, and the cooperation scenario in response to a scenario execution request addressed to an endpoint that is an address for executing the cooperation scenario. Network service providing system including a service composition device, an event service distribution device, a requester device that transmits an event notification when an event is detected, and a service component that provides the service are connected via a network. Event service distribution method in the network service providing system, wherein the event service distribution device of the network service providing system receives the event notification received from the requester device, and the execution target corresponding to the event notification An event routing table storage step that associates and stores in the storage means endpoint information that is information indicating an address for executing a nario, and an event notification received from the requester device as a search key, and from the storage means the linkage scenario. An event service distribution method comprising: a distribution step of reading endpoint information and transmitting the cooperation scenario execution request to the endpoint.

  According to the present invention, the event service distribution device stores the event notification received from the requester device in association with the endpoint information, which is information indicating the address for executing the execution target cooperation scenario corresponding to the event notification. Event routing table storage means, and distribution means for reading the endpoint information of the cooperation scenario from the event routing table storage means and transmitting the cooperation scenario execution request to the endpoint using the event notification received from the requester device as a search key It was decided.

  As a result, when an event that triggers the execution of the cooperation scenario occurs, the requester apparatus side transmits the identification information of the cooperation scenario and an execution request signal corresponding to the interface used in the service composition apparatus that executes the cooperation scenario. Instead, by transmitting only the event notification to the event service distribution device, the service composition device can execute the cooperation scenario. This eliminates the need for a storage means for storing the identification information of the cooperation scenario on the requester device side and a circuit for generating a signal that complies with the interface of the service synthesis device, and can increase the cost of the requester device. is there.

  Hereinafter, an event service distribution system according to an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a schematic block diagram showing the overall configuration of the event service distribution system according to the present embodiment. The event service distribution system includes a service component 7 that is a server that provides a Web service, a network service platform 2 that is a server that executes a linkage scenario that links services provided by the service component 7, and an event that triggers the execution of the linkage scenario. A requester 11 for notification, a user terminal 13 as a terminal device on the service user side, and a UDDI (Universal Description, Discovery, and Integration) 14 are connected via the network 1. The network 1 includes a public network such as a telephone network and the Internet, and a private network such as a LAN (Local Area Network) and a dedicated line.

In the figure, the network service platform 2 includes a service composition unit 3, a service component database 5, a scenario database 6, and an event / service distribution unit 10 connected via a service bus 4, and is received from the requester 11. Execute the coordination scenario based on the notification of the event to be performed.
In the network service platform 2, the service composition unit 3 sequentially calls the web services provided by the service component 7 based on the deployed cooperation scenario.

The scenario database 6 is a database device that stores a cooperation scenario to be executed that is deployed (arranged) in the service composition unit 3. Here, for example, a scenario 8-1 registered by the user terminal 13 and a scenario 8- 2 is remembered. The scenario 8-1 and the scenario 8-2 stored in the scenario database 6 describe a plurality of Web service execution procedures. The scenarios 8-1 and 8-2 themselves also have a plurality of Web services. It is a Web service that provides a service to be linked.
FIG. 2 is a conceptual diagram showing the contents of the cooperation scenario described in scenario 8-1. When the notification of the event that triggers the execution of the scenario 8-1 is received from the requester 11, the service composition unit 3 executes the scenario 8 based on the procedure described in the scenario 8-1 from the processing of the calling instruction of the service component 7. -1 is executed.

Returning to FIG. 1, the service component database 5 is a database device that stores information related to the service component 7 such as endpoint information that is address information of the service component 7, an overview of the Web service provided by the service component 7, and an interface. is there.
In accordance with an instruction from the user terminal 13, the scenario creating unit 9 refers to the information regarding the service component 7 stored in the service component database 5, creates a cooperation scenario, and writes the created cooperation scenario in the scenario database 6. Deploy to the service composition unit 3.

  The scenario creation unit 9 applies, for example, the techniques presented in Reference Documents 1 and 2 using, for example, GUI (Graphical User Interface), so that a user operating the user terminal 13 can easily create a cooperation scenario. (Reference 1: JP 2008-21095, collaborative scenario creation support system and method and program thereof, Reference 2: Moriya, Onishi, Yoshida, Ogawa, Hirano, “A Support System for Designing Ubiquitous Service Composition” Scenarios ”, IEEE Proc. ICC 2007, pp.1594-1599, 2007).

In addition, the scenario creation unit 9 acquires from the service composition unit 3 the endpoint information of the deployed cooperation scenario as address information of the cooperation scenario deployed to the service composition unit 3. FIG. 3 is an example of a WSDL document corresponding to the scenario 8-1 deployed in the service composition unit 3. W1 in the figure is endpoint information W1 “http: // serviceengine / ws / tokusuruService1” indicating an address for executing the cooperation scenario.
FIG. 4 is an example of a WSDL document corresponding to the scenario 8-2 deployed in the service composition unit 3. W2 in the figure is endpoint information W2 “http: // serviceengine / ws / tokusuruService2” indicating an address for executing the cooperation scenario.
The service synthesizing unit 3 receives the execution request for the address described in the endpoint information and executes the cooperation scenario.

Returning to FIG. 1, the event / service distribution unit 10 includes an event routing table storage unit 110, a determination unit 120, and a table update unit 130, and responds to an event notification received from the requester 11 via the network 1. The cooperation scenario to be executed is determined, and the determined cooperation scenario is executed by the service composition unit 3.
The event routing table storage unit 110 of the event / service distribution unit 10 stores an event routing table in which a scenario ID (identifier) and an endpoint used when executing a scenario are associated with event identification information.

FIG. 5 is a diagram showing a data configuration example and a data example of the event routing table stored in the event routing table storage unit 110. As shown in the figure, the event routing table includes columns of items of scenario ID information for identifying a cooperation scenario, endpoint information, and event identification information included in an event notification received from the requester 11. It is a two-dimensional table format table.
The event identification information in the event routing table is, for example, information such as start event information indicating the event type of the event detected by the requester 11 and notification parameters notified from the requester 11, and is information for identifying the event. .

Returning to FIG. 1, the determination unit 120 of the event / service distribution unit 10 determines which one of the cooperation scenarios deployed in the service composition unit 3 is the execution target based on the notification of the event received from the requester 11. A scenario distribution determination process is performed to determine whether the scenario is a linkage scenario.
In the scenario distribution determination process by the determination unit 120, the endpoint information corresponding to the event identification information included in the received event notification is read from the event routing table storage unit 110, and the received event notification is addressed to the read endpoint. It is a process to transfer.

The table updating unit 130 updates the event routing table by associating the event identification information from the requester 11 with the end point information acquired by the scenario creating unit 9 and writing it in the event routing table storage unit 110.
The service bus 4 connects the service composition unit 3, service component database 5, scenario database 6, scenario creation unit 9, and event / service distribution unit 10 described above.

The service component 7 is a Web service that is connected to the network 1 and has an interface defined, and is referred to and called sequentially or in parallel by the service composition unit 3 in the network service platform 2 based on a cooperation scenario.
The requester 11 is a device that is connected to the network 1 and transmits an event notification to the network service platform 2 when an event occurs. In the present embodiment, the requester 11 is a device that includes, as an example of an event, a sensor that detects the presence or absence of water leakage in a building, and notifies the network service platform 2 of a water leakage alarm when water leakage is detected.

  Further, the requester 11 has a function of “Notification Producer” defined in OASIS WS-Brokered Notification shown in References 3 and 4, and notifies the event / service distribution unit 10 of interface information of the requester 11 (references). 3: OASIS, “Web Services Base Notification 1.3 (WS-Base Notification)”, [online], [search May 14, 2008], Internet <http://docs.oasis-open.org/wsn/wsn -ws_base_notification-1.3-spec-pr-02.pdf>, Reference 4: OASIS, “Web Services Brokered Notification 1.3 (WS-Brokered Notification)”, [online], [Search May 14, 2008], Internet <http://docs.oasis-open.org/wsn/wsn-ws_brokered_notification-1.3-spec-pr-02.pdf>).

The user terminal 13 is, for example, a computer terminal such as a personal computer, a PDA (Personal Digital Assistants: information portable terminal), or a mobile phone, and outputs a scenario creation instruction to the scenario creation unit 9 of the network service platform 2 or a service The execution result of the scenario executed by the synthesis unit 3 is received.
The UDDI 14 includes a storage device that stores the endpoint information of the requester 11, the event identification information included in the notification of the event of the requester 11, and the interface information of the requester 11, in response to a search request from the outside. In response, a search result of information stored in the storage device is output.

  Next, the operation of the event service distribution system according to the embodiment of the present invention will be described with reference to the drawings. FIG. 6 shows a processing flow in an event service distribution system comprising two processes, a registration process and a scenario execution process. Here, as a registration process, the scenario creation unit 9 creates a scenario 8-1 in response to a registration request from the user terminal 13, and the created scenario 8-1 and a requester that triggers the execution of the scenario 8-1. A process of registering the notification from the event / service distribution unit 10 in association with the notification from 11 will be described as an example. The scenario execution process will be described with reference to the information registered in the event / service distribution unit 10 as an example of the process of executing the scenario 8-1 in response to an event notification transmitted from the requester 11.

<Registration process>
Based on the user operation, the requester 11 outputs a SOAP message of a registration request “Register PublisherRequest” including the endpoint information of the requester 11 and event identification information (event topic information) to the event / service distribution unit 10. FIG. 7 is an example of a SOAP message for a registration request transmitted by the requester 11.

As shown in FIG. 7, the SOAP message “RegisterPublisherRequest”, which is a registration request, includes the endpoint information “http: // requester1 / PublisherEndpoint” of the requester 11 and the event identification information that the requester 11 outputs to the event / service distribution unit 10. It is a request including. The event identification information transmitted by the requester 11 is event identification information “WaterLeakAlarm” indicating a water leakage warning.
Event topic information as event identification information is described based on, for example, the WS-Topic format shown in Reference 5 (Reference 5: OASIS, “Web Services Topics 1.3 (WS-Topics)”, [online ], [Search May 14, 2008], Internet <http://docs.oasis-open.org/wsn/wsn-ws_topics-1.3-spec-os.pdf>).

  Returning to FIG. 6, the event / service distribution unit 10 shifts to a registration standby mode for requester 11 data in the event routing table based on the registration request received from the requester 11. Specifically, the event / service distribution unit 10 writes the event identification information of the received registration request in a new row of the event routing table of the event routing table storage unit 110 and temporarily stores the endpoint information of the requester 11. Is stored in the internal storage means.

  Further, the event / service distribution unit 10 transmits a SOAP message of “Register Publisher Response” notifying that the standby mode of the registration procedure has been started to the requester 11 as a response message corresponding to the registration request (step S101). FIG. 8 is a SOAP message example of a response that the event / service distribution unit 10 transmits to the requester 11.

  As shown in FIG. 8, the SOAP message “RegisterPublisherResponse”, which is a response corresponding to the registration request from the requester 11, is a response including the endpoint information “http: // EventRoutingGateway / PublisherRegistrationManager” of the event / service distribution unit 10. . The requester 11 stores the endpoint information of the event / service distribution unit 10 included in the received registration start notification as address information of an event notification destination.

  A user who operates the requester 11 confirms that the requester 11 has received the notification of the standby mode of the registration procedure, and creates a scenario to be executed in response to the event notification in the requester 11. Specifically, by user operation, the user terminal 13 transmits an event topic transmission request to the scenario creation unit 9 of the network service platform 2, and receives event topic list information from the scenario creation unit 9. The user terminal 13 outputs a scenario 8-1 creation request to the scenario creating unit 9 in response to a user operation based on the received event topic list information. Based on the received creation request, the scenario creation unit 9 generates information about the scenario 8-1 and the scenario ID that is identification information of the scenario 8-1 (step S102).

  The scenario creation unit 9 deploys the generated scenario 8-1 to the service composition unit 3 (step S103), and receives endpoint information and scenario ID when executing the deployed scenario 8-1 from the service composition unit 3 (Step S104). The scenario creation unit 9 notifies the event / service distribution unit 10 of the endpoint information of the received scenario 8-1 (step S105), and the table update unit 130 of the event / service distribution unit 10 receives the received scenario 8-1. Is written in the event routing table row of the requester 11 to be registered (step S106).

  When registration in the event routing table storage unit 110 is completed, the event / service distribution unit 10 transmits a SOAP message “Subscribe” based on the endpoint information of the requester 11 temporarily stored in Step S101. The SOAP message “Subscribe” transmitted by the event / service distribution unit 10 is a notification indicating that the registration process is completed and the event / service distribution unit 10 subscribes (accepts) notification of an event from the requester 11. The requester 11 notifies the event / service distribution unit 10 that the notification has been received (step S107).

Through the above steps S101 to S107, the correspondence between the event notification received by the event / service distribution unit 10 from the requester 11 and the cooperation scenario to be executed based on the notification is an event as a new row in the event routing table. / Registered in the service distribution unit 10.
Similar to the registration process described above, the user terminal 13 creates a cooperation scenario of the scenario 8-2 based on the user operation, and the scenario creation unit 9 deploys the scenario 8-2 to the service composition unit 3. Further, as shown in FIG. 5, the event / service sorting unit 10 stores a row of the event routing table of the scenario 8-2 in addition to the scenario 8-1. As shown in the figure, the event identification information included in the notification of the event for which scenario 8-2 is the execution target is XML (notification parameter “X = 1” and notification parameter “Y = 2”). Event identification information in the form of (Extensible Markup Language).

<Scenario execution process>
Next, after the processing of the registration process described above, when the event routing table relating to the scenario 8-1 and the scenario 8-2 is registered in the event / service distribution unit 10, the requester 11 detects a water leakage event. The flow of processing in the scenario execution process will be described.
The requester 11 detects the leak of water as an event (step S108), and transmits an event notification including the event identification information “WaterLeakAlert” to the event / service distribution unit 10. Here, the requester 11 transmits the SOAP message “Notification” to the endpoint stored in step S101 (here, the event / service distribution unit 10) as an event notification (step S109).

The event / service distribution unit 10 reads the endpoint information of the corresponding scenario 8-1 from the event routing table storage unit 110 using the event identification information “WaterLeakAlert” of the notification of the received event as a search key (step S110). The event / service distribution unit 10 transmits the received event notification to the address of the read endpoint information (here, the service composition unit 3 in which the scenario 8-1 is deployed).
When receiving the notification of the event addressed to the endpoint of the deployed scenario 8-1, the service composition unit 3 executes the cooperation scenario based on the scenario 8-1 stored in the scenario database 6 (step S111).

  According to the above-described embodiment, when the requester 11 stores the endpoint information of the event / service distribution unit 10 and transmits only the event notification to the event / service distribution unit 10, the network service platform 2 notifies the event notification. The corresponding linkage scenario is selected based on the event identification information included in, and the selected linkage scenario is executed. As a result, it follows the memory that stores the information of the cooperation scenario to be executed for each event, the configuration for determining for each event which execution request of the cooperation scenario is to be transmitted, and the interface defined in the transmission destination of the execution request The requester 11 is not required to have a configuration for generating a request signal. Therefore, there is an effect that it is possible to provide the user with a system that can execute the cooperation scenario without increasing the processing amount without complicating the apparatus configuration of the requester 11.

  Further, the event / service distribution unit 10 receives all the event notifications from the requester 11 and transmits a scenario execution request to the service composition unit 3 together with the received notifications, thereby changing the interface and service contents in the service composition unit 3. Even if there is a service, it is possible to provide the user with a service for executing the cooperation scenario without changing the event notification content, the notification destination, or the like according to the change on the requester 11 side. Thereby, there is an effect that it is possible to provide a cooperation scenario execution service with improved convenience.

  In the above-described embodiment, the requester 11 transmits the SOAP message “RegisterPublisherRequest” when the event / service distribution unit 10 acquires the interface information of the requester 11. However, the present invention is not limited to this. For example, FIG. The interface information may be acquired by any method such as using the UDDI 14.

  Specifically, for example, the event / service distribution unit 10 transmits a SOAP message “find_service” or a SOAP message “find_business”, which is an event notification type service search request, to the UDDI 14. In response to a request from the event / service distribution unit 10, the UDDI 14 responds to the event / service distribution unit 10 with a SOAP message including the endpoint information of the requester 11 and event identification information that is event topic information. The event / service distribution unit 10 is applied by transmitting a SOAP message “RegisterPublisherResponse” including the endpoint information of the event / service distribution unit 10 to the requester 11 based on the endpoint information included in the received SOAP message response. Is possible.

In the network service platform 2, the event / service sorting unit 10 has been described as including the event routing table storage unit 110. However, the event routing table storage unit 110 is not limited to this. Any configuration can be applied as long as the event / service distribution unit 10 can be connected, such as a configuration connected via 1 or the like.
Further, the requester 11 and the service component 7 shown in FIG. 1 are applicable even if they have a plurality of configurations.

The network service platform 2, the service component 7, the requester 11, the UDDI 14, and the user terminal 13 described above have a computer system therein. The operation processes of the event / service distribution unit 10, the service composition unit 3, the scenario creation unit 9, the requester 11, the user terminal 13, and the UDDI 14 of the network service platform 2 are stored in a computer-readable recording medium in the form of a program. The computer system reads out and executes this program, and the above processing is performed. The “computer system” herein includes a CPU, various memories, an OS, and hardware such as peripheral devices.
Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used.

6 is recorded on a computer-readable recording medium, and the program for realizing the function of the network service platform 2 shown in FIG. 1 is computer-readable. It is also possible to perform a process of automatically selecting a cooperation scenario to be executed in response to an event by causing the computer system to read and execute the program recorded on the recording medium and executing the program.
The “computer-readable recording medium” means a flexible disk, a magneto-optical disk, a ROM, a writable nonvolatile memory such as a flash memory, a portable medium such as a CD-ROM, a hard disk built in a computer system, etc. This is a storage device.

Further, the “computer-readable recording medium” refers to a volatile memory (for example, DRAM (Dynamic DRAM)) 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. Random Access Memory)), etc., which hold programs for a certain period of time.
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.

1 is a block diagram showing an overall configuration of an event service distribution system according to an embodiment of the present invention. It is a conceptual diagram which shows the content of the scenario 8-1 in the embodiment. It is a figure which shows the data example of the WSDL document of the scenario 8-1 in the embodiment. It is a figure which shows the data example of the WSDL document of the scenario 8-2 in the embodiment. It is a figure which shows the data structure of the event routing table storage means 110 in the embodiment, and a data example. It is a flowchart which shows the flow of operation | movement of the event service distribution system by the embodiment. It is a figure which shows the example of SOAP message "RegisterPublisherRequest" which the requester 11 by the same embodiment transmits. It is a figure which shows the example of SOAP message "RegisterPublisherResponse" which the event / service distribution part 10 by the embodiment transmits.

Explanation of symbols

1 Network 2 Network Service Platform (Network Service Providing System)
3 Service composition department (service composition device)
4 Service Bus 5 Service Component Database 6 Scenario Database (Cooperation Scenario Storage Device)
7 Service Component 8-1 Scenario 8-2 Scenario 9 Scenario Creation Unit 10 Event / Service Distribution Unit (Event Service Distribution Device)
110 Event routing table storage means 120 Judgment means (sorting means)
130 Table Update Unit 11 Requester 13 User Terminal 14 UDDI (Registry Device)

Claims (5)

A cooperation scenario storage device that stores a cooperation scenario in which a service execution procedure is described; a service composition device that executes the cooperation scenario in response to a scenario execution request addressed to an endpoint that is an address for executing the cooperation scenario; and an event A network service providing system comprising a service distribution device, a requester device that transmits an event notification when an event is detected, and an event service distribution system in which a service component that provides the service is connected via a network,
The event service distribution device of the network service providing system is:
An event routing table storage unit that stores event notifications received from the requester device in association with endpoint information that is information indicating an address for executing an execution target cooperation scenario corresponding to the event notification;
Using an event notification received from the requester device as a search key, comprising: a distribution unit that reads endpoint information of a collaboration scenario from the event routing table storage unit and transmits the collaboration scenario execution request to the endpoint. Event service distribution system. The event service distribution system further includes a user terminal device connected to a network,
The user terminal device
Send a registration request for requesting registration of the event notification transmitted from the requester device and the endpoint information of the cooperation scenario executed based on the event notification,
The event service distribution device includes:
Table updating means for writing, in the event routing table storage means, event notifications transmitted from the requester device based on the registration request received from the user terminal device, and endpoint information of cooperative scenarios executed based on the event notifications The event service distribution system according to claim 1, further comprising: The event service distribution system further comprises a registry device connected to the network and a user terminal device connected to the network,
The registry device stores the endpoint information of the requester device in association with event notification information transmitted by the requester device,
The user terminal device
Send a registration request to request registration with the endpoint information of the cooperation scenario to be executed based on the event notification sent from the requester device,
The event service distribution device includes:
Based on the registration request received from the user terminal device, the event notification from the requester device and the endpoint information which is the address information of the requester device are read from the registry device, the event notification, and the event notification The event service distribution system according to claim 1, further comprising: a table updating unit that writes the endpoint information of the cooperation scenario to be executed based on the information into the event routing table storage unit. A cooperation scenario storage device that stores a cooperation scenario in which a service execution procedure is described; a service composition device that executes the cooperation scenario in response to a scenario execution request addressed to an endpoint that is an address for executing the cooperation scenario; and an event Network service providing system including a service distribution device, a requester device that transmits an event notification when an event is detected, and a service component that provides the service, the event service distribution device in an event service distribution system connected via a network Because
An event routing table storage unit that stores event notifications received from the requester device in association with endpoint information that is information indicating an address for executing an execution target cooperation scenario corresponding to the event notification;
And distribution means for reading out the end point information of the cooperation scenario from the event routing table storage means using the event notification received from the requester device as a search key and transmitting the cooperation scenario execution request to the end point. Event service distribution device. A cooperation scenario storage device that stores a cooperation scenario in which a service execution procedure is described; a service composition device that executes the cooperation scenario in response to a scenario execution request addressed to an endpoint that is an address for executing the cooperation scenario; and an event An event service distribution method in an event service distribution system in which a network service providing system including a service distribution device, a requester device that transmits an event notification when an event is detected, and a service component that provides the service are connected via a network There,
The event service distribution device of the network service providing system,
An event routing table storage step for storing the event notification received from the requester device and the endpoint information, which is information indicating an address for executing the cooperation scenario to be executed corresponding to the event notification, in the storage unit in association with each other;
A distribution step of using the event notification received from the requester device as a search key to read end point information of a cooperation scenario from the storage means and transmitting the cooperation scenario execution request to the end point. Service distribution method.

Images