JP2006020341A - Image forming apparatus including web service functions - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an image forming apparatus capable of offering Web services without installing a plurality of drivers for utilizing a plurality of image forming functions in a computer terminal that a user uses, and without depending on a machine type of the computer terminal or its operating system. <P>SOLUTION: In an image forming apparatus, a network communication control means controls communications by a process request from a device connected through a network and a process response to the device, and a Web service providing process part performs processing for controlling the image forming apparatus based on a message described in accordance with a predetermined message exchange protocol within the process request and generates the process response, in accordance with the predetermined message exchange protocol, showing a process result. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  In the present invention, it is only necessary to install standard Web service compatible software on a computer terminal used by a user without installing a plurality of driver software in order to use a plurality of image forming functions. It is an object of the present invention to provide an image forming apparatus that can provide a Web service without depending on the model or operating system of the computer terminal and can uniformly process processing requests from other devices.

  2. Description of the Related Art In recent years, image forming apparatuses in which functions of apparatuses such as a printer, a copy machine, a facsimile machine, and a scanner are housed in a single casing are generally known. Such a composite-type image forming apparatus is provided with a display unit, a printing unit, an imaging unit, and the like in one casing, and three types of applications corresponding to a printer, a copy unit, and a facsimile device, respectively. The apparatus is operated as a printer, a copy, a scanner, or a facsimile apparatus.

  However, in the conventional composite image forming apparatus, when functions such as a printer, a copy, a facsimile, and a scanner are used from a plurality of PCs (personal computers) connected via a network, each image forming function is assigned to each PC. It was necessary to install software such as drivers according to The software installed in the PC must be compatible with the model and operating system of the PC. In addition, similar requests may be requested between devices such as servers. However, since the required processing protocol and processing unit are different, it is necessary to satisfy both requirements at the time of mounting. Furthermore, in the conventional usage mode, there is a restriction that only processing determined by the driver can be performed.

  Therefore, an object of the present invention is to install a plurality of driver software for using a plurality of image forming functions in a computer terminal used by a user and without depending on a model or operating system of the computer terminal. Another object of the present invention is to provide an image forming apparatus that can be used as a programmable application component in which the functions of the image forming apparatus can be accessed using various Internet standard Web protocols via a network. Also provided is an image forming apparatus that realizes a distributed environment in which a Web service interacts with another Web service within the image forming apparatus or between the image forming apparatus and another apparatus.

  In order to solve the above problems, the present invention provides a network communication control means for performing communication control of a processing request from a device connected via a network and a processing response to the device, and a predetermined description format in the processing request. Web service means for processing internal information related to the image forming apparatus based on the described message and generating a processing response indicating the processing result is provided.

  Such an image forming apparatus can provide a Web service without using SOAP. The predetermined description format is a description format negotiated with the device, and is, for example, XML.

  The present invention may also be an image forming method for performing processing in the image processing apparatus.

  Furthermore, in order to solve the above-described problem, the present invention provides a processing request generation means for generating a processing request indicating the processing request according to a predetermined description format in response to a processing request by a user, and the image formation according to the predetermined description format. Output control means for controlling the output of the processing result indicated by the processing response to the processing request transmitted from the apparatus.

  Such a user terminal can receive a desired Web service from an apparatus that provides a plurality of Web services without depending on the model or operating system.

  According to the present invention, it is only necessary to install standard Web service compatible software without installing a plurality of driver software in order to use a plurality of image forming functions in a computer terminal used by a user. In addition, it is possible not only to make a request for processing to a multi-function peripheral having a plurality of image forming functions, but also to uniformly request processing from other devices, without depending on the model or operating system of the computer terminal. It becomes possible to process.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  An image forming apparatus according to an embodiment of the present invention (hereinafter referred to as a fusion machine) that fuses various image forming functions has a functional configuration as shown in FIG. FIG. 1 is a block diagram showing a functional configuration of a multi-function apparatus that fuses various image forming functions according to an embodiment of the present invention.

  In FIG. 1, the MFP 1200 includes a plotter 1201, a scanner 1202, a hardware resource 1203 such as a facsimile, and the like, a software group 1210 including a platform 1220 and an application 1230, and a MFP starter 1240. It has.

  The MFP starter 1240 is first executed when the MFP 1200 is turned on to start the platform 1220 and the application 1230.

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

  The control service 1250 is formed by a plurality of service modules. Specifically, an SCS (System Control Service) 1222, an ECS (Engine Control Service) 1224, an MCS (Memory Control Service) 1225, and an OCS (Operation panel control service) 1226, FCS (FAX Control Service) 1227, NCS (Network Control Service) 1228, and IMH (Imaging Memory Handler) 1229. Note that the platform 1220 has a function defined in advance. It has an application program interface that can receive a processing request from an application.

  The OS 1221 is an operating system such as UNIX (registered trademark), and executes the software of the platform 1220 and the application 1230 in parallel as processes. By using open source UNIX (registered trademark), the safety of the program can be secured, the network can be supported, and the source code can be easily obtained. Furthermore, OS and TCP / IP royalties are unnecessary, and outsourcing is easy.

  The SRM 1223, together with the SCS 1222, performs system control and resource management, and includes engine units such as scanners and plotters, memory, HDD files, host I / O (Centro I / F, network I / F, IEEE 1394 I / F, RS232CI / F, etc.) arbitration is performed according to a request from a higher layer using hardware resources, and execution control is performed.

  Specifically, the SRM 1223 determines whether the requested hardware resource is available (whether it is not used by another request). If it is available, the requested hardware resource is Tell the upper layer that it is available. Also, hardware resource usage scheduling may be performed in response to a request from an upper layer, and the requested contents (for example, paper conveyance and image forming operation by the printer engine, memory allocation, file generation, etc.) may be directly executed. .

  The SCS 1222 includes application management (function 1), operation unit control (function 2), system screen display (job list screen, counter display screen, etc.) (function 3), LED display (function 4), resource management (function 5), A plurality of functions such as interrupt application control (function 6) are performed. Specifically, in application management (function 1), application registration and processing for notifying other applications of the information are performed. In the operation unit control (function 2), exclusive control of the operation unit use right of the application is performed. In the system screen display (function 3), a warning screen corresponding to the state of the engine unit is displayed according to the request content from the application having the operation unit usage right. In LED display (function 4), display control of system LEDs such as warning LEDs and application keys is performed. Resource management (function 5) provides services for exclusive control of engine resources (scanners, staples, etc.) that must be excluded when an application (ECS) executes a job. In the interrupt application control (function 6), control and service for preferential operation of a specific application are performed.

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

  The MCS 1225 performs memory control. Specifically, the MCS 1225 acquires and releases an image memory, uses a hard disk device (HDD), compresses and decompresses image data, and the like.

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

  The FCS 1227 performs facsimile transmission / reception using PSTN / ISDN network 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 Program Interface).

  The NCS 1228 is a module group for providing a service that can be commonly used for applications that require network I / O. The NCS 1228 distributes data received by each protocol from the network side to each application, and distributes data from the application. Mediates when sending to the network side.

  In this embodiment, for example, NCS 1228 controls data communication with a network device connected via the Internet by HTTP (Hypertext Transfer Protocol Daemon) out of a plurality of protocols by HTTP (Hypertext Transfer Protocol), and makes an HTTP request. A processing unit corresponding to the Web service specified by the header may be activated by a function call, and the processing result by the Web service may be notified to the network device by an HTTP response. The Web service is provided according to a message described in XML (eXtensible Markup Language), for example.

  The IMH 1229 maps image data from a virtual memory area (user virtual space) to a physical memory. In response to the process activation, a system call is performed to map a virtual memory area for the process, or to release the mapped virtual memory area when the process ends.

  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 that is a scanner application, a Web service processing application 1215 that is a Web service application, and a process inspection application 1216 that is a process inspection application. Each of the applications 1211 to 1216 can execute an operation by using each process on the platform 1220. Therefore, a screen display control program that performs screen control, key operation control, job generation, and the like is the main component. Note that a new application can also be installed via the network via the network connected by the NCS 1228. Each application can be added or deleted for each application.

  The Web service processing application 1215 performs predetermined processing using a SOAP processing unit 70 that exchanges messages according to SOAP (Simple Object Access Protocol) and a control service 1250 via an API (Application Program Interface), and the processing result is obtained. A Web service function (WSF) 1400 provided as a Web service via a WS-API (Web Service Application Program Interface).

  As described above, the MFP 1200 centrally processes the processing that is commonly required for each application by the platform 1220.

  Next, the hardware configuration of the MFP 1200 will be described. FIG. 2 is a block diagram showing a hardware configuration of the MFP 1200 shown in FIG. As shown in FIG. 2, the MFP 1200 includes an operation panel 1310, a FAX control unit 1530, a USB (Universal Serial Bus) 1330, an IEEE 1394 1340, an engine unit 1350 (a plotter 1201, a scanner 1202, etc. are connected) and a controller 1300. The ASIC 1301 is connected via a PCI (Peripheral Component Interconnect) bus or the like.

  The controller 1300 connects the ASIC 1301 to the MEM-C 1302, HDD (Hard Disk Drive) 1303, and the like, and connects the ASIC 1301 and the CPU 1304 via the NB 1305 of the CPU chipset. Thus, the reason for connecting via the NB 1305 is that the interface of the CPU 1304 itself is not disclosed.

  Here, the ASIC 1301 and the NB 1305 are not connected via the PCI, but are connected via the AGP 1308. The reason for connecting through the AGP 1308 in this way is that the MFP 1200 executes and controls a plurality of processes forming the platform 1220 and the application 1230 shown in FIG. This is because performance decreases.

  The CPU 1304 performs overall control of the MFP 1200. Specifically, the SCS 1222, SRM 1223, ECS 1224, MCS 1225, OCS 1226, FCS 1227, and 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, and the process inspection application 1216 that form the application 1230 are activated and executed.

  The NB 1305 is a bridge for connecting the CPU 1304 to the MEM-P 1306, SB 1307, and ASIC 1301, and the MEM-P 1306 is a system memory used as a drawing memory for the multifunction peripheral. The SB 1307 is an NB 1305, ROM, and PCI device This is a bridge for connecting 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 applications having hardware elements for image processing.

  The HDD 1310 is a storage for accumulating image data, accumulating programs, accumulating font data, and accumulating forms. The operation panel 1310 accepts input operations from an operator and displays them for the operator. It is an operation unit.

  Accordingly, 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 / outputting image data to / from these storage units, the input / output 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 that has been proposed to speed up graphics processing, and makes the graphics accelerator card faster by directly accessing the system memory with high throughput.

  Hereinafter, a functional configuration example for providing the Web service by the MFP 1200 having the above-described functional configuration illustrated in FIG. 1 and the hardware configuration illustrated in FIG. 2 will be described. Here, the Web service means that the MFP 1200 performs a predetermined process in response to a service request by an HTTP request from a network device and provides the processing result to the network device as an HTTP response.

  First, a mechanism for providing a Web service from the MFP 1200 via a network will be described with reference to FIG. FIG. 3 is a diagram illustrating a configuration example of a network in which a Web service is provided. In FIG. 3, a detailed description of the functional configuration is omitted in order to explain an outline of a mechanism for providing a Web service.

  In FIG. 3, the MFP 1200 includes a Web server 1101 that controls communication with the network device 10, a SOAP processing unit 70 that exchanges Web service request and response messages with the network device 10 according to SOAP, and an interface. A Web service function (WSF) that starts a predetermined Web service function 1400 based on the definition 211 and receives a response from the Web service function 1400 and a Web service function (WSF) that is started by the Web server 1101 and provides a Web service by executing processing. ) 1400. The SOAP processing unit 70 may be included in the handler 1103 in a functional configuration described later.

  The interface definition 211 is WSDL (Web Service Description Language) indicating the service specification of a Web service registered in the UDDI server 100, and the handler 1103 realizes the Web service specification described in the WSDL. The multi-function apparatus 1200 can also be configured to include an automatic handler generator 210 that automatically generates a handler 1103 based on the interface definition 211.

  The UDDI server 100 has a function of managing WSDL indicating the service specifications of the Web service performed by the MFP 1200 from the MFP 1200 and providing the WSDL found in response to the search request. And a service broker 110 that mediates and a UDDI registry 112 that manages WSDL registered from the MFP 1200.

  A case where the service broker 110 provides a Web service desired by the network device 10 will be described. In response to a web service request from the network device 10, the service broker 110 searches the WSDL corresponding to the request from the UDDI registry 112 and is based on the web service specification described in the WSDL found in the UDDI registry 112. Then, according to SOAP, a request message indicating a request for the Web service is transmitted to the MFP 1200. When the Web server 1101 of the MFP 1200 receives a Web service request, the SOAP processing unit 70 processes the request message, and the handler 1103 activates a Web service function 1400 that performs processing according to the message. When the handler 1103 receives a response from the Web service function 1400, the response is processed as a response message according to SOAP by the SOAP processing unit 70, and is transmitted to the service broker 110 by the Web server 1101.

  When the service broker 110 receives a response message indicating a response of the Web service from the Web server 1101, the service broker 110 further transmits the response to the network device 10. As described above, the network broker 10 can request a Web service from the MFP 1200 without acquiring the WSDL by the service broker 110 that mediates between the network device 10 and the MFP 1200.

  Further, the network device 10 may acquire WSDL corresponding to a desired Web service from the UDDI server 100. In this case, the network device 10 causes the UDDI server 100 to search for the WSDL corresponding to the desired Web service, and acquires the WSDL that the UDDI server 100 has found in the UDDI registry. Then, the network device 10 transmits a request message indicating a request for the Web service to the multi-function apparatus 1200 according to SOAP, based on the specification of the Web service described by the acquired WSDL.

  When the Web server 1101 of the MFP 1200 receives a Web service request, the SOAP processing unit 70 and the handler 1103 perform the same process as described above, and then perform a process corresponding to the request message indicating the Web service request. A function (WSF) 1400 is activated. Then, the Web service function (WSF) 1400 that executed the process returns a response to the process to the handler 1103. When the Web server 1101 receives a response through the processing of the handler 1103 and the SOAP processing unit 70, the response message indicating the response of the Web service according to SOAP is transmitted to the network device 10. As described above, the network device 10 may request a desired Web service from the MFP 1200 according to SOAP based on the acquired WSDL.

  Further, in the MFP 1200, the Web service function (WSF) 1400 may have a configuration that can be described in WSDL. In other words, a Web service request based on WSDL can be processed, and a Web service request according to a predetermined procedure between the network device 10 and the MFP 1200 can be processed.

  In the configuration example of the network where the Web service is provided, a case where SOAP, which is a message exchange procedure, is used will be described. However, the message exchange procedure capable of providing the Web service is not limited to SOAP, and is integrated. It may be realized by a predetermined message exchange procedure negotiated between the device 1200 and the network 10.

  The MFP 1200 also has an automatic handler generation unit 210 that automatically generates a handler 1103 based on the interface definition 211, so that the Web service function (WSF) 1400 can execute the Web service registered in the UDDI server 100. It may be automatically generated based on WSDL describing the specification. In this case, the MFP 1200 itself can dynamically generate the handler 1103 as needed based on the newly registered WSDL. For example, it can be realized by setting the operating environment of the handler 1103 as an environment in which a Java (registered trademark) program can operate. Alternatively, the handler automatic generation unit 210 may be used in the development environment, and the generated object code of the handler 1103 may be mounted on the MFP 1200. In this case, the man-hour for developing the handler 1103 can be reduced.

  The automatic generation processing in the handler automatic generation unit 210 that generates the handler 1103 will be described with reference to FIGS. For example, it is assumed that the Web service function 1400 provides a Web service that performs file management processing and provides the result. In this case, the interface definition 211 for the Web service function 1400 is described, for example, as shown in FIGS. The request message and the response message are described in XML.

  4 and 5 are diagrams showing examples of description of interface definition by WSDL. In FIG. 4, a <type> tag 240 defining a data type defines a data type for describing a message, and a schema definition is set. In this example, only </ type> is described, indicating that it is only the basic type of the XML schema.

  In the definition information 242 defined by the <message> tag 241 (description <message name = "filemanagementInput">) that defines the message format, the description <part name = "fileId" type = "xs: unsignedInt" /> and the description By <part name = "operationCode" type = "xs: unsignedInt" />, the file management request input parameter (filemanagementInput) is composed of unsigned integer (unsignedInt) fileId and unsigned integer (unsignedInt) operationCode. Define that. Also, in the definition information 244 defined by the <message> tag 243 (description <message name = "filemanagementOnput">) that defines the message format, the description <part name = "requestId" type = "xs: unsignedInt" /> Defines that the output parameter (filemanagementOnput) of the file management request is composed of a requestId of an unsigned integer (unsignedInt).

  In the definition information 246 defined by the <portType> tag 245 (description <portType name = "netdocPortType">) that defines a set of operations, an input message and an output message for each operation are defined. For example, in the definition information 248 defined by the <operation> tag 247 (description <operation name = "filemanagement">), the description <input message = "tns: filemanagementInput" /> defines that the input message is filemanagementInput. Also, the description <output message = "tns: filemanagementOutput" /> defines that the output message is filemanagementOutput. In this case, only file management is defined.

  Defined by <binding> tag 249 (description <binding name = "netdocHttpBinding" type = "tns: netdocPortType">) that maps operations and messages defined by <portType> tag 245 to specific protocols and data formats In the definition information 250, for the port type defined by netdocPortType, a map to the operation and message protocol and data format is defined.

  In the definition information 50, an RPC with a SOAP HTTP binding is performed by a <sb: binding> tag 51 (description <sb: binding transport = "http://schemas.xmlsoap.org/soap/http" style = "rpc" />). Use of (Remote Procedure Call) is defined. The <operation> tag 52 (description <operation name = "filemanagement">) defines a SOAP message regarding file management (filemanagement) below.

