JP2006072911A - Server, service providing program, and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a server for easily and appropriately defining an operation when a client uses a service in response to the addition and change of the service to be provided to the client, and to provide a service providing program and a recording medium. <P>SOLUTION: The server 200 is connected to the client 100, which uses the prescribed service, via a network and provides the service to the client 100. The server has a scenario management function of providing a scenario with the operation of the client 100 in using the service defined therein to the client 100 in response to a scenario acquisition request. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a server, a service providing program, and a recording medium, and more particularly to a server that provides a service used by a client, a service providing program, and a recording medium that records the service providing program.

  In recent years, a server that provides various services such as an authentication service and a device management service to a client as a Web service (hereinafter referred to as a Web service server) has attracted attention. The Web service server performs calling of a Web service, transmission / reception of data, and the like using an XML (extensible Markup Language) based protocol represented by SOAP (Simple Object Access Protocol), for example.

  A client using a Web service (hereinafter referred to as a Web service client) obtains information on methods and parameters of the Web service using WSDL (Web Service Description Language), and then invokes the Web service using SOAP. Had gone.

  WSDL is information required when using a Web service, and defines a data description method for acquiring method and parameter information possessed by the Web service. In other words, the Web service client has acquired the I / F specification of the Web service by WSDL (see, for example, Patent Document 1).

  FIG. 1 is a configuration diagram of an example of a Web service system. The Web service system of FIG. 1 has a configuration in which a Web service client 100, one or more Web service servers 200, and a service discovery 300 are connected via a network. Note that the Web service system can be configured without the service discovery 300.

  A Web service client 100 that uses a Web service includes an application 110 and a network I / F 120. The application 110 includes a U / I (user interface) 111, an operation definition unit 112, and a WSDL processing unit 113.

  The web service server 200 that provides the web service includes a network I / F 210 and a web service execution unit 220. The service discovery 300 for managing the web service includes a service management unit 310 and a storage unit 320 in which WSDL is stored.

  FIG. 2 is a sequence diagram showing processing of the Web service system. In steps S <b> 1 to S <b> 2, the web service server 200 that provides the web service registers the WSDL describing the I / F specification of the web service in the service discovery 300. Further, the web service client 100 using the web service searches the service discovery 300 for the web service provided by the web service server 200 in steps S3 to S4.

  A user who operates the Web service client 100 determines a Web service to be used from the searched Web services. In steps S <b> 5 to S <b> 6, the Web service client 100 acquires information (for example, the Web service name, the IP address of the Web service server 200, WSDL, etc.) related to the Web service selected by the user from the service discovery 300.

