JP2006252481A - Function providing device, function providing method, function providing program and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a function providing device capable of easily adding a function which can be provided for external equipment, a function providing method, a function providing program and a recording medium. <P>SOLUTION: The function providing device 1 capable of providing the external equipment 2 with the function 14 comprises: general purpose interfaces 10 and 11 for receiving requests from the external equipment 2 to the functions 14 and distributing them to the respective functions 14; and dedicated interfaces 12 provided for the respective functions 14 for achieving the requests distributed to the respective functions 14 by the general purpose interfaces 10 and 11. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a function providing apparatus, a function providing method, a function providing program, and a recording medium, and more particularly to a function providing apparatus, a function providing method, a function providing program, and a function providing program capable of providing one or more functions to an external device. The present invention relates to a recorded recording medium.

  The function providing device accepts a request from an external device and realizes the request with various functions. For example, an image handling apparatus that receives a request from an external device via a network and realizes the request with various functions is an example of a function providing apparatus. The image handling device referred to here includes a printer device, a copy device, a facsimile device, a scanner device, or a multifunction device in which some or all of the functions of each device described above are housed in one housing.

  The multifunction device is provided with a display unit, a printing unit, an imaging unit, and the like in a single casing, and with an application corresponding to each of a printer device, a copy device, a facsimile device, and a scanner device. Operates as a device, a facsimile device, and a scanner device.

  In recent years, with the development and popularization of networks such as the Internet and LAN, multifunction devices have communication functions. A multifunction device having a communication function can be connected to an external device via a network, and provision of a so-called Web service has been desired.

  The Web service uses a WWW (World Wide Web) related technology, and functions such as software can be used through a network. Patent Document 1 describes a composite image forming apparatus that provides a Web service to devices via a network.

  In a conventional multifunction device, when providing a Web service to an external device connected via a network, it is necessary to define a Web service interface (WSDL) for each function. Here, WSDL (Web Service Description Language) is a language specification based on XML (eXtensible Markup Language) for describing Web services.

  WSDL defines a method for describing what functions a Web service has and what requests it should make in order to use it. FIG. 1 is a configuration diagram illustrating an example of a system including a multifunction peripheral (MFP) that provides a Web service.

