JP2004272888A - Service providing device, user terminal equipment, service providing method, service using method, service provision program, service using program, and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To promptly provide necessary information when a user selects service. <P>SOLUTION: In this service providing device having a service providing means for providing service to be used by the user, the service providing means has a service information providing means 50 for providing information regarding the service to be used when the user selects the service in response to a request from a user terminal device. <P>COPYRIGHT: (C)2004,JPO&NCIPI

Description

  The present invention relates to a service providing device, a user terminal device, a service providing method, a service using method, a service providing program, a service using program, and a recording medium.

2. Description of the Related Art Conventionally, a service discovery method for discovering a service provided by each device connected to a network has been known (for example, see Patent Document 1).
JP 2000-209231 A

  However, the above-described conventional method has a problem that even when a service is discovered, information necessary for a user to select a service is not included.

  FIG. 1 is a diagram (part 1) for explaining a problem of the related art. The client in FIG. 1 and each server are connected via a network.

  In step S1, the client sends a search request for service A to server A, server B, and server C by multicast to discover service A.

  Proceeding to step S2 following step S1, server A having service A and server B having service A transmit a search response to the effect that service A exists to the client.

  The client can discover the service A by obtaining the search response. However, there is a problem that the search response does not include information required when the client user selects the service A.

  For example, even if the service A is a print service and the user wants to print in color, the search response does not include the detailed information of the print service. Could not determine if the print service was compatible with color.

  In fact, in the conventional example shown in FIG. 1, the client proceeds to step S3 following step S2, and the client transmits a request for acquiring detailed information of the service A provided by each to the server A and the server B. .

  Proceeding to step S4 following step S3, the server A and the server B transmit to the client an acquisition response to the acquisition request including detailed information of the service A provided by each.

  The client acquires the detailed information of the service A for the first time by acquiring the acquisition response, and the user selects and uses the service A provided by the server A or the service A provided by the server B. be able to.

  As described above, in FIG. 1, the method of transmitting the search request for the service A to the server A, the server B, and the server C by multicast when the client discovers the service A has been described. There is also a method in which a client transmits a request for acquiring a list of services provided by a server for each server.

  FIG. 2 is a diagram (part 2) for describing a problem of the related art. The client in FIG. 2 and each server are connected via a network.

  In step S5, the client transmits a service list acquisition request to server A, server B, and server C to discover service A.

  Proceeding to step S6 following step S5, the server A, the server B, and the server C generate a list of services provided by each, and transmit an acquisition response including the service list to the client.

  The client can discover the service A by acquiring an acquisition response including the service list from each server.

  However, similarly to the above-described method, there is a problem that the acquisition response including the service list does not include information required when the user of the client selects the service A.

  In fact, in the conventional example shown in FIG. 2, the client proceeds to step S7 following step S6, and the client transmits a request for acquiring detailed information of the service A provided by each client to the server A and the server B. .

  Proceeding to step S8 following step S7, the server A and the server B transmit to the client an acquisition response to the acquisition request, including the detailed information of the service A provided by each.

  As described above, the client acquires the detailed information of the service A for the first time by acquiring the acquisition response, and the user determines whether the service A provided by the server A or the service A provided by the server B is provided. You can select and use it.

  The present invention has been made in view of the above points, and has as its object to promptly provide information necessary for a user to select a service.

  Another object of the present invention is to quickly obtain information required when a user selects a service.

  Therefore, in order to solve the above problem, the present invention is a service providing device having a service providing means for providing a service used by a user, wherein the service providing means responds to a request from a user terminal device, A service information providing means for providing information on the service used when a user selects the service is provided.

  According to the present invention, there is provided a service providing apparatus having service providing means for providing a service used by a user, wherein the service providing means selects the service in response to a request from a user terminal device. The provision of the service information providing means for providing information on the service used in such a case makes it possible to promptly provide the user terminal with information required when the user selects a service.

  Further, the present invention is a user terminal device used by a user who uses a service provided by a service providing unit, wherein the request creating unit creates a request including a search condition related to the service, Response receiving means for receiving a response including information on the service used when the user selects the service.

  According to the present invention, a user terminal device used by a user who uses a service provided by a service providing unit, a request creating unit that creates a request including a search condition related to the service, Response receiving means for receiving a response including information on the service used when the user selects the service, thereby quickly obtaining information required when the user selects the service. be able to.

  As means for solving the above problems, a service providing method, a service using method, a service providing program, a service using program, and a recording medium may be used.

  According to the present invention, information required when a user selects a service can be promptly provided.

  Further, according to the present invention, it is possible to quickly acquire information required when a user selects a service.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
(System configuration diagram of the first embodiment)
FIG. 3 is a system configuration diagram for explaining an example of a system configuration for implementing the present invention. FIG. 3 shows a configuration necessary for the description, and a configuration unnecessary for the description is omitted. The same applies to the following drawings.

  As shown in FIG. 3, in the present system, a service information providing server 10, a client 20, and an image forming apparatus 1200 are connected via a network 5.

  The client 20 generates a request including a search condition for searching for a Web service, and transmits the generated request to the service information providing server 10.

  On the other hand, the service information providing server 10 has a Web service providing service 41 for providing a Web service used by the user, and the Web service providing service 41 has a service information providing unit.

  The service information providing unit provides information on the Web service provided by the Web service providing service 41 based on the request.

  The client 20 receives and analyzes the response, generates a screen including information on the Web service as display content, and displays the screen on a display.

  Further, the client 20 generates a request to acquire a list of information on Web services provided by the service information providing server 10, and transmits the generated request to the service information providing server 10.

  On the other hand, the service information providing unit provides information on the Web service provided by the Web service providing service 41 based on the request.

Note that the image forming apparatus 1200 is an example of an apparatus having hardware functions required for the service provided by the web service providing service 41.
(System configuration diagram of the second embodiment)
FIG. 4 is a system configuration diagram for explaining another example of the system configuration for implementing the present invention.

  In the system configuration shown in FIG. 4, the client 20 and the image forming apparatus 1200 are connected via the network 5.

  The system configuration in FIG. 4 is different from the system configuration in FIG. 3 in that the image forming apparatus 1200 has a Web service providing service 41.