First, the value of the SOAPAction header at the time of file management request is determined by the <sb: operation> tag 253 (description <sb: operation soapAction = "http://foo.bar.com/netdoc/filemanagement"/>)."
http://foo.bar.com/netdoc/filemanagement ”.

  Next, in the definition information 255 defined by the <input> tag 254, the description <sb: body encodingStyle = "http://schemas.xmlsoap.org/soap/encoding/" use = "literal" namespace = "http: //foo.bar.com/netdoc / "/> defines the input encoding format and describes <sb: body encodingStyle =" http://schemas.xmlsoap.org/soap/encoding/ "use =" literal "namespace =" http://foo.bar.com/netdoc/ "/> defines the output encoding format.

  Then, in the definition information 259 defined by the <service> tag 258 (description <service name = "netdoc">) that defines a collection of network endpoints, the <port> tag 260 (description <port name = "netdocPort" binding = "tns: netdocHttpBinding">) defines a netdocPort that is one of the network endpoints, and the description <sb: address location = "http://printer.foo.bar.com/netdoc" /> The address location of the end point of the network is defined. That is, it is defined that the binding of the service name “netdoc” is “netdocHttpBinding” and the service URL (Uniform Resource Locator) is “http://printer.foo.bar.com/netdoc”.

  As described above, the interface definition 211 defined in WSDL determines the data type, determines the operation, and determines the URL and SOAPAction header.

  The automatic generation processing performed by the handler automatic generation unit 210 based on the interface definition 211 will be described based on the flowchart shown in FIG. 6 with reference to FIGS. 7 and 8. FIG. 6 is a flowchart for explaining automatic generation processing for generating the source code of the handler. FIG. 7 is a diagram illustrating an example of the generated structure definition code. FIG. 8 is a diagram illustrating an example of a function that calls a Web service function.

  In FIG. 6, the handler automatic generation unit 210 generates a structure definition code (step S150). In this case, a code defining the structure “Netdoc_filemanagementInput” used as the argument 30 input to the file management function 301 that executes the file management process shown in FIG. 8 is generated. For example, a code such as “typedef struct _netdoc_filemanagementInput” is generated as a declaration statement, and subsequently, a code 261 shown in FIG. 7 is generated based on the definition information 242 defined by the <message> tag 241 in FIG. . That is, in the definition information 242 of FIG. 4, a code such as “unsigned int fileId;” is generated with name = “fileId” as the component “fileId” and type = “unsignedInt” as an unsigned integer. Also, a code such as “unsigned int operationCode;” is generated as a component “operationCode” by name = “operationCode” and an unsigned integer by type = “unsignedInt”. Then, a code for applying the structure definition “_nnetdoc_filemanagementInput” to the structure “Netdoc_filemanagementInput” is generated. A structure for input is defined by generating the code 261.

  Next, a code defining a structure “Netdoc_filemanagementOutput” used as an argument 31 output from the file management function 301 is generated. For example, a code such as “typedef struct_netdoc_filemanagementOutput” is generated as a declaration statement, and subsequently, a code 262 shown in FIG. 7 is generated based on the definition information 242 defined by the <message> tag 241 in FIG. . That is, in the definition information 244 of FIG. 4, a code such as “unsigned int requestId;” is generated with name = “requestId” as the component “requestId” and type = “unsignedInt” as an unsigned integer. Then, a code for applying the structure definition “_netdoc_filemanagementOutput” to the structure “Netdoc_filemanagementOutput” is generated. An output structure is defined by generating the code 262.

  The handler automatic generation unit 210 generates a function declaration for calling the file management function 301 (step S151). In this case, in order to call the file management function 301 based on the definition information 248 defined by the <operation> tag 247 in FIG. 4, for example, “SoapFault netdoc_filemanagement (Netdoc_filemanagementInput * in, Netdoc_filemanagementOutput * out);” The correct code.

  The handler automatic generation unit 210 generates a code for converting a request message processed by the SOAP processing unit 70 into a DOM (Document Object Model) tree indicating a relation between tags when the request message is described in XML (step S153). ), A code for calling the Web service function 1400 is generated (step S154). That is, the handler automatic generation unit 210 generates the code of the file management function 301 using the function declaration code generated in step S151.

  Subsequently, the handler automatic generation unit 210 generates a code for determining whether or not the processing result from the Web service function 1400 is an error, and a code for performing a process in the case of an error (step S155). Furthermore, the handler automatic generation unit 210 generates a code for converting the DOM tree into a response message (step S156).

  As described above, the handler automatic generation unit 210 can generate the handler 1103 based on the interface definition 211. With such a configuration, the source code for realizing the handler 1103 can be automatically generated, so that it is not necessary to create a simple and repetitive DOM programming. Therefore, high-quality software development can be performed in a short period of time. In addition, since the Web service function 1400 can be in a format that can be handled easily in a programming language for both input and output, the developer does not need deep knowledge about XML or HTTP. Therefore, the cost required for developer education can be reduced. Furthermore, even when a protocol is added or changed, the source code of the handler 1103 can be automatically generated simply by changing the interface definition 211. Therefore, high maintainability can be realized.

  Hereinafter, an example of the functional configuration of the MFP 1200 capable of providing a Web service will be described with the MFP 1200 and the network device 10.

  First, the MFP 1200 that provides a Web service to a network device connected via a network based on a message described in XML without using SOAP, which is a message exchange procedure, will be described. FIG. 9 is a diagram illustrating a first functional configuration example of a multi-function peripheral that provides a Web service. In FIG. 9, only the main functional configuration is shown in the functional configuration of the multi-functional apparatus 1200 shown in FIG. 1, and other functional configurations are omitted.

  In FIG. 9, the MFP 1200 performs communication control according to HTTP, distributes the processing to the internal Web service providing processing unit, and file management Web service providing processing as a plurality of Web service providing processing units. Unit 40 and other Web service provision processing unit 49, handler 1103 for distributing processing, scanner 1202, HDD 1303, plotter 1201, operation panel 1310, FAX control unit 1530, and the like. The Web server 500 includes httpd 2 that performs communication control according to HTTP, and a distributor 30 that distributes processing to a Web service providing processing unit corresponding to the HTTP request.

  The file management Web service provision processing unit 40 includes, for example, a file management execution unit 400 that controls file management such as storage of documents in the HDD 1303 as a Web service function 1400 (FIG. 3) that executes a Web service.

  As shown in FIG. 3, the handler 1103 is a processing unit generated by the automatic handler generation unit 210 based on WSDL describing the Web service functions of the Web service provision processing units 40 and 49 provided by the interface regular 211. The XML processing unit 50 shared by the plurality of Web service providing processing units 40 and 49, and the file management execution unit 400 based on the processing message indicating the processing content of the Web service analyzed by the XML processing unit 50. The dispatcher (Dispatcher) 60 which distributes is provided.

  In the MFP 1200, for convenience of explanation, only the file management web service provision processing unit 40 and the other web service provision processing unit 49 are shown as a plurality of web service provision processing units, but more web service provision processing units are shown. It can also be set as the structure which has these. In this case, the handler 1103 includes a plurality of dispatchers 60 that distribute the processing to the execution units of the plurality of Web service providing processing units. Further, the XML processing unit 50 is shared in the handler 1103 by the plurality of Web service providing processing units.

  The network device 10 connected to the MFP 1200 via the network 15 controls input data from an input device such as a keyboard or a mouse, and also controls output data to be displayed on the monitor 9. 11, the XML processing unit 13 that processes the processing contents of the Web service for the MFP 1200 and the processing results of the Web service from the MFP 1200 by XML, and the request / response processing that analyzes the generation and response of a request according to HTTP Part 14. Here, the HTTP request indicates that a Web service is requested by data communication in accordance with HTTP, and the HTTP response indicates a response that notifies the processing result of the Web service. Further, in this first functional configuration example, the body part of the HTTP request and the HTTP response is described in XML.

  A user who uses such a network device 10 requests the MFP 1200 from a screen for requesting the MFP 1200 for a desired Web service (step S1). In response to the web service request from the user, the input / output control unit 11 notifies the request / response processing unit 14 of the request data (step S2). The request / response processing unit 14 generates an HTTP request based on the request data from the input / output control unit 11 (step S3). When the XML processing unit 13 describes the processing content in the body of the HTTP request by XML, the request / response processing unit 14 The request is transmitted to the MFP 1200 via the network 15 (step S4).

  When the Web server 500 of the MFP 1200 receives the HTTP request by httpd2, the distributor 30 distributes the received HTTP request to the Web service provision processing unit specified by the header part of the HTTP request (step S5). For example, when the file management Web service provision processing unit 40 is specified in the header part of the HTTP request, the file management Web service provision processing unit 40 is function-called by the distributor 30.

  In the file management Web service provision processing unit 40, the handler 1103 acquires the processing content from the body part described in the XML of the HTTP request by the XML processing unit 50 (step S6), and notifies the dispatcher 60 of the acquired processing content. (Step S7). The dispatcher 60 distributes the processing by the Web service to the file management execution unit 400 according to the notified processing content (step S8). The file management execution unit 400 executes processing on the HDD 1303 according to the processing content, and acquires the processing result (step S9). For example, processing such as addition, update, or deletion of a document designated as processing content is executed. The file management execution unit 400 notifies the processing result to the XML processing unit 50 (step S10). The XML processing unit 50 generates a body part of an HTTP response in which the notified processing result is described in XML (step S11). Then, the Web server 500 that has received the notification from the file management Web service provision processing unit 40 transmits an HTTP response having the processing result described in XML as a body part to the network device 10 via httpd2.

  When the network device 10 receives the HTTP response, the XML processing unit 13 analyzes the body part of the HTTP response and acquires the processing result (step S13), and the request / response processing unit 14 acquires the acquired processing. The result is passed to the input / output control unit 11 as output data to be displayed on the monitor 9 (step S14). Then, the input / output control unit 11 performs control so that the received output data is displayed on the monitor 9 (step S15).

  In the above first functional configuration example, the network device 10 requests the Web service from the remote location to the MFP 1200 by describing the processing contents in the body part of the HTTP request according to the XML description format decided in advance. It can be performed. Further, the MFP 1200 can provide a Web service to the network device 10 at a remote location by describing the processing result in the body part of the HTTP response according to the XML description format determined in advance. It becomes. The multi-functional apparatus 1200 can also provide a Web service to a plurality of network devices 10 via the network 15.

  Next, a functional configuration example of the MFP 1200 that can provide a Web service according to SOAP will be described. Hereinafter, each exemplified Web service provision processing unit is a function that executes a process (service) described based on a service specification described in WSDL.

  Hereinafter, a functional configuration example of the MFP 1200 that provides a Web service using SOAP will be described. FIG. 10 is a diagram illustrating a second functional configuration example of a multifunction peripheral that provides a Web service. 10, the same components as those in FIG. 9 are denoted by the same reference numerals, and the description thereof is omitted. Since the processing flow is the same, the description thereof is omitted. In the second functional configuration example shown in FIG. 10, the MFP 1200 has a plurality of handlers 1103 corresponding to a plurality of Web service providing processing units such as the file management Web service providing processing unit 40 and the other Web service providing processing unit 49. The SOAP processing unit 70 is shared by the Web service providing processing unit, and the XML processing unit 50 and the dispatcher 60 are included in the SOAP processing unit 70, which is different from the first functional configuration example. Yes. In addition, the network device 10 includes a SOAP processing unit 12 for exchanging messages with the MFP 1200 according to SOAP, and the SOAP processing unit 12 includes an XML processing unit 13 that processes a message described in XML. The configuration is different from the first functional configuration example.

  In such a multi-function apparatus 1200, the SOAP processing unit 70 analyzes the header part of the HTTP request, distributes the process by the dispatcher 60, and the XML processing unit 50 processes the processing content from the message described in XML of the body part of the HTTP request. To get. For example, the dispatcher 60 distributes processing by the Web service to the file management execution unit 400. After that, the SOAP processing unit 70 that has received the processing result from the file management execution unit 400 that executed the processing describes the processing result in XML in the body part of the HTTP request by the XML processing unit 50, and the HTTP request in accordance with SOAP. Is transmitted to the network device 10.

  In the second functional configuration example, the dispatcher 60 may be included in the XML processing unit 50.

  As described above, in the MFP 1200 and the network device 10 to which SOAP is applied, the network device 10 can realize RPC (Remote Procedure Call) using XML for the MFP 1200.

  An HTTP request and an HTTP response for exchanging messages between the MFP 1200 and the network device 10 according to SOAP will be described with reference to FIG. FIG. 11 is a diagram illustrating an example of an HTTP request and an HTTP response. FIG. 11A is a diagram illustrating an example of an HTTP request. In the HTTP request shown in FIG. 11A, a URI (Uniform Resource Indicator) 16 indicates a URI to which an HTTP request is transmitted by the POST method, and is “netdoc”, for example. Further, a URI indicating the purpose of the request is shown in SOAPAction 17, and “file management” is designated by “http://foo.bar.com/netdoc/filemanagement”, for example.

  The distributor 30 of httpd2 of the MFP 1200 in FIG. 10 calls the file management Web service provision processing unit 40 as a function by “filemanagement” specified by SOAPAction17. The file management Web service provision processing unit 40 processes the HTTP request according to the SOAP by the SOAP processing unit 70. In the SOAP processing unit 70, the dispatcher 60 distributes the process to the file management execution unit 400 according to “filemanagement” specified by the SOAPAction 17. Further, the XML processing unit 50 analyzes the message 18 described in XML in the body of the SOAP envelope (from <SOAP-ENV: Body> to </ SOAP-ENV: Body>). For example, the message 18 is shown from <ns: filemanagement> to </ ns: filemanagement>. “Filemanagement” indicates a command. The processing content requested by the message 18 performs processing of the file ID “123” specified by <fileId> to </ fileId> and the operation code “3” specified by <operationCode> to </ operationCode>. It is shown that. For example, operation code “3” requests file deletion, operation code “1” requests file addition, and operation code “2” requests file editing.

  In this case, the file management execution unit 400 to which the process is distributed by the dispatcher 60 deletes the document with the fill ID “123” from the HDD 1303 according to the processing content analyzed by the XML processing unit 50.

  In the above example, the file management method is specified by the setting of <operationCode> with one command “filemanagement”. However, the file management process is subdivided into, for example, a file addition Web service and a file editing Web service. A plurality of Web services such as a file deletion Web service may be included in the Web service processing application 1215 as the Web service function 1400. In this case, for example, the command corresponding to each Web service, such as “fileadd”, “fileedit”, and “filedelete”, is set in the XML message 18 so that the operation code by <operationCode> is changed. It becomes unnecessary.

  FIG. 11B is a diagram illustrating an example of an HTTP response. The HTTP response shown in FIG. 11B is created by the SOAP processing unit 70 of the file management Web service provision processing unit 40 based on the processing result of the file management Web service provision processing unit 40. In the HTTP response shown in FIG. 11B, the SOAP processing unit 70 sets “200” as the status code 20 and “OK” as the explanatory phrase 21 based on the processing result of the file management Web service provision processing unit 40. To do. Further, the XML processing unit 50 generates a message 22 described in XML in the body of the SOAP envelope (from <SOAP-ENV: Body> to </ SOAP-ENV: Body>). The response of the command “filemanagement” is indicated by <ns: filemanagementResponse> to </ ns: filemanagementResponse>. For example, the request ID “10” is set by <requestId> and </ requestId>. The network device 10 that has received this HTTP response processes the message 22 described in XML by the XML processing unit 13 to confirm that the processing has been performed normally.

  Next, a functional configuration of the MFP 1200 in which the SOAP processing unit 70 and the XML processing unit 50 are individually shared by a plurality of Web service providing processing units will be described. FIG. 12 is a diagram illustrating a third functional configuration example of a multi-function peripheral that provides a Web service. In FIG. 12, the same components as those in FIG. 10 are denoted by the same reference numerals, and the description thereof is omitted. Since the processing flow is the same, the description thereof is omitted. In the third functional configuration example shown in FIG. 12, the multi-function apparatus 1200 includes a plurality of file management web service provision processing units 40 and other web service provision processing units 49, as in the second functional configuration example shown in FIG. The handler 1103 corresponding to the Web service providing processing unit includes a SOAP processing unit 70 shared by a plurality of Web service providing processing units. The XML processing unit 50 includes a plurality of Web services independent of the SOAP processing unit 70. The point shared by the service providing processing unit is different from the second functional configuration example. In the third functional configuration example, the dispatcher 60 is included in the SOAP processing unit 70 as in the second functional configuration example, but the configuration may be included in the XML processing unit 50. The network device 10 has the same functional configuration as the network device 10 shown in FIG.

  As described above, in the MFP 1200 and the network device 10 to which SOAP is applied, the network device 10 can realize RPC (Remote Procedure Call) using XML for the MFP 1200.

  The multi-function apparatus 1200 can be configured to have a plurality of Web service provision processing units corresponding to each of a plurality of functions. FIG. 13 is a diagram illustrating a fourth functional configuration example of a multi-function peripheral that provides a Web service. In FIG. 13, the same components as those in FIG. 10 are denoted by the same reference numerals, and the description thereof is omitted. In the third functional configuration example shown in FIG. 12, the MFP 1200 provides a file management Web service provision processing unit 40 that provides a Web service for managing documents stored in the HDD 1303 and a Web service that controls the scanner 1202. A scanner control web service provision processing unit 41 that performs a print web service provision processing unit that provides a web service that controls the plotter 1201, and an operation unit control web service provision processing unit 43 that provides a web service that controls the operation panel 1310. And have. The file management Web service provision processing unit 40 includes a file management execution unit 400 that executes processing for the HDD 1303, and the scanner control Web service provision processing unit 41 performs scanner processing for the scanner 1202. 401, the print Web service provision processing unit 42 has a plotter control execution unit 402 that executes processing for the plotter 1201, and the operation unit control Web service provision processing unit 43 executes processing for the operation panel 1310. An operation unit control execution unit 403 is provided.

  Further, similarly to the third functional configuration example, in the handler 1103, the XML processing unit 50 and the SOAP processing unit 70 are independently shared by the plurality of Web service providing processing units 40 to 43. Further, the dispatchers 60 to 63 are configured to correspond to the plurality of Web service provision processing units 40 to 43, respectively.

  The network device 10 has the same functional configuration as that of the network device 10 shown in FIG.

  In such a fourth functional configuration example, in the MFP 1200 and the network device 10 to which SOAP is applied, the network device 10 realizes RPC (Remote Procedure Call) using XML for the MFP 1200. Can do. Further, the network device 10 can receive provision of the desired Web service by transmitting an HTTP request corresponding to the desired Web service from the multi-functional apparatus 1200 having the plurality of Web service providing processing units 40 to 43. . Accordingly, the network device 10 can use these functions as a Web service without installing a plurality of drivers for using the functions of the image forming apparatus such as the scanner 1202, the HDD 1303, the plotter 1201, and the operation panel 1310. it can.

  Next, an example of a functional configuration of the MFP 1200 that executes a combination of a plurality of Web service provision processing units in response to a single HTTP request of the network device 10 will be described. FIG. 14 is a diagram illustrating a fifth functional configuration example of a multi-function peripheral that provides a Web service. 14, the same components as those in FIGS. 12 and 13 are denoted by the same reference numerals, and the description thereof is omitted. The fifth functional configuration example shown in FIG. 14 is different from the third functional configuration example shown in FIG. 12 in that the MFP 1200 includes a file management Web service provision processing unit 40 and a print Web service provision processing unit 42. And a composite web service provision processing unit 90 that controls the file management web service provision processing unit 40 and the print web service provision processing unit 42 in combination. The file management web service provision processing unit 40 and the print web service provision The processing unit 42, the composite web service provision processing unit 90, and the other web service provision processing unit 49 are configured to share the XML processing unit 50 and the SOAP processing unit 70 in the handler 1103. Furthermore, the SOAP processing unit 70 includes dispatchers 60, 62, 68, 69, and the like that distribute the processing to the execution units 400, 412, 80, and the like.

  The file management execution unit 400 of the file management Web service provision processing unit 40 as the Web service function 1400 (FIG. 3) executes the file management processing to the HDD 1303 based on the processing distributed by the dispatcher 60 and the composite Web. A file management process designated by the service execution unit 80 is executed. Further, the file print execution unit 412 of the print Web service provision processing unit 42 as the Web service function 1400 executes file printing based on the processing distributed by the dispatcher 62 and is designated by the composite Web service execution unit 80. Prints the file that is created.

  The composite web service provision processing unit 90 includes a composite web service execution unit 80 that executes the file management web service provision processing unit 40 and the print web service provision processing unit 42 in combination.

  The network device 10 has the same functional configuration as that of the network device 10 shown in FIG.

  In FIG. 14, when the MFP 1200 receives, for example, an HTTP request that requests storage printing for storing and printing a document in the HDD 1303 from the network device 10, the composite Web service provision processing unit 90 displays the composite Web service execution unit 80. The file management execution unit 400 stores the document in the HDD 1303, and then performs a series of processes for causing the file print execution unit 412 to execute the printing process by specifying the file ID of the stored document.

  As described above, the composite Web service execution unit 80 causes the file management execution unit 400 and the file print execution unit 412 to perform processing in succession, so that the network device 10 connected via the network 15 is connected once. It is possible to receive a series of web services provided by two or more web service provision processing units simply by transmitting the HTTP request. Further, since the composite Web service execution unit 80 itself does not need to have an entity as the Web service function 1400 that performs file management processing and printing processing, development efficiency can be greatly reduced. Furthermore, the network device 10 can also request the provision of a web service only by the file management web service provision processing unit 40 and the provision of the web service only by the print web service provision processing unit 42.

  As described above, the MFP 1200 can provide a wide range of Web services by combining a plurality of execution units that form an image and perform processing for actually providing a Web service, and combinations thereof.

  In the above first to fifth functional configuration examples, the configuration has been described in which the MFP 1200 provides a Web service to one network device 10, but in the case of being connected to a plurality of network devices 10 via the network 15. It is possible to provide a desired Web service to each network device 10.

  Further, the processing content to the MFP 1200 can be described in XML, and the message exchange procedure is set to SOAP, so that the network device 10 can be connected to the Web without depending on the model or operating system of the network device 10. It is possible to receive service provision.

  Further, the user can use various Internet standard web protocols via the network without installing a plurality of driver software for using a plurality of image forming functions in a computer terminal to be used. It can be used as a programmable application component that can be accessed and used.

  Further, it is possible to realize a distributed environment in which a Web service communicates with another Web service in the MFP 1200 or between the MFP 1200 and another device.

  According to the above embodiment, the MFP 1200 that forms an image processes various internal information related to image processing such as operation panel control, print processing, file management, scanner control, and the like, and provides the processing result to the request source. Service can be realized. The internal information here refers to various types of image processing, such as image information, status information about the image information, and information such as control parameters for changing the settings of the device main body or changing the network IP, and the multifunction device 1200. Various types of information are shown, and it is possible to perform predetermined processing on the internal information and provide the processing result as a Web service according to the above embodiment.

  In the above embodiment, httpd2 corresponds to the network communication control means, and each of the web service provision processing units 40 to 43, 49 and 90 corresponds to the web service provision processing means, the file management execution unit 400, the scanner. Each of the control execution unit 401, the plotter control execution unit 402, and the operation unit control execution unit 403 corresponds to a Web service execution unit. The SOAP processing unit 70 corresponds to a protocol processing unit, and the XML processing unit 50 corresponds to a message processing unit.