As described above, the Web service client 100 acquires the WSDL of the Web service selected by the user as shown in the sequence diagram shown in FIG. Therefore, the Web service client 100 can know what command the Web service has and what parameters should be given in what format in order to execute the command.
JP 2004-30360 A

  However, although WSDL defines the I / F specification of a web service, it does not define the operation of the web service client 100 when using the web service. Therefore, even if the Web service client 100 acquires WSDL, there is a problem that it cannot respond when the Web service providing method is changed, when a new function is added, or when a new Web service is added.

  For example, the operation of the Web service client 100 when using the Web service is coded in advance in the operation definition unit 112. Therefore, there is a problem that the Web service client 100 has to modify the operation definition unit 112 when a Web service providing method is changed, when a new function is added, or when a new Web service is added. there were.

  In Patent Document 1, a dedicated API (Application Program Interface) is created on a proxy server based on the acquired WSDL, and a Web service client uses the Web service via the dedicated API. It does not define the behavior of the Web service client when it is used.

  The present invention has been made in view of the above points, and a server, a service providing program, and a server capable of easily and appropriately defining an operation when a client uses a service according to addition or change of a service provided to the client An object is to provide a recording medium.

  In order to solve the above problems, the present invention is a server that is connected to a client that uses a predetermined service via a network and that provides the service to the client, and that defines the operation of the client when using the service Is provided with a scenario management function for providing the client to the client in response to a scenario acquisition request. In addition, this invention is good also as a computer-readable recording medium which recorded the service provision program for making a server perform said each function, and the program.

  In the present invention, a scenario defining the operation of the client when using the service is provided to the client, and the processing procedure when the client uses the service can be determined according to the scenario. As a result, the server can provide the scenario to the client, so that the operation of the client when using the service can correspond to the addition or change of the service.

  According to the present invention, it is possible to provide a server, a service providing program, and a recording medium that can easily and appropriately define an operation when a client uses a service according to the addition or change of the service provided to the client.

  Next, the best mode for carrying out the present invention will be described based on the following embodiments with reference to the drawings. In the following embodiments, a Web service is described as an example of a service provided from a server to a client, but other services may be used. FIG. 3 is a configuration diagram of an example of a Web service system according to the present invention.

  The Web service system of FIG. 3 has a configuration in which a Web service client 100, one or more Web service servers 200, a service discovery 300, and a scenario creation device 400 are connected via a network such as the Internet or a LAN (local area network). It is. Note that the Web service system can be configured without the service discovery 300.

  A Web service client 100 that uses a Web service includes an application 110 and a network I / F 120. The application 110 includes a U / I 111, a WSDL processing unit 113, and a scenario processing unit 114. The application 110 is connected to the network via the network I / F 120.

  The web service server 200 that provides the web service includes a network I / F 210, a web service execution unit 220, and a scenario management unit 230. The web service execution unit 220 and the scenario management unit 230 are connected to the network via the network I / F 210. A service discovery 300 for managing a Web service includes a service management unit 310 and a storage unit 320 in which WSDL is stored.

  The scenario creation device 400 that creates a scenario includes an application 410 and a network I / F 420. The application 410 includes a U / I 411, an editor control unit 412, a data analysis unit 413, an XML generation unit 414, and a storage unit 415 in which a scenario is stored. The application 410 is connected to the network via the network I / F 420. The scenario created by the scenario creation device 400 defines the operation of the Web service client 100 when using the Web service.

  FIG. 4 is a hardware configuration diagram of an embodiment of a computer that implements a Web service server. 4 includes an input device 1001, a display device 1002, a drive device 1003, an auxiliary storage device 1005, a memory device 1006, an arithmetic processing device 1007, and an interface device that are mutually connected by a bus B. 1008. Note that the various devices constituting the computer of FIG. 4 may be housed in one housing or may be housed in a plurality of housings.

  The input device 1001 includes a keyboard, a mouse, and the like, and is used to input various operation instructions. The display device 1002 includes a display and displays various windows and data necessary for operation. The interface device 1008 is an interface for connecting to a network, and includes a modem, a router, and the like.

  A service providing program for controlling the Web service server is provided by a recording medium 1004 such as a CD-ROM. The recording medium 1004 on which the service providing program is recorded is set in the drive device 1003, and the service providing program is installed in the auxiliary storage device 1005 via the drive device 1003.

  The recording medium 1004 on which the service providing program is recorded is a recording medium that records information optically, electrically, or magnetically, such as a CD-ROM, flexible disk, magneto-optical disk (MO), or ROM, flash memory, etc. As described above, various types of recording media such as a semiconductor memory for electrically recording information can be used.

  The service providing program includes a program provided on a recording medium or the like of another computer connected through the interface device 1008. A service providing program recorded in a recording medium or the like of another computer is downloaded via the interface device 1008 and installed in the auxiliary storage device 1005. The auxiliary storage device 1005 stores the installed service providing program and various files necessary for the processing of the service providing program. The memory device 1006 reads and stores the service providing program from the auxiliary storage device 1005 at the time of activation.

  The arithmetic processing device 1007 implements the web service execution unit 220 and the scenario management unit 230 of the web service server 200 in various processes according to the service providing program stored in the memory device 1006.

