JP2003091514A - Client server system and method therefor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable a user of a client device to select a server device appropriate to execution of a service on the basis of a past history. SOLUTION: In this system, a service history generation means generates the service history showing possibility or the like of provision of the service by that server device to one of the client devices and the server devices, from stored information. A history request means request notice of the service history to the server device via a network. A history notice means notifies the request origin client device of the service history according to the request from the client device. A server device selection means display the service history received from the server device to the user as a UI image and selects the server device capable of properly executing the service according to user's operation.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a client / server system in which a client device and a server device are connected via a network. Further, the present invention relates to a service notifying method for notifying a client device of information on a service provided by a server device in a client server system. The present invention also relates to a server device selection method for selecting a server device in a client device based on the notified service. The present invention also relates to a server device and a client device that form the above-mentioned client server system. Also,
The present invention relates to a program for executing the above method in the above server device and client device.

[0002]

2. Description of the Related Art A client server system is used in which a client device and a server device are connected via a network, and the server device provides a service in response to a request from the client device. In such a system, as a method for supporting a user who wants to use a server device from a client device, for example, “Japanese Patent Laid-Open No. 2000-172469” (reference 1) stores setting information in a printer and automatically sets the setting. A method for selectively selecting a target is disclosed.

Further, "Japanese Patent Laid-Open No. 2000-148425" (Reference 2) manages information on a print shop,
A method of analyzing submitted orders and selecting a suitable print shop is disclosed. However, in any of the methods disclosed in the documents, a combination of server devices is used when a suitable server device is selected by using the past history or a plurality of server devices is required to execute a job. Cannot be presented to anyone,

[0004]

SUMMARY OF THE INVENTION The present invention has been made in view of the above-mentioned problems of the prior art, and enables a user to select an appropriate server device based on a past history. It is an object of the present invention to provide a client server system and a method thereof. Further, according to the present invention, when it is necessary to link a plurality of server devices to a job execution based on a past history, it is possible to show the user an optimal combination of server devices for a job execution in a short time. It is an object of the present invention to provide a client-server system and a method therefor.

[0005]

[First Client / Server System] In order to achieve the above object, a first client / server system according to the present invention includes a plurality of server devices each providing a predetermined service, A client-server system including one or more client devices each requesting a service to the server device, wherein each of the one or more client devices has a service history for each of the plurality of server devices. History requesting means for requesting notification of a service history indicating the service history, and server device selection for selecting one or more of the plurality of server devices based on the service history returned from the plurality of server devices in response to the request. Means and service requesting means for requesting a service from the selected one or more server devices The a, each of the plurality of server devices, and a service history generating means for generating the service history, in response to a request from the client device,
A history notifying unit for notifying the generated service history.

[0006] Preferably, the service history of each of the server devices includes auxiliary information indicating at least one of the server device and the client device involved in the service, and the server device selection means of each of the client devices is One or more of the plurality of server devices are selected based on the service to be requested and the auxiliary information included in the service history from the server device.

[Description of First Client / Server System] The first client / server system according to the present invention will be described below with reference to an example. Note that the following examples are intended to embody the present invention and help understanding thereof, and are not intended to limit the technical scope of the present invention. Further, the client device and the server device simply mean a device requesting a service and a device providing a service, and a device having such a function is a client according to the present invention regardless of its name. It is included in the device and the server device.

In a client server system according to the present invention, a client device such as a personal computer (PC) and a server device such as a network printer device and a network scanner are connected via a network such as Ethernet (registered trademark). Composed. A client device (PC) requests a service from a server device (printer / scanner) via a network, and the server device executes the service in response to a request from the client device.

[Service History Generating Means] The server device
Information is stored such as which client device and server device the service was provided to, and whether each provided service ended in success or failed. Based on the stored information, the service history generation means of the server device determines to which client device and server device the server device can provide the service, and with which server device the cooperation operation can be performed. Generate the service history shown.

[History Requesting Means] The history requesting means of the client device requests the server device via the network to notify the service history generated by the server device.

[History Notifying Unit] The history notifying unit of the server device notifies the generated client service history to the requesting client device in response to a request from the client device.

[Server device selection means] The server device selection means of the client device displays the service history received from the server device to the user as a user interface (UI) image, for example. When the user performs a selection operation on the UI image, the server selection means can appropriately execute the service to be requested according to the operation (the service to be requested includes a plurality of server devices). Server device combination) is selected in the case of execution by a combination of.

[Service Requesting Means] The service requesting means of the client device requests the server device selected by the server device selecting means to provide a service.

[Second Client / Server System] A second client / server system according to the present invention includes a plurality of server devices each providing a predetermined service, and a plurality of server devices each requesting the service from the server device. A client-server system including a first client device and a second client device, wherein the first client device indicates to the second client device a service history of each of the plurality of server devices. History requesting means for requesting notification of service history, and server device selecting means for selecting one or more of the plurality of server devices based on the service history returned from the second client device in response to the request. , A service requesting a service to the selected one or more server devices The second client device, the second client device having a service history generating device for generating the service history, and a history notification for notifying the generated service history in response to a request from the first client device. And means.

Preferably, the service history of the second client device includes a server device and a client device involved in the service, or auxiliary information indicating at least one of them, and the server device selection of the first client device. The means selects one or more of the plurality of server devices based on the service to be requested and the auxiliary information included in the service history from the server device.

[0016] Preferably, the second client device has history requesting means for requesting notification of service history to each of the plurality of server devices.
The service history generation means of the client device generates the service history from the service history returned from each of the plurality of server devices in response to the request.

The service history generating means of the second client device generates the service history based on the server device and / or the client device involved in the service provided by each of the plurality of server devices, or one of them. .

[First Client Device of Second Client / Server System] Each component of the first client device of the second client / server system is
The configuration is almost the same as the corresponding components in the client device of the first client server system described above. However, the history requesting means of the second client device is different in that it requests the second client device to notify the service history, not to each server device.

[Second Client Device of Second Client / Server System] The second client device, as described above, to which client device and server device the second client device has provided the service, Upon receiving notification of service information indicating whether or not each provided service has succeeded, a service history is generated. The generated service history is notified to the requesting first client device in response to a request from the first client device and is used for server selection.

[Third Client / Server System] Further, a third client / server system according to the present invention includes a plurality of first server devices each providing a predetermined service, and a plurality of first server devices for each of the first server devices. A client-server system including one or more client devices for requesting a service, and a second server device for providing the client device with a history of services of each of the plurality of first server devices. The device is configured to send the first server device to the second server device.
Of the plurality of first server devices based on the history requesting means for requesting the notification of the service history showing the service history of each server device, and the service history returned from the second server device in response to the request. Server device selecting means for selecting one or more of the above, and service requesting means for requesting a service to the selected one or more first server devices, wherein the second server device is A service history generating means for generating the service history, and a history notifying means for notifying the generated service history in response to a request from the client device.

[0021] Preferably, the service history of the second server device includes auxiliary information indicating at least a server device and a client device that have provided a service, or any one of these, and the server device selecting means of the client device, One or more of the plurality of server devices are selected based on the service to be requested and the auxiliary information included in the service history from the server device.

Preferably, the second server device has history requesting means for requesting notification of service history to each of the plurality of first server devices, and the second server device includes The service history generation means generates the service history from the service history returned from each of the plurality of server devices in response to the request.