The MFP 1000 in FIG. 1 has a print function, a document storage function, and a FAX function, and defines a Web service interface (WSDL) for each function. The client 1001 connected to the MFP 1000 via the network needs to know the interface (WSDL) of each Web service in order to use the Web service provided by the MFP 1000.
Japanese Patent Laid-Open No. 2004-5503

  In the conventional MFP 1000, when a new function is provided as a Web service, it is also necessary to add a Web service interface (WSDL). The conventional MFP 1000 has a problem that it is difficult to dynamically add a Web service interface (WSDL), and a new function cannot be dynamically added as a Web service. “Dynamically adding” refers to incorporation into the multifunction machine 1000 in operation.

  SUMMARY An advantage of some aspects of the invention is that it provides a function providing apparatus, a function providing method, a function providing program, and a recording medium that can easily add functions that can be provided to an external device.

  In order to solve the above problems, the present invention is a function providing apparatus capable of providing one or more functions to an external device, accepting a request from the external device for the one or more functions, and receiving the request A general-purpose interface that distributes each function; and a dedicated interface that is provided for each function and that implements the request distributed by the general-purpose interface for each function.

  The present invention is also a function providing method of a function providing apparatus capable of providing one or more functions to an external device, and accepts a request from the external device for the one or more functions, and receives the request from the function And a step of realizing the request distributed for each function by the general-purpose interface by the function.

  Further, the present invention provides a general-purpose interface that accepts a request from the external device for the one or more functions, and distributes the request for each function to a computer that can provide one or more functions to the external device; It is a function providing program that is provided for each function, and causes the request distributed for each function by the general-purpose interface to function as a dedicated interface for realizing the function.

  Further, the present invention is a computer-readable recording medium on which the function providing program described above is recorded.

  In the present invention, the function providing device has a general-purpose interface and a dedicated interface. The external device can use various functions of the function providing device as long as it knows the general-purpose interface. In addition, a dedicated interface is provided for each function, and a request from an external device can be actually realized by the function while absorbing the difference between the functions. The general-purpose interface can easily register a dedicated interface.

  Therefore, the function providing apparatus can provide a general-purpose interface for using the function to the external device, and can easily register a dedicated interface for each function in the general-purpose interface. The external device can easily use the function added to the function providing apparatus by using the general-purpose interface.

  According to the present invention, it is possible to provide a function providing apparatus, a function providing method, a function providing program, and a recording medium that can easily add a function that can be provided to an external device.

  Next, the best mode for carrying out the present invention will be described based on the following embodiments with reference to the drawings. In the present embodiment, a multifunction peripheral is described as an example of a function providing apparatus, but the present invention is not limited to a multifunction peripheral. The present invention can be applied to various devices, devices, and the like that accept requests from external devices and realize the requests with various functions.

  FIG. 2 is a block diagram showing an example of a system including a multifunction machine according to the present invention. 2 has a printing function, a document storage function, a FAX function, and an OCR function. 2 is a function in which a printing function, a document storage function, and a FAX function are incorporated, and an OCR function is a function added by a recording medium such as an IC card that can be dynamically inserted and removed.

  The MFP 1 includes a Web service interface (WS I / F) 10, a Web service side framework (Web service side FW) 11, a function side FW 12, a changing unit 13, and various functions 14.

  The WS I / F 10 is a general-purpose interface and is unchanged. The client 2 as an example of the external device can use various functions of the multifunction device 1 as a Web service as long as the client 2 knows the WS I / F 10 that is a general-purpose interface. In the case of the MFP 1 shown in FIG. 2, the WS I / F 10 prepares at least an I / F (WSDL) that can acquire a service list, acquire necessary parameters, request a document operation, request an information reference, and request an information setting.

  The Web service side FW 11 has functions for registering and canceling Web services provided to the client 2. The Web service side FW 11 is a framework capable of registering the function of the MFP 1 as the function of the Web service. The Web service side FW 11 accepts the abstracted request from the client 1 via the WS I / F 10 and distributes the request to the function side FW 12 provided for each function.

  The function side FW 12 converts the request distributed by the Web service side FW 11 into an execution command, and controls the function 14 via the changing unit 13 by the execution command, thereby realizing the request from the client 1. The variable unit 13 is developed in a form that depends on the interface of the function 14.

  The Web service side FW 11 can register each function 14 of the multifunction device 1. Specifically, the Web service side FW 11 can register each function 14 of the multifunction device 1 via the variable unit 13 and the function side FW 12. In FIG. 2, the OCR function represents an example of a function 14 that is dynamically added after a dynamically detachable recording medium such as an IC card is inserted into a socket or the like. The Web service side FW 11 dynamically registers the dynamically added OCR function.

  The structure of the Web service side FW 11 can be represented by the class diagram of FIG. FIG. 3 is a class diagram showing the structure of the Web service side FW. 3 is an I / F class 20, a service user class 21, a document class 22, a document operation request form class 23, an information setting request form class 24, an information reference request form class 25, a reference result class 26, and a service. The structure includes a class 27, an acceptable request class 28, a service manager class 29, a service list class 30, a service monitoring class 31, and a service status notification class 32.

  FIG. 4 is a class diagram showing the structure for registration processing among the class diagrams showing the structure of the Web service side FW. In FIG. 4, portions 40 and 41 surrounded by a dotted line represent the structure for Web service registration processing. FIG. 5 is a class diagram showing the structure for request processing among the class diagrams showing the structure of the Web service side FW. In FIG. 5, a portion 42 surrounded by a dotted line represents a structure for request processing of a Web service.

  The structure of the function side FW 12 can be represented by the class diagram of FIG. FIG. 6 is a class diagram showing the structure of the function side FW. The class diagram of FIG. 6 has a structure including an I / F class 50, a request form class 51, an execution command class 52, an executable request list class 53, an executable request class 54, and a necessary parameter class 55.