Hereinafter, the Web service system will be described in detail focusing on the processing of the Web service server of the present invention. First, a scenario in which the operation of the Web service client 100 when using the Web service is defined will be described.
(Scenario creation)
A scenario defining the operation of the web service client 100 when using the web service is created by the scenario creation device 400. For example, the application 410 of the scenario creation device 400 has an editor function for creating a state transition diagram. The user creates a state transition diagram using the editor function of the application 410.

  The state transition diagram created by the user represents the operation of the Web service client 100 when using the Web service by the state, the method to be used, and the state transition condition. The data analysis unit 413 analyzes the state transition diagram created by the user from the viewpoint of the state, the method to be used, and the state transition condition. Then, the XML generation unit 414 creates a scenario based on the analysis result of the data analysis unit 413.

  FIG. 5 is an image diagram of an example in which the created scenario is expressed in a natural language. The scenario of FIG. 5 is described in natural language for easy understanding, but is originally described in XML. The scenario in FIG. 5 defines the operation of the Web service client 100 when using the Web service as a basic series, an alternative series, and an exception series. FIG. 5 is an example of a scenario created from the state transition diagram of FIG.

  7 to 11 are configuration diagrams of examples of scenarios described in XML. 7 to 11 are examples of scenarios created from the state transition diagram of FIG. The scenario shown in FIGS. 7 to 11 includes a state definition part, a method definition part, and a state transition condition definition part.

  7 and 8 show the state definition part of the scenario. 9 and 10 show the method definition portion of the scenario. FIG. 11 shows the state transition condition definition part of the scenario.

  It should be noted that tags <state>, <method>, and <arc> included in the scenarios of FIGS. 7 to 11 represent states, methods, and state transition conditions. Therefore, the scenario creation device 400 can create a scenario described in XML as shown in FIGS. 7 to 11 from the state transition diagram created by the user.

The scenario created by the scenario creation device 400 is stored in the storage unit 415 from the XML generation unit 414. The scenario stored in the storage unit 415 is registered in the scenario management unit 230 of the Web service server 200 via the network I / F 420, the network, and the network I / F 210. The scenario stored in the storage unit 415 may be registered in the storage unit 320 of the service discovery 300 via the network I / F 420, the network, and the service management unit 310.
(Scenario provided)
FIG. 12 is a sequence diagram of an embodiment of the scenario providing process performed by the Web service system according to the present invention. In step S <b> 11, the scenario management unit 230 of the Web service server 200 receives a scenario acquisition request from the application 110 of the Web service client 100.

  The scenario management unit 230 of the Web service server 200 transmits a scenario in which the operation of the Web service client 100 when using the Web service is defined to the application 110 of the Web service client 100 as a response to the scenario acquisition request in step S11.

  Then, the scenario processing unit 114 included in the application 110 of the Web service client 100 creates a state transition of the Web service client 100 using the received scenario.

  FIG. 13 is a sequence diagram of another embodiment of the scenario providing process performed by the Web service system according to the present invention. In step S21, the scenario management unit 230 of the Web service server 200 makes a scenario registration request to the service management unit 310 of the service discovery 300. The scenario registration request in step S21 includes a scenario and a web service name.

  The service management unit 310 of the service discovery 300 registers a scenario in response to the scenario registration request. In step S22, the service management unit 310 responds to the scenario registration request in step S21.

  In step S23, the application 110 of the Web service client 100 sends a scenario acquisition request to the service management unit 310 of the service discovery 300. In step S24, the service management unit 310 searches for a scenario in which the operation of the web service client 100 when using the web service is defined, and the scenario is sent to the application 110 of the web service client 100 as a response to the scenario acquisition request in step S23. Send.

Then, the scenario processing unit 114 included in the application 110 of the Web service client 100 creates a state transition of the Web service client 100 using the received scenario.
(Scenario synchronization)
When the scenario registered in the Web service server 200 or the service discovery 300 is changed, the scenario transmitted to the Web service client 100 needs to be changed in the same manner to synchronize the scenario.

  FIG. 14 is a sequence diagram of an embodiment of scenario synchronization processing performed by the Web service system according to the present invention. When the scenario is changed, the scenario management unit 230 of the web service server 200 proceeds to step S31 and notifies the web service execution unit 220 of the scenario change. When receiving the scenario change notification, the Web service execution unit 220 stands by until an operation request from the Web service client 100 is received.

  In step S32, when an operation request for using the web service is received from the web service client 100, the web service execution unit 220 of the web service server 200 receives the scenario change notification in step S31. Then, a scenario acquisition request is transmitted to the scenario management unit 230.

  In step S 34, the web service execution unit 220 acquires the changed scenario from the scenario management unit 230. In step S35, the web service execution unit 220 transmits the operation result corresponding to the operation request in step S32 and the additional scenario representing the changed scenario to the application 110 of the web service client 100 as a response to the operation request in step S32.

  If the scenario change notification is not received in step S31, the web service execution unit 220 does not execute steps S33 and S34, and proceeds to step S35. In step S35, the operation result corresponding to the operation request in step S32 and the fact that the scenario is changed are transmitted to the application 110 of the Web service client 100 as a response to the operation request in step S32. An acquisition process may be performed.