1 is a block diagram showing a functional configuration of a multi-functional apparatus that fuses various image forming functions according to an embodiment of the present invention. FIG. FIG. 2 is a block diagram illustrating a hardware configuration of the MFP 1200 illustrated in FIG. 1. It is a figure which shows the structural example of the network by which a Web service is provided. It is a figure which shows the example of a description of the interface definition by WSDL. It is a figure which shows the example of a description of the interface definition by WSDL. It is a flowchart for demonstrating the automatic generation process which produces | generates the source code of a handler. It is a figure which shows the example of the code | symbol of the produced | generated structure definition. It is a figure which shows the example of the function which calls a web service function. It is a figure which shows the example of 1st function structure of the compound machine which provides Web service. It is a figure which shows the 2nd function structural example of the compound machine which provides Web service. It is a figure which shows the example of an HTTP request and an HTTP response. It is a figure which shows the 3rd function structural example of the compound machine which provides a Web service. It is a figure which shows the 4th function structural example of the compound machine which provides Web service. It is a figure which shows the 5th function structural example of the compound machine which provides Web service.

Explanation of symbols

2 httpd (Hypertext Transfer Protocol Daemon)
30 Distributor 40-49 Web service provision processing unit 50 XML processing unit, 60 dispatcher 70 SOAP processing unit 1200 MFP,
1201 Plotter 1202 Scanner 1210 Software group 1230 Application, 1220 Platform 1221 OS, 1222 SCS
1223 SRM, 1224 ECS
1225 MCS, 1226 OCS
1227 FCS, 1228 NCS
1229 IMH, 1240 Fusion machine starter 1300 Controller, 1301 ASIC
1302 MEM-C, 1303 HDD
1304 CPU, 1305 NB
1306 MEM-P, 1307 SB
1308 AGP, 1310 Operation Panel 1330 USB, 1340 IEEE 1394
1350 Engine part, 1500 Network I / F part 1530 FAX control unit