The operations of the Web service side FW 11 represented by the class diagram of FIG. 3 and the function side FW 12 represented by the class diagram of FIG. 6 will be described below.
(When the MFP starts up)
FIG. 7 is an image diagram illustrating an example of the multifunction machine at the time of activation. When the MFP 1 is activated, the MFP 1 registers the incorporated functions 14 in the Web service FW 11 as Web service functions. In the MFP 1 of FIG. 7, the print function, document storage function, and FAX function are registered in the Web service side FW 11 as Web service functions.

  FIG. 8 is a sequence diagram showing the operation of the Web service side FW at the time of activation. In step S 1, the printing function requests the instance of the service monitoring class 31 to add. In step S 2, the service monitoring class 31 instance performs service registration with the service list class 30 instance.

  In step S3, an instance of the service list class 30 generates an instance of the printing service class 27. In step S4, an instance of the service list class 30 initializes an instance of the printing service class 27. In step S5, the instance of the printing service class 27 makes an acceptance request inquiry to the printing function. In step S 6, the printing function issues an acceptance request notification to the printing service class 27 instance.

  In step S 7, the instance of the printing service class 27 generates an instance of the normal printing acceptable request class 28 in response to the acceptable request notification. In step S8, an instance of the print service class 27 generates an instance of the aggregated print acceptance request class 28 in response to the acceptance request notification.

  In step S9, the FAX function requests the instance of the service monitoring class 31 to add. In step S 10, the service monitoring class 31 instance performs service registration with the service list class 30 instance.

  In step S11, an instance of the service list class 30 generates an instance of the FAX service class 27. In step S12, the service list class 30 instance is initialized with respect to the FAX service class 27 instance. In step S13, the FAX service class 27 instance makes an acceptance request inquiry to the FAX function. In step S14, the FAX function issues an acceptance request notification to the FAX service class 27 instance.

  In step S15, an instance of the FAX service class 27 generates an instance of the FAX transmission acceptance request class 28 in response to the acceptance request notification.

  In step S16, the document storage function requests the instance of the service monitoring class 31 to add. In step S 17, the service monitoring class 31 instance performs service registration with the service list class 30 instance.

  In step S18, the instance of the service list class 30 generates an instance of the service class 27 for document storage. In step S19, the service list class 30 instance is initialized with respect to the document storage service class 27 instance. In step S20, the instance of the document storage service class 27 makes an acceptance request inquiry to the document storage function. In step S 21, the document storage function issues an acceptance request notification to the instance of the document storage service class 27.

  In step S22, the instance of the document storage service class 27 generates an instance of the document search acceptance request class 28 in response to the acceptance request notification. In step S23, the instance of the document storage service class 27 generates an instance of the document deletion acceptance request class 28 in response to the acceptance request notification.

  By the processing shown in the sequence diagram of FIG. 8, the Web service side FW 11 generates the instance shown in FIG. FIG. 9 is an object diagram showing an instance generated on the Web service side FW when the MFP is activated.

  FIG. 10 is a sequence diagram showing the operation of the function side FW at the time of activation. FIG. 10 shows a sequence diagram of the function side FW 12 of the print function as an example, but the same applies to the document storage function and the FAX function.

  In step S31, an instance of the I / F class 50 is initialized to an instance of the acceptable request list class 53. In step S32, an instance of the acceptable request list class 53 generates an instance of the acceptable request class 54 for normal printing. In step S33, an instance of the acceptable request list class 53 is initialized to an instance of the acceptable printing request class 54 for normal printing.

  Proceeding to step S 34, the instance of the normal printing acceptance request class 54 generates an instance of the necessary parameter class 55 of the target document. In step S35, an instance of the normal printing acceptance request class 54 generates an instance of the required parameter class 55 for the number of sheets. Proceeding to step S 36, the instance of the normal printing acceptance request class 54 generates an instance of the execution command class 52.

  In step S37, the acceptable request list class 53 generates an instance of the acceptable request class 54 for aggregate printing. Proceeding to step S38, an instance of the acceptable request list class 53 is initialized to an instance of the acceptable request class 54 for aggregate printing.

  In step S39, an instance of the aggregate print acceptance request class 54 generates an instance of the necessary parameter class 55 of the target document. In step S40, an instance of the aggregate print acceptance request class 54 generates an instance of the required parameter class 55 for the number of sheets. Proceeding to step S41, an instance of the aggregate print acceptance request class 54 generates an instance of the aggregate type necessary parameter class 55. Proceeding to step S 42, the instance of the collective print acceptance request class 54 generates an instance of the execution command class 52.