Then, the scenario processing unit 114 included in the application 110 of the Web service client 100 changes the scenario of the Web service client 100 using the received additional scenario, and is registered in the Web service server 200 or the service discovery 300. Synchronize with.
(Create state transition)
FIG. 15 is a flowchart of an embodiment of a state transition creation process performed by the Web service client according to the present invention. The flowchart of FIG. 15 is an example in which all state transitions are constructed before the use of the Web service is started.

  In step S41, the scenario processing unit 114 included in the application 110 of the Web service client 100 acquires a scenario in which the operation of the Web service client 100 is defined when the desired Web service is used by the scenario providing process as described above. .

  In step S42, the scenario processing unit 114 analyzes the XML of the scenario acquired in step S41. In step S43, the scenario processing unit 114 determines whether there is a state included in the scenario. For example, in the scenario of FIGS. 7 to 11, the scenario processing unit 114 determines the presence / absence of a state using a tag <state>.

  If it is determined that there is a state (YES in S43), the scenario processing unit 114 proceeds to step S44 and registers the state. For example, in the scenario shown in FIGS. 7 to 11, the first state “administrator authentication” is registered. If it is determined that there is no state (NO in S43), the scenario processing unit 114 ends the process.

  Proceeding to step S45 following step S44, the scenario processing unit 114 determines the presence or absence of the method registered in the immediately preceding step S44. For example, the state “administrator authentication” in the scenarios of FIGS. 7 to 11 has a method m1 “password use session start method”. The scenario processing unit 114 determines the presence / absence of a registered method using a tag <method>.

  If it is determined that there is a method (YES in S45), the scenario processing unit 114 proceeds to step S46, and determines whether the method is a method of another Web service. For example, in the case of the scenario shown in FIGS. 7 to 11, the scenario processing unit 114 determines whether the method is a method of another Web service using the method definition portion. It is determined whether the method is another Web service method based on whether the <service> tag is present and the namespace or WSDL written in the <service> attribute is different from the Web service currently being analyzed. Yes.

  If it is determined that the method is not another Web service method (NO in S46), the scenario processing unit 114 proceeds to step S47, and causes the WSDL processing unit 113 to acquire the method specifications from, for example, the WSDL acquired from the service discovery 300.

  Proceeding to step S48, the scenario processing unit 114 adds the method to the method list in the current state registered at the immediately preceding step S44. 7 to 11, the scenario processing unit 114 adds the method m1 “password use session start method” to the state “administrator authentication”.

  On the other hand, if it is determined that the method is another web service method (YES in S46), the scenario processing unit 114 proceeds to step S49, acquires the scenario and WSDL of the other web service, and creates a state transition creation process for the other web service. Is implemented by recursive processing.

  Proceeding to step S45 following step S48 or S49, the scenario processing unit 114 determines whether there is a remaining method registered in the immediately preceding step S44. That is, the scenario processing unit 114 repeats the processes of steps S45 to S49 for all the methods registered in the immediately preceding step S44.

  If it is determined that there is no method (NO in S45), scenario processing unit 114 proceeds to step S50. For example, in the case of the scenario of FIGS. 7 to 11, the scenario processing unit 114 does not have any method other than the method m1 “password use session start method” in the state “administrator authentication”. After performing the processes of S45 to S48, the process proceeds to step S50.

  In step S50, the scenario processing unit 114 sets the state transition condition registered in step S44 based on the scenario state transition condition definition part. For example, in the scenario of FIGS. 7 to 11, the scenario processing unit 114 sets the transition to the state “determined to be managed” when the method m1 “password use session start method” is “OK”, and the “NG” Sometimes set to end the process.

  Proceeding to step S43 following step S50, the scenario processing unit 114 determines whether there is a remaining state included in the scenario. That is, the scenario processing unit 114 performs steps S43 to S50 for all states included in the scenario.

  As described above, according to the state transition creation process of FIG. 15, the scenario processing unit 114 can create the state transition as shown in FIG. 6 as the processing procedure of the Web service client 100 when using the Web service based on the acquired scenario.

  FIG. 16 is a flowchart of another embodiment of the state transition creation process performed by the Web service client according to the present invention. The flowchart in FIG. 16 is an example in which state transitions are dynamically constructed after the use of a Web service is started.

  In step S51, the scenario processing unit 114 included in the application 110 of the Web service client 100 acquires a scenario in which the operation of the Web service client 100 is defined when the desired Web service is used by the scenario providing process as described above. .

  In step S52, the scenario processing unit 114 analyzes the XML of the scenario acquired in step S51. Proceeding to step S53, the scenario processing unit 114 acquires the first state included in the scenario. For example, in the scenario of FIGS. 7 to 11, the scenario processing unit 114 acquires the state “administrator authentication”.

  In step S54, the scenario processing unit 114 determines whether or not the acquired state is the end. If it is determined that the acquired state is the end (YES in S54), the scenario processing unit 114 ends the process. On the other hand, if it is determined that the acquired state is not the end (NO in S54), the scenario processing unit 114 proceeds to step S55, and determines whether there is a method in the acquired state.

  If it is determined that there is a method (YES in S55), the scenario processing unit 114 proceeds to step S56, and determines whether the method is a method of another Web service. If it is determined that the method is not a method of another Web service (NO in S56), the scenario processing unit 114 proceeds to step S57, and causes the WSDL processing unit 113 to acquire the method specification from the WSDL.

  Proceeding to step S58, the scenario processing unit 114 transmits a method execution request to the Web service server 200 using the method specification acquired at the immediately preceding step S57. In step S59, the scenario processing unit 114 obtains a method execution response to the request in step S58 from the Web service server 200.

  On the other hand, if it is determined that the method is another web service method (YES in S56), the scenario processing unit 114 proceeds to step S60, acquires the scenario and WSDL of the other web service, and creates a state transition creation process for the other web service. Is implemented by recursive processing.

  Progressing to step S55 following step S59 or S60, the scenario processing unit 114 determines whether there is a remaining method in the acquired state. That is, the scenario processing unit 114 repeats the processes in steps S55 to S60 for all methods in the acquired state.

  If it is determined that there is no method (NO in S55), scenario processing unit 114 proceeds to step S61. For example, in the case of the scenario of FIGS. 7 to 11, the scenario processing unit 114 does not have any method other than the method m1 “password use session start method” in the state “administrator authentication”. After performing the processes of S55 to S60, the process proceeds to step S61.

  In step S61, the scenario processing unit 114 acquires the next state from the scenario based on the method execution response and the scenario state transition condition definition part. 7 to 11, the scenario processing unit 114 acquires the state “determined to be managed” from the scenario when the response when the method m1 “password use session start method” is executed is “OK”.

  Progressing to step S54 following step S61, the scenario processing unit 114 determines whether or not the acquired state is a termination. That is, the scenario processing unit 114 performs steps S54 to S61 for all states included in the scenario.