Preferably, the first server device and the client device transmit service-related data via a network, and the second server device is connected to the network and the second server device is connected to the network. The server device is
It has monitor means for monitoring data relating to services transmitted between each of the plurality of first server devices and each of the client devices, and the service history generation means of the second server device monitors the data. The service history is generated based on the data.

[Second Server Device of Third Client / Server System] The third client / server system further includes a second server device for creating / managing a service history in the above-mentioned first client / server system. Take the configuration. In the third client-server system, each client device receives the service history notification from the second server device and selects the server device.

[First Server Device] The first server device according to the present invention includes a plurality of server devices each providing a predetermined service, and one or more server devices each requesting the service from the server device. In the client server system including the client device, each of the one or more client devices requests a service history notification indicating a service history to each of the plurality of server devices, Based on service histories returned from a plurality of server devices in response to the request, one or more of the plurality of server devices are selected, and a service is provided to the one or more selected server devices. A service history generating unit that requests and generates the service history, and generates the service history in response to a request from the client device. To notify the service history and a history notification means.

[First Client Device] The first client device according to the present invention includes a plurality of server devices each providing a predetermined service, and one or more server devices each requesting the service to the server device. In the client server system including the client device, the plurality of server devices each generate the service history, and notify the generated service history in response to a request from the client device. , History request means for requesting notification of service history indicating a history of service to each of the plurality of server devices, and the plurality of server devices based on the service history returned from the plurality of server devices in response to the request. Server device selecting means for selecting one or more of the server devices, and the selected one. Against above server device, and a service request unit for requesting the service.

[Second Client Device] Further, a second client device according to the present invention includes a plurality of server devices each providing a predetermined service and a first client device requesting a service from each of the server devices. The second client device in a client-server system including a client device and a second client device, wherein the first client device is the second client device.
Requesting a service history notification indicating the history of services of each of the plurality of server devices, and based on the service history returned from the second client device in response to the request, the plurality of servers. A service history generating means for selecting one or more of the devices, requesting a service from the selected one or more server devices, and generating the service history; History notification means for notifying the generated service history in response to a request.

Preferably, the service history generating means is
The service history is generated based on the server device and / or the client device that has provided the service provided by each of the plurality of server devices.

[Second Server Device] Further, a second server device according to the present invention includes a plurality of first server devices each providing a predetermined service, and a service for each of the first server devices. One or more client devices requesting a request, and the plurality of first devices to the client device.
Providing a history of services of each server device of the second
A second server device in a client-server system including the server device, the client device having a service history indicating a history of services of the first server device with respect to the second server device. Requesting the notification, selecting one or more of the plurality of first server devices based on the service history returned from the second server device in response to the request, and selecting the selected one.
Service history generating means for requesting a service from one or more first server devices and generating the service history, and history notifying means for notifying the generated service history in response to a request from the client device. Have and.

Preferably, the first server device and the client device transmit service-related data via a network, the second server device is connected to the network, and the plurality of first server devices are connected to the network. 1 has a monitor unit for monitoring data relating to a service transmitted between each of the server device and each of the client devices, and the service history generation unit generates the service history based on the monitored data. To do.

[First Service Notification Method] Further, the first service notification method according to the present invention is such that a plurality of server devices each providing a predetermined service and a service request to each of the server devices are requested. A service notification method in the server device in a client-server system including one or more client devices, comprising:
Each of the one or more client devices requests a notification of a service history indicating a service history from each of the plurality of server devices, and based on the service history returned from the plurality of server devices in response to the request. Select one or more of the plurality of server devices, request a service from the selected one or more server devices, generate the service history, and make a request from the client device. Accordingly, the generated service history is notified.

[Server Device Selection Method] The server device selection method according to the present invention also includes a plurality of server devices each providing a predetermined service, and one or more clients each requesting a service to the server device. A method for selecting a server device in the client device in a client server system including a device,
Each of the plurality of server devices generates the service history, notifies the generated service history in response to a request from the client device, and indicates a service history to each of the plurality of server devices. Requesting notification of history, selecting one or more of the plurality of server devices based on the service history returned from the plurality of server devices in response to the request, and selecting the one or more servers Request service from the device.

[Second Service Notification Method] A second service notification method according to the present invention includes a plurality of server devices each providing a predetermined service, and a plurality of server devices each requesting the service. A service notification method in the second client device in a client server system including a first client device and a second client device, wherein the first client device is configured to: Requesting notification of a service history indicating the history of services of each of the plurality of server devices, and determining one or more of the plurality of server devices based on the service history returned from the second client device in response to the request. Selected,
A service is requested to the selected one or more server devices, the service history is generated, and the generated service history is notified in response to a request from the first client device.

[Third Service Notifying Method] A third service notifying method according to the present invention is directed to a plurality of first server devices each providing a predetermined service and to each of the first server devices. Second server in a client-server system including one or more client devices requesting a service based on a request, and a second server device providing the client device with a history of services of each of the plurality of first server devices. A service notification method in an apparatus, wherein the client apparatus requests the second server apparatus to notify a service history indicating a history of each service of the first server apparatus, and in response to the request. Select one or more of the plurality of first server devices based on the service history returned from the second server device. , The selected one or more of the first
Requesting a service, generating the service history, and notifying the generated service history in response to a request from the client apparatus.

[First Service Notification Program] Also,
A first service notification program according to the present invention is a client-server system that includes a plurality of server devices that respectively provide a predetermined service, and one or more client devices that respectively request the server device for the service. A service notification program in a server device, wherein each of the one or more client devices requests a notification of a service history indicating a service history from each of the plurality of server devices, and a plurality of client devices respond to the request. Based on the service history returned from the server device, one or more of the plurality of server devices are selected, a service is requested to the selected one or more server devices, and the service history is displayed. In response to the generating step and the request from the client device,
Causing the computer to execute the step of notifying the generated service history.

[Server Selection Program] Further, the server selection program according to the present invention includes a plurality of server devices each providing a predetermined service, and one or more client devices each requesting a service to the server device. A server device selection program in the client device in a client server system including: each of the plurality of server devices generates the service history, and notifies the generated service history in response to a request from the client device. Then, a step of requesting a notification of service history indicating a history of service to each of the plurality of server devices, and the plurality of servers based on the service history returned from the plurality of server devices in response to the request Selecting one or more of the devices, and For the selected one or more server devices, and a step of requesting a service to the computer.

[Second Service Notification Program] Also,
A second service notification program according to the present invention includes a plurality of server devices each providing a predetermined service, and a first server device requesting a service from each of the server devices.
A service notification program in the second client device in a client-server system including the client device and the second client device, wherein One of the plurality of server devices based on the service history returned from the second client device in response to the request, requesting notification of the service history indicating the service history of each of the server devices.
Selecting one or more, requesting a service from the selected one or more server devices, and generating the service history; and generating the service history in response to a request from the first client device. Causing the computer to execute the steps of notifying the service history.

[Third Service Notification Program] Also,
A third service notification program according to the present invention includes a plurality of first server devices each providing a predetermined service, and one or more client devices requesting a service from the first server device, respectively. A service notification program in the second server device in a client server system, comprising: a second server device that provides a history of services of each of the plurality of first server devices to the client device; , The first server with respect to the second server device
One of the plurality of first server devices based on the service history returned from the second server device in response to the request, requesting a service history notification indicating the service history of each server device Selecting the above, requesting a service from the selected one or more first server devices, and generating the service history; and the generated service in response to a request from the client device. And notifying the history.