By the processing shown in the sequence diagram of FIG. 10, the function side FW 12 generates the instance shown in FIG. FIG. 11 is an object diagram showing an instance generated by the function side FW when the MFP is activated.
(When adding multifunction device functions)
FIG. 12 is an image diagram illustrating an example of a multifunction machine when a function is added. When the MFP 1 is activated and a recording medium such as an IC card is inserted into a socket or the like and becomes readable, the function 14 recorded on the recording medium is dynamically transferred to the Web service side FW 11. sign up. In the MFP 1 of FIG. 12, the OCR function recorded on a recording medium such as an IC card is dynamically registered in the Web service FW 11.

  FIG. 13 is a sequence diagram illustrating the operation of the Web service side FW when a function is added. In step S51, the OCR function requests the instance of the service monitoring class 31 to add. In step S 52, the service monitoring class 31 instance performs service registration with the service list class 30 instance.

  In step S53, an instance of the service list class 30 generates an instance of the OCR service class 27. In step S54, an instance of the service list class 30 is initialized with respect to an instance of the OCR service class 27. In step S55, the OCR service class 27 instance makes an acceptance request inquiry to the OCR function. In step S56, the OCR function issues an acceptance request notification to the instance of the OCR service class 27.

  In step S57, an instance of the OCR service class 27 generates an instance of the layout analysis acceptable request class 28 in response to the acceptable request notification. In step S58, the instance of the OCR service class 27 generates an instance of the character recognition acceptance request class 28 in response to the acceptance request notification.

  Following the sequence diagram of FIG. 13, the function side FW 12 performs the processing shown in the sequence diagram of FIG. FIG. 14 is a sequence diagram showing the operation of the function side FW when a function is added. Proceeding to step S61, an instance of the I / F class 50 is requested from the Web service side FW 11 to obtain an acceptance request. In step S62, the instance of the I / F class 50 requests the acceptable request list class 53 to search for acceptable requests.

  In step S63, the instance of the acceptable request list class 53 notifies the acceptable request in the acceptable request list to the instance of the I / F class 50 by the acceptable request search result notification. In step S64, the instance of the I / F class 50 notifies the Web service side FW11 of an acquisition result for step S61.

  By the processing shown in the sequence diagrams of FIGS. 13 and 14, the Web service side FW 11 generates an instance shown in FIG. FIG. 15 is an object diagram showing an instance generated on the Web service side FW when adding a function of the MFP. FIG. 15 shows an object diagram after the addition of functions. In FIG. 15, a new instance is added to the portion 60 surrounded by a dotted line.

  Note that when a new function is added, the multifunction device 1 may broadcast a function registration notification indicating that the new function has been registered to each client 2. FIG. 16 is an image diagram of an example of a multifunction peripheral that broadcasts a function registration notification. When a new function is registered, the multifunction device 1 broadcasts a function registration notification to each client 2 by the process shown in the sequence diagram of FIG.

  FIG. 17 is a sequence diagram illustrating an example of a process for broadcasting a function registration notification to each client 2. Note that the sequence diagram of FIG. 17 is the same as the sequence diagram of FIG. The processing in steps S61 to S68 is the same as that in steps S51 to S58 in FIG.

In step S 69, the instance of the service monitoring class 31 sends an additional notification to the instance of the service status notification class 32. The instance of the service status notification class 32 broadcasts a function registration notification to each client 2. With the processing shown in the sequence diagram of FIG. 17, the multifunction device 1 can broadcast a function registration notification to each client 2.
(When the multifunction device is canceled)
FIG. 18 is an image diagram illustrating an example of the multifunction machine when the function is released. When a recording medium such as an IC card is pulled out from, for example, a socket or the like and becomes unreadable during activation, the multifunction device 1 dynamically changes the function 14 recorded on the recording medium to the Web service side FW11. Release from. In the multi function device 1 of FIG. 18, the OCR function recorded on the recording medium such as an IC card is dynamically released from the Web service side FW 11.

  FIG. 19 is a sequence diagram showing the operation of the Web service side FW when the function is released. In step S71, the OCR function requests the instance of the service monitoring class 31 to cancel. In step S 72, the service monitoring class 31 instance cancels the service list class 30 instance.

  In step S73, the instance of the service list class 30 discards the instance of the OCR service class 27. In step S74, the instance of the OCR service class 27 discards the instance of the layout analysis acceptance request class 28. In step S75, the instance of the OCR service class 27 discards the instance of the character recognition acceptance request class 28.

  By the process shown in the sequence diagram of FIG. 19, the Web service side FW 11 generates the instance shown in FIG. FIG. 20 is an object diagram showing an instance of the Web service side FW after the function release of the multifunction peripheral. FIG. 20 shows an object diagram after the function is released. In FIG. 20, the instance of the OCR service class 27, the instance of the layout analysis acceptable request class 28, and the instance of the character recognition acceptable request class 28 are discarded.