As described above, according to the state transition creation process of FIG. 16, the scenario processing unit 114 dynamically creates the state transition as shown in FIG. 6 as the processing procedure of the Web service client 100 when using the Web service based on the acquired scenario. Web services can be used.
(Change state transition)
For example, the scenario processing unit 114 included in the application 110 of the Web service client 100 acquires an additional scenario by the scenario synchronization process of FIG. The scenario processing unit 114 can perform the state transition creation process of FIG. 15 or FIG. 16 and create a state transition based on the changed scenario.

  The scenario processing unit 114 searches for a state that needs to be changed, a method to be used, and a state transition condition based on the state transition created from the scenario before the change and the state transition created from the scenario after the change or the additional scenario. The scenario processing unit 114 performs scenario change processing such as addition or deletion of a state, a method to be used, and a state transition condition based on a search result of a state that needs to be changed, a method to be used, and a state transition condition.

  FIG. 17 is an image diagram of an example of a scenario change process. Note that the scenario change process in FIG. 17 is an example of adding a scenario. FIG. 17A is a state transition diagram of a scenario before addition. FIG. 17B is a state transition diagram of the scenario to be added. FIG. 17C is a state transition diagram of the scenario after the addition.

FIG. 18 is an image diagram of another example of the scenario change process. Note that the scenario change process in FIG. 18 is an example of deleting a scenario. FIG. 18A is a state transition diagram of a scenario before deletion. FIG. 18B is a state transition diagram of the scenario to be deleted. FIG. 18C is a state transition diagram of the scenario after deletion.
(Application use)
Here, a change in screen transition when a new scenario is added to the scenario represented by the state transition as shown in FIG. 19 will be described. FIG. 19 is an example state transition diagram created from a scenario.

  When the user instructs activation, the application 110 uses the U / I 111 to present an initial screen 2000 as shown in FIG. 20 to the user. FIG. 20 is a screen transition diagram of an example by an application.

  When the user presses the “Start” button on the initial screen 2000, the application 110 executes the session start method m1 and the management target search method m2, and when a response indicating success is received, the management target determination screen 2100 as shown in FIG. Present to the user. When the user selects a management target name as a setting type on the management target determination screen 2100, the application 110 executes the management target determination method m3 and the management target setting item reference method m4, and receives a response indicating success. A management target setting item setting screen 2200 is presented to the user.

  Here, it is assumed that the user selects the management target name “system setting” from the management target determination screen 2100. When the user inputs time and security settings on the management target setting item setting screen 2200, the application 110 executes the management target setting item setting method m5 and the session end method m6, and then ends the process.

  When the authentication service is added to the scenario represented by the state transition as shown in FIG. 19 using the scenario change process described above, the scenario is changed to the scenario represented by the state transition of FIG. In the scenario represented by the state transition of FIG. 22, a user authentication screen 2300 as shown in FIG. 23 is added between the screen transitions of the initial screen 2000 and the management target determination screen 2100.

  For example, when the user presses the “Start” button on the initial screen 2000, the application 110 presents a user authentication screen 2300 as shown in FIG. After the user name and password are input on the user authentication screen 2300, when the button “OK” is pressed, the application 110 executes the user authentication service a1.

  As described above, the Web service server 200 provides the Web service client 100 with a scenario in which the operation of the Web service client 100 when using the Web service is defined, and processing when the Web service client 100 uses the service according to the scenario. Since the procedure can be determined, the operation of the Web service client 100 when using the service can correspond to the addition or change of the service.

  The present invention is not limited to the specifically disclosed embodiments, and various modifications and changes can be made without departing from the scope of the claims.