[0039]

BEST MODE FOR CARRYING OUT THE INVENTION [Background of the Invention] First, a technology as a background of the present invention will be described. FIG. 1 is a diagram illustrating an information processing device. As illustrated in FIG. 1, when connected to a network and receiving a processing request and an input, processing is performed,
An information processing device that outputs a processing result is used. There is a tendency for such information processing apparatuses to become more and more diverse in the future, and it is important to select an optimum information processing apparatus from many information processing apparatuses.

For example, a conversion process of a physically existing object or an image in which it is captured and electronic information, that is, conversion from a paper document (printed matter) to an electronic document (image data) or an electronic document to a paper document. When the processing is performed using the information processing apparatus as illustrated in FIG. 1, the attributes of the image to be converted (color / black and white, the number of pages, the number of copies, etc.), the attributes of the information processing apparatus (color / black and white). In addition, there are many items that must be considered in order to select the optimum information processing device, such as information related to management such as usage rights.

FIGS. 2 to 4 are first to third examples illustrating first to third processes executed by linking a plurality of information processing apparatuses.
FIG. Further, as illustrated in FIGS. 2 to 4, when a plurality of types of processing apparatuses are combined to perform processing, among a large number of combinations of attributes of paper documents and electronic documents and attributes of information processing apparatuses. From
Since it is necessary to search for a suitable one, it becomes more difficult to select the optimum information processing device.

As an example of the method of selecting the information processing apparatus described above, a method of using a database can be considered. However, the method using the database is appropriate because the administrator of the computer network registers / manages the attributes of the information processing apparatus connected to the computer network in the database, and the person who uses the information processing apparatus refers to the database. It is necessary to select an appropriate information processing device. Therefore, according to this method, the type of information processing device
As the number of machines increases, the labor and effort of the administrator increases,
In addition, information processing devices that the administrator does not know are not registered in the database.

Further, a method of selecting an information processing device based on the past record (history) of use of the information processing device can be considered. This is a method in which a device or the like that has requested processing retains information such as the address of the processing request destination as a history, and when a similar processing request occurs again, the history is referred to and the processing request destination is selected. For example, the use of a bookmark of a web browser and the use of a fax transmission history can be cited as examples of this method. However,
Such a history can be referenced only by the device itself that holds the history.

FIG. 5 is a diagram exemplifying the history held in the terminal for instructing the processing and the device for performing the conversion processing. According to the present invention, when a plurality of various, various, and many information processing devices connected to a computer network are combined to perform cooperative processing, the history held in the device as shown in FIG. By making it possible to refer to each device, each device connected to the network can select an optimum information processing device.

[First Embodiment] The first embodiment of the present invention will be described below. FIG. 6 is a diagram illustrating a configuration of the network system 1. As shown in FIG. 6, the network system 1 includes a scanner device 12 and a printer device 14 that provide services as a server device, and a plurality of personal computers (PCs) 16 and 16 ′ that request services from the server device as client devices. A history server 18 (details will be described later in the third embodiment) is connected via a network 10 such as Ethernet and TCP / IP.

[Hardware Configuration] FIG. 7 is a diagram showing the hardware configuration of the scanner device 12 shown in FIG. As shown in FIG. 7, the scanner device 12 includes a CPU 1
02, memory 104, and other control devices 100, C
A display device 110 such as an RT display device, an input device 112 such as a keyboard / mouse, a communication device 114 that performs data communication with the network 10, a scanner unit 120 that reads an image into image data, and a CD-ROM.
A storage device 130 such as an HDD.

That is, the scanner device 12 is provided with a service via the network 10 from the printer device 14 and the PC 16 (hereinafter, simply referred to as “PC 16” when either one of the PCs 16 and 16 ′ is shown without being specified). It is configured as a network scanner that receives an image, reads an image, and returns the obtained image data to the request source.

FIG. 8 is a diagram showing a hardware configuration of the printer device 14 shown in FIG. As shown in FIG.
The printer device 14 has a configuration in which the scanner device 120 of the scanner device 12 is replaced with a printer unit 140. That is, the printer device 14 is configured as a network printer that receives a service request from the PC 16 via the network 10 and prints image data.

FIG. 9 is a diagram showing the configuration of the PC 16 shown in FIG. As shown in FIG. 9, the PC 16 replaces the control device 100 with the PC main body 160, and the scanner device 12
The scanner device 120 is removed from the configuration shown in FIG. 7, and the computer is configured as a general computer capable of communicating via a network. The history server 18
Also has the same configuration as the PC 16 (not shown).

[Software on Server Side] FIG. 10
In the scanner device 12 (FIG. 7) and the printer device 14 (FIG. 8) shown in FIG. 6, provides a service in cooperation with other nodes and stores and manages the history of the provided service. It is a figure which shows the structure of. As shown in FIG. 10, the cooperation management program 2 includes a communication control unit 200, a cooperation control unit 202, a device control unit 206, and a cooperation management unit 22. Cooperation management unit 22
Includes a cooperation monitor 220, a cooperation history database (cooperation history DB) 222, a cooperation history storage unit 224, and a cooperation history notification unit 226.

As described above, also in the scanner device 12, the cooperation management program 2 is executed in the same manner as in the printer device 14 to realize the same function, but here, for simplification of description, the printer will be described below. A case where the cooperation management program 2 is executed in the device 14 will be described.
The cooperation management program 2, for example, is supplied to the printer device 14 via the recording medium 132, loaded into the memory 102 (FIG. 8), and executed.

With these components, the cooperation management program 2 provides a history of services independently provided to the PC 16 by the printer device 14 (service history) and the printer device 14 in cooperation with the scanner device 12 to the PC 16. Store and manage the history of services you have done. Further, the cooperation management program 2 notifies the PC 16 of the stored and managed service history in response to the request from the PC 16.