When the function is released, the multifunction device 1 may broadcast the released function to each client 2. The multifunction device 1 is not limited to when a recording medium such as an IC card is removed from a socket or the like and becomes unreadable, and the administrator can select and cancel the function 14.
(When registering other MFP functions)
FIG. 21 is an image diagram illustrating an example of a multifunction peripheral in which functions of other multifunction peripherals are registered. The multi-function device 1 can register the FAX function (not shown) of another multi-function device 1a connected via a network as its own function. Specifically, the multifunction machine 1 registers the FAX function of the other multifunction machine 1a in the web service side FW 11 as a web service function. Note that the method of registering the FAX function of the MFP 1a in the Web service FW 11 as a Web service function is basically the same as the method of registering each function incorporated in the own machine in the Web service FW 11 as a Web service function. Since this is the same, the description is omitted.

For example, when there is a FAX availability inquiry from the client 2, the MFP 1 transfers the FAX availability inquiry to the MFP 1a. When there is a response to the FAX availability inquiry from the multifunction device 1a, the multifunction device 1 transfers the response to the client 2.
(When using a multifunction device)
FIG. 22 is a sequence diagram illustrating an example of processing when the MFP is used from the client. First, the client 2 displays a screen as shown in FIG. 23 on the screen. FIG. 23 is an image diagram of an example of a screen for selecting a device. The operator who operates the client 2 selects the multifunction machine 1 that wants to use the Web service on the screen of FIG. In the screen of FIG. 23, the MFP 1 can be selected by IP address, and the MFP 1 can be searched and selected.

  In step S101, the client 2 requests the multifunction device 1 to confirm what kind of Web service the multifunction device 1 selected on the screen of FIG. Upon receiving the confirmation request in step S101, the multifunction device 1 notifies the client 2 of a list of Web services and acceptance requests. For example, the multifunction device 1 notifies a list of Web services and acceptable requests as shown in FIG. FIG. 24 is a data example of a list of Web services and acceptable requests.

  The data example of FIG. 24 includes the names of available Web services, requests for accepting each Web service, and types of requests that can be accepted. The client 2 displays a screen as shown in FIG. 25 according to the list of Web services and acceptance requests notified from the multifunction device 1. FIG. 25 is an image diagram of an example of a screen for selecting a Web service.

  An operator who operates the client 2 selects a Web service to be used and a request for acceptance on the screen of FIG. In the screen of FIG. 25, “document storage service” is selected as the Web service to be used, and “document search” is selected as the acceptable request.

  In step S103, the client 2 requests the MFP 1 to acquire parameters necessary for executing the Web service selected on the screen of FIG. Upon receiving the acquisition request in step S103, the multifunction device 1 proceeds to step S104, and notifies the client 2 of parameters necessary for executing the Web service and the acceptance request.

  For example, the multifunction device 1 notifies a list of parameters as shown in FIG. FIG. 26 is a data example of a parameter list. The data example of FIG. 26 represents an example of parameters necessary for the acceptance request “document search”. The data example of FIG. 26 includes the parameter name and parameter type necessary for executing the selected Web service and acceptance request. The client 2 displays a screen as shown in FIG. 27 according to the list of parameters notified from the multifunction device 1.

  FIG. 27 is an image diagram of an example of a screen for inputting parameters. The operator who operates the client 2 inputs parameters required for executing the Web service to be used and the acceptance request on the screen of FIG. In the screen of FIG. 27, a document name, a creator name, and a creation date and time are input as parameters necessary for executing the Web service “document storage service” and the acceptance request “document search” to be used.

  In step S105, the client 2 makes an execution request using the parameters input on the screen of FIG. Upon receiving the execution request in step S105, the multi-function device 1 executes the Web service and the acceptable request using the parameters included in the execution request. In step S106, the multi function device 1 notifies the client 2 of the result. The client 2 displays a screen as shown in FIG. 28 in response to the result notification notified from the multifunction device 1.

  FIG. 28 is an image diagram of an example of a screen for notifying the result. The operator who operates the client 2 can confirm the execution result of the used Web service and the acceptable request on the screen of FIG. In the screen of FIG. 28, a record including a document name, a creator name, and a creation date / time is displayed as an execution result of the Web service “document storage service” and the acceptable request “document search”.

  The sequence diagram shown in FIG. 22 will be described in more detail. The sequence diagram shown in FIG. 22 can be broadly divided into Web service confirmation processing in steps S101 and S102, parameter acquisition processing in steps S103 and S104, and execution request processing in steps S105 and S106.

  FIG. 29 is a sequence diagram illustrating an example of the Web service confirmation process. In step S111, an instance of the I / F class 20 is requested by the client 2 to acquire a service list. In step S112, the instance of the I / F class 20 transfers the service list acquisition from the client 2 to the instance of the service list class 30. Proceeding to steps S113 to S115, the instance of the service list class 30 confirms the acceptance request to the instance of the service class 27.

  Proceeding to step S116, the instance of the service list class 30 notifies the acquisition result for the service list acquisition of step S112. In step S 117, the instance of the I / F class 20 transfers the acquisition result notification from the instance of the service list class 30 to the client 2. With the processing shown in the sequence diagram of FIG. 29, the multi-function device 1 can confirm the names of available Web services, requests for accepting each Web service, and types of requests that can be accepted, and notify the client 2.

  FIG. 30 is a sequence diagram illustrating an example of parameter acquisition processing on the Web service side FW. FIG. 31 is a sequence diagram illustrating an example of the parameter acquisition process of the function side FW. The sequence diagram of FIG. 30 represents parameter acquisition processing in the case of the Web service “document storage service” and the acceptable request “document search”.

  In step S121, an instance of the I / F class 20 is requested to acquire necessary parameters from the client 2. In step S122, the instance of the I / F class 20 transfers necessary parameter acquisition from the client 2 to the instance of the service list class 30.

  In step S123, the service list class 30 instance requests the service class 27 instance to obtain necessary parameters. In step S124, the instance of the service class 27 requests the instance of the acceptable request class 28 to acquire necessary parameters.

  After the processing in step S124, the process proceeds to step S131 in FIG. 31, and the I / F class 50 is requested to acquire necessary parameters from the Web service side FW11. In step S 132, the instance of the I / F class 50 transfers the required parameter acquisition request from the Web service side FW 11 to the instance of the acceptable request list class 53.

  In step S 133, the instance of the acceptable request list class 53 transfers the necessary parameter acquisition request from the instance of the I / F class 50 to the instance of the acceptable document request class 54 for document search. In step S 134, the instance of the document search acceptance request class 54 acquires necessary parameters from the necessary parameter class 55 instance.

  Proceeding to step S135, the instance of the document search receivable request class 54 sends a necessary parameter acquisition result notification to the receivable request list class 53 instance. Proceeding to step S136, the instance of the acceptable request list class 53 notifies the necessary parameter acquisition result to the instance of the I / F class 50. Proceeding to step S137, the instance of the I / F class 50 notifies the Web service side FW11 of the necessary parameter acquisition result.

  After the processing of step S137, the process proceeds to step S125 of FIG. 30, and the instance of the acceptable request class 28 notifies the instance of the service class 27 of the necessary parameter acquisition result. In step S126, the instance of the service class 27 notifies the instance of the service list class 30 of the necessary parameter acquisition result.

  In step S127, the instance of the service list class 30 notifies the necessary parameter acquisition result to the instance of the I / F class 20. In step S128, the instance of the I / F class 20 transfers a necessary parameter acquisition result notification to the client 2.

  30 and 31, the multi-function device 1 can acquire the parameters necessary for executing the selected Web service and acceptance request and notify the client 2 of the parameters.

  FIG. 32 is a sequence diagram illustrating an example of execution request processing of the Web service side FW. FIG. 33 is a sequence diagram illustrating an example of the execution request process of the function side FW. In step S141, the client 2 makes an information reference request to an instance of the I / F class 20. In step S142, the instance of the I / F class 20 generates an instance of the service user class 21. In step S 143, the instance of the I / F class 20 makes an information reference request to the instance of the service user class 21.

  In step S144, the instance of the service user class 21 generates an instance of the information reference request form class 25. In step S145, the instance of the service user class 21 notifies the start of the request to the instance of the information reference request form class 25.

  In step S146, the information reference request class 25 instance requests the service class 27 instance to execute the service. In step S 147, the service class 27 instance requests a service request from the acceptable request class 28 instance.

  After the processing in step S147, the process proceeds to step S161 in FIG. 33, and the I / F class 50 is notified of the request execution from the Web service side FW11. In step S162, the instance of the I / F class 50 generates an instance of the request form class 51. In step S163, the instance of the I / F class 50 notifies the instance of the request form class 51 of the request execution.

  In step S164, the instance of the request form class 51 makes an execution command acquisition request to the instance of the acceptable request list class 53. Proceeding to step S165, the instance of the acceptable request list class 53 makes an execution command acquisition request to the acceptable request class 54.

  In step S166, the instance of the request form class 51 requests execution of the instance of the execution command class 52. When the requested execution ends, the instance of the execution command class 52 proceeds to step S167 and notifies the instance of the request form class 51 of completion.

  In step S168, the instance of the request form class 51 notifies the execution result to the instance of the I / F class 50. Proceeding to step S169, the instance of the I / F class 50 notifies the execution result to the Web service side FW11. Note that the instance of the I / F class 50 notifies the Web service FW 11 of the execution result, and then proceeds to step S170 to discard the instance of the request form class 51.

  After the processing of step S170, the process proceeds to step S148 of FIG. 32, and the instance of the acceptable request class 28 notifies the execution result to the instance of the service class 27. In step S149, the service class 27 instance generates an instance of the reference result class 26. In step S150, the instance of the service class 27 sends a reference result notification to the instance of the information reference request form class 25.

  In step S151, the instance of the information reference request form class 25 notifies the instance of the service user class 21 of the completion of the request. In step S152, the instance of the service user class 21 notifies the instance of the I / F class 20 of the completion of the request. In step S 153, the instance of the I / F class 20 transfers a request result notification to the client 2.

  32 and FIG. 33, the multifunction device 1 can execute the function 14 in response to an execution request from the client 2.

  The present invention is not limited to the specifically disclosed embodiments, and various modifications and changes can be made without departing from the scope of the claims. The general-purpose interface described in the claims corresponds to the WS I / F 10 and the Web service-side FW 11, the dedicated interface corresponds to the function-side FW 12, the interface unit corresponds to the WS I / F 10, and the general-purpose framework unit Corresponds to the Web service side FW11.