As described above, the Web service providing service 41 shown in FIG. 4 has the service information providing unit, and the service information providing unit analyzes the request from the client 20 and provides the service information providing unit. A response including information on the Web service is generated.
(Description of First Embodiment)
Hereinafter, a functional configuration diagram of the service information providing server 10 will be described with reference to FIG.

  FIG. 5 is a functional configuration diagram of an example of the service information providing server.

  As shown in FIG. 5, the service information providing server 10 includes a Web server 40 and a Web service providing service 41. Here, the Web server 40 is software that provides its own data and functions, and the service information providing server 10 is a computer that provides its own data and functions.

  The Web server 40 controls data communication with the client 20 connected via the network 5 by HTTP (Hypertext Transfer Protocol), and calls a Web service providing service 41 corresponding to the Web service specified by the HTTP request header. The processing result of the Web service providing service 41 is transmitted to the client 20 by an HTTP response or the like. The Web server 40 shown in FIG. 5 may have the same configuration as the Web server 500 included in the MFP 1200 described later.

  On the other hand, as the Web service providing service 41 for providing a Web service, the service providing server 10 includes, for example, a print service providing service 42 for providing a Web service for printing, and a repository service providing service 43 for providing a Web service for a repository. And

  Each of these Web service providing services 41 has a service information providing unit 50 described later.

  The service information providing unit 50 provides information related to the Web service provided by the respective Web service providing services 41 corresponding to the request based on the request obtained from the Web server 40, as described later. The service information providing unit 50 returns the generated response to the Web server 40.

  The service information providing unit 50 is realized in such a manner that a program corresponding to the service information providing unit 50 is mounted on each Web service providing service 41.

  FIG. 6 is a hardware configuration diagram of an example of the service information providing server.

  The hardware configuration of the service information providing server 10 illustrated in FIG. 6 includes a drive device 31, a ROM (Read Only Memory) 33, a RAM (Random Access Memory) 34, and a CPU that are mutually connected by a bus B. (Central Processing Unit) 35, an interface device 36, and an HDD (Hard Disk Drive) 37.

  The interface device 36 is an interface that connects the service information providing server 10 to the network 5.

  Programs corresponding to the print service providing service 42 and the repository service providing service 43 in which the service information providing unit 50 is mounted, and a main program for controlling the entire processing of the service information providing server 10 are, for example, CD-ROMs and the like. It is provided to the service information providing server 10 by the recording medium 32 or downloaded through the network 5. The recording medium 32 is set in the drive device 31, and the program, the main program, and the like are installed from the recording medium 32 into the HDD 37 via the drive device 31.

  The ROM 33 stores data and the like. The RAM 34 reads and stores the program, the main program, and the like from the HDD 37 when the service information providing server 10 is started. The CPU 35 executes processing in accordance with the program and the main program read and stored in the RAM 34.

  FIG. 7 is a diagram for explaining an example of the function of the service information providing unit using a functional block diagram.

  The service information providing unit 50 includes a request analysis unit 51, a response generation unit 52, a service information management unit 53, and a service information determination unit 54.

  The request analysis unit 51 analyzes the contents of the request from the client 20 acquired from the Web server 40, and holds, for example, information included in the request. The details of the request will be described with reference to FIGS. 13 and 15 described later.

  The service information management unit 53 manages information related to Web services stored in the service information storage unit 55. For example, the service information management unit 53 searches the service information storage unit 55 based on a search condition included in a request from the client 20, or acquires information on a Web service that meets the search condition from the service information storage unit 55. Or updates the information on the Web service stored in the service information storage unit 55.

  For example, based on a search result performed by the service information management unit 53, the service information determination unit 54 receives a request for a Web service provided by the Web service providing service 41 in which the service information providing unit 50 is installed. It is determined whether the Web service is present.

  The service information storage unit 55 stores information on a Web service provided by the Web service providing service 41 in which the service information providing unit 50 is mounted. The details of the information stored in the service information storage unit 55 will be described later with reference to FIGS.

  Note that the service information storage unit 55 does not have to have a configuration for each service information providing unit 50 installed in each Web service providing service 41, and one service information storage unit 55 is installed in each Web service providing service 41. The service information providing unit 50 may be configured to share the information.

  The response generation unit 52 generates a response including the information on the Web service acquired by the service information management unit 53 from the service information storage unit 55. The details of the response will be described with reference to FIGS. 14, 16, 17, and 18 described later.

  Hereinafter, another example of the functional configuration of the service information providing unit 50 will be described with reference to FIG. FIG. 8 is a diagram for explaining another example of the function of the service information providing unit using a functional block diagram.

  The functional configuration of the service information providing unit 50 illustrated in FIG. 8 is different from the functional configuration of the service information providing unit 50 illustrated in FIG. 7 in that the request analyzing unit 51 and the response generating unit 52 are different from each other. , And is included in the Web server 40.

  In the case of the configuration shown in FIG. 8, for example, information included in the request is passed to the service information management unit 53 and managed by the service information management unit 53.

  With the configuration shown in FIG. 8, for example, there is a case where a plurality of Web service providing services 41 exist in the service providing server 10 and the service information providing unit 50 is mounted for each Web service providing service 41. However, the request analysis unit 51 and the response generation unit 52 can be shared and used in the plurality of service information providing units 50.

  In the following, for simplicity of description, the service information providing unit 50 will be described as having a functional configuration as shown in FIG. 7 unless otherwise specified. However, this does not limit the implementation of the present invention.

  FIG. 9 is a diagram (part 1) for explaining the service information storage unit.

  As illustrated in FIG. 9, the service information storage unit 55 includes, as items, a Name, a Display Name, an Access port, an Access Uri, a Type, and a Machine Name.

  In the Name, the name of a Web service provided by the Web service providing service 41 in which the service information providing unit 50 is installed is stored.

  The Display Name stores the display name of the Web service in English.

  The Access Port stores the port number of the end point of the Web service (the POST destination of the SOAP request).

  The Access URI stores a request URI (a part after the host description part of the HTTP URL) of the end point of the Web service (the POST destination of the SOAP request).

  Type stores the implementation type of the Web service. For example, even if the service name space is the same, the implementation type distinguishes each service when a plurality of services having different implementations, objectives, performance, security, usage fees, and the like exist on the same host. Used for

  In the Machine Name, the name of the device that provides the Web service is stored in English.

  When one service information storage unit 55 is configured to be shared by the service information providing units 50 mounted on each Web service providing service 41, each Web service providing service 41 provides each item described above. Information related to the Web service is stored.

  In response to a request from the client 20 described below, the service information providing unit 50 displays a name for displaying a Web service provided by the Web service providing service 41 in which the service information providing unit 50 is mounted, and displays a name of the Web service. A response including an implementation type, a name of a device that provides the Web service, and the like is generated.

  An example of a request from the client 20 will be described with reference to FIG. 13 described later. An example of a response to the client 20 will be described with reference to FIG. 14 described later.

  The client 20 obtains a response including the display name of the Web service, the implementation type of the Web service, the name of a device that provides the Web service, and the like. 20. A screen for displaying the name of the Web service required when the user operating the Web server 20 selects the Web service and the name of the device providing the Web service is generated and provided to the user. can do.

  FIG. 10 is a diagram (part 2) for explaining the service information storage unit.

  As illustrated in FIG. 10, the service information storage unit 55 includes Name, Display Name, Display Name ja, Access port, Access Uri, Type, Machine Name, and Machine Name ja as items.

  The service information storage unit 55 illustrated in FIG. 10 is different from the service information storage unit 55 illustrated in FIG. 9 in that items of Display Name ja and Machine Name ja are newly added.

  In Display Name ja, the display name of the Web service provided by the Web service providing service 41 in which the service information providing unit 50 is mounted is stored in Japanese.

  In the Machine Name ja, the name of the device that provides the Web service is stored in Japanese.

  As will be described later with reference to FIG. 15, when the service information providing unit 50 specifies the language of the information related to the Web service included in the response in the request from the client 20 as Japanese, the Web described in Japanese A response including a name for displaying a service and a name of a device that provides a Web service is generated.

  An example of a request for specifying a language will be described with reference to FIG. 15 described later. An example of a response including Japanese will be described with reference to FIG. 16 described later.

  The client 20 obtains a response including the display name of the Web service described in Japanese and the name of the device that provides the Web service, and so on. Generates a screen that is displayed when the user operating the Web browser selects the Web service, the display name of the Web service described in Japanese, and the name of the device that provides the Web service. And can be provided to the user.

  FIG. 11 is a diagram (part 3) for explaining the service information storage unit.

  As shown in FIG. 11, the service information storage unit 55 stores a Name, a Display Name, a Display Name ja, an Access port, an Access Uri, a Type, a Machine Name, a Machine Name ja, and an Icon. Included as

  In the service information storage unit 55 shown in FIG. 11, an item of Icon is newly added as compared with the service information storage unit 55 shown in FIG.

  In the Icon, information on an icon related to a Web service provided by the Web service providing service 41 in which the service information providing unit 50 is mounted is stored.

  In response to a request from the client 20 described later, the service information providing unit 50 stores the Web service providing service 41 in which the service information providing unit 50 is mounted, which is stored in the service information storage unit 55 illustrated in FIG. Generates a response including information on an icon related to the Web service provided by the Web server.

  An example of a response including icon information will be described with reference to FIG. 17 described later.

  The client 20 can generate a screen including the icon related to the Web service by obtaining a response including information on the icon related to the Web service, and can provide the screen to the user.

  Hereinafter, another example of the service information storage unit 55 will be described with reference to FIG. FIG. 12 is a diagram (part 4) for explaining the service information storage unit.

  FIGS. 9 to 11 show an example in which the service information storage unit 55 is configured in a form such as a relational database (RDB). However, the service information storage unit 55 is stored in XML as shown in FIG. (Extensible Markup Language) database (XMLDB). The contents stored in the service information storage unit 55 shown in FIG. 12 are the same as the contents stored in the service information storage unit 55 shown in FIG.

  FIG. 13 is a diagram (part 1) for explaining a request.

  In the request shown in FIG. 13, the ID of the Web service to be searched is described by “http: // foo / var / repository” after “ST:”, and “type =” after “?” "mfp" describes the search condition in the form of "key = value".

  As shown in FIG. 13, the client 20 transmits a search request including a search condition after “?” To the service information providing server 10 by multicast.

  The client 20 can search the Web service using the search request including the search condition, thereby searching for the Web service more in accordance with the user's request.

  Note that the client 20 can also specify a plurality of search conditions as “key1 = value1 & key2 = value2...” As search conditions.

  FIG. 14 is a diagram (part 1) for explaining the response.

  In the response shown in FIG. 14, the ID of the Web service is described by “http: // foo / var / repository” after “ST:”, and “type = mfp & machinename = third Floor” after “?” “east side & displayname = Repository for Development section” describes information related to the Web service provided by the Web service providing service 41 in which the service information providing unit 50 is implemented.

  More specifically, "type = mfp" describes the implementation type of the Web service, "machinename = third Floor east side" describes the name of the device that provides the Web service in English, and "displayname = Repository for Development section "describes the display name of the Web service in English.

  Since an actual response cannot include a space, an escape sequence for an HTTP space character (% 20) is included instead of a space. However, for the sake of simplicity, the embodiment of the present invention will be described. In, the explanation is given including the space.

  When the service information providing unit 50 receives the request as shown in FIG. 13 once, as shown in FIG. 14, after the “?”, The implementation type of the Web service, the name of the device providing the Web service, A response including information required when a user selects a Web service such as a name for displaying a service can be generated and transmitted to the client 20.

  FIG. 15 is a diagram (part 2) for explaining the request.

  In the request illustrated in FIG. 15, “lang = ja” after “type = mfp &” specifies the language of information related to the Web service included in the response to the request.

  More specifically, in the request of FIG. 15, “lang = ja” may be used to respond to the information corresponding to Japanese among the information on the Web service included in the response to the request in Japanese. Is specified.

  The client 20 searches for a Web service using a request in which language designation information for designating a language of information related to the Web service included in a response to the request is included in additional information of search conditions after “?”. As a result, information on the Web service described in a language easy to understand for the user can be obtained as a response and provided to the user.

  FIG. 16 is a diagram (part 2) for explaining the response.

  In the response shown in FIG. 16, “type = mfp & machinename = third-floor east side & displayname = depository repository service” indicates information on the Web service provided by the Web service providing service 41 in which the service information providing unit 50 is installed. However, portions corresponding to Japanese are described in Japanese.

  Note that the actual response is described in an escaped form, such as%, as in the case of a blank, but for simplification of description, in the embodiment of the present invention, Explanations are given using words.

  Upon receiving the request as shown in FIG. 15 transmitted by the client 20, the service information providing unit 50 analyzes the “lang =” portion included in the request shown in FIG. After the "?", A response including information on the Web service described in Japanese can be generated and transmitted to the client 20.

  FIG. 17 is a diagram (part 4) for explaining the response.

  In the response shown in FIG. 17, “icon = jh76FSD8wefqwde2DSte53uiweyr7wyr723fr23rr8fwe” describes icon information related to the Web service provided by the Web service providing service 41 in which the service information providing unit 50 is installed.

  The service information providing unit 50 generates a response including information on the icon related to the Web service as shown in FIG. 17 so that the user can select a Web service in response to a single search request. A response including icon information that provides ease can be provided to the client 20.

  FIG. 18 is a diagram (part 4) for explaining the response.

  As described with reference to FIGS. 13 and 15, the client 20 transmits a search request for searching for a Web service provided by the Web service providing service 41 to the service information providing server 10 by multicast, and also provides service information. An HTTP 1.1 GET request for acquiring a list of Web services provided by the Web service providing service 41 of the server 10 is transmitted to the service information providing server 10.

  The service information providing unit 50 mounted on each Web service providing service 41 that has obtained the GET request generates a response as shown in FIG.

  The tag of <machineName lang = "en"> <// machineName> shown in FIG. Stored in English.

  In the tag of <machineName lang = "ja"> <// machineName>, the name of the device that provides the Web service is stored in Japanese.

  In the <displayName lang = "en"> </ displayName> tag, the display name of the Web service is stored in English.

  The <displayName lang = "ja"> </ displayName> tag stores the display name of the Web service in Japanese.

  FIG. 19 is a diagram (part 5) for explaining the response.

  When the Web server 40 obtains the response as described in FIG. 18 from the service information providing unit 50 mounted on each Web service providing service 41, the Web server 40 generates a response including the response as illustrated in FIG. Send to client 20.

  The service information providing server 10 generates a response including a list of Web services provided by the service information providing server 10 as shown in FIG. Can provide the client 20 with a response including information necessary for selecting a Web service.

  Hereinafter, an example of the service information providing process in the service information providing unit 50 will be described with reference to FIGS.

  FIG. 20 is a flowchart (part 1) of the service information providing process.

  When the service information providing unit 50 obtains a search request transmitted from the client 20 as described with reference to FIGS. 13 and 15 from the Web server 40, the service information providing unit 50 starts processing from the following step S10.

  In step S10, the request analysis unit 51 analyzes the content of the acquired request.

  For example, the request analysis unit 51 converts the search condition (type = mfp) described after “?” In the request described in FIG. 13 and the language specification information specified by “lang =” described in FIG. To analyze.

  Proceeding to step S11 following step S10, the service information management unit 53 acquires, from the service information storage unit 55, information on the Web service provided by the Web service providing service 41 in which the service information providing unit 50 is mounted. .

  For example, the service information management unit 53 uses the service information storage unit 55 as shown in FIG. To obtain information related to.

  Proceeding to step S12 following step S11, the service information determining unit 54 compares the search condition analyzed in step S10 with the information on the Web service acquired in step S11, and implements the service information providing unit 50. It is determined whether the Web service provided by the provided Web service providing service 41 is the Web service requested in the request.

  The service information determining unit 54 determines that the Web service provided by the Web service providing service 41 in which the service information providing unit 50 is mounted is the Web service requested in the request (YES in step S12). If it is determined that the Web service provided by the Web service providing service 41 in which the service information providing unit 50 is provided is not the Web service requested in the request (NO in Step S12), the process proceeds to Step S13. To end.

  For example, the service information determination unit 54 compares the value of the type as the search condition obtained from the request shown in FIG. 13 with the value of the implementation type of the service obtained from the service information storage unit shown in FIG. Then, it is determined whether the Web service provided by the Web service providing service 41 in which the service information providing unit 50 is mounted is the Web service requested in the request.

  In step S13, the service information determination unit 54 determines whether a response in Japanese is required based on the result analyzed in step S10.

  If the service information determination unit 54 determines that a response in Japanese is required (YES in step S13), the process proceeds to step S15, and determines that a response in Japanese is not required ( (NO in step S13), and proceeds to step S14.

  For example, the service information determination unit 54 determines whether a response in Japanese is required based on whether or not “lang = ja” is included in the request as a result of the analysis in step S10.

  In step S14, the response generation unit 52 generates a response that does not include Japanese (for example, see FIG. 14) using the information on the Web service acquired in step S11.

  In step S15, the response generation unit 52 generates a response including Japanese (for example, see FIG. 16 or FIG. 17) using the information on the Web service acquired in step S11.

  By performing the processing shown in FIG. 20, the service information providing unit 50 analyzes the content of the search request as shown in FIGS. 13 and 15, and responds to the request in FIGS. Can be generated.

  Hereinafter, another example of the service information providing process will be described with reference to FIG. FIG. 21 is a flowchart (part 2) of the service information providing process.

  When the service information providing unit 50 obtains the search request transmitted from the client 20 as described with reference to FIGS. 13 and 15 from the Web server 40, the service information providing unit 50 starts the processing from the following step S40.

  In step S40, the request analysis unit 51 analyzes the content of the acquired request and creates a query. If the service information storage unit 55 is in the RDB format as shown in FIGS. 9 to 11, the request analysis unit 51 creates a query using SQL (Structured Query Language) and stores the service information. When the unit 55 has the XMLDB format as shown in FIG. 12, a query is created using XQuery.

  Proceeding to step S41 following step S40, the service information management unit 53 performs a search on the service information storage unit 55 using the query created in step S40. The query includes, for example, a search condition (type = mfp) described after “?” In the request described in FIG. 13 and language designation information specified by “lang =” described in FIG. Is included.

  Proceeding to step S42 following step S41, the service information determination unit 54 determines whether there is information related to the Web service requested in the request based on the result of the search performed in step S41.

  If the service information determination unit 54 determines that there is information related to the Web service requested in the request (YES in step S42), the process proceeds to step S43, in which the information related to the Web service requested in the request exists. If not (NO in step S42), the process ends.

  In step S43, the service information management unit 53 acquires information on the Web service requested in the request from the service information storage unit 55. For example, when Japanese is specified by “lang =” in the request, the service information management unit 53 determines that the information related to the Web service corresponding to Japanese is related to the Web service written in Japanese. Get information.

  Proceeding to step S44 following step S43, the response generation unit 52 generates a response including the information on the Web service acquired in step S43.

  Even if the processing as shown in FIG. 21 is performed, the service information providing unit 50 analyzes the contents of the search request as shown in, for example, FIG. 13 and FIG. A response as shown in FIG. 17 can be generated.

  FIG. 22 is a flowchart (part 3) of the service information providing process.

  When the service information providing unit 50 acquires the HTTP 1.1 GET request transmitted from the client 20 from the Web server 40, the service information providing unit 50 starts the processing from step S20 described below.

  In step S20, the request analysis unit 51 analyzes the content of the acquired request.

  Proceeding to step S21 following step S20, the service information management unit 53 acquires, from the service information storage unit 55, information on the Web service provided by the Web service providing service 41 in which the service information providing unit 50 is mounted. .

  For example, the service information management unit 53 stores, from the service information storage unit 55 as shown in FIG. get.

  Proceeding to step S22 following step S21, the response generation unit 52 generates a response (for example, see FIG. 18).

  By performing the processing illustrated in FIG. 22, the service information providing unit 50 can analyze the content of the HTTP 1.1 GET request and generate a response to the request as illustrated in FIG.

  Hereinafter, the hardware configuration of the client 20 will be described with reference to FIG.

  FIG. 23 is a hardware configuration diagram of an example of the client.

  The hardware configuration of the client 20 shown in FIG. 23 includes an input device 21, a display device 22, a drive device 23, a ROM (Read Only Memory) 25, and a RAM (Random) which are interconnected by a bus B. Access Memory (Access Memory) 26, CPU (Central Processing Unit) 27, interface device 28, and HDD (Hard Disk Drive) 29.

  The input device 21 includes a keyboard and a mouse operated by the user of the client 20, and is used to input various operation signals to the client 20.

  The display device 22 is configured by a display or the like operated by a user of the client 20, and displays various screens described later.

  The interface device 28 is an interface that connects the client 20 to the network 5.

  A service information acquisition program for acquiring information on the service required when the user selects a service is provided to the client 20 by a recording medium 24 such as a CD-ROM, or is downloaded via the network 5. . The recording medium 24 is set in the drive device 23, and data and the service information acquisition program are installed from the recording medium 24 into the HDD 29 via the drive device 23.

  The ROM 25 stores data and the like. The RAM 26 reads and stores the service information acquisition program from the HDD 29 when the client 20 starts up. The CPU 27 executes processing in accordance with the service information acquisition program read and stored in the RAM 26.

  FIG. 24 is a diagram for explaining an example of the function of the client using a functional block diagram.

  As shown in FIG. 24, the client 20 includes a request generation unit 60, a response analysis unit 61, a user I / F unit 62, and a network I / F unit 63.

  The request generation unit 60 generates a Web service search request (for example, see FIG. 13 or 15) and an HTTP1.1 GET request.

  The response analysis unit 61 analyzes a response (for example, see FIGS. 14, 16, 17, and 19) received from the service information providing server 10.

  The user I / F unit 62 generates a screen as shown in FIGS. 25 and 26 described later and displays the screen on a display. When a button or the like on the displayed screen is clicked by the user, the event information is acquired and notified to the request generation unit 60 and the like.

  The network I / F unit 63 is an interface for connecting the client 20 and another device. The network I / F unit 63 transmits the request generated by the request generation unit 60 to the service information providing server 30 via the network 5, For example, a response from the server 30 is received via the network 5.

  Hereinafter, an example of a screen generated and displayed by the user I / F unit 62 will be described with reference to FIGS.

  FIG. 25 is a diagram illustrating an example of a search service selection screen.

  The user I / F unit 62 generates a screen for allowing the user to select a Web service to be searched, as shown in FIG. 25, based on a request from the user who operates the client 20, and displays the screen on the display.

  The user operating the client 20 selects a Web service to be searched using a screen as shown in FIG.

  For example, when the repository service is selected by the user and the OK button is clicked, the user I / F unit 62 acquires the event information and notifies the request generation unit 60 and the like.

  Upon acquiring the event information indicating that the user has selected the repository service and clicked the OK button from the user I / F unit 62, the request generation unit 60 generates, for example, a request as shown in FIG. It is transmitted to the providing server 10 or the like.

  FIG. 26 is a diagram for describing an example of a search result screen.

  The client 20 receives a response (for example, see FIGS. 14, 16, 17, and 19) from the service information providing server 10 or the like.

  The response analysis unit 61 analyzes the response, and the user I / F unit 62 generates a screen as shown in FIG. 26 based on the analysis result analyzed by the response analysis unit 61 and displays the screen on the display.

  In FIG. 26, as a result of the searched Web service, a display name of the Web service and a name of a device that provides the Web service are written in Japanese, and an icon (MFP icon) related to the Web service is displayed. Have been.

  As shown in FIGS. 25 and 26, the user designates a Web service to be searched by using the service information providing server 10 and the client 20 according to the present invention, and executes the search only once. The user can acquire the information required when selecting.

  Hereinafter, an example of the service information acquisition process in the client 20 will be described with reference to FIG.

  FIG. 27 is a flowchart of an example of the service information acquisition process.

  The request generation unit 60 obtains, from the user I / F unit 62, information indicating that the Web service to be searched is specified by the user and the OK button is clicked on the search service selection screen as illustrated in FIG. The processing from the following step S30 is started.

  In step S30, the request generation unit 60 generates a Web service search request (for example, see FIG. 13 or 15) and / or an HTTP1.1 GET request.

  Proceeding to step S31 following step S30, the network I / F unit 63 transmits the request generated in step S30.

  For example, the network I / F unit 63 transmits a Web service search request shown in FIG. 13 or FIG. 15 to the service information providing server 10 or the like via the network 5 by multicasting or a HTTP 1.1 GET request. Is transmitted to the service information providing server 10.

  Proceeding to step S32 following step S31, the network I / F unit 63 responds to a search for a Web service transmitted from the service information providing server 10 or the like via the network 5 (for example, FIG. 14, FIG. 16, FIG. 17) and / or a response to the HTTP 1.1 GET request (for example, see FIG. 19).

  Proceeding to step S33 following step S32, the response analysis unit 61 analyzes the response obtained in step S32.

  Proceeding to step S34 following step S33, the user I / F unit 62 generates, for example, a screen as shown in FIG. 26 based on the result analyzed in step S33.

  Proceeding to step S35 following step S34, the user I / F unit 62 displays the screen generated in step S34 on a display.

  By performing the processing shown in FIG. 27, the client 20 transmits a request as shown in FIGS. 13 and 15 and / or a GET request of HTTP 1.1 to the service information providing server 10, and 17, and / or a response as shown in FIG. 19, and a user searches for and / or obtains information required when the user selects a Web service by a single search and / or acquisition request. Can be provided.

The client 20 uses a dedicated program to interpret the response shown in FIGS. 14, 16 and 17 and the response shown in FIG. 19 to generate and display a screen. For example, an XSLT (XML Style Language Language Transform) processor for converting an XML-based language as shown in FIGS. 18 and 19 into an HTML-based language between the service information providing server 10 and the client 20 is described. And the response returned from the service information providing server 10 may be displayed on the browser of the client 20.
(Explanation of the second embodiment)
Hereinafter, an image forming apparatus (hereinafter, referred to as a multifunction peripheral) that forms an image will be described as another example of a device on which an application that provides a Web service and in which the service information providing unit 50 is mounted operates.

  FIG. 28 is a block diagram illustrating a functional configuration of the multifunction peripheral.

  In FIG. 28, a multifunction peripheral 1200 includes a plotter 1201, a scanner 1202, a hardware resource 1203 such as a facsimile, etc., and a software group 1210 including a platform 1220 and an application 1230; It has.

  The multifunction peripheral activation unit 1240 is executed first when the multifunction peripheral 1200 is powered on, and activates the platform 1220 and the application 1230.

  The platform 1220 interprets the processing request from the application 1230 and generates a hardware resource acquisition request as described below. The platform 1220 manages one or more hardware resources, and acquires from the control service 1250. It has a system resource manager (SRM (System Resource Manager) 1223) for arbitrating requests and an OS 1221.

  The control service 1250 is formed by a plurality of service modules. Specifically, the SCS (System Control Service) 1222, the ECS (Engine Control Service) 1224, the MCS (Memory Control Service) 1225, and the OCS (Operation) A Control Service (FAS) 1227; a FCS (FAX Control Service) 1227; an NCS (Network Control Service) 1228; and an IMH (Imaging Memory Handler) 1229. The platform 1220 has an application program interface that enables a processing request from the application to be received by a predefined function.

  The OS 1221 is an operating system such as UNIX (registered trademark), and executes each software of the platform 1220 and the application 1230 as a process in parallel.

  The SRM 1223 controls the system and manages resources together with the SCS 1222. The SRM 1223 includes an engine unit such as a scanner and a plotter, a memory, an HDD file, a host I / O (a Centro I / F, a network I / F, an IEEE1394 I / F, It performs arbitration in accordance with a request from an upper layer using hardware resources such as RS232CI / F, and controls execution.

  The SCS 1222 performs a plurality of functions such as application management, operation unit control, system screen display (job list screen, counter display screen, etc.), LED display, resource management, interrupt application control, and the like.

  The ECS 1224 controls an engine unit such as a plotter 1201, a scanner 1202, and other hardware resources 1203, and performs image reading and printing operation, status notification, jam recovery, and the like.

  The MCS 1225 performs memory control.

  The OCS 1226 is a module that controls an operation panel serving as information transmission means between the operator and the main body control. The OCS 1226 provides processing for notifying the main body control of key operation events of the operator, and provides a library function for each application to construct a GUI. Processing, processing for managing the constructed GUI information for each application, processing for reflecting the display on the operation panel, and the like are performed.

  The FCS 1227 performs facsimile transmission / reception using PSTN / ISDN from each application layer of the system controller, registration / quotation of various facsimile data managed by BKM (backup SRAM), facsimile reading, facsimile reception printing, and fusion transmission / reception. API (Application Programming Interface) 1205 is provided.

  The NCS 1228 is a group of modules for providing services that can be used in common to applications that require network I / O. The NCS 1228 distributes data received from the network according to each protocol to each application, and distributes data from an application. Intermediary when sending to the network side.

  In the present embodiment, for example, the NCS 1228 controls data communication with a client connected via the Internet using HTTPd (Hypertext Transfer Protocol Daemon) 2 among a plurality of protocols using HTTP (Hypertext Transfer Protocol), and performs an HTTP request. The processing unit corresponding to the Web service specified by the header may be started by a function call, and the result of the processing by the Web service may be notified to the client by an HTTP response. The Web service is provided according to a message described in XML, for example.

  The IMH 1229 maps image data from a virtual memory area (user virtual space) to a physical memory.

  The application 1230 includes a printer application 1211 that is a printer application having a page description language (PDL), PCL, and PostScript (PS), a copy application 1212 that is a copy application, and a fax application 1213 that is a facsimile application. , A scanner application 1214 as a scanner application, a web service processing application 1215 as a web service application, a process inspection application 1216 as a process inspection application, and a distribution application 1217 as a distribution application.

  The Web service processing application 1215 receives an HTTP request for requesting a Web service, and transmits a HTTP response to the Web server 500 that provides the Web service, and controls the control service 1250 via an API (Application Program Interface) 1205. A Web service function (WSF) 1400 that performs a predetermined process using the service, and provides a result of the process as a web service via a WS-API (Web Service Application Program Interface).

  As in the system configuration shown in FIG. 4, the MFP 1200 is connected to the client 20 via the network 5. The Web service providing service 41 described with reference to FIG. 4 corresponds to the Web service processing application 1215.

  In the present embodiment, the service information providing unit 50 described in the first embodiment is realized by, for example, mounting a program corresponding to the service information providing unit 50 in each Web service function (WSF) 1400.

  The processing in the service information providing unit 50 is the same as that described in the first embodiment.

  When acquiring the search request described with reference to FIGS. 13 and 15 from the client 20 connected to the MFP 1200 via the network 5, the service information providing unit 50 starts the processing shown in FIG. A response to the request as shown in FIGS. 14, 16 and 17 is generated.

  When the service information providing unit 50 obtains the HTTP 1.1 GET request from the client 20 connected to the MFP 1200 via the network 5, the service information providing unit 50 starts the processing shown in FIG. Generate a response as shown in.

  The multifunction peripheral 1200 unifies the processing commonly required for each application by the platform 1220.

  Hereinafter, an example of the service information providing unit 50 mounted on the MFP 1200 will be described with reference to FIG. FIG. 29 is a diagram (part 1) illustrating the service information providing unit mounted on the multifunction peripheral.

  As shown in FIG. 29, the service information providing unit 50 is implemented for each of the print service providing service 42 and the repository service providing service 43 which are WSFs 1400, and includes a request analyzing unit 51, a response generating unit 52, a service information managing unit Unit 53 and a service information determination unit 54.

  The distributor 2a is a distribution unit that distributes processing to the WSF 1400 corresponding to the HTTP request. The sspd2b is a daemon for exchanging information described in XML with the client 20 based on SSDP (Simple Service Discover Protocol).

  The service information storage unit 45 is configured by an HDD 1303 or a flash memory of the MFP 1200 described later.

  Hereinafter, another example of the service information providing unit 50 mounted on the MFP 1200 will be described with reference to FIG. 30. FIG. 30 is a diagram (part 2) illustrating the service information providing unit mounted on the MFP.

  The functional configuration of the service information providing unit 50 illustrated in FIG. 30 is different from the functional configuration of the service information providing unit 50 illustrated in FIG. 29 in that the request analyzing unit 51 and the response generating unit 52 are different from each other. , And is included in the Web server 500.

  With the configuration illustrated in FIG. 30, even when a plurality of WSFs 1400 exist in the multifunction peripheral 1200 and the service information providing unit 50 is mounted for each WSF 1400, the plurality of service information providing units 50 , The request analysis unit 51 and the response generation unit 52 can be shared and used.

  Next, a hardware configuration of the MFP 1200 will be described. FIG. 31 is a block diagram illustrating a hardware configuration of the multifunction peripheral. As shown in FIG. 31, the MFP 1200 includes an operation panel 1310, a facsimile control unit (FCU) 1530, an engine unit 1350 (to which a scanner 1202 and the like are connected), a plotter 1201 and an ASIC 1301 of a controller 1300 through a PCI (Peripheral). Component Interconnect) bus 1309 and the like.

  The controller 1300 connects the ASIC 1301 with a MEM-C 1302, a hard disk drive (HDD) 1303, and the like, and connects the ASIC 1301 and the CPU 1304 via an NB 1305 of a CPU chipset.

  The CPU 1304 performs overall control of the MFP 1200. Specifically, the SCS 1222, the SRM 1223, the ECS 1224, the MCS 1225, the OCS 1226, the FCS 1227, and the NCS 1228 that form the platform 1220 on the OS 1221 are started and executed as processes. At the same time, the printer application 1211, the copy application 1212, the fax application 1213, the scanner application 1214, the web service processing application 1215, the process inspection application 1216, and the distribution application 1217, which form the application 1230, are activated and executed.

  The NB 1305 is a bridge for connecting the CPU 1304 to the MEM-P 1306, the SB 1307, the NIC (Network Interface Card) 1341, the USB (Universal Serial Bus) 1330, the IEEE 13941340, the Centronics 1342, and the ASIC 1301.

  The MEM-P 1306 is a system memory used as a drawing memory of the multifunction peripheral, and the SB 1307 is a bridge for connecting the NB 1305 to a ROM, a PCI device, and peripheral devices. The MEM-C 1302 is a local memory used as an image buffer for copying and a code buffer, and the ASIC 1301 is an IC for image processing having a hardware element for image processing.

  The HDD 1303 is a storage for storing image data, storing programs, storing font data, and storing forms. The operation panel 1310 receives an input operation from an operator and performs display for the operator. An operation unit.

  Therefore, the ASIC 1301 is provided with a RAM interface for connecting the MEM-C 1302 and a hard disk interface for connecting the HDD 1303. When inputting and outputting image data to and from these storage units, The destination is switched to the RAM interface or the hard disk interface.

  The AGP 1308 is a bus interface for a graphics accelerator card proposed to speed up graphics processing, and speeds up the graphics accelerator card by directly accessing the system memory at high throughput.

  Even if the device on which the application providing the Web service on which the service information providing unit 50 is installed operates is the multifunction peripheral 1200, the client 20 can request the Web service search (for example, see FIG. 13 or FIG. 15). And / or generates and transmits an HTTP 1.1 GET request, and transmits a Web service search response (for example, see FIGS. 14, 16, and 17) and / or an HTTP 1.1 GET request from the MFP 1200. (See FIG. 19, for example), and the information required when the user selects the Web service can be provided to the user by one search and / or acquisition request.

  Although the preferred embodiments of the present invention have been described in detail, the present invention is not limited to the specific embodiments, and various modifications may be made within the scope of the present invention described in the appended claims.・ Change is possible.

FIG. 11 is a diagram (part 1) for describing a problem of the conventional technology. FIG. 11 is a diagram (part 2) for describing a problem of the related art. FIG. 1 is a system configuration diagram for explaining an example of a system configuration for implementing the present invention. FIG. 11 is a system configuration diagram for explaining another example of a system configuration for implementing the present invention. FIG. 3 is a functional configuration diagram of an example of a service information providing server. FIG. 2 is a hardware configuration diagram of an example of a service information providing server. FIG. 4 is a diagram for describing an example of a function of a service information providing unit using a functional block diagram. FIG. 11 is a diagram for describing another example of the function of the service information providing unit using a functional block diagram. FIG. 3 is a diagram (part 1) for explaining a service information storage unit; FIG. 11 is a diagram (part 2) for explaining the service information storage unit; FIG. 11 is a diagram (part 3) for explaining the service information storage unit; FIG. 11 is a diagram (part 4) for explaining the service information storage unit; FIG. 11 is a diagram (part 1) for explaining a request. FIG. 11 is a diagram (part 1) for explaining a response. FIG. 11 is a diagram (part 2) for explaining the request. FIG. 11 is a diagram (part 2) for explaining a response. FIG. 11 is a diagram (part 4) for explaining a response. FIG. 11 is a diagram (part 4) for explaining a response. FIG. 11 is a diagram (No. 5) for explaining a response. It is a flowchart (the 1) of the service information provision processing. It is a flowchart (the 2) of a service information provision process. It is a flowchart (the 3) of the service information provision processing. FIG. 2 is a hardware configuration diagram of an example of a client. FIG. 3 is a diagram for describing an example of a function of a client using a functional block diagram. It is a figure for explaining an example of a search service selection screen. It is a figure for explaining an example of a search result screen. It is a flowchart of an example of service information acquisition processing. FIG. 2 is a block diagram illustrating a functional configuration of the multifunction peripheral. FIG. 3 is a diagram (part 1) illustrating a service information providing unit mounted on the multifunction peripheral. FIG. 3 is a diagram (part 2) illustrating a service information providing unit mounted on the multifunction peripheral. FIG. 2 is a block diagram illustrating a hardware configuration of the multifunction peripheral.

Explanation of reference numerals

2 httpd (Hypertext Transfer Protocol Daemon)
5 Network 10 Service Information Providing Server 20 Client 21 Input Device 22 Display Device 23 Drive Device 24 Recording Medium 25 ROM (Read Only Memory)
26 RAM (Random Access Memory)
27 CPU (Central Processing Unit)
28 Interface device 29 HDD (Hard Disk Drive)
31 Drive device 32 Recording medium 33 ROM (Read Only Memory)
34 RAM (Random Access Memory)
35 CPU (Central Processing Unit)
36 Interface device 37 HDD (Hard Disk Drive)
Reference Signs List 40 Web server 41 Web service providing service 42 Print service providing service 43 Repository service providing service 50 Service information providing unit 51 Request analyzing unit 52 Response generating unit 53 Service information managing unit 54 Service information determining unit 55 Service information storing unit 60 Request generating unit 61 Response analysis unit 62 User I / F unit 63 Network I / F unit 1200 Multifunction machine 1201 Plotter 1202 Scanner 1203 Other hardware resources 1210 Software group 1220 Platform 1221 OS (Operating System)
1222 SCS (System Control Service)
1223 SRM (System Resource Manager)
1224 ECS (Engine Control Service)
1225 MCS (Memory Control Service)
1226 OCS (Operation panel Control Service)
1227 FCS (FAX Control Service)
1228 NCS (Network Control Service)
1229 IMH (Imaging Memory Handler)
1230 Application 1301 ASIC (Application Specific Integrated Circuit)
1302 MEM-C
1303 HDD (Hard Disk Drive)
1304 CPU (Central Processing Unit)
1305 NB (North Bridge)
1306 MEM-P (system memory)
1307 SB (South Bridge)
1308 AGP (Accelerated Graphics Port)
1309 PCI Bus (Peripheral Component Interconnect Bus)
1310 Operation panel 1330 USB (Universal Serial Bus) target 1340 IEEE1394
1341 NIC (Network Interface Card)
1342 Centronics 1350 Engine 1530 FCU (FAX control unit)

Claims (26)

A service providing apparatus having service providing means for providing a service used by a user,
A service providing unit for providing information on the service used when the user selects the service in response to a request from a user terminal device; .   2. The service providing apparatus according to claim 1, wherein the service information providing unit includes a service information obtaining unit that obtains information on the service from a service information storage unit that stores information on the service. The request includes a search condition for the service,
The service information providing unit further includes a determination unit that determines whether the information about the service acquired by the service information acquisition unit is the information about the service requested in the request, based on the search condition. 3. The service providing apparatus according to claim 2, comprising: The request includes a search condition for the service,
2. The service according to claim 1, wherein the service information providing unit includes a search unit that searches for information about the service from a service information storage unit that stores information about the service based on the search condition. Providing device.   The service providing apparatus according to claim 1, wherein the service information providing unit includes a request analysis unit configured to analyze a request from the user terminal device.   The said service information provision means has response creation means which creates the response containing the information regarding the said service used when the said user selects the said service, The Claim 1 characterized by the above-mentioned. Service providing equipment.   The service providing apparatus according to claim 1, further comprising a service information storage unit configured to store information on the service. The information on the service stored in the service information storage means is described in two or more languages,
8. The service providing apparatus according to claim 7, wherein the request includes language specification information for specifying a language of information on the service included in a response corresponding to the request. In the response corresponding to the request, as information related to the service,
The name of the service,
The name of the device providing the service,
The type of service,
Icon information related to the service,
The service providing apparatus according to claim 1, wherein at least one of them is included.   The service providing apparatus according to claim 1, wherein the service providing apparatus is an image forming apparatus that forms an image. A user terminal device used by a user who uses a service provided by a service providing unit,
Request creating means for creating a request including a search condition relating to the service,
Response receiving means for receiving a response including information related to the service used when the user selects the service, in response to the request,
A user terminal device comprising:   12. The user terminal device according to claim 11, further comprising a screen generating unit that generates a screen including information on the service based on the response received by the response receiving unit. A service providing method in a service providing means for providing a service used by a user,
A service providing method, comprising a service information providing step of providing information on the service used when the user selects the service in response to a request from a user terminal device.   14. The service providing method according to claim 13, further comprising a service information acquiring step of acquiring information on the service from service information storage means for storing information on the service.   The request includes a search condition related to the service, and based on the search condition, whether the information related to the service acquired in the service information acquisition step is the information related to the service requested in the request. 15. The service providing method according to claim 14, further comprising a determining step of determining whether or not the service is provided.   The request includes a search condition related to the service, and further includes a search step of searching for information related to the service by a service information storage unit that stores information related to the service based on the search condition. 14. The service providing method according to claim 13, wherein:   17. The service providing method according to claim 13, further comprising a request analysis step of analyzing a request from the user terminal device.   18. The service providing method according to claim 13, further comprising a response creating step of creating a response including information on the service used when the user selects the service.   19. The service providing method according to claim 13, wherein the request includes language specification information for specifying a language of information on the service included in a response corresponding to the request. In the response corresponding to the request, as information related to the service,
The name of the service,
The name of the device providing the service,
The type of service,
Icon information related to the service,
20. The service providing method according to claim 13, wherein at least one or more are included. A service usage method using a service provided by a service providing means,
A request creating step of creating a request including a search condition relating to the service;
In response to the request, a response receiving step of receiving a response including information on the service used when the user selects the service,
A service utilization method comprising:   22. The service using method according to claim 21, further comprising a screen generating step of generating a screen including information on the service based on the response received in the response receiving step.   A service providing program for causing a computer to execute the service providing method according to any one of claims 13 to 20.   A service utilization program for causing a computer to execute the service utilization method according to claim 21 or 22.   A computer-readable recording medium on which the service providing program according to claim 23 is recorded.   A computer-readable recording medium recording the service utilization program according to claim 24.

Images