[Communication Control Unit 200] FIG. 11 is a diagram showing an Ethernet data frame and an IP packet. FIG. 12 is a diagram showing an IP header of an IP packet transmitted using the payload portion of the Ethernet data frame shown in FIG. The communication control unit 200 (FIG. 10) controls the communication device 114 to operate the network 1
0 to another node (scanner device 12, PC 16,
16 'and the history server 18).

That is, the communication control unit 200 sends data input from other components of the cooperation management program 2 to other nodes, and also receives data sent from other nodes via the network 10. Then, it outputs to other components of the cooperation management program 2. For transmitting data between the printer device 14 and another node, for example,
The Ethernet frame shown in FIG. 11 is used, and the IP packet shown in FIG. 11 is attached to the data transmitted in the payload part of the Ethernet data frame.

[Cooperation control unit 202] Coordination control unit 202
(FIG. 10) performs processing for cooperating with other nodes in various modes as illustrated in FIGS. 2 to 4 in response to a service request from the PC 16. That is, as shown in FIG. 2, the cooperation control unit 202 performs control for cooperation with the PC 16 when printing the image data sent from the PC 16. Further, in the cooperation control unit 202, as shown in FIG. 3, the PC 16 requests a service from the scanner device 12, and the scanner device 12 causes the printer device 14 to execute a service.
When a print request is issued to the scanner device 12, control is performed to cooperate with the scanner device 12. Further, as illustrated in FIG. 4, when the PC 16 requests a service from the printer device 14 and the printer device 14 requests the scanner device 12 to read an image, the PC device 16 cooperates with the scanner device 12 and the PC 16. For processing.

[Device Control Unit 206] The device control unit 206 controls the printer unit 140 according to the control of the cooperation control unit 202, prints the image data sent from the PC 16 or the scanner device 12, and provides a print service. To do.

[Cooperation Monitor 220] Coordination Monitor 220
Indicates services provided by the printer device 14 in cooperation with other nodes by monitoring data processed by the cooperation control unit 202. For example, cooperation information including cooperation destination information, setting information, and normal / abnormal end information described below. To generate the cooperation history D
Output to B222. That is, the cooperation history DB 22
2 refers to the “start point IP address” and the “end point IP address” included in the IP header (FIG. 12) of the data transmitted to other nodes and processed by the cooperation control unit 202, and the printer 2 It detects which of the other nodes the device 14 cooperates with to provide the service (cooperation destination information). Further, the cooperation history DB 222 is the cooperation control unit 2
02 detects the setting (setting information) made to the device control unit 206. Further, the cooperation history DB 222 detects whether or not the cooperation control unit 202 has normally finished providing the service (normal / abnormal end information).

[Cooperation History DB 222] Cooperation History DB 22
2 stores the cooperation information sequentially input from the cooperation monitor 220 in the cooperation history storage unit 224. Also, cooperation history D
B222 is, for example, a service type indicating that the printer device 14 is a printer, and a printing speed (pp) of the printer unit 140 set in the device control unit 206.
m), print density, whether or not color printing is possible, and performance information of the printer device 14 such as a protocol (lpd),
It is set from the display device 110, and the cooperation history storage unit 224 stores the limitation of the user, the installation location (which building is installed), and the auxiliary information indicating the installation user. This auxiliary information includes, for example, the performance of the server device (print speed, print density, compatible protocol, color printing compatible,
Corresponding document size (A3, A4, letter, postcard, etc.), corresponding document (PS, ART, etc.), output tray information, sorter presence / absence, staple device presence / absence, punching punch device presence / absence, document device presence / absence (enlargement / Reduction, mirror image conversion, negative / positive conversion, N-up (printing multiple pages on one sheet), page orientation, presence / absence of automatic document feeder, etc., user (user ID, etc.), information limiting the user ( Only some users can use it), installation location (physical installation location), installation user (installer's user ID, etc.), usage frequency (how many times the service was used, and which function was used many times) Or which user has used it many times, the time of use, information indicating the data to be processed (processed data itself, processed data is in color) Etc. there), the time required for service, and the like result the number of services.

Further, the cooperation history DB 222 adds the usage frequency of the printer device 14 and the service providing time to the cooperation information, the service type, the performance information and the auxiliary information stored in the cooperation history storage unit 224 to obtain the service history. To generate. This service history includes the server device and the client device that provided the service, or any one of these network addresses (IP address, MAC address, URL, etc.) as the minimum necessary elements, and in addition to this, the service type (print service , Scanner service, FAX service, etc.) and the result of the service as necessary information. Further, the cooperation history DB 222,
In response to a request from the cooperation history notification unit 226, the generated service history is output to the cooperation history notification unit 226.

[Cooperation History Notification Unit 226] FIG.
3 is a diagram showing a hierarchical structure of a communication protocol used between the PC 16 and the printer device 14 shown in FIG. The cooperation history notification unit 226 responds to the history request sent from the PC 16 via the network 10 to the cooperation history DB 222.
The service history input from is output to the PC 16. For communication between the PC 16 and the printer device 14, the FTP protocol or HT shown in FIG. 13 is used.
The TP / HTTPS protocol or the like is used.

[Software on Client Side] FIG. 14
FIG. 7 is a diagram showing a configuration of a server selection program 3 in the PC 16 shown in FIG. 6, which selects a server device based on a service history received from the server device and requests a service. As shown in FIG. 14, the server selection program 3
Is composed of a communication control unit 200, a cooperation control unit 202, a device driver 32, and a cooperation management unit 30. The server selection program 3 is the cooperation management program 2 (see FIG.
0), PC16,16 'by the recording medium 132
And is loaded into the memory 104 (FIG. 16) and executed.

The cooperation management unit 30 is composed of a cooperation monitor 220, a cooperation history DB 222, a cooperation history storage unit 224, a cooperation history notification unit 226, a service history reception unit 300, and a user interface control unit 302. Note that, of the components of the server selection program 3, those similar to those of the cooperation management program 2 shown in FIG. 10 are denoted by the same reference numerals.

[Device Driver 32] The device driver 32 communicates with the scanner device 12 and the printer device 14 under the control of the cooperation control unit 202,
Run the service.

[Service History Receiving Unit 300] The service history receiving unit 300 requests the service history from the scanner device 12 and the printer device 14, respectively, and the scanner device 12 and the printer device 14 respond to the request.
The service history returned from is received, and the cooperation history DB 22
Output to 2.

[User Interface Control Unit 302]
15 to 18 are first to fourth diagrams illustrating user interface images (UI images) displayed on the display device 110 (FIG. 9) by the user interface control unit 302 illustrated in FIG. 14. User interface controller 3
02 displays the content of the service history to the user from the service history managed by the cooperation history DB 222, generates a UI image used for the user's operation, and displays the display device 11
0 (FIG. 9).

That is, the user interface controller 3
02 receives a service history from the cooperation history DB 222 and indicates a server device capable of cooperation in the form of a first U
The I image (FIG. 15) is generated and displayed. Also, the user interface control unit 302 generates a second UI image (FIG. 16) for performing a keyword search of the server device and displays it on the display device 110. In addition, the user interface control unit 302 is the U shown in FIG. 15 or 16.
In response to the user's selection operation for the I image, a third UI image displaying auxiliary information of the selected server device (see FIG. 1).
7) is generated and displayed on the display device 110. In addition, the user interface control unit 302 displays the service history as
For example, sort using a general sort algorithm,
Fourth UI image showing sorted server devices (FIG. 18)
Is generated and displayed on the display device 110.

Further, the user interface controller 30
2 is a server device (scanner device 1) that accepts a user operation on the displayed UI image and requests a service.
2 and the printer device 14 or any one of them), and the selected server device is set in the cooperation control unit 202.

[Operation of Network System 1] Below,
The operations of the scanner device 12, the printer device 14 and the PC 16 in the network system 1 will be described. In the printer device 14 and the scanner device 12 (server selection program 3; FIG. 10), the cooperation control unit 202 sets P
When a service request is received from C16 or the like and a service is performed in cooperation with another node, the cooperation monitor 220 monitors the cooperation control unit 202 and stores cooperation information in the cooperation history DB 222.
Output to.

Cooperation history DB 22 of cooperation management program 2
The cooperation history storage unit 2 stores cooperation information input from the cooperation monitor 220, service type and performance information input from the device control unit 206, and auxiliary information input from the input device 112 (FIGS. 7 and 8). The service history is stored in 224 and a service history is generated from the stored information.

FIG. 19 shows a communication sequence (S10) for the PC 16 shown in FIG. 6 to receive notification of service history from the scanner device 12 and the printer device 14, respectively.
FIG. As shown in FIG. 19, the service history receiving unit 3 of the PC 16 (server selection program 3; FIG. 14)
00 requests the service history from the printer device 14 (S100). The cooperation history notification unit 226 (FIG. 10) of the printer device 14 (cooperation management program 2; FIG. 10)
Upon receiving this request, the service history is read from the cooperation history DB 222 and transmitted to the PC 16 (S1).
02).