1 is a configuration diagram illustrating an example of a system including a multifunction peripheral (MFP) that provides a Web service. It is a block diagram showing an example of the system containing the multifunctional device by this invention. It is a class diagram showing the structure of Web service side FW. It is a class diagram showing the structure for registration processing among the class diagrams showing the structure of Web service side FW. It is a class diagram showing the structure for request processing among the class diagrams showing the structure of Web service side FW. It is a class diagram showing the structure of the function side FW. FIG. 3 is an image diagram illustrating an example of a multifunction machine at startup. It is a sequence diagram showing operation | movement of the Web service side FW at the time of starting. FIG. 6 is an object diagram showing an instance generated on the Web service side FW when the MFP is activated. It is a sequence diagram showing operation | movement of the function side FW at the time of starting. FIG. 6 is an object diagram illustrating an instance generated by a function side FW when a multifunction machine is activated. FIG. 3 is an image diagram illustrating an example of a multifunction machine when a function is added. It is a sequence diagram showing operation | movement of the Web service side FW at the time of a function addition. It is a sequence diagram showing operation | movement of the function side FW at the time of a function addition. FIG. 5 is an object diagram showing an instance generated on the Web service side FW when adding a function of a multifunction peripheral. FIG. 6 is an image diagram of an example of a multifunction peripheral that broadcasts a function registration notification. It is a sequence diagram of an example of a process for broadcasting a function registration notification to each client. FIG. 3 is an image diagram illustrating an example of a multifunction machine when a function is released. It is a sequence diagram showing operation | movement of the Web service side FW at the time of function cancellation | release. FIG. 10 is an object diagram illustrating an instance of a Web service side FW after the multifunction device is released. FIG. 10 is an image diagram illustrating an example of a multifunction peripheral in which functions of other multifunction peripherals are registered. FIG. 10 is a sequence diagram illustrating an example of processing when a multifunction device is used from a client. It is an image figure of an example of the screen which selects an apparatus. It is an example of data of a list of Web services and acceptable requests. It is an image figure of an example of the screen which selects a Web service. It is an example of data of a list of parameters. It is an image figure of an example of the screen which inputs a parameter. It is an image figure of an example of the screen which notifies a result. It is an example sequence diagram showing a Web service confirmation process. It is an example sequence diagram showing the parameter acquisition process of the Web service side FW. It is a sequence diagram of an example showing the parameter acquisition process of the function side FW. It is a sequence diagram of an example showing execution request processing of the Web service side FW. It is a sequence diagram of an example showing the execution request process of the function side FW.