Claims (6)

Network communication control means for performing communication control of a processing request from a device connected via a network and a processing response to the device;
Web service means for performing processing for controlling the image forming apparatus based on a message described according to a predetermined description format in the processing request, and generating a processing response according to the predetermined description format indicating the processing result; An image forming apparatus comprising: The web service provision processing means includes:
2. The image forming apparatus according to claim 1, further comprising handler means for converting the message into a data structure related to processing for controlling the image forming apparatus. A plurality of Web service provision processing means;
The handler means is:
Message processing means which can be shared by the plurality of Web service providing processing means and which processes the message in accordance with the predetermined description format;
3. The image forming apparatus according to claim 2, further comprising a distribution unit that distributes the process to a Web service execution unit corresponding to specific information for specifying the Web service indicated by the message processed by the message processing unit. . A distribution unit that analyzes a request type of the processing request received by the network communication control unit and distributes the processing request to one of the plurality of Web service providing processing units based on the analysis result;
Each of the plurality of Web service providing processing means analyzes specific information specifying the Web service in the processing request, and executes a Web service characterized by executing the Web service characterized by the specific information based on the analysis result 4. The image forming apparatus according to claim 3, further comprising a distribution unit that distributes the processing to the unit. An application having the Web service provision processing means;
A control service for managing hardware resources used in the image forming process and controlling use of the hardware resources in response to a use request from the application;
The image forming apparatus according to claim 1, further comprising an operating system that controls the application and the control service. A user terminal communicating with the image forming apparatus according to claim 1,
Processing request generation means for generating a processing request indicating the processing request according to a predetermined description format in response to a processing request by a user;
A user terminal comprising: output control means for controlling output of a processing result indicated by a processing response to the processing request transmitted from an apparatus that provides a Web service according to a predetermined description format.

Images