Similarly, the service history receiving unit 300 of the PC 16 (server selection program 3; FIG. 14) requests the service history from the scanner device 12 (S1).
10). Upon receiving this request, the cooperation history notification unit 226 of the scanner device 12 (cooperation management program 2; FIG. 10) reads the service history from the cooperation history DB 222,
The data is transmitted to the PC 16 (S112).

The PC 16 which has received the service history from the scanner device 12 and the printer device 14 by the above communication
The service history receiving unit 300 of (server selection program 3; FIG. 14) stores the received service history in the cooperation history DB2.
It outputs to 22. The cooperation history DB 222 of the PC 16 (server selection program 3) stores and manages the input service history in the cooperation history storage unit 224.

When the user of the PC 16 tries to use the service of the server device, the user interface control unit 302 (FIG. 14) of the PC 16 displays the UI image illustrated in FIGS. 15 to 18 on the display device 110 (FIG. 9). ) Is displayed. When the user performs a selection operation on the UI image displayed by the user interface control unit 302, the user interface control unit 302 responds to the operation by using the scanner device 12 and the printer device 1 as server devices.
4 is selected and set in the cooperation control unit 202.

First, the print processing performed by the PC 16, the scanner device 12 and the printer device 14 in cooperation with each other in the manner shown in FIG. 2 will be described. FIG. 20 shows P shown in FIG.
FIG. 9 is a diagram showing a communication sequence (S12) for C16 to receive a service from the scanner device 12 and the printer device 14 in the manner as shown in FIG. As shown in FIG. 20, the PC 16 (server selection program 3; FIG.
In 4), the cooperation control unit 202 requests the scanner device 12 to scan an image according to the setting from the user interface control unit 302 (S120).
The cooperation control unit 202 of the scanner device 12 (cooperation management program 2; FIG. 10) returns a scan response indicating the start of image scanning to the PC 16 (S122), and the scanner unit 120 (FIG. 7) via the device control unit 206. ) Is controlled to scan the image (S124).

When the image scanning is completed, the cooperation control unit 202 of the scanner device 12 (cooperation management program 2; FIG. 10) transfers the image data (scan data) obtained as a result of the scan from the device control unit 206 to the PC 1
6 (S126). Scanner device 12
When the transmission of the scan data is completed, the cooperation control unit 202 of the (cooperation management program 2) notifies the PC 16 of the end of the scan (S128).

PC 16 (server selection program 3; FIG. 1)
The cooperation control unit 202 of 4) requests printing to the printer device 14 (S130). In response to this request, the cooperation control unit 202 of the printer device 14 (cooperation management program 2; FIG. 10) returns a print response indicating that printing is possible.
The cooperation control unit 202 of 16 (server selection program 3; FIG. 14) transmits the received scan data as print data to the printer device 14 (S134).

When the print data is received, the printer device 1
4 (cooperation management program 2; FIG. 10)
2 is a printer unit 140 via the device control unit 206.
(FIG. 8) is controlled to print the received print data (S136). When printing is completed, the printer device 14
The cooperation control unit 202 of (cooperation management program 2) is a PC
The end of printing is notified to 16 (S138).

Scanner device 12 and printer device 14
In the (cooperation management program 2; FIG. 10), the cooperation monitor 220 monitors the operation of the above cooperation control unit 202, and the cooperation information with the PC 16 obtained as a result of the monitoring is stored in the cooperation history DB 222. The cooperation history DB 222 outputs the inputted cooperation information to the cooperation history storage unit 2
Stored in 24 and managed.

Next, the print processing performed by the PC 16, the scanner device 12, and the printer device 14 in cooperation with each other in the manner shown in FIG. 4 will be described. FIG. 21 shows P shown in FIG.
FIG. 9 is a diagram showing a communication sequence (S14) for C16 to receive a service from the scanner device 12 and the printer device 14 in the manner as shown in FIG. As shown in FIG. 21, the PC 16 (server selection program 3; FIG.
In 4), according to the setting from the user interface control unit 302, the cooperation control unit 202 specifies the scanner device 12 to the printer device 14 and requests the printer device 14 to print the scan data generated by the scanner device 12. (S140).

The cooperation controller 202 of the printer device 14 (cooperation management program 2; FIG. 10) returns a print response indicating the start of printing to the PC 16 (S142), and requests the scanner device 12 to perform scanning. (S15
0). Upon receiving the scan request, the cooperation control unit 202 of the scanner device 12 (cooperation management program 2; FIG. 10) returns a scan response indicating the start of scanning to the PC 16 (S1).
52), the scanner unit 12 via the device control unit 206.
0 (FIG. 7) is controlled to execute the scan (S15
4). When the scan is completed, the cooperation control unit 202 of the scanner device 12 (cooperation management program 2; FIG. 10) transmits the scan data to the printer unit 140 (S1).
56) When the transmission is completed, the printer device 14 is notified of the end of the scan (S158).

Upon receiving the scan end notification, the cooperation control unit 202 of the printer device 14 (cooperation management program 2; FIG. 10) controls the printer unit 140 (FIG. 8) via the device control unit 206 to print. Execute (S16
0). When printing is completed, the cooperation control unit 202 of the printer device 14 (cooperation management program 2) notifies the PC 16 of the end of printing (S162).

Scanner device 12 and printer device 14
In the (cooperation management program 2; FIG. 10), the cooperation monitor 220 monitors the operation of the above cooperation control unit 202, and the cooperation information with the PC 16 obtained as a result of the monitoring is stored in the cooperation history DB 222. The cooperation history DB 222 outputs the inputted cooperation information to the cooperation history storage unit 2
Stored in 24 and managed.

[Modification] The cooperation monitor 220 has information about the person who requested the service (user ID, etc.) and information indicating the data to be processed (the image data itself or the image data is in color). Other information such as the time required to provide the service (time information) and the number of service products (the number of prints), and the cooperation history DB2.
22 may store and manage such information.

Although the IP address is used as the information indicating the cooperation destination of the scanner device 12 / printer device 14 managed by the cooperation history DB 222, a MAC address or a URL may be used instead of the IP address.

[Second Embodiment] As a second embodiment of the present invention, a method in which the PC'16 'shown in FIG. 6 collects service histories and notifies the PC16 will be described below. In FIG. 22, the PC 16 'shown in FIG.
And the service history from the printer device 14,
It is a figure which shows the communication sequence (S20) when notifying to C16. As shown in FIG. 22, when the PC '16' requests the service history from the printer device 14 (S
200), and the printer device 14 responds to this request with P
The service history is transmitted to C'16 '(S20).
2). Similarly, when the PC'16 'requests the service history from the scanner device 12 (S204), the scanner device 12 transmits the service history to the PC'16' in response to this request (S206). ). The above communication sequence is the same as that of the PC 16 shown in FIG.

PC 16 (server selection program 3; FIG. 1)
When the service history receiving unit 300 of 4) makes a service history request to the PC '16' (S210), the PC '
16 '(server selection program 3) cooperation history notification unit 2
26 receives this request, reads the service history from the cooperation history DB 222, and notifies the PC 16 (S21).
2).