It is a block diagram of an example of a Web service system. It is a sequence diagram showing processing of a Web service system. It is a block diagram of an example of the Web service system by this invention. It is a hardware block diagram of one Example of the computer which implement | achieves a Web service server. It is an image figure of an example which expressed the created scenario in natural language. It is an example state transition diagram showing a scenario. It is a block diagram (1/5) of an example of the scenario described by XML. It is a block diagram (2/5) of an example of the scenario described by XML. It is a block diagram (3/5) of an example of the scenario described by XML. It is a block diagram (4/5) of an example of the scenario described by XML. It is a block diagram (5/5) of an example of the scenario described by XML. It is a sequence diagram of one Example of the scenario provision process which the Web service system by this invention performs. It is a sequence diagram of the other Example of the scenario provision process which the Web service system by this invention performs. It is a sequence diagram of one Example of the scenario synchronization process which the Web service system by this invention performs. It is a flowchart of one Example of the state transition creation process which the Web service client by this invention performs. It is a flowchart of the other Example of the state transition creation process which the Web service client by this invention performs. It is an image figure of an example of a scenario change process. It is an image figure of another example of scenario change processing. It is an example state transition diagram created from a scenario. It is an example screen transition diagram (1/2) by an application. It is an example screen transition diagram (2/2) by an application. It is an example state transition diagram changed by scenario change processing. It is an image figure of an example of an initial screen.

