JP2004362449A - Service providing device, service coordinator device, service providing method, service coordinating method and program, as well as computer readable recording medium having the program recorded thereon - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a device which secures user requirements, especially response requirement, and executes plural kinds of service in combination. <P>SOLUTION: The service providing device comprises: a storage device 51 which stores SLA information 10 indicating service provision conditions of plural kinds of services; a reception part 52 which receives request information for requesting the provision of each service constituting cooperative service obtained by combining several kinds of service among the plural kinds of service as a group; a cooperative service management part 6 which manages a current provision state of each service constituting the cooperative service and judges, according to the conditions indicated by the SLA information 10 stored in the storage device 51, whether each service constituting the cooperative service requested by the received request information can be provided; and an execution part 54 which provides each service constituting the cooperative service requested by the request information received by the reception part 52. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a service providing device or a service coordinator device, or a service providing method or a service coordinating method. In particular, it relates to a service cooperation control method.
[0002]
[Prior art]
The following means for providing a technology capable of efficiently providing an application service requested by a user are described in the literature. In an application service providing method for providing an application service to a user, an application or an application provider that satisfies a user requirement that is a requirement requested by a user from among a plurality of applications provided by one or more application providers, and It includes a step of selecting an application to be provided, and a step of providing an application service by performing data format conversion, communication protocol conversion, or workflow management between the selected applications. (See Patent Document 1)
[0003]
[Patent Document 1]
JP 2001-306535 A
[0004]
[Problems to be solved by the invention]
In the application / service / providing system having the configuration described in Patent Document 1, a user accesses an intermediate provider, receives a list of application classifications from the intermediate provider, and selects a target application. Next, a requirement input sheet is received from the intermediate provider, and user requirements (functional requirements, charging requirements, response requirements) are input. The intermediate provider displays a list of application candidates satisfying the function requirements and the billing requirements, and the user selects an application from the candidate list. The intermediate provider saves the user requirement information in the user requirement database and starts the service. When a situation occurs in which the response requirement cannot be satisfied during the service execution, a new application candidate list is created, the user selects from the candidate list, switches the application to be executed, or maintains the current state, and continues the service.
[0005]
The application / service / providing system having the above configuration has the following problems.
When selecting an application, it is possible to confirm whether each application satisfies the user requirements, but it is not possible to confirm whether the entire linked application service satisfies the user requirements.
In addition, when the requests from many users overlap, the response requirement cannot be satisfied during the execution of the cooperative service, and the application switching process is performed dynamically.If there is no application that satisfies the response requirement, Since the user is notified, the processing is interrupted, and there is a problem that the response requirement cannot be guaranteed and the entire cooperative application cannot be executed.
In addition, there is a problem that the process of dynamically measuring the response requirement becomes a load on the provider.
[0006]
An object of the present invention is to provide an apparatus that can execute a combination of a plurality of services while guaranteeing a response requirement among user requirements.
[0007]
[Means for Solving the Problems]
A service providing device according to the present invention includes: a storage unit that stores a plurality of service providing condition information indicating service providing conditions of a plurality of services;
A receiving unit that receives request information requesting to provide each service of a service group in which some of the plurality of services are combined as a group;
A service group that manages the current provision status of each service of the service group and that is requested by the request information received by the reception unit based on the service provision conditions indicated by the plurality of service provision condition information stored by the storage unit A management unit that determines whether it is possible to provide each service of
An execution unit configured to execute provision of each service of a service group required by the request information received by the reception unit based on a result determined by the management unit.
[0008]
BEST MODE FOR CARRYING OUT THE INVENTION
Embodiment 1 FIG.
In the first embodiment, when a plurality of services are operated in cooperation with each other, a service requester is determined based on service level agreement information previously connected between a service provider (service provider device) and a service coordinator (service coordinator device). A description will be given of a cooperative service control method in which a request from a (service requester device) is accepted, a service is allocated and managed, so that a response requirement among user requirements is guaranteed, and a plurality of services can be executed in combination.
[0009]
FIG. 1 is a configuration diagram illustrating an example of the service cooperation control method according to the first embodiment.
In FIG. 1, a service coordination control system in a service coordination control system includes a plurality of service providers 21 and 31 that provide a service, a service requester 12 that is a client requesting the service, a service provider 21 or a service provided by the service provider 31. A service coordinator 5 (an example of a service coordinator device and a service providing device) that is provided to the service requester 12 in combination is provided. The plurality of combined provision services provided to the service requester 12 may be a plurality of provision services provided by one service provider (for example, the service provider 21), or a plurality of service providers (for example, the service provider 21). , 31) may be provided.
[0010]
The service provider 21 includes a storage device 25 that stores a provided service 22 provided by the service provider 21 and load information 23 indicating a processing status of the provided service by the service provider 21, and an SLA (service provider 21 processes service level agreement information). (Service level agreement) processing unit 24. Similarly, the service provider 31 includes a storage device 35 that stores the provided service 32 provided by the service provider 31 and the load information 33 indicating the processing status of the provided service, and the service provider 21 processes the service level agreement information. And an SLA processing unit 34 that performs the processing.
[0011]
The service coordinator 5 includes a cooperative service management unit 6 (an example of a management unit) for operating a plurality of services in cooperation, a storage device 51 (an example of a storage unit), a reception unit 52, a transmission unit 53, An execution unit 54 is provided. The coordination service management unit 6 includes an SLA processing unit 7 for adjusting the service level by the service coordinator 5 and a coordination service execution management unit 8 for processing the coordination service. The storage device 51 stores a cooperation service definition 9 for managing combination information of a plurality of services, SLA information 10, and a cooperation service execution management table 11 for managing actual services.
[0012]
The service requester 12 has a storage device 121, and a client program that requests a service is stored in the storage device 121.
[0013]
Next, the operation will be described.
The storage device 51 stores SLA information 10 (an example of a plurality of service provision condition information) indicating service provision conditions of a plurality of services set in advance with a service provider that provides the service.
[0014]
The receiving unit 52 receives, from the service requester 12, request information for requesting to provide each service of a service group obtained by combining any of the plurality of services as a group, and transfers each service of the service group to the service. Received from the providers 21 and 31.
[0015]
The cooperative service management unit 6 manages the current provision status of each service of the service group, and the reception unit 52 uses the service provision condition indicated by the plurality of service provision condition information stored in the storage device 51 to control the service provision condition. It is determined whether each service of the service group required by the received request information can be provided.
[0016]
The execution unit 54 receives the request information received from the service requester 12 by the receiving unit 52 based on the result determined by the cooperative service management unit 6 and receives the request information from the service providers 21 and 31 by the receiving unit 52. Each service of the specified service group is executed and provided to the service requester 12.
[0017]
If the transmission unit 53 cannot provide all the services of the service group requested by the request information received by the reception unit 52 as a result of the determination by the cooperation service management unit 6, the reception unit 52 The rejection information for rejecting the received request information is transmitted to the service requester 12.
[0018]
In the first embodiment, the service coordinator 5 is configured to provide the service requester 12 by combining a plurality of services provided by the service provider 21 or the service provider 31 separately from the service provider. 5 may be provided. That is, the storage device 51 stores SLA information 10 (which is an example of a plurality of service provision condition information) indicating service provision conditions of a plurality of services.
Then, the receiving unit 52 receives request information requesting to provide each service of a service group in which some of the plurality of services are combined as a group.
The cooperative service management unit 6 manages the current provision status of each service of the service group, and based on the service provision conditions indicated by the plurality of service provision condition information stored by the storage device 51, It is determined whether or not each service of the service group required by the request information received by 52 can be provided.
Then, the execution unit 54 provides each service of the service group required by the request information received by the reception unit 52, based on the result determined by the cooperation service management unit 6.
[0019]
FIG. 2 is a flowchart illustrating the operation of the service cooperation control method according to the first embodiment.
The operation of the service cooperation control system in the service cooperation control system configured as described above will be described with reference to FIG.
First, the service requester 12 accesses the service coordinator 5 (S201).
[0020]
The cooperation service management unit 6 in the service coordinator 5 displays a list of cooperation services to be provided based on the cooperation service definition 9 stored in the storage device 51 (S208).
[0021]
The service requester 12 selects a cooperation service (an example of a service group) to be executed from the displayed cooperation services. (S202). In other words, the receiving unit 52 in the service coordinator 5 receives the reception information related to the selection operation as the request information when the service requester 12 selects the cooperative service to be executed.
[0022]
The cooperation service management unit 6 in the service coordinator 5 checks the cooperation service execution management table 11 stored in the storage device 51 as to whether the selected cooperation service is executable (S209).
[0023]
The coordination service management unit 6 in the service coordinator 5 determines whether the selected coordination service can be executed (S210). If the coordination service is not accepted, the rejection (rejection information) is transmitted from the transmission unit 53 (S211). If it is acceptable, the selected cooperative service is registered in the cooperative service execution management table 11 (S212), and the receivable (receivable information) is transmitted from the transmission unit 53 (S213).
[0024]
The service requester 12 receives the acceptability (S203), determines whether or not the acceptability is possible (S204), and terminates the selection of the cooperative service if it is not accepted (S207). If it can be accepted, data necessary for executing the cooperative service is input (S205), and the execution unit 54 in the service coordinator 5 executes the cooperative service based on the data received via the receiving unit 52 (S214).
[0025]
When the cooperative service is completed, the cooperative service management unit 6 of the service coordinator 5 transmits an execution completion notification and an execution result (S215), deletes the cooperative service from the cooperative service execution management table 11 (S216), and ends (S217).
The service requester 12 receives the cooperation service execution completion notification and the execution result (S206), and ends (S207).
[0026]
As described above, the service cooperative control system in the service cooperative control system provides the service providers 21 and 31 that provide the service, the service requester 12 that requests the execution of the service, and executes a plurality of services in response to the service request. The service coordinator 5 performs service level agreements for guaranteeing the execution time for service requests between the service providers 21 and 31 and the service coordinator 5. Based on the service level agreement information, a plurality of service requesters 12 are provided. In order to guarantee the response time, a cooperation service execution management table 11 is provided.
[0027]
FIG. 3 is a diagram illustrating an example of service level agreement (SLA) information according to the first embodiment.
The service coordinator 5 concludes a service level agreement with the service providers 21 and 31 to guarantee the number of processings of a certain service and the execution time of the service, and uses that information as service level definition information (an example of service provision condition information). ).
[0028]
FIG. 4 is a diagram illustrating an example of the cooperative service definition information according to the first embodiment.
The cooperative service execution management unit 8 in the service coordinator 5 determines the processing time required to execute a cooperative service (an example of a service group) from the service in the SLA information and the processing time required to execute the cooperative service. It is calculated and managed as linked service definition information. The service coordinator 5 displays a list of executable cooperative services to the service requester 12 based on the cooperative service definition 9 (cooperative service definition information).
[0029]
FIG. 5 is a diagram illustrating an example of the cooperation service execution management table according to the first embodiment.
The cooperative service execution management table 11 manages when and how much all the services constituting the cooperative service are used as a whole in the set unit time. In FIG. 5, the unit time is set to 5 seconds. In FIG. 5, a management state 501 indicates a management state in a case where 250 requests are made for each of the cooperation service 1 and the cooperation service 2.
The management state 502 in FIG. 5 is a state in which 250 request requests of the cooperation service 1 have been received 5 seconds after the state of the management state 501. In this state, if a request for the cooperative service 1 is received, the service B1 which is one of the services configuring the cooperative service 1 cannot satisfy the number of processes that can be processed defined in the SLA after 20 seconds. Is impossible.
[0030]
FIG. 6 is a flowchart illustrating a procedure for checking the cooperation service execution management table.
The procedure for checking the cooperation service execution management table will be described with reference to FIG. In the cooperation service execution management table check, the cooperation service management unit 6 acquires the services constituting the cooperation service and their execution order from the cooperation service definition 9 (cooperation service definition information) stored in the storage device 51 (S601). .
Next, the cooperative service management unit 6 acquires the number of processes that can be performed and the processing time of each service from the SLA information 10 (SLA definition information) (S602).
Next, the cooperation service management unit 6 divides the processing time of each service into the management unit time of the cooperation service execution management table 11 (S603).
Next, the cooperative service management unit 6 compares the number of processes recorded in the cooperative service execution management table 11 with the number of processable processes of the service for the first service executed per unit time (S604).
When the number of processes managed on the table does not exceed the number of processes that can be processed (S605), the cooperative service management unit 6 counts up the number of processes in the cooperative service execution management table 11 (S606).
When the comparison is completed for all services per unit time (S607), the cooperative service management unit 6 ends the check and determines that the service requester 12 can accept the service (S608).
When the number of processes that can be processed is exceeded in S605, the cooperative service management unit 6 counts down the number of processes of all services that have been counted up so far (S609), ends the process, and determines that the service requester cannot accept the process (S609). S610).
[0031]
As described above, by managing the execution of the cooperative service based on the SLA concluded between the service providers 21 and 31 and the service coordinator 5, the processing time of the entire cooperative service can be guaranteed. .
[0032]
Embodiment 2 FIG.
In the first embodiment, since the number of processable cases defined in the SLA definition information is fixed, the number of requests from the service requester 12 executed by the service coordinator 5 is large and there is no room for the number of processable cases. In the case where there is a margin in the number of processes that can be provided by the service providers 21 and 31, or when the number of requests is small and the number of services being executed is small while the number of processes being executed by the other service coordinator 5 is large. Cannot be redistributed.
In the second embodiment, in addition to the operation of the first embodiment, in FIG. 1, the SLA processing unit 7 of the service coordinator 5 is replaced by the SLA processing unit 24 of the service provider 21 (the SLA processing unit 34 in the case of the service provider 31). And the service provider 21 responds to the execution information managed by the SLA processing unit 24 as to whether or not the change is possible, and the service coordinator 5 changes the SLA information 10. The configuration of the second embodiment is the same as that of FIG.
[0033]
The transmission unit 53 sends the inquiry information for changing the service provision condition indicated by at least one of the service provision condition information among the plurality of service provision condition information stored by the storage device 51 to the service provider 21 or the service provider 31. Or both.
The receiving unit 52 receives the response information to the inquiry information transmitted by the transmitting unit 53.
The cooperative service management unit 6 determines whether it is possible to provide all the services of the service group required by the request information received by the receiving unit 52, based on the response information received by the receiving unit 52. I do.
The execution unit 54 determines the request information received from the service requester 12 by the receiving unit 52 based on the result determined by the cooperative service management unit 6 based on the answer information. All the services of the service group received from the service provider 21 (or the service provider 31 or both) are executed and provided to the service requester 12.
[0034]
FIG. 7 illustrates the operation of the second embodiment.
If the SLA processing unit 7 in the service coordinator 5 cannot accept the SLA in S210, it inquires of the service provider 21 whether or not the SLA can be changed (S218).
In the service provider 21, the SLA processing unit 24 refers to the load information 23 and replies whether or not the change is possible as response information (S222).
The SLA processing unit 7 in the service coordinator 5 determines the received response (S219), and if the change is not possible, transmits a rejection to the service requester 12 via the transmission unit 53 (S211).
When the change is possible in S219, the SLA processing unit 7 in the service coordinator 5 issues an SLA change request to the service provider 21 (S220), and changes the SLA information 10 (SLA definition information) stored in the storage device 51 ( In step S221, the cooperative service based on the request from the service requester 12 is registered in the cooperative service execution management table 11 (S212).
Upon receiving the SLA change request, the SLA processing unit 24 in the service provider 21 changes the SLA (S223), and changes the SLA definition information (S224).
[0035]
As described above, in the second embodiment, when a service request is requested from a service requester, the service level agreement can be changed according to the cooperative service execution management status, the service level agreement is provided to the service provider. A means is provided for inquiring whether or not the change of the setting is possible.
[0036]
According to the present embodiment, since the service level can be dynamically changed, there is an effect that the number of executable cooperative service processes can be changed.
[0037]
Embodiment 3 FIG.
In the second embodiment, the number of executable processes managed in the linked service execution management table 11 in response to the linked service execution request from the service requester 12 has reached the number of executable processes defined in the SLA definition information. In such a case, the linked service cannot be executed. However, the service providers 21 and 31 may have time to execute the service.
In the third embodiment, in addition to the second embodiment, in FIG. 1, the SLA processing unit 7 of the service coordinator 5 inquires the SLA processing unit 24 of the service provider 21 about a change in the number of processes that can be processed by the SLA, The service coordinator 5 responds to the execution information managed by the SLA processing unit 24 of the service provider 21 whether the increase is possible, and the service coordinator 5 increases the SLA information 10. The configuration of the third embodiment is the same as that of FIG.
[0038]
FIG. 8 is a flowchart illustrating the operation of the third embodiment.
If the SLA processing unit 7 in the service coordinator 5 cannot accept the request in S210, the SLA processing unit 7 inquires of the service provider 21 whether the SLA can be changed (increased) (S218).
The SLA processing unit 24 of the service provider 21 refers to the load information 23 and answers whether or not the change (increase) is possible (S222).
The SLA processing unit 7 in the service coordinator 5 determines the received response (S219), and if the change (increase) is impossible, transmits a rejection to the service requester 12 via the transmission unit 53 (S211).
If the change (increase) is possible, the SLA processing unit 7 in the service coordinator 5 issues an SLA change (increase) request to the service provider 21 (S220), and changes the SLA information 10 (SLA definition information) (S221). The registration in the cooperation service execution management table 11 is performed (S212).
Upon receiving the SLA change (increase) request, the service provider 21 increases the SLA (S223) and changes the SLA definition information (S224).
[0039]
As described above, in the third embodiment, when the conditions determined by the service level agreement can be increased between the service provider and the service coordinator, the service level can be increased and the number of executable requests can be temporarily increased.
[0040]
According to the third embodiment, since the service level can be dynamically increased, the number of executable cooperative service processes can be increased.
[0041]
Embodiment 4 FIG.
In the second embodiment, the number of executable processes managed in the cooperative service execution management table 11 in response to the cooperative service execution request from the service requester 12 is significantly larger than the number of processable processes defined in the SLA definition information. If it is small, there is no need to maintain the current SLA. However, the service providers 21 and 31 may want to execute a service.
In the fourth embodiment, in addition to the second embodiment, the SLA processing unit 7 of the service coordinator 5 inquires of the SLA processing unit 24 of the service provider 21 about a change in the number of processes that can be managed by the SLA in FIG. The service coordinator 5 decreases the SLA information 10 by responding to the execution information managed by the SLA processing unit 24 of the service provider 21 whether or not the reduction is possible.
[0042]
FIG. 9 is a flowchart illustrating the operation of the present embodiment.
If the SLA processing unit 7 in the service coordinator 5 can accept the request in S210, the SLA processing unit 7 inquires of the service provider whether the SLA can be changed (decreased) (S218).
The SLA processing unit 24 of the service provider 21 refers to the load information 23 and replies whether the change (decrease) is possible (S222).
The SLA processing unit 7 in the service coordinator 5 judges the received answer (S219), and if it is impossible to change (decrease), registers it in the cooperative service execution management table 11 (S212).
If the change (decrease) is possible, the SLA processing unit 7 in the service coordinator 5 issues an SLA change (decrease) request to the service provider 21 (S220), changes the SLA definition information (S221), and executes the linked service execution management table. 11 is registered (S212).
Upon receiving the SLA change (reduction) request, the service provider 21 changes the SLA (S223) and changes the SLA definition information (S224).
[0043]
As described above, in the fourth embodiment, when the conditions determined by the service level agreement can be reduced between the service provider and the service coordinator, the service level can be reduced, and the number of executable requests can be temporarily reduced.
[0044]
According to the fourth embodiment, since the service level can be dynamically reduced, the number of processes once increased can be reduced, and even if the number of processes has not increased, execution can be performed by another service coordinator. There is an effect that the number of processes of the cooperative service can be increased.
[0045]
Embodiment 5 FIG.
In the first embodiment, when the number of requests from the service requester 12 exceeds the number of processes that can be processed defined in the SLA definition information, the execution of the cooperative service cannot be performed.
[0046]
In the fifth embodiment, by examining the cooperation service execution management table 11, it is possible to determine whether the requested cooperation service can be executed, and to notify the information. In other words, based on the current provision status of each service of the service group to be managed, the cooperative service management unit 6 checks all the services of the service group required by the request information received from the service requester 12 by the reception unit 52. The transmission unit 53 transmits a time determined by the cooperative service management unit 6 to the service requester 12.
[0047]
FIG. 10 is a flowchart illustrating the operation of the fifth embodiment.
If the service cannot be accepted in S210, the cooperation service execution management unit 8 in the cooperation service management unit 6 searches the cooperation service execution management table 11 to obtain a time at which the service can be executed (S225).
The cooperation service execution management unit 8 in the service coordinator 5 transmits the rejection of acceptance and the time at which the cooperation service can be executed to the service requester 12 via the transmission unit 53 (S211).
The service requester 12 requests execution of the cooperative service again at an executable time based on this information.
[0048]
As described above, in the fifth embodiment, when a request for a service that cannot be accepted at present is requested, a time when the request can be accepted is notified from the cooperation service execution management status.
[0049]
According to the fifth embodiment, it is possible to know the time at which a cooperative service that cannot be executed at present becomes executable, so that there is an effect that there is no needless wait.
[0050]
Embodiment 6 FIG.
In the fifth embodiment, it is possible to know when the desired cooperative service becomes executable. In the sixth embodiment, the service coordinator 5 is further provided with an execution reservation management table, and by managing the information, it is possible to execute the cooperative service when it becomes executable.
[0051]
FIG. 11 is a configuration diagram illustrating an example of the service cooperation control method according to the sixth embodiment.
In FIG. 11, the storage device 51 further stores an execution reservation management table 14. The cooperation service management unit 6 further has a reservation time management unit 15. Other configurations are the same as those in FIG.
[0052]
The cooperative service management unit 6 can provide all the services of the service group required by the request information received from the service requester 12 by the receiving unit 52 based on the current provision status of each service of the service group. The execution unit 54 reserves execution of all the services of the service group required by the request information at a possible time, and the execution unit 54 transmits the service requester 12 from the service requester 12 by the reception unit 52 at the time reserved by the cooperation service management unit 6. All the services of the service group requested by the received request information are executed and provided to the service requester 12.
[0053]
FIG. 12 is a flowchart illustrating the operation of the sixth embodiment.
The reservation time management unit 15 in the cooperation service management unit 6 of the service coordinator 5 searches the cooperation service execution management table 11 if it cannot be accepted in S210, and obtains the time when the service can be executed (S225). Is registered in the execution reservation management table 14 at that time (S226).
The reservation time management unit 15 registers the time in the cooperation service execution management table 11 (S212), and sets a timer at the reservation time (S227).
The reservation time management unit 15 in the coordination service management unit 6 of the service coordinator transmits, via the transmission unit 53, the service requester 12 and the time when the execution of the coordination service has been reserved, to the service requester 12 (S228).
The execution unit 54 of the service coordinator starts the execution process of the cooperative service at the time set in the timer (S214).
[0054]
FIG. 13 is a diagram illustrating an example of an execution reservation management table according to the sixth embodiment.
The execution reservation management table 14 manages reservation times, cooperative service names, and client names.
[0055]
As described above, in the sixth embodiment, when a request for a service that cannot be accepted at present is requested, the time when the request can be accepted is notified from the cooperation service execution management status, and the execution reservation management table is set. The execution start from that time is reserved by this table.
[0056]
According to the sixth embodiment, it is possible to know when a cooperative service that cannot be executed at present becomes executable, reserve its start, and execute it without re-executing it.
[0057]
Embodiment 7 FIG.
In each of the above embodiments, the review of the SLA definition information is limited to the services constituting the cooperative service to be executed. In the seventh embodiment, the service level can be changed by extending the review of the SLA definition information to all services, thereby predicting the demand for all the managed services.
[0058]
When the request for the cooperative service 2 is received in the state of the management state 502 in FIG. 5, the cooperative service 2 executes the service B2 and can be received. However, at 00:00:20, the number of services B1 is 500 which can be processed as defined in the SLA information, indicating that the service B1 cannot be accepted. Therefore, the service coordinator 5 adjusts the increase of the SLA with the service providers 21 and 31. If the SLA can be increased, the service coordinator 5 can receive the cooperative service 1 in advance. At this time, the storage device 51 holds the temporarily changed processable number as the temporarily processable number of the SLA information 10.
[0059]
FIG. 14 illustrates the operation of the seventh embodiment.
After dividing the processing time of each service into the management unit time of the cooperation service execution management table 11 (S603), the cooperation service management unit 6 assigns a unit The number of cases currently managed per hour is compared with the number of cases that can be processed (S611), and if there is room for change by executing the steps from S218 to S224 in FIG. 7 (S612), the SLA definition information is changed. (S613) After the processing for all services is completed (S614), the processing of S604 is executed.
[0060]
As described above, in the seventh embodiment, regardless of the service request request from the service requester 12, the service level fluctuation can be predicted from the currently managed cooperative service execution management status, and the service level agreement can be changed in advance. It has a configuration.
[0061]
According to the seventh embodiment, a service request can be predicted, and by changing the SLA information in advance, there is an effect that the number of cases that cannot be executed at the time of request is reduced.
[0062]
Embodiment 8 FIG.
In the eighth embodiment, in addition to the above-described seventh embodiment, the number of processed cases of all services is checked, and if there is a service that is likely to be insufficient (for example, 90% of the number of processes that can be processed is executed), the service can be processed. Change the SLA to increase the number of cases.
FIG. 15 is a flowchart illustrating the operation of the eighth embodiment.
The cooperative service management unit 6 divides the processing time of each service into the management unit time of the cooperative service execution management table (S603), and then sets the unit time for all the services managed in the cooperative service execution management table 11. The number of cases that can be processed and the number of cases that can be processed are compared (S611), and if there is room for change (increase) by executing the steps from S218 to S224 in FIG. 7 (S612), the SLA definition information is changed. After the change (increase) (S613), and the processing is completed for all services (S614), the processing of S604 is executed.
[0063]
As described above, in the eighth embodiment, a change in service level can be predicted from the currently managed cooperative service execution management status, and the service level can be increased in advance.
[0064]
According to the eighth embodiment, the number of cases that can be processed can be increased in advance, and there is an effect that the possibility that execution of the cooperative service fails is reduced.
[0065]
Embodiment 9 FIG.
In the ninth embodiment, in addition to the seventh embodiment, the number of processed cases of all services is checked, and if there is a service that is likely to be excessive (for example, only 20% or less of the number of processes that can be processed is executed), processing is possible. Change the SLA to reduce the number of cases.
FIG. 16 is a flowchart illustrating the operation of the ninth embodiment.
After dividing the processing time of each service into the management unit time of the cooperation service execution management table 11 (S603), the cooperation service management unit 6 assigns a unit The number of cases currently managed per hour is compared with the number of cases that can be processed (S611), and if there is room for change (decrease) by executing the steps from S218 to S224 in FIG. 7 (S612), the SLA definition information Is changed (decreased) (S613), and after the processing is completed for all services (S614), the processing of S604 is executed.
[0066]
As described above, in the ninth embodiment, a change in service level can be predicted from the currently managed cooperative service execution management status, and the service level can be reduced in advance.
[0067]
According to the ninth embodiment, the number of cases that can be processed can be reduced in advance, and there is an effect that the possibility that another service provider fails to execute a cooperative service is reduced.
[0068]
Embodiment 10 FIG.
In the eighth embodiment, the number of cooperative services that can be processed can be changed in advance, but the service requester of the cooperative service that has already been reserved has no means of knowing it, and cannot be changed.
In the tenth embodiment, a change in service level is predicted from the currently managed cooperative service execution management status, the service level is increased in advance, and the cooperative service management unit is changed when the time available for accepting a request is shortened. Notify the time.
[0069]
FIG. 17 is a flowchart illustrating the operation of the tenth embodiment.
After dividing the processing time of each service into the management unit time of the cooperation service execution management table 11 (S603), the cooperation service management unit 6 assigns a unit The number of cases currently managed per hour and the number of cases that can be processed are compared (S611), and if there is room for change (increase) by executing the steps from S218 to S224 in FIG. 7 (S612), the SLA definition information Is changed (increased) (S613), and after all services have been processed (S614), if there is a service whose start time can be changed among the cooperative services currently reserved in the execution reservation management table 14 (S615). Then, the service requester 12 is notified that the reservation time can be changed (S616), and the processing of S604 is executed.
[0070]
According to the tenth embodiment, the service requester can be notified of the time when the service can be accepted, and the waiting time of the service requester can be reduced.
[0071]
Embodiment 11 FIG.
In the sixth and tenth embodiments, the reserved time cannot be changed even if the time at which the cooperative service can be executed becomes earlier.
In the eleventh embodiment, the service level fluctuation is predicted from the currently managed cooperative service execution management status, and when the service level can be increased in advance and the time available for accepting requests is earlier, the cooperative service execution management unit Changes the reserved time at which to start executing.
[0072]
FIG. 18 is a flowchart illustrating the operation of the eleventh embodiment. The cooperative service management unit 6 divides the processing time of each service into the management unit time of the cooperative service execution management table (S603), and then sets the unit time for all the services managed in the cooperative service execution management table 11. The number of cases that can be processed and the number of cases that can be processed are compared (S611), and if there is room for change (increase) by executing the steps from S218 to S224 in FIG. 7 (S612), the SLA definition information is changed. After the change (increase) (S613) and the processing for all services is completed (S614), if there is a service whose start time can be changed among the cooperative services currently reserved in the execution reservation management table 14 (S615), The reservation time is changed (S616), and the process of S604 is executed.
[0073]
According to the eleventh embodiment, when the time at which the reserved cooperative service becomes executable becomes earlier, the reservation time can be changed, and the cooperative service execution result can be obtained earlier.
[0074]
In the above description of the embodiments, the service providers 21 and 31, the service coordinator 5, and the service requester 12 are not shown, but a system unit, a CRT (Cathode Ray Tube) display device, and a keyboard (K / B). , A mouse, a compact disk device (CDD), a printer device, and a scanner device. The CRT display device, K / B, mouse, CDD, printer device, and scanner device are connected to the system unit by cables.
Although not shown, the service providers 21 and 31, the service coordinator 5, and the service requester 12 each include a CPU (Central Processing Unit) that executes a program. The CPU is connected to a ROM (Read Only Memory) (an example of a storage device), a RAM (Random Access Memory) (an example of a storage device), a communication board, a CRT display device, a K / B, a mouse, via a bus. It is connected to an FDD (Flexible Disk Drive), a magnetic disk device (an example of a storage device), a CDD, a printer device, and a scanner device. The communication board is connected to the Internet.
Here, the communication board is not limited to the Internet, and may be connected to a LAN (Local Area Network) or a WAN (Wide Area Network) such as ISDN.
The magnetic disk device stores an operating system (OS), a window system, a group of programs, and a group of files. The program group is executed by a CPU, an OS, and a window system.
[0075]
Further, in the above description, what is described as “-unit” in the description of each embodiment can be partially or entirely configured by a computer-operable program. These programs can be created in C language, for example. Alternatively, HTML, SGML, or XML may be used. Alternatively, the screen may be displayed using JAVA (registered trademark).
When constituted by programs, the programs stored in the above-described program group are those executed by those described as “-unit” in the description of each embodiment. In the file group, those described as "-information" and "-table" in the description of the above embodiment are stored.
In addition, what is described as “-unit” in the description of each embodiment may be realized by firmware stored in a ROM. Alternatively, the present invention may be implemented by software, hardware, or a combination of software, hardware, and firmware.
Further, a program for implementing the above-described embodiments includes a magnetic disk device, an FD (Flexible Disk), an optical disk, a CD (Compact Disk), an MD (Mini Disk), a DVD (Digital Versatile Disk), and the like. The information may be stored using a recording device using a medium.
The output unit may use an output device such as a CRT display device, another display device, or a printer device.
[0076]
【The invention's effect】
According to the present invention, it is possible to provide an apparatus capable of guaranteeing a response requirement among user requirements and executing a plurality of services in combination.
[Brief description of the drawings]
FIG. 1 is a configuration diagram illustrating an example of a service cooperation control method according to a first embodiment.
FIG. 2 is a flowchart illustrating an operation of a service cooperation control method according to the first embodiment.
FIG. 3 is a diagram illustrating an example of service level agreement (SLA) information according to the first embodiment;
FIG. 4 is a diagram showing an example of linked service definition information according to the first embodiment.
FIG. 5 is a diagram illustrating an example of a cooperative service execution management table according to the first embodiment;
FIG. 6 is a flowchart illustrating a procedure for checking a cooperation service execution management table.
FIG. 7 is a diagram illustrating the operation of the second embodiment.
FIG. 8 is a flowchart illustrating the operation of the third embodiment.
FIG. 9 is a flowchart illustrating the operation of the fourth embodiment.
FIG. 10 is a flowchart illustrating the operation of the fifth embodiment.
FIG. 11 is a configuration diagram illustrating an example of a service cooperation control method according to a sixth embodiment.
FIG. 12 is a flowchart illustrating the operation of the sixth embodiment.
FIG. 13 is a diagram illustrating an example of an execution reservation management table according to the sixth embodiment.
FIG. 14 is a diagram illustrating the operation of the seventh embodiment.
FIG. 15 is a flowchart illustrating the operation of the eighth embodiment.
FIG. 16 is a flowchart illustrating the operation of the ninth embodiment.
FIG. 17 is a flowchart illustrating the operation of the tenth embodiment.
FIG. 18 is a flowchart illustrating an operation of the eleventh embodiment.
[Explanation of symbols]
1 cooperation service, 2 cooperation service, 5 service coordinator, 6 cooperation service management unit, 7 SLA processing unit, 8 cooperation service execution management unit, 9 cooperation service definition, 10 SLA information, 11 cooperation service execution management table, 12 service requester, 14 execution reservation management table, 15 reservation time management unit, 21 service provider, 22 provided service, 23 load information, 24 SLA processing unit, 25 storage device, 31 service provider, 32 provided service, 33 load information, 34 SLA processing unit, 35 storage device, 51 storage device, 52 reception unit, 53 transmission unit, 54 execution unit, 121 storage device, 501 management state, 502 management state.

Claims (10)

A storage unit that stores a plurality of service provision condition information indicating service provision conditions of the plurality of services,
A receiving unit that receives request information requesting to provide each service of a service group in which some of the plurality of services are combined as a group;
A service group that manages the current provision status of each service of the service group and that is requested by the request information received by the reception unit based on the service provision conditions indicated by the plurality of service provision condition information stored by the storage unit A management unit that determines whether it is possible to provide each service of
A service providing device, comprising: an execution unit that provides each service of a service group required by the request information received by the reception unit based on a result determined by the management unit. A storage unit that stores a plurality of service provision condition information indicating service provision conditions of a plurality of services set in advance with a service provider that provides a service,
A receiving unit that receives, from a service requester, request information requesting to provide each service of a service group obtained by combining any of the plurality of services as a group, and receives each service of the service group from the service provider; When,
A service group that manages the current provision status of each service of the service group and that is requested by the request information received by the reception unit based on the service provision conditions indicated by the plurality of service provision condition information stored by the storage unit A management unit that determines whether it is possible to provide each service of
Based on the result determined by the management unit, the request unit receives the request information received from the service requester by the reception unit. The service unit executes each service of the service group received from the service provider by the reception unit. A service coordinator device comprising: The service coordinator device further includes, when the request information received by the reception unit cannot provide all the services of the service group required by the reception unit as a result of the determination by the management unit, the request received by the reception unit. 3. The service coordinator device according to claim 2, further comprising a transmission unit that transmits reception rejection information for rejecting information reception to the service requester. The service coordinator further transmits to the service provider inquiry information requesting a change in service provision conditions indicated by at least one of the plurality of service provision condition information stored in the storage unit. With
The receiving unit receives response information to the inquiry information transmitted by the transmitting unit,
The management unit, based on the response information received by the receiving unit, determines whether it is possible to provide all the services of the service group required by the request information received by the receiving unit,
The execution unit, based on a result determined by the management unit based on the answer information, requests the request information received from the service requester by the reception unit, the service received from the service provider by the reception unit is obtained by the reception unit 3. The service coordinator according to claim 2, wherein all the services of the group are executed and provided to the service requester. The management unit determines a time at which all the services of the service group required by the request information received by the reception unit can be provided, based on a current provision status of each service of the service group to be managed. ,
4. The service coordinator according to claim 3, wherein the transmission unit transmits the time determined by the management unit to the service requester. The management unit, based on the current provision status of each service of the service group, the request information is received at a time when all the services of the service group required by the request information received by the reception unit can be provided. Reserve the execution of all services of the desired service group,
The execution unit executes all services of a service group requested by the request information received from the service requester by the reception unit at a time reserved by the management unit, and provides the service requester with the service group. 4. The service coordinator device according to claim 3, wherein A storage step of storing a plurality of service provision condition information indicating service provision conditions of a plurality of services in a storage device,
A receiving step of receiving request information for providing each service of a service group in which some of the plurality of services are combined as a group;
A service group that manages the current provision status of each service of the service group and that is requested by the request information received in the receiving step based on the service provision conditions indicated by the plurality of service provision condition information stored in the storage step A management process for determining whether it is possible to provide each service of
A service providing method for providing each service of a service group required by the request information received in the receiving step based on a result determined in the managing step. A storage step of storing a plurality of service provision condition information indicating service provision conditions of a plurality of services set in advance with a service provider that provides a service in a storage device,
A receiving step of receiving, from a service requester, request information for providing each service of a service group obtained by combining any of the plurality of services as a group, and receiving each service of the service group from the service provider; When,
A service group that manages the current provision status of each service of the service group and that is requested by the request information received in the receiving step based on the service provision conditions indicated by the plurality of service provision condition information stored in the storage step A management process for determining whether it is possible to provide each service of
Based on the result determined by the managing step, the request information received from the service requester in the receiving step is executed. Each service of the service group received from the service provider in the receiving step is obtained. A service coordinating method comprising: an execution step of providing a service. A storage process of storing a plurality of service provision condition information indicating service provision conditions of a plurality of services in a storage device;
A receiving process of receiving request information for requesting to provide each service of a service group in which some of the plurality of services are combined as a group;
A service group that manages the current provision status of each service of the service group and that is requested by the request information received by the reception process based on the service provision conditions indicated by the plurality of service provision condition information stored by the storage process Management processing to determine whether it is possible to provide each service of,
On the basis of the result determined by the management process, a program for causing a computer to execute an execution process of providing each service of a service group required by the request information received by the reception process or the program is recorded. Computer-readable recording medium. A storage process of storing a plurality of service providing condition information indicating service providing conditions of a plurality of services set in advance with a service provider that provides a service in a storage device;
A receiving process for receiving, from a service requester, request information for providing each service of a service group obtained by combining any of the plurality of services as a group, and receiving each service of the service group from the service provider; When,
A service group that manages the current provision status of each service of the service group and that is requested by the request information received by the reception process based on the service provision conditions indicated by the plurality of service provision condition information stored by the storage process Management processing to determine whether it is possible to provide each service of,
On the basis of the result determined by the management processing, the request information received from the service requester by the reception processing is executed. Each service of the service group received from the service provider is executed by the reception processing. For causing a computer to execute the execution process provided by the computer or a computer-readable recording medium on which the program is recorded.

Images