FIG. 23 is a diagram showing a communication sequence (S22) when the PC 16 shown in FIG. 6 collects the service history between the scanner device 12 and the printer device 14 and notifies the PC'16 '. . As shown in FIG.
The PC 16 executes a print processing sequence with the scanner device 12 and the printer device 14, for example (S2).
20). The communication sequence of S220 is, for example, as shown in FIG.
Same as 0.

During the communication sequence of S220, the PC 16
Cooperation monitor 22 of (server selection program 3; FIG. 14)
0 monitors the processing of the cooperation control unit 202, generates cooperation information, and outputs it to the cooperation history DB 222. PC1
6 (server selection program 3) cooperation history DB 222
Generates a service history from the cooperation information input from the cooperation monitor 220, stores it in the cooperation history storage unit 224, and manages it.

PC 16 (server selection program 3; FIG. 1)
When the service history receiving unit 300 of 4) makes a service history request to the PC '16' (S222), the PC '16'
16 '(server selection program 3) cooperation history notification unit 2
26 receives this request, reads the service history from the cooperation history DB 222, and notifies the PC 16 (S22).
4). The communication sequence between these PCs 16 and 16 'is the same as the communication sequence of S210 and S212 shown in FIG. As described above, the PC '16', which has obtained the service history from the PC 16, executes the communication sequence shown in FIG. 20, for example, with the scanner device 12 and the printer device 14 to perform printing.

[Third Embodiment] As a third embodiment of the present invention, a method in which the history server 18 shown in FIG. 6 generates a service history and notifies the PC 16, 16 'will be described below. FIG. 24 is a diagram showing the configuration of the service history notification program 4 executed by the history server 18 shown in FIG.

As shown in FIG. 24, the service history notification program 4 includes a service history receiving section 300 and a cooperation history D.
B222, cooperation history storage unit 224, cooperation history notification unit 22
6 and the network monitor 40. The service history notification program 4 is the cooperation management program 2
As with the server selection program 3 (FIG. 10) and the recording medium 132, the PC 16 (FIG. 9) is used.
Is supplied to the history server 18 having the same configuration as that of the memory 10
4 is loaded and executed. Note that, in FIG. 24, of the components of the service history notification program 4, the same components as those of the cooperation management program 2 (FIG. 10) and the server selection program 3 (FIG. 14) are denoted by the same reference numerals. .

[Network Monitor 40] The network monitor 40 monitors packets transmitted through the network 10 via the communication control unit 200, and
PC16, 1 out of IP packets transmitted 0
6 ', the scanner device 12 and the printer device 14 are associated with each other to be extracted. Further, the service notification program 40 generates cooperation information and auxiliary information from the extracted packet, further generates a service history from these, and outputs the service history to the cooperation history DB 222. That is, the network monitor 40 has a function of monitoring the network 10, a function of the cooperation monitor 220, and a function of generating a service history.

First, the history server 18 shown in FIG. 6 requests a service history from the scanner device 12 and the printer device 14, and in response to this request, the scanner device 12,
A case of notifying the PC 16 of the service history returned from 14 will be described. FIG. 25 shows the history server 18 shown in FIG.
FIG. 10 is a diagram showing a communication sequence (S30) in which the request for the service history is made to the scanner device 12 and the printer device 14 and the service history obtained in response to the request is notified to the PC 16.

The service history receiving section 300 of the history server 18 (service history notification program 4; FIG. 24) requests the service history from the printer device 14 (S30).
0), the service history returned from the printer device 14 in response to the request is received (S302). Similarly, the service history receiving unit 300 of the history server 18 (service history notification program 4) requests the service history from the scanner device 12 (S304), and the scanner device 1 responds to the request.
The service history returned from 2 is received (S306).

The service history receiving unit 300 outputs the received service history to the cooperation history DB 222, and the cooperation history DB 222 stores the service history receiving unit 300.
The service history input from is stored in the cooperation history storage unit 224 and managed.

When the service history receiving section 300 of the PC 16 (server selection program 3; FIG. 4) requests the service history from the history server 18, the history history of the history server 18 (service history notification program 4; FIG. 24) is notified. The unit 226 reads the service history from the cooperation history DB 222 and returns it to the PC 16 (S310) The PC 16 that has received the service history from the history server 18 is:
Using the received service history, for example, as shown in FIG. 20, a communication sequence of print processing is performed between the scanner device 12 and the printer device 14.

Next, a case where the history server 18 shown in FIG. 6 monitors the IP packets transmitted through the network 10 to create a service history and notifies the PCs 16 and 16 'will be described. FIG. 26 is a diagram showing a communication sequence (S32) in which the history server 18 shown in FIG. 6 monitors the IP packets transmitted through the network 10, creates a service history, and notifies the PCs 16 and 16 ′.

The PC 16 (FIG. 6) requests the printer 14 for printing (S320), and the printer 14 returns a print response in response to this request (S322).
Sends print data to the printer device 14 (S32
4) The printer device 14 returns the print completion to the PC 16 (S326).

The PC 16 requests the scanner device 12 to scan the image (S328), the scanner device 12 returns a scan response in response to the request (S330), and the scanner device 12 sends the scan data to the PC 16. (S332), the scanner device 12 sets the scan end to P
It returns to C16 (S334). The network monitor 40 of the history server 18 (service history notification program 4; FIG. 24) monitors IP packets of these communications transmitted through the network 10, creates a service history, and outputs the service history to the cooperation history DB 222. . Cooperation history DB22
2 stores the service history input from the network monitor 40 in the cooperation history storage unit 224 and manages it.

When the PC '16' requests the service history from the history server 18 (S340), the history server 18 (service history notification program 4;
The cooperation history notification unit 226 in FIG. 24) is the cooperation history DB 22.
The service history is read from No. 2 and returned to the PC '16' (S342). The PC'16 'uses the service history received from the history server 18 to perform communication as shown in FIG. 20, for example, and perform print processing (S350).

As described above, the history server 18 is connected to the PC 16,
The case of adding to the network system 1 separately from 16 'has been described as the third embodiment.
6'with the network monitor 40 added to the history server 1
By providing the function of 8, it is possible to obtain the same effect as when the history server 18 is added to the network system 1.

[0102]

As described above, according to the client server system and the method thereof according to the present invention, the user can select an appropriate server device based on the past history. Further, according to the client server system and the method thereof according to the present invention, when it is necessary to link a plurality of server devices to a job execution based on the past history, it is possible to execute the job in a short time. The optimum combination of server devices can be shown to the user.

[Brief description of drawings]

FIG. 1 is a diagram illustrating an information processing device.

FIG. 2 is a first diagram exemplifying a process executed by linking a plurality of information processing devices.

FIG. 3 is a second diagram illustrating an example of processing executed by linking a plurality of information processing apparatuses.

FIG. 4 is a third diagram showing an example of processing executed by linking a plurality of information processing apparatuses.

FIG. 5 is a diagram exemplifying a history held in a terminal instructing a process and a device performing a conversion process.

FIG. 6 is a diagram illustrating a configuration of a network system.

7 is a diagram showing a hardware configuration of the scanner device shown in FIG.

8 is a diagram showing a hardware configuration of the printer device shown in FIG.