Explanation of symbols

100 Web service client 110, 410 Application 111, 411 U / I
113 WSDL processing unit 114 Scenario processing unit 120, 210, 420 Network I / F
DESCRIPTION OF SYMBOLS 200 Web service server 220 Web service execution part 230 Scenario management part 300 Service discovery 310 Service management part 320,415 Storage part 400 Scenario creation apparatus 412 Editor control part 413 Data analysis part 414 XML generation part 1001 Input apparatus 1002 Display apparatus 1003 Drive apparatus 1004 Recording medium 1005 Auxiliary storage device 1006 Memory device 1007 Arithmetic processing device 1008 Interface device B bus

Claims (21)

A server connected to a client using a predetermined service via a network and providing the client with the service;
A server having a scenario management function for providing a scenario defining a client operation when using the service to the client in response to a scenario acquisition request.   The server according to claim 1, further comprising a service execution function for providing the service to the client in response to a service use request from the client. The scenario management function notifies the service execution function of a scenario change when the scenario is changed,
When the service execution function receives a service use request from the client after being notified of the change of the scenario, the service execution function acquires the changed scenario from the scenario management function and along with the service corresponding to the service use request The server according to claim 2, wherein the server is provided to the client.   The server according to claim 1, wherein the scenario management function provides the client with a scenario representing a client operation at the time of using the service by a state, a method to be used, and a state transition condition.   The server according to claim 1, wherein the scenario management function provides a scenario including a state definition part, a method definition part, and a state transition condition definition part to the client.   2. The server according to claim 1, wherein the scenario management function provides the client with a scenario in which the operation of the client when using the service is defined by a basic series, an alternative series, and an exception series.   The server according to claim 1, wherein the scenario management function registers the scenario in advance with another server that provides the scenario to the client. The scenario management function notifies the service execution function of a scenario change when the scenario is changed,
When the service execution function receives a service use request from the client after being notified of the change of the scenario, the service execution function provides the client with a service according to the change of the scenario and the service use request,
The server according to claim 2, wherein the scenario management function provides the client with the changed scenario.   The server according to any one of claims 1 to 8, wherein the scenario management function provides a scenario described in XML to the client.   The server according to claim 1, wherein the scenario management function provides a scenario defining a client operation when using a Web service to the client in response to a scenario acquisition request. A server connected to a client using a predetermined service via a network and providing a service to the client;
A service providing program for executing a scenario management function for providing a scenario defining a client operation when using the service to the client in response to a scenario acquisition request.   12. The service providing program according to claim 11, further comprising a service execution function for providing the service to the client in response to a service use request from the client. The scenario management function notifies the service execution function of a scenario change when the scenario is changed,
When the service execution function receives a service use request from the client after being notified of the change of the scenario, the service execution function acquires the changed scenario from the scenario management function and along with the service corresponding to the service use request The service providing program according to claim 12, wherein the service providing program is provided to the client.   12. The service providing program according to claim 11, wherein the scenario management function provides the client with a scenario representing a client operation at the time of using the service by a state, a method to be used, and a state transition condition.   12. The service providing program according to claim 11, wherein the scenario management function provides a scenario including a state definition part, a method definition part, and a state transition condition definition part to the client.   12. The service providing program according to claim 11, wherein the scenario management function provides the client with a scenario in which the operation of the client when using the service is defined by a basic series, an alternative series, and an exception series.   12. The service providing program according to claim 11, wherein the scenario management function registers the scenario in advance in another server that provides the scenario to the client. The scenario management function notifies the service execution function of a scenario change when the scenario is changed,
When the service execution function receives a service use request from the client after being notified of the change of the scenario, the service execution function provides the client with a service according to the change of the scenario and the service use request,
13. The service providing program according to claim 12, wherein the scenario management function provides the changed scenario to the client.   19. The service providing program according to claim 11, wherein the scenario management function provides a scenario described in XML to the client.   The service providing program according to any one of claims 11 to 19, wherein the scenario management function provides a scenario defining a client operation when using a Web service to the client in response to a scenario acquisition request.   A computer-readable recording medium on which the service providing program according to any one of claims 11 to 20 is recorded.

Images