Explanation of symbols

1 MFP 2 Client 10 Web Service Interface (WS I / F)
11 Web service side framework (Web service side FW)
12 Function side FW
13 Variable part 14 Function

Claims (21)

A function providing device capable of providing one or more functions to an external device,
A general-purpose interface that accepts a request from the external device for the one or more functions, and distributes the request for each function;
A function providing apparatus, comprising: a dedicated interface that is provided for each function, and that implements the request distributed by the function by the general-purpose interface by the function. The general-purpose interface includes an interface unit with the external device,
The function providing apparatus according to claim 1, further comprising: a general-purpose framework unit that distributes a request from the external device for the one or more functions received by the interface unit for each function.   The function providing apparatus according to claim 1, wherein the dedicated interface converts the request into an execution instruction corresponding to the function, and controls the function according to the execution instruction to realize the request. .   The function providing apparatus according to any one of claims 1 to 3, wherein the general-purpose interface is capable of registering the function added dynamically.   5. The function providing apparatus according to claim 4, wherein the dedicated interface is provided together with the function when the function is dynamically added.   6. The function providing apparatus according to claim 4, wherein the general-purpose interface transmits a function registration notification to the external device when the function is dynamically added.   7. The general-purpose interface can dynamically add the function recorded on the recording medium when a recording medium that can be dynamically inserted and removed is inserted. The function providing apparatus according to one item.   The function providing apparatus according to claim 1, wherein the general-purpose interface can release the function that has been dynamically deleted.   The function providing apparatus according to claim 8, wherein the general-purpose interface transmits a function release notification to the external device when the function is dynamically deleted.   10. The general-purpose interface is capable of dynamically releasing the function recorded on the recording medium when a recording medium that can be dynamically inserted and removed is extracted. Function providing device.   The function providing apparatus according to claim 1, wherein the general-purpose interface can register functions of other function providing apparatuses.   The function providing apparatus according to claim 1, wherein the general-purpose interface provides the function to the external device as a Web service.   The general-purpose interface acquires a list of functions that can be provided to the external device and parameters necessary for each function, and is capable of selecting one function from the list of functions and executing the selected function. 13. The function providing apparatus according to claim 1, wherein means for inputting necessary parameters is provided to the external device.   The function providing apparatus according to claim 13, wherein the general-purpose interface transmits a result notification for the request to the external device. A function providing method of a function providing apparatus capable of providing one or more functions to an external device,
Receiving a request from the external device for the one or more functions, and distributing the request for each function;
Realizing the request distributed for each function by the general-purpose interface with the function.   16. The function providing method according to claim 15, further comprising the step of registering the function added dynamically.   17. The function providing method according to claim 15, further comprising the step of releasing the function that has been dynamically deleted. A computer capable of providing one or more functions to an external device;
A general-purpose interface that accepts a request from the external device for the one or more functions, and distributes the request for each function;
A function providing program that is provided for each function and functions as a dedicated interface that realizes the request distributed by the function by the general-purpose interface. The general-purpose interface includes an interface unit with the external device,
19. The function providing program according to claim 18, further comprising a general-purpose framework unit that distributes requests from the external device for the one or more functions received by the interface unit for each function.   20. The function providing program according to claim 18 or 19, wherein the dedicated interface converts the request into an execution instruction corresponding to the function, and controls the function by the execution instruction to realize the request. .   A computer-readable recording medium on which the function providing program according to any one of claims 18 to 20 is recorded.

Images