9 is a diagram showing a hardware configuration of a PC 16 shown in FIG.

FIG. 10 is a view showing a cooperation management program for providing a service in cooperation with another node in the scanner device (FIG. 7) and the printer device (FIG. 8) shown in FIG. 6 and storing and managing the history of the provided service. It is a figure which shows a structure.

FIG. 11 is a diagram showing an Ethernet data frame and an IP packet.

12 is a diagram showing an IP header of an IP packet transmitted using the payload portion of the Ethernet data frame shown in FIG.

13 is a diagram showing a hierarchical structure of a communication protocol used between a PC and a printer device (FIG. 6).

14 is a diagram showing a configuration of a server selection program that selects a server device based on a service history received from the server device and requests a service in the PC shown in FIG.

15 is a first diagram illustrating a user interface image (UI image) displayed on the display device (FIG. 9) by the user interface control unit shown in FIG.

16 is a second diagram illustrating a user interface image (UI image) displayed on the display device (FIG. 9) by the user interface control unit shown in FIG.

17 is a third diagram illustrating a user interface image (UI image) displayed on the display device (FIG. 9) by the user interface control unit shown in FIG.

18 is a fourth diagram illustrating a user interface image (UI image) displayed on the display device (FIG. 9) by the user interface control unit shown in FIG.

FIG. 19 is a diagram showing a communication sequence (S10) for the PC shown in FIG. 6 to receive notification of service history from each of the scanner device and the printer device.

20 is a diagram showing a communication sequence (S12) for the PC shown in FIG. 6 to receive a service from the scanner device and the printer device in the manner shown in FIG.

21 is a diagram showing a communication sequence (S14) for the PC shown in FIG. 6 to receive a service from the scanner device and the printer device in the manner shown in FIG.

FIG. 22 is a diagram showing a communication sequence (S20) when the PC ′ shown in FIG. 6 collects service history from the scanner device and the printer device and notifies the PC.

23 is a diagram showing a communication sequence (S22) in the case where the PC shown in FIG. 6 collects service history between the scanner device and the printer device and notifies the PC 'of the service history.

24 is a diagram showing the structure of a service history notification program executed in the history server shown in FIG.

25 is a diagram showing a communication sequence (S30) in which the history server shown in FIG. 6 requests a service history from the scanner device and the printer device and notifies the PC of the service history obtained in response to the request. .

FIG. 26 is a history server shown in FIG. 6 monitoring packets transmitted through the network to create a service history;
It is a figure which shows the communication sequence (S32) notified to PC and PC '.

[Explanation of symbols]

1 ... Network system 10 ... Network 12 ... Scanner device 100 ... Control device 102 ... CPU 104 ... Memory 110 ... Display device 112 ... Input device 114 ... communication device 120 ... Scanner section 130 ... Recording device 132 ... Recording medium 2 ... Cooperation management program 200 ... Communication control unit 202 ... Cooperation control unit 206 ... Device control unit 22 ... Cooperation management unit 220 ... Cooperation monitor 222 ... Cooperation history DB 224 ... Cooperation history storage unit 226 ... Cooperation history notification section 14 ... Printer device 140 ... Printer unit 16, 16 '... PC 160 ... PC body 3 ... Server selection program 30 ... Cooperation management department 300 ... Service history receiver 32: Device driver 18 ... History server 4 ... Service history notification program 40 ... Network monitor

   ─────────────────────────────────────────────────── ─── Continued front page    (72) Inventor Isao Uesawa             430 Sakai, Nakai-cho, Ashigarakami-gun, Kanagawa Prefecture             Kunakai Fuji Xerox Co., Ltd. (72) Inventor Katsuya Mitsutake             430 Sakai, Nakai-cho, Ashigarakami-gun, Kanagawa Prefecture             Kunakai Fuji Xerox Co., Ltd. F term (reference) 5B045 BB47 GG02                 5B089 GA13 GA21 JA32 JB14 KA13                       KB04 KB06 LB12

Claims (28)

[Claims] 1. A client-server system including a plurality of server devices each providing a predetermined service, and one or more client devices requesting a service to the server device, respectively. Each client device, based on the service history returned from the plurality of server devices in response to the request, history request means for requesting the notification of the service history indicating the history of the service to each of the plurality of server devices, A server device selecting unit that selects one or more of the plurality of server devices, and a service requesting unit that requests a service to the one or more selected server devices; Each of the server devices includes a service history generating unit that generates the service history, and a request from the client device. Accordingly, a client server system having a history notifying unit for notifying the generated service history. 2. The service history of each of the server devices includes auxiliary information indicating at least one of the server device and the client device involved in the service, and the server device selection means of each of the client devices can request the request. Based on the service and auxiliary information included in the service history from the server device,
The client server system according to claim 1, wherein one or more of the plurality of server devices are selected. 3. A client-server system including a plurality of server devices each providing a predetermined service, and a first client device and a second client device requesting a service to the server device, respectively. The first client device requests a history of a service history indicating a history of services of each of the plurality of server devices to the second client device; A server device selecting unit that selects one or more of the plurality of server devices based on the service history returned from the client device, and a service that requests a service from the one or more selected server devices. Requesting means, the second client device, the service history for generating the service history Client-server system comprising a forming unit, in response to said first request from the client device, and a history notifying means for notifying the service history of the product. 4. The service history of the second client device includes auxiliary information indicating at least one of a server device and a client device involved in the service, and a server device selecting means of the first client device. ,
The client server system according to claim 3, wherein one or more of the plurality of server devices are selected based on the service to be requested and auxiliary information included in the service history from the server device. 5. The second client device has history requesting means for requesting notification of service history to each of the plurality of server devices, and the service history generating means of the second client device is The client server system according to claim 3, wherein the service history is generated from a history of services returned from each of a plurality of server devices in response to the request. 6. The service history generating means of the second client device stores the service history based on a server device and / or a client device involved in a service provided by each of the plurality of server devices, or one of them. The client-server system according to claim 3 or 4, which is generated. 7. A plurality of first server devices each providing a predetermined service, one or more client devices each requesting a service to the first server device, and the client device having the plurality of first server devices. A client server system including a second server device that provides a history of services of each of the first server devices, wherein the client device is configured such that each of the first server devices is different from the second server device. One of the plurality of first server devices based on the service history returned by the second server device in response to the request Server device selecting means for selecting the above, and for the selected one or more first server devices,
A second server device, the service history generating device generating the service history, and notifying the generated service history in response to a request from the client device. A client-server system having history notifying means. 8. The service history of the second server device is:
The server device selecting means of the client device includes the server device and the client device that have provided the service, or auxiliary information indicating at least one of them, and is included in the service to be requested and the service history from the server device. The client-server system according to claim 7, wherein one or more of the plurality of server devices are selected based on auxiliary information. 9. The second server device has history requesting means for requesting notification of service history to each of the plurality of first server devices, and a service history of the second server device. 9. The client server system according to claim 7, wherein the generation unit generates the service history from the history of services returned from each of the plurality of server devices in response to the request. 10. The first server device and the client device transmit data related to a service via a network, the second server device is connected to the network, and the second server device is connected. Has monitor means for monitoring data relating to a service transmitted between each of the plurality of first server devices and each of the client devices, and the service history generating means of the second server device is The client / server system according to claim 7, wherein the service history is generated based on monitored data. 11. A server device in a client-server system, comprising: a plurality of server devices each providing a predetermined service; and one or more client devices requesting a service to the server device, respectively. Each of the one or more client devices requests a notification of a service history indicating a service history from each of the plurality of server devices, and based on the service history returned from the plurality of server devices in response to the request. A service history generating unit that selects one or more of the plurality of server devices, requests a service from the one or more selected server devices, and generates the service history; and the client device. Server device having history notifying means for notifying the generated service history in response to a request from the server 12. The client device in a client server system, comprising: a plurality of server devices each providing a predetermined service; and one or more client devices requesting a service to the server device, respectively. Each of the plurality of server devices generates the service history, notifies the generated service history in response to a request from the client device, and a service history indicating a service history to each of the plurality of server devices. History requesting means for requesting notification of the above, and server device selecting means for selecting one or more of the plurality of server devices based on the service history returned from the plurality of server devices in response to the request, It has a service request means for requesting a service to one or more selected server devices. That client device. 13. A second client-server system in a client-server system, comprising: a plurality of server devices each providing a predetermined service; and a first client device and a second client device requesting a service from each of the server devices. The client device of
Client device requests the second client device to notify service history indicating the history of services of each of the plurality of server devices, and the service history returned from the second client device in response to the request. A service history generation unit that selects one or more of the plurality of server devices, requests a service from the selected one or more server devices, and generates the service history based on A client device having history notification means for notifying the generated service history in response to a request from the first client device. 14. The service history generating means generates the service history based on a server device and / or a client device that has provided a service provided by each of the plurality of server devices, or one of them. The described client device. 15. A plurality of first server devices each providing a predetermined service, one or more client devices requesting a service to the first server device, respectively, and a plurality of the client devices having the plurality of client devices. A second server device in a client-server system including a second server device that provides a history of services of each of the first server devices, wherein the client device comprises:
Requesting a notification of a service history indicating a history of each service of the first server device to the second server device, and based on a service history returned from the second server device in response to the request, Service history generating means for selecting one or more of the plurality of first server devices, requesting a service from the selected one or more first server devices, and generating the service history. And a history notification unit for notifying the generated service history in response to a request from the client device. 16. The first server device and the client device transmit data related to a service via a network, the second server device is connected to the network, and the plurality of first server devices are connected to the network. A monitoring unit configured to monitor data relating to a service transmitted between each server device and each client device, wherein the service history generation unit generates the service history based on the monitored data. Item 16. The server device according to Item 15. 17. A service notification method in a server device in a client server system, comprising: a plurality of server devices each providing a predetermined service; and one or more client devices each requesting the server device for a service. Then, each of the one or more client devices requests a notification of a service history indicating a service history from each of the plurality of server devices, and a service returned from the plurality of server devices in response to the request. Based on the history, one or more of the plurality of server devices are selected, a service is requested to the selected one or more server devices, the service history is generated, and from the client device, The service notification method for notifying the generated service history in response to the request. 18. A method of selecting a server device in a client device in a client server system, comprising: a plurality of server devices each providing a predetermined service; and one or more client devices each requesting a service to the server device. That is, each of the plurality of server devices generates the service history, notifies the generated service history in response to a request from the client device, and notifies each of the plurality of server devices of the service. Requesting notification of service history indicating history, selecting one or more of the plurality of server devices based on the service history returned from the plurality of server devices in response to the request, and selecting the selected one. A method for selecting a server device that requests a service to one or more server devices. 19. A second client-server system in a client-server system, comprising: a plurality of server devices each providing a predetermined service; and a first client device and a second client device each requesting a service to the server device. In the service notification method in the client device, the first client device requests the second client device to notify a service history indicating a history of services of each of the plurality of server devices. Select one or more of the plurality of server devices based on the service history returned from the second client device in response to the request, and request a service from the one or more selected server devices. Then, the service history is generated, and in response to a request from the first client device, Service notification method for notifying the generation service history was. 20. The service notification method according to claim 19, wherein the generation of the service history is performed based on a result of the service provided from each of the plurality of server devices. 21. A plurality of first server devices that respectively provide a predetermined service, one or more client devices that respectively request a service from the first server device, and a plurality of the client devices that include the plurality of client devices. A service notification method in the second server device in a client-server system including a second server device that provides a history of services of each of the first server devices,
The client device requests the second server device to notify the service history indicating the history of each service of the first server device, and the service returned from the second server device in response to the request. Based on history
Selecting one or more of the plurality of first server devices,
For the selected one or more first server devices,
A service notification method comprising requesting a service, generating the service history, and notifying the generated service history in response to a request from the client device. 22. The first server device and the client device transmit data related to a service via a network, the second server device is connected to the network, and the plurality of first server devices are connected to the network. 22. The service notification method according to claim 21, wherein data relating to a service transmitted between each server device and each client device is monitored, and the generation of the service history is performed based on the monitored data. 23. A service notification program in a server device in a client server system, comprising: a plurality of server devices each providing a predetermined service; and one or more client devices each requesting a service to the server device. Then, each of the one or more client devices requests a notification of a service history indicating a service history from each of the plurality of server devices, and a service returned from the plurality of server devices in response to the request. Selecting one or more of the plurality of server devices based on a history, requesting a service from the selected one or more server devices, and generating the service history; In response to a request from the device, the step of notifying the generated service history Service notification program to be executed by the computer. 24. A server device selection program in a client server system in a client server system, comprising: a plurality of server devices each providing a predetermined service; and one or more client devices each requesting a service to the server device. That is, each of the plurality of server devices generates the service history, notifies the generated service history in response to a request from the client device, and notifies each of the plurality of server devices of the service. Requesting notification of service history indicating history, selecting one or more of the plurality of server apparatuses based on service history returned from the plurality of server apparatuses in response to the request, A service requesting service is sent to one or more selected server devices. Server device selection program for executing the up to the computer. 25. A second client-server system comprising a plurality of server devices each providing a predetermined service, and a first client device and a second client device each requesting the server device for the service. A service notification program in the client device, wherein the first client device requests the second client device to notify a service history indicating a history of services of each of the plurality of server devices; Select one or more of the plurality of server devices based on the service history returned from the second client device in response to the request, and request a service from the one or more selected server devices. And generating the service history, from the first client device Upon request, the service notification program for executing the steps on a computer that notifies the service history of the product. 26. In the step of generating the service history, the generation of the service history is performed based on a server device and / or a client device that has provided a service provided by each of the plurality of server devices, or one of them. The service notification program according to claim 25. 27. A plurality of first server devices that respectively provide a predetermined service, one or more client devices that respectively request a service from the first server device, and a plurality of the client devices. A service notification program in the second server device in a client server system including a second server device providing a history of services of each of the first server devices, wherein the client device is the second server device. Requesting notification of service history indicating the history of each service of the first server device, and based on the service history returned from the second server device in response to the request, the plurality of first Selecting one or more of the server devices and providing services to the selected one or more first server devices. Determined City, and generating the service history, said in response to a request from the client device, the service notification program and a step of notifying the service history of the product. 28. The first server device and the client device transmit data related to a service via a network, the second server device is connected to the network, and the plurality of first server devices are connected to the network. A step of monitoring data relating to a service transmitted between each of the server devices and each of the client devices, wherein the step of generating the service history includes generating the service history based on the monitored data. The service notification method according to claim 27, which is performed by.