BACKGROUND OF THE INVENTION 1. Field of the Invention
The present invention generally relates to output information providing methods, output information providing systems, document outputting methods, and document outputting systems for editing and outputting a document.
2. Description of the Related Art
Conventionally, a document can be printed out by using a printer or an MFP (Multi-Function Printer) connected to a network through a personal computer (hereinafter, called PC). Recently, in addition to the above functions, various services have been developed and provided as Web services. In this case, various services as the Web services are realized by an application loaded in the PC serving as a client with respect to the Web services.
As described above, conventionally, the application loaded in the client PC serves as the client with respect to each of the Web services. Thus, it is possible to architect the application suitable for various requirements. However, the application is required to send and receive information to/from each of the Web services, which is subject to inquire what kind of edit can be performed or to notify edit contents. That is, the client PC is required to communicate with a plurality of the Web services.
SUMMARY OF THE INVENTION It is a general object of the present invention to provide output information providing methods, output information providing systems, document outputting methods, and document outputting systems, in which the above-mentioned problems are eliminated.
A more specific object of the present invention is to provide an output information providing method, an output information providing system, a document outputting method, and a document outputting system, in that client PC can effectively output a document and send and receive information concerning an edit to/from a Web service.
The above objects of the present invention are achieved by an output information providing method for providing an edit property indicating edit contents executable for a document and an output property indicating an output method executable when the document is output, the output information providing method including: receiving an output condition property candidate obtain request for obtaining an output condition property candidate; and providing the output condition property candidate to a request originator sending the output condition property candidate obtain request.
The above objects of the present invention are achieved by an output information providing system for providing an output condition property candidate including an edit property indicating edit contents executable with respect to a document and an output property indicating an output method executable when the document is output, to a client requesting editing or outputting the document, the output information providing system including: an output condition property candidate obtain request receiving part receiving an output condition property candidate obtain request for obtaining an output condition property candidate from the client; and an output condition property candidate providing part providing the output condition property candidate to the client.
The above objects of the present invention are achieved by a document outputting method for editing and outputting a document, including: receiving an output condition property candidate obtain request including an output property indicating an outputting method executable when the document is output; providing the output condition property candidate to a request originator sending the output condition property candidate; receiving a document output request including an output condition being selected from the output condition property; editing the document based on the output condition; and outputting the document being edited based on the output condition.
The above objects of the present invention are achieved by a document outputting system for providing an edit property indicating edit contents executable for a document and an output property indicating an outputting method executable when the document is output to a client requesting outputting the document, the document outputting system including: an output property candidate obtain request receiving part receiving an output property candidate obtain request for obtaining an output condition property candidate from the client; an output condition property candidate providing part providing the output condition property candidate to the client; a document output request receiving part receiving a document output request including an output condition being selected from the output condition property candidate; an editing service part editing the document based on the output condition; and an outputting service part outputting the document being edited based on the output condition.
BRIEF DESCRIPTION OF THE DRAWINGS In the following, embodiments of the present invention will be described with reference to the accompanying drawings.
FIG. 1 is a block diagram showing a configuration of adocument processing system100 according to the present invention;
FIG. 2 is a block diagram showing a functional configuration of a multi-functional apparatus according to the present invention;
FIG. 3 is a block diagram showing a hardware configuration of the multi-functional apparatus according to the present invention;
FIG. 4 is a block diagram showing a hardware configuration of a client PC according to the present invention;
FIG. 5 is a block diagram showing a system configuration according to a first embodiment of the present invention;
FIG. 6 is a block diagram showing a functional configuration in the system configuration according to the first embodiment of the present invention;
FIG. 7 is a diagram showing a sequence flow according to the first embodiment of the present invention;
FIG. 8 is a diagram showing an example of a print property according to the first embodiment of the present invention;
FIG. 9 is a diagram showing an example of an edit property according to the first embodiment of the present invention;
FIG. 10 is a flowchart for explaining a process for generating a print condition property candidate according to the first embodiment of the present invention;
FIG. 11 is a flowchart for explaining the process for generating the print condition property candidate according to the first embodiment of the present invention;
FIG. 12 is a diagram showing a first process according to the first embodiment of the present invention;
FIG. 13 is a diagram showing a SOAP message in a case in that a client PC indicates an image editing service, according to the first embodiment of the present invention;
FIG. 14 is a diagram showing a SOAP message in a case in that the image editing service is predetermined beforehand to use, according to the first embodiment of the present invention;
FIG. 15 is a diagram showing an example of the print condition property candidate according to the first embodiment of the present invention;
FIG. 16 is a diagram showing another example the print condition property candidate according to the first embodiment of the present invention;
FIG. 17 is a diagram showing a second process according to the first embodiment of the present invention;
FIG. 18 is a diagram showing an example of a SOAP message including an image editing service candidate according to the first embodiment of the present invention;
FIG. 19 is a diagram showing another SOAP message including the edit capability according to the first embodiment of the present invention;
FIG. 20 is a diagram showing a screen to set a print function and an advanced function, according to the first embodiment of the present invention;
FIG. 21 is a diagram showing a sequence flow for explaining the process for printing a document according to the first embodiment of the present invention;
FIG. 22 is a diagram showing the sequence flow for explaining the process for printing a document according to the first embodiment of the present invention;
FIG. 23 is a diagram showing an example of the SOAP message informed by a sdocument print request according to the first embodiment of the present invention;
FIG. 24 is a flowchart for explaining a process conducted by a printing WS according to the first embodiment of the present invention;
FIG. 25 is a diagram showing a prototype of a function used by in step S108 inFIG. 21, according to the first embodiment of the present invention;
FIG. 26 is a diagram showing a SOAP message showing a document edit request according to the first embodiment of the present invention;
FIG. 27 is a diagram showing a SOAP message showing an edit result notice according to the first embodiment of the present invention;
FIG. 28 is a diagram showing a SOAP message for a document print accept result according to the first embodiment of the present invention;
FIG. 29 is a diagram showing a system configuration according to a second embodiment of the present invention;
FIG. 30 is a diagram showing a functional configuration according to the second embodiment of the present invention;
FIG. 31 is a diagram showing a sequence flow of a process for obtaining the print condition property candidate according to the second embodiment of the present invention;
FIG. 32 is a diagram showing a sequence flow of a process concerning a print according to the second embodiment of the present invention;
FIG. 33 is a diagram showing the sequence flow of the process concerning a print according to the second embodiment of the present invention;
FIG. 34 is a diagram showing a SOAP message for a document print request according to the second embodiment of the present invention;
FIG. 35 is a block diagram showing a system configuration according to a third embodiment of the present invention;
FIG. 36 is a block diagram showing a functional configuration according to the third embodiment of the present invention;
FIG. 37 is a diagram showing a sequence flow of a process concerning a print, according to the third embodiments of the present invention;
FIG. 38 is a diagram showing a sequence flow of the process concerning a print, according to the third embodiments of the present invention;
FIG. 39 is a diagram showing a SOAP message for a document ticket create request according to the third embodiment of the present invention;
FIG. 40 is a diagram showing the SOAP message for a response with respect to the document ticket create request according to the third embodiment of the present invention;
FIG. 41 is a block diagram showing a system configuration according to a fourth embodiment of the present invention;
FIG. 42 is a block diagram showing a functional configuration according to the fourth embodiment of the present invention;
FIG. 43 is a diagram showing a sequence flow of a process concerning a print according to the fourth embodiment of the present invention;
FIG. 44 is a diagram showing the sequence flow of the process concerning a print according to the fourth embodiment of the present invention;
FIG. 45 is a diagram showing a system configuration according to a fifth embodiment of the present invention;
FIG. 46 is a block diagram showing a functional configuration according to the fifth embodiment of the present invention;
FIG. 47 is a diagram showing a sequence flow of a process for obtaining a print condition property according to the fifth embodiment of the present invention;
FIG. 48 is a diagram showing a sequence flow of a process concerning a print according to the fifth embodiment of the present invention;
FIG. 49 is a diagram showing the sequence flow of the process concerning the print according to the fifth embodiment of the present invention;
FIG. 50 is a block diagram showing a system configuration according to a sixth embodiment of the present invention;
FIG. 51 is a diagram showing a functional configuration according to the sixth embodiment of the present invention;
FIG. 52 is a diagram showing a sequence flow of the process for obtaining a print condition property candidate according to the seventh embodiment of the present invention;
FIG. 53 is a diagram showing a sequence flow of a process concerning a print according to the sixth embodiment of the present invention:
FIG. 54 is a diagram showing the sequence flow of the process concerning a print according to the sixth embodiment of the present invention:
FIG. 55 is a block diagram showing a system configuration according to a seventh embodiment of the present invention;
FIG. 56 is a diagram showing a functional configuration according to the seventh embodiment of the present invention;
FIG. 57 is a diagram showing a sequence flow of a process for obtaining the print condition property according to the seventh embodiment of the present invention;
FIG. 58 is a diagram showing a sequence flow of a process concerning a print according to the seventh embodiment of the present invention;
FIG. 59 is a diagram showing the sequence flow of the process concerning a print according to the seventh embodiment of the present invention;
FIG. 60 is a block diagram showing a system configuration according to an eighth embodiment of the present invention;
FIG. 61 is a diagram showing a functional configuration according to the eighth embodiment of the present invention;
FIG. 62 is a diagram showing a sequence flow of a process for obtaining a print condition property candidate according to the eighth embodiment of the present invention;
FIG. 63 is a diagram showing a sequence flow of a process concerning a print according to the eighth embodiment of the present invention;
FIG. 64 is a diagram showing the sequence flow of the process concerning a print according to the eighth embodiment of the present invention;
FIG. 65 is a diagram showing a configuration in that a single Web service client (WSC) can use a plurality of Web services (WS), according to the present invention;
FIG. 66 is a diagram showing another configuration in that a single Web service can use a plurality of Web service client (WSC), according to the present invention; and
FIG. 67 is a diagram showing a configuration formed by the MFP-A described inFIG. 65 and the MFP-B described inFIG. 66, according to the present invention.
DESCRIPTION OF THE PREFERRED EMBODIMENTS In the following, embodiments of the present invention will be described with reference to the accompanying drawings. In the embodiments of the present invention, a document processing system is described as an output information providing system, and a case in that an output of a document is a print will be described. Accordingly, “output” is read as “print”. For example, in the following embodiments, an output property can be read as a print property. Also, in the following, for example, “obtain” includes a meaning of “generate”.
Moreover other outputs, for example, an output by a facsimile transmission, a distribution to other computers, and a like can be considered.
Furthermore, in the following, “image” and “document” are used. A document includes one or more images and bibliographic information. Accordingly, in the following embodiments, to edit and print out a document expresses to edit and print out an image included in the document. Even if an expression of editing and printing out a document is used, the image included in the document can be edited and printed out.
[Overview]
First, the document processing system according to the present invention will be described with reference toFIG. 1. InFIG. 1, adocument processing system100 includes aprinting service210 as a Web service, animage editing service211 as a Web service, adocument management service212 as a Web service, and at least one client PC (Personal Computer)213, which can communicate with each other. As shown inFIG. 1,documents301 and302 are sent and received amongservices210,211, and212. Thedocument management service212 includes a document DB (database)214.
Theclient PC213 is a personal computer which a user uses to edit and/or print out a document, and includes an application to use the above-describedservices210,211, and212.
Theprinting service210 receives a document print request from theclient PC213, prints out the document, and provides a print property showing a printing method executable when printing out the document in response to a request sent from theclient PC213.
Theimage editing service211 is a service for editing a document, and provides an edit property showing edit contents being executable with respect to the document. Thedocument management service212 manages the document by using thedocument DB214.
As described above, theWeb services210,211, and212 send and receive information such as the document, the edit property, and the like to/from each other.
As described above, theprinting service210, theimage editing service211, and thedocument management service212 may not be specific apparatuses, but represent elements of thedocument processing system100. Accordingly, theprinting service210, theimage editing service211, and thedocument management service212 may be implemented in different apparatuses, respectively or in a single apparatus.
Therefore, in each of the following embodiments, different combinations of the Web services and apparatuses will be described. Prior to each explanation of the following embodiment, a multi-functional apparatus implementing the above-describedWeb services210,211, and212, and theclient PC213 will be described according to the present invention.
FIG. 2 is a block diagram showing a functional configuration of the multi-functional apparatus according to the present invention. Themulti-functional apparatus1 includes asoftware group2, aboot part3, andhardware resources4.
Theboot part3 is executed first when themulti-functional apparatus1 is turned on, and activates an application layer5, and aplatform layer6. For example, theboot part3 reads out programs of the application layer5 and theplatform layer6 from an HDD (Hard Disk Drive) or a like, and transfers the programs read out from the HDD or the like to a memory area. Thehardware resources4 include ascanner11, aplotter12, and anotherhardware resource13 such as an ADF (Auto Document Feeder).
Thesoftware group2 includes the application layer5 and theplatform layer6 being activated on an operating system (hereinafter, called OS) such as UNIX>. The application layer5 includes programs to conduct each specific process for a user service concerning an image formation such as a printer, a copier, a facsimile, a scanner, and a like.
The application layer5 includes aprinter application21 being an application for the printer, acopy application22 being an application for the copy, aFAX application23 being an application for the facsimile, ascanner application24 being an application for the scanner, aWEB page application25, a SOAP (Simple Object Access Protocol)communication application26, at least one or more common function (hereinafter, called SFs (Service Functions))28 and29, and a WEB service function (hereinafter, called WSF) provided between theWEB page application25 and theSOAP communication application26, and theSFs28 and29.
TheWSF27 includes an application program interface (hereinafter, called WS-API)51 to receive a process request from theWEB page application25 and theSOAP communication application26 by functions being defined beforehand. Also, theSFs28 and29 include an application program interface (hereinafter, called SF-API)52 to receive a process request from theWSF27 by a function being defined beforehand.
When theWSF27 receives the process request from theWEB page application25 and theSOAP communication application26 through the WS-API51, theWSF27 selects one of theSFs28 and29 in response to the process request. TheWSF27 sends the process request received through the WS-API51 to the selected one of theSFs28 and29 through the SF-API52. When the selected one of theSFs28 and29 receives the process request through the SF-API52, the selected one of theSFs28 and29 conducts a process corresponding to the process request. TheSOAP communication application26 generates and interprets a SOAP message as a server of theWeb service210,211, or212.
Theplatform layer6 includes acontrol service layer9 for interpreting the process request received from theapplication layer6 and for creating an acquisition request for acquiring thehardware resources4, a system resources manager (hereinafter, called SRM)39 for mediating the acquisition request received from thecontrol service layer9 by managing one ormore hardware resources4, and a handler layer10 for managing thehardware resources4 in response to the acquisition request received from theSRM39.
Thecontrol service layer9 includes at least one of service modules such as a network control service (hereinafter, called NCS)31, a delivery control service (hereinafter, called DCS)32, an operation panel control service (hereinafter, called OCS)33, a certification control service (hereinafter, called CCS)34, an engine control service (hereinafter, called ESC)35, a memory control service (hereinafter, called MCS)36, a user information control service (hereinafter, called UCS)37, a system control service (hereinafter, called SCS)38, and a like.
Theplatform layer6 includes an application program interface (hereinafter, called API)53 for receiving the process request from theapplication layer6 by a function being defined beforehand. The OS executes software for the application layer5 and theplatform layer6 as processes in parallel.
A process of theNCS31 provides a service for applications requiring a network I/O to use in common. The process of theNCS31 distributes data received from each protocol at a network side to a relative application, and intermediates to send data from each application to the network side.
For example, theNCS31 controls a data communication with a network device connected through a network in accordance with an HTTP (HyperText Transfer Protocol) by an httpd (HyperText Transfer Protocol Daemon) A process of theDSC32 controls a distribution of accumulated documents. A process of theOCS33 controls an operation panel, which is an information transmitting part between an operator and a main unit control of themulti-functional apparatus1. A process of theCCS34 conducts a process concerning a user certification.
A process of theECS35 controls an engine part such as thescanner11, theplotter12, and the anotherhardware resource13. A process of theMCS36 acquires and releases a memory area, and conducts a memory control to control use of the HDD. A process ofUCS37 manages user information.
A process of theSCS38 conducts processes such as an application management, an operation panel control, a system screen display, an LED display, a hardware resource management, an interruption control of the applications, and a like.
A process of theSRM39 conducts the system control with theSCS38, and manages thehardware resources4. For example, the process of theSRM39 mediates the acquisition request from an upper layer using thehardware resources4, and conducts an execution control.
In detail, the process of theSRM39 determines whether or not one of thehardware resources4, which corresponds to the acquisition request, is available (is used by another acquisition request). If available, the process of theSRM39 informs the upper layer that the one of thehardware resources4 to which the acquisition request is made is available. Also, the process of theSRM39 schedules to use thehardware resources4 with respect to the acquisition request received from the upper layer, and directly conducts various operations in accordance with request contents (for example, a sheet feed and an image creating operation, a memory acquisition, a file generation, and a like).
A handler layer10 includes a FAX control unit handler (hereinafter, called FCUH)40 for managing a FAX control unit (hereinafter, called FCU), which will be described later, and an image memory handler (hereinafter, called IMH)41 for assigning the memory area to a process and managing the memory area being assigned to the process. TheSRM39 and theFCUH40 conduct a process request with respect to thehardware resources4 by using an engine I/F (InterFace)54, which can send the process request with respect to thehardware resources4 by a function being defined beforehand.
Themulti-functional apparatus1 can centralize and process in common among the applications at theplatform layer6. Next, a hardware configuration of themulti-functional apparatus1 will be described with reference toFIG. 3.
FIG. 3 is a block diagram showing the hardware configuration of the multi-functional apparatus according to the present invention. Themulti-functional apparatus1 includes acontroller board60, anoperation panel59, theFCU68, and anengine71. Moreover, theFCU68 includes a G3standard support unit69, and a G4standard support unit70.
Moreover, thecontroller board60 includes a CPU (Central Processing Unit)61, an ASIC (Application Specific Integrated Circuit)66, an HDD (Hard Disk Drive)65, a system memory (MEM-P)63, a local memory (MEM-C)64, a north bridge (hereinafter, called NB)62, a south bridge (hereinafter, called SB)73, a NIC (Network Interface Card)74, a USB (Universal Serial Bus)device75, an IEEE 1394device76, and acentronics™ device77.
Theoperation panel59 is connected to theASIC66 of thecontroller board60. TheSB73, theUSB device75, the IEEE 1394device76, and thecentronics™ device77 are connected to theNB62 through aPCI bus79.
TheFCU68 and theengine71 are connected to theASIC66 of thecontroller board60 through aPCI bus78.
Thecontroller board60 connects to the local memory (MEM-C)64 of theASIC66 and theHDD65, and also connects to theCPU61 and theASIC66 through theNB62 of a CPU chip set. As described above, since theCPU61 and theASIC66 are connected through theNB62, this hardware configuration can be realized even if an interface of theCPU61 is not opened to the public.
Moreover, instead of connecting theASIC66 and theNB62 to each other through a PCI bus, theASIC66 and theNB62 are connected through an AGP (Accelerated Graphics Port)67. As described above, in order to control executions of one or more processes forming the application layer5 and theplatform layer6, theASIC66 and theNB62 are connected to each other through the AGP67 but not a PCI bus. Accordingly, it is possible to prevent from degrading performance of themulti-functional apparatus1.
TheCPU61 controls the entiremulti-functional apparatus1. TheCPU61 activates and executes theNCS31, theDCS32, theOCS33, theCCS34, theECS35, theMCS36, theUCS37, theSCS38, theSRM39, theFCUH40, and theIMH41 as processes on the OS, respectively. Moreover, theCPU61 activates and executes theprinter application21, thecopy application22, theFAX application23, thescanner application24, theWeb page application25, and theSOAP communication application26, which form the application layer5.
TheNB62 is a bridge to connect theCPU61, thesystem memory63, theSB73, and theASIC66 to each other. Thesystem memory63 is a memory used as an drawing memory of themulti-functional apparatus1. TheSB73 is a bridge to connect theNB62, thePCI bus79, and a peripheral device to each other. Also, thelocal memory64 is a memory used as a drawing buffer for a copy, a coding buffer, and a like.
TheASIC66 is an IC (Integrated Circuit) for an image process including hardware elements for the image process. Also, theHDD65 is a storage for accumulating image data, document data, programs, font data, forms, and a like. Theoperation panel59 receives an input operation from a user and also displays information for the user.
Next, a hardware configuration of theclient PC213 inFIG. 1 will be described with reference toFIG. 4.
As shown inFIG. 4, in the hardware configuration inFIG. 4, theclient PC213 includes aninput unit122, adisplay unit123, adrive unit124 for arecording medium125, anauxiliary storage unit126, amemory unit127, aCPU120, and aninterface unit121.
Theinput unit122 includes a keyboard and a mouse, and is used for a user to input various operation signals to theclient PC213. Thedisplay unit123 displays various screens and data necessary for the user to operate theclient PC213. Theinterface unit121 is an interface to connect theclient PC213 to a network or to connect to another device. For example, theinterface unit121 includes the NIC (Network Interface Card), a modem, a USB (Universal Serial Bus), and a like.
A program for operating theclient PC213 is provided by therecording medium125 such as a CD-ROM (Compact Disk-Read Only Memory) or a like or by downloading through the network. Also, therecording medium125 is set to thedrive unit124, and then data and the program are installed into theauxiliary storage unit126 through thedrive unit124.
Theauxiliary storage unit126 stores the data and the program, necessary files, and a like. Thememory unit127 reads out and stores the program from theauxiliary storage unit126 when the computer system is activated. TheCPU120 executes a process in accordance with the program read out from theauxiliary storage unit126 and stored in thememory unit127.
In the following, eight embodiments will be described. In the following explanations, parts that have been explained will be omitted. Also, parts that are the same as the ones are previously described by the same reference numerals and the explanation thereof will be omitted. For example, the NCS is denoted by thesame reference numeral31.
First Embodiment In a first embodiment, most explanation will be about a process concerning a print condition property candidate. A process concerning a print will be described after the process concerning the print condition property candidate is described.
FIG. 5 is a block diagram showing a system configuration according to the first embodiment of the present invention. In the system configuration shown inFIG. 5, aclient PC213, aprinting service210, animage editing service211, and adocument DB214, anddocuments301,302, and303 are shown.
As shown inFIG. 5, in the first embodiment, a document subject to print out or edit is included in theclient PC213. Moreover, inFIG. 5, threedocuments301,302, and303 are shown as documents to send and receive. Accordingly, in the first embodiment, sending and receiving the documents is performed three times.
Next, a functional configuration will be described with reference toFIG. 6 in detail.FIG. 6 is a block diagram showing the functional configuration in the system configuration according to the first embodiment of the present invention. InFIG. 6, theclient PC213, an MFP-A221 as onemulti-functional apparatus1, and an MFP-B222 as anothermulti-functional apparatus1 are shown.
Theclient PC213 includes anapplication229 having a user interface and anetwork interface230.
The MFP-A221 includes theNCS31 having thehttpd223, a Web service server (WSS)224, a Web service client (WSC)225, aprinting WSF226, theECS35, and theplotter12. Also, the MFP-B222 includes theNCS31 having thehttpd223, the Web service server (WSS)224, animage editing WSF227, and astorage area228 for an image edit.
As described above, theapplication229 is used when a user prints out a document. Theapplication229 has a scheme for changing the user interface in response to a tag in an XML (extensible Markup Language) sentence showing available service. This available service is shown by the print condition property candidate, which will be described later.
The Web service server (WSS)224 converts a SOAP request message sent from a Web service client such as theclient PC213 into an execution request of the Web service function (hereinafter, called WSF), and sends the execution request to a specific WSF. The Web service server (WSS)224 converts an execution result received from the WSF in the MFP-A221 (MFP-B222) into a SOAP response message, and sends the SOAP response message to the Web service client (client PC213) that sent the SOAP request message.
The Web service client (WSC)225 converts the execution request of the Web service sent from the Web service or the application in the MFP-A221 (MFP-B222) into the SOAP request message, and sends the SOAP request message to a specific Web service. The Web service client (WSC)225 analyses the SOAP response message sent from the Web service located in the network, and sends a result to the Web service or the application in the MFP-A221 (MFP-B222), which sent the SOAP request message. In the first embodiment, the Web service client (WSC)225 provided in the MFP-B222 is not used.
Theprinting WSF226 prints out a document by using theECS35. Theimage editing WSF227 edits an image. For example, thestorage area228 for the image edit is an area which is temporarily provided in theHDD65, thesystem memory63, or thelocal memory64.
In the above-described first embodiment, the Web service server (WSS)224 and the Web service client (WSC)225 inFIG. 6 correspond to theWeb page application25 and theSOAP communication application26 inFIG. 2, respectively.
Next, a sequence flow for obtaining the print condition property candidate will be described with reference toFIG. 7.FIG. 7 is a diagram showing the sequence flow according to the first embodiment of the present invention. In the sequence flow inFIG. 7, a sequential process, which is conducted among theclient PC213, the MFP-A221, and the MFP-B222, are shown. InFIG. 7, aprinting WS240 collectively represents the Web service server (WSS)224 and theprinting WSF226 in the MFP-A221 inFIG. 6. Also, animage editing WS241 collectively represents the Web service server (WSS)224 and theimage editing WSF227 in the MFP-B222 inFIG. 6.
In addition, the sequential process in the sequence flow shown inFIG. 7 is a process for obtaining the print condition property candidate. This print condition property candidate includes an edit property showing the edit contents executable for a document, and a print property showing a printing method executable when the document is printed out. The property and the print property will be described later.
The sequence flow will be described. In step S101, theclient PC213 informs a print condition property candidate obtain request, which is an obtain request for obtaining the print condition property candidate, to theprinting WS240. In step S102, theprinting WS240 informs a WS request send request, which requests sending a WS request to an indicated Web service, to the Web service client (WSC)225. In this case, a URL (Uniform Resource Locater) of the image editing WS, and a method name showing an edit property candidate obtain request are informed with the WS request send request.
In step S103, the Web service client (WSC)225 informs the edit property candidate obtain request to theimage editing WS241 by a SOAP message. In step S104, in response to this SOAP message, theimage editing WS241 informs an edit property notice to the Web service client (WSC)225 by the SOAP message. By sending the edit property notice, the edit property is informed to the MFP-A221. Processes in steps S103 and S104 in theimage editing WS241 correspond to a step of obtaining an edit property.
In step S105, the Web service client (WSC)225 informs a WS request result notice to theprinting WS240. In this case, the edit property candidate informed from the MFP-B222 is also informed to theprinting WS240. When the edit property candidate is informed to theprinting WS240, theprinting WS240 generates the print condition property candidate from the print property candidate held by theprinting WS240 and the edit property candidate informed from the MFP-B222. This process conducted by theprinting WS240 will be described in accordance with a flowchart later.
In step S106, after theprinting WS240 generates the print condition property candidate, theprinting WS240 informs the print condition property candidate by the SOAP message.
By the above-described processes, theclient PC213 can obtain the print condition property candidate.
Next, the print property and the edit property will be described in detail.FIG. 8 is a diagram showing an example of the print property according to the first embodiment of the present invention. As shown inFIG. 8, the print property includes “NUMBER OF COPIES”, “SHEET SIZE”, “BOTH SIDE PRINT YES/NO”, “COLLATE YES/NO”, and a like.
In the print property, “NUMBER OF COPIES” shows whether or not the user can indicate the number of copies for a document. “SHEET SIZE” shows whether or not the user can indicate the size of sheet to print out. “BOTH SIDE PRINT YES/NO” shows whether or not the user can conduct a both side print. “COLLATE YES/NO” shows whether or not the user can collate each of copies of the document.
As shown in this example of the print property described above, basic available print options concerning a print are listed. Since the print property is obtained when the print condition property candidate is generated, for example, processes in step S105 and step S106 correspond to a print property obtaining step.
Next, the edit property will be described with reference toFIG. 9.FIG. 9 is a diagram showing an example of the edit property according to the first embodiment of the present invention. As shown inFIG. 9, in the edit property, “PASTE CONFIDENTIAL STAMP”, “DRAWING OPERATION”, “DELETE/COPY/PASTE/MOVE/CONVERT COLOR FOR INDICATED AREA”, “CONTINUOUSLY EDIT MULTIPLE PAGES”, and “REMOVE STAIN OF GROUND” are listed.
“PASTE CONFIDENTIAL STAMP” shows whether or not the user can paste a confidential stamp to a document and then print out the document with the confidential stamp. “DRAWING OPERATION” shows whether or not the user can draw a straight line, a broken line, a curved line, a polygon, a circle, and a letter. “DELETE/COPY/PASTE/MOVE/CONVERT COLOR FOR INDICATED AREA” shows a list of processes with respect to the indicated area, and shows whether or not the user can delete the indicated area, copy the indicated area, paste the indicated area, move the indicated area, and convert a color of the indicated area. “CONTINUOUSLY EDIT MULTIPLE PAGES” shows whether or not the user can continuously edit multiple pages. “REMOVE STAIN OF GROUND” shows whether or not the user can remove a stain of a color of the document.
As shown in this example of the print property described above, it is possible to conduct various edits with respect to the document. In other embodiments described in the following, the print property and the edit property will be used as the same manner, and the print property and the edit property will include the same contents.
Next, the process for generating the print condition property candidate described above inFIG. 7 will be described with reference toFIG. 10 andFIG. 11.FIG. 10 andFIG. 11 are flowcharts for explaining the process for generating the print condition property candidate according to the first embodiment. The process for generating the print condition property candidate is continued from a flowchart inFIG. 10 to a flowchart inFIG. 11. Also, the process for generating the print condition property candidate is a process conducted by theprinting WS240 in steps S101 through S106 inFIG. 7.
In step S201 corresponding to a step of receiving an output condition property candidate obtain request, theprinting WS240 receives the print condition property obtain request. In step S202 corresponding to a step of obtaining an output property, theprinting WS240 generates a property candidate necessary to a print execution. In this case, the print property candidate is generated.
Next, in step S203, theprinting WS240 determines whether or not there is a Web service client (WSC) to be an edit client (edit C). When there is no Web service client (WSC), theprinting WS240 advances to step S214 inFIG. 11. When there is the Web service client (WSC), theprinting WS240 determines the image editing service candidates in step S204. In the following step S205, theprinting WS240 substitutes the number of the image editing service candidates to a variable X.
Step S206 inFIG. 10 through step S210 inFIG. 11 are looped by evaluating an expression at a top of the loop. When the variable X becomes greater than “0” (zero) the loop is terminated.
In step S207 inFIG. 11 in the loop, the edit property candidate obtain request is informed to theimage editing WS241 through the Web service client (WSC)225. In step S208, theprinting WS240 obtains the edit property candidate from theimage editing WS241 by the edit property notice. The variable X is incremented in step S209 and the loop ends in step S210. The loop in steps S207 through S209 is repeated until the variable X becomes greater than “0” (zero).
When the loop is terminated, theprinting WS240 determines whether or not the number of the image editing service candidates is greater than “1” in step S211. When the number of the image editing service candidates is equal to “1”, the process for generating the print condition property candidate advances to step S213. When the number of the image editing service candidates is greater than “1”, theprinting WS240 merges a plurality of edit properties in step S212 corresponding to a step of merging the edit properties.
After theprinting WS240 merges the plurality of edit properties, theprinting WS240 merges the print property generated in step S202 and the edit properties so as to generate the print condition property candidate in step S213 corresponding to a step of obtaining the output condition property candidate. Subsequently, theprinting WS240 sends the print condition property candidate to theclient PC213 in step S214 corresponding to a step of providing the output condition property candidate, and then terminates the process for obtaining the print condition property candidate.
By conducting the process for obtaining the print condition property candidate, the MFP-A221 can provide the edit property available by the MFP-B222 being different from the MFP-A221 in addition to the edit property of the MFP-A221 itself, to theclient PC213.
The sequence flow shown inFIG. 7 describes the process in that theclient PC213 obtains the print condition property candidate. As a first process for this process, both the print property and the edit property are collectively obtained at one time as described above with reference to the sequence flow inFIG. 7 and the flowcharts inFIG. 10 andFIG. 11. Alternatively, as a second process for this process, the print property is obtained from theprinting WS240 and the edit property is separately obtained from theimage editing WS241.
The first process will be described with reference toFIG. 12.FIG. 12 is a diagram showing the first process according to the first embodiment of the present invention. InFIG. 12, theclient PC213, theprinting service210, and theimage editing service211 are shown. InFIG. 12, the print condition property candidate including aprint property402 and anedit property401 is shown between theclient PC213 and theprinting service210, and theedit property401 is shown between theprinting service210 and theimage editing service211.
In a flow of the first process inFIG. 12, first, theclient PC213 informs the print condition property candidate obtain request to theprinting service210 in step S301. In step S302, theprinting service210 informs the edit property candidate obtain request to theimage editing service211. In step S303, theimage editing service211 informs theedit property401 to theprinting service210. Theprinting service210 merges theedit property401 and theprint property402, and informs the print condition property candidate to theclient PC213 in step S304.
In the first process inFIG. 12, a singleimage editing service211 is shown. However, in a case in that a plurality of theimage editing services211 are configured, three methods can be considered as a determining method for determining which one ofimage editing services211 is used.
In a first determining method, one of theimage editing services211, which is indicated by theclient PC213 in step S301, is used. In a second determining method, theimage editing services211 are searched for through the network, and one of theimage editing services211 being searched is used. In a case of the second determining method, the edit property, which is indicated by theclient PC213 when a document is printed out, may be considered to determine theimage editing service211 to use. In a third method, theimage editing service211 is predetermined beforehand to use.
In any one of the above-described determining methods, one or moreimage editing services211 can be determined to use. In a case of determining a plurality of theimage editing services211, the edit properties obtained from the plurality of theimage editing service211 are merged together as described inFIG. 11.
Next, various examples of the SOAP messages used in the determining methods will be described.FIG. 13 is a diagram showing a SOAP message in a case in that the client PC indicates the image editing service, according to the first embodiment of the present invention. InFIG. 13, a SOAP message M11 is an example of the SOAP message in the case of the first determining method in that the client PC indicates theimage editing service211. By anXML sentence410 shown by a tag <m:getPrint Capability> in the SOAP message M11, a URL of theimage editing service211 indicates “http://111.222.333.444/editservice”.
FIG. 14 is a diagram showing a SOAP message in a case in that the image editing service is predetermined beforehand to use, according to the first embodiment of the present invention. As shown inFIG. 14, in this case of the third determining method in that theimage editing service211 is predetermined beforehand to use, a SOAP message M12 omits the URL of theimage editing service211 shown in the SOAP message M11 inFIG. 13. Since theimage editing service211 is determined beforehand to use, it is not required to indicate theimage editing service211 to use in the third determining method.
Next, examples of the print condition property candidate will be described with reference toFIG. 15 andFIG. 16.FIG. 15 is a diagram showing an example of the print condition property candidate according to the first embodiment of the present invention. InFIG. 15, a SOAP message M13 for the print condition property candidate shows that the user can set the number of copies, the size of a sheet and a direction, and can set to paste the confidential stamp and a page stamp.
In detail, anXML sentence411 shows that the user can set the number of copies from 1 to 99 as shown by “1-99”. AnXML sentence412 shows that the user can set “A4” or “B4” as the size of a sheet as shown by “A4F/B4F”. AnXML sentence413 shows that the user can set to paste the confidential stamp or the page stamp as shown by “secret_stamp/page_stamp”.
FIG. 16 is a diagram showing another example the print condition property candidate according to the first embodiment of the present invention. A SOAP message M14 for the print condition property candidate shows the same contents as the SOAP message M13 but has a different data structure from the SOAP message M13 shown inFIG. 15. In detail, anXML sentence414 inFIG. 16 corresponds to theXML sentence411 inFIG. 15, theXML sentence415 inFIG. 16 corresponds to theXML412 inFIG. 15, and anXML sentence416 inFIG. 16 corresponds to theXML sentence416 inFIG. 15.
As described above, since the print condition property candidate is informed by XML sentences using tags, it is not required to modify theapplication229 of theclient PC213 even if the print condition property candidate is changed.
Next, the second process will be described with reference toFIG. 17.FIG. 17 is a diagram showing the second process according to the first embodiment of the present invention. InFIG. 17, theclient PC213, theprinting service210, theimage editing service211 are shown. InFIG. 17, theprint property402, theedit capability420, and the imageediting service candidate421 are shown between theclient PC213 and theprinting service210. Theedit property401 is shown between theclient PC213 and theimage editing service211.
Theedit capability420 is edit information concerning an edit and informing that a document can be edited by using theimage editing service211. Also, the imageediting service candidate421 is optional information to inform the image editing service candidate, for example, by using an URL. In a case in that the imageediting service candidate421 is not informed, theclient PC213 is required to inform theimage editing service211 to use. As described above, information concerning a provider providing the edit property is sent to theclient PC213.
Next, in a flow of the second process inFIG. 17, in step S401, theclient PC213 informs the print candidate property candidate obtain request to theprinting service210. In step S402, theprinting service210 informs theprint property402, theedit capability420, the imageediting service candidate421 to theclient PC213.
In step S403, theclient PC213 sends the edit property candidate obtain request to the imageediting service candidate421 informed from theprinting service210 or/and theimage editing service211 searched by theclient PC213 itself. In step S404, theimage editing service211 informs an edit property candidate.
As described above, in the second process, theclient PC213 separately obtains the edit property and the print property. A SOAP message sent from theclient PC213 to theprinting service210 is the same as the SOAP message shown inFIG. 14. Also, a SOAP message sent from theprinting service210 to theclient PC213 is the same as the SOAP message shown inFIG. 18 orFIG. 19.
FIG. 18 is a diagram showing an example of a SOAP message including the image editing service candidate according to the first embodiment of the present invention. A SOAP message M15 including the image editing service candidate shown inFIG. 18 shows theprint property402, theedit capability420, and the imageediting service candidate421. AnXML sentence426 corresponds to theprint property402. AnXML sentence427 corresponds to theedit capability420 and shows by “true” that the user can edit a document. AnXML sentence425 corresponds to the imageediting service candidate421 and shows the URL of the imageediting service candidate421.
The SOAP message inFIG. 18 shows the imageediting service candidate421 by theXML sentence425. Alternatively, a SOAP message in a case in that the imageediting service candidate421 is not informed is shown inFIG. 19.FIG. 19 is a diagram showing another SOAP message including the edit capability according to the first embodiment. As shown inFIG. 19, in a SOAP message M16, anXML sentence426 corresponding to theprint property402 and anXML sentence427 corresponding to theedit capability420 are shown but the imageediting service candidate421 is not shown.
When theclient PC213 receives the SOAP messages described above, theclient PC213 requests theimage editing service211 to send theedit property401 and receives theedit property401 from theimage editing service211.
After theclient PC213 obtains theedit property401 and theprint property402, theclient PC213 displays ascreen440 as shown inFIG. 20.FIG. 20 is a diagram showing a screen to set a print function and an advanced function, according to the first embodiment of the present invention. InFIG. 20, thescreen440 is displayed in the same manner in the first process and the second process.
Thescreen440 will be described. Thescreen440 is displayed for the user to set to use or not functions shown by theprint property402 and theedit property401 and for the user to conduct to print out a document.
Thescreen440 displays aprint function430 showing functions executable by obtaining theprint property402, anadvanced function431 showing functions executable by obtaining theedit property401, aprint button436 for executing a print, and a cancelbutton437 for canceling the print.
Moreover, at theprint function430, asetting area432 for setting the number of copies, and asetting area434 for setting the size of a sheet are displayed. Thesetting area432 for setting the number of copies is a text box for the user to set the number of copies as shown inFIG. 20. Thesetting area434 for setting the size of sheet is a pull-down menu for the user to select and set the size of a sheet.
Furthermore, at theadvanced function431 displays asetting area435 for setting a confidential stamp. In a case of pasting the confidential stamp, the user checks a radio button and selects and sets a drawing location from the pull-down menu.
After the user sets theprint function430 and theadvanced function431, if the user cancels the settings, the user presses the cancelbutton437. If the user executes a print, the user presses theprint button436. When the user presses theprint button436, theclient PC213 requests the MFP-A221 to print out the document. A process concerning a print after the user presses theprint button436 will be described with reference toFIG. 21 andFIG. 22.FIG. 21 andFIG. 22 are diagrams showing a sequence flow for explaining the process for printing a document according to the first embodiment of the present invention.
In step S107, theclient PC213 sends a document print request to the MFP-A221. The document print request is conducted by a SOAP message, which will be described later. A document and a print condition created by selecting from the print condition property candidate by the user are informed by the document print request. In the process shown inFIG. 21 andFIG. 22, as the print condition, theclient PC213 requests to paste the confidential stamp.
When the document print request is informed to theprinting WS240, theprinting WS240 conducts a process flow of the printing service, which will be described later. Theprinting WS240 sends a WS request send request, which requests the Web service client (WSC)225 to send a WS request to the MFP-B222, to the Web service client (WSC)225 in step S108. This WS request send request informs a method name showing a document edit request, edit contents including a paste of the confidential stamp, a URL of theimage editing WS241, and a document, to the Web service client (WSC)225.
In step S109, the Webservice client WSC225 sends the document edit request to the MFP-B222. The document edit request is informed by a SOAP message, which will be described later. This SOAP message informs the document and the edit contents including the paste of the confidential stamp, which are informed by the WS request send request in step S108.
Subsequently, the process will be described inFIG. 22. In step S110, theimage editing WS241 edits the document and informs an edit result to the Web service client (WSC)225 with an edited document to the Web service client (WSC)225. The edit result is sent by a SOAP message, which will be described inFIG. 27. Next, in step S111, the Web service client (WSC)225 sends the edit result with the edited document to theprinting WS240.
When theprinting WS240 receives the edited document, theprinting WS240 prints out the edited document, and informs a document print accept result to theclient PC213 in step S112. The document print accept result is informed by a SOAP message, which will be described inFIG. 28.
The process concerning a print according to the present invention has been described above. Next, the SOAP messages informed in the process concerning a print and a flowchart of the process will be described. First, the SOAP message informed by the document print request in step S107 will be described with reference toFIG. 23.FIG. 23 is a diagram showing an example of a SOAP message informed by the document print request according to the first embodiment of the present invention. A SOAP message M17 shown inFIG. 23 includes information concerning a document name, the number of copies, the size of a sheet, and a stamp.
AnXML sentence450 shows that the document to send has the document name “content.tiff”. AnXML sentence451 shows three copies. AnXML sentence452 shows to print out the edited document by horizontal A4. AnXML sentence453 shows to paste the confidential stamp.
Next, the process conducted by theprinting WS240 inFIG. 21 andFIG. 22 will be described with reference toFIG. 24. In step S501, theprinting WS240 accepts the document print requests. Next, theprinting WS240 determines a presence of an edit indication in step S502. When there is no edit indication, theprinting WS240 advances to step S505.
When there is the edit indication, theprinting WS240 sends the document edit request to theimage editing WS241 through the Web service client (WSC)225 in step S503. In step S504, theprinting WS240 obtains an edit result notice and the edited document from theimage editing WS241.
In step S505, theprinting WS240 sends a print request for the edited document to theECS35. In step S506, theprinting WS240 sends the document print accept result to theclient PC213 and terminates the process.
Next, a function used in step S108 inFIG. 21 will be described with reference toFIG. 25.FIG. 25 is a diagram showing a prototype of the function used by in step S108 inFIG. 21, according to the first embodiment of the present invention. The function shown inFIG. 25 is a function used in C programming language or C++ language. The function shown inFIG. 25 has a function name “callWebService” and a return value of an integer type, and five arguments. These five arguments will be described.
“webServiceURL” is a pointer of a character type and indicates a top address where a URL of a Web service is stored in a memory. “webServiceName” indicates a top address where a service name of the Web service is stored in the memory.
“webServiceMethodName” indicates a top address where the method name is stored in the memory. “argumentList” indicates an address storing a top address where method arguments are stored in the memory. “resultList” indicates an address storing a top address where response data are stored in the memory. “error” stores error information.
“webServiceURL”, “webServiceName”, “webServiceMethodName”, and “argumentList” are set at a side using the function, and “resultList” and “error” are set by the function.
Next, the SOAP message to the MFP-B222 in step S109 inFIG. 21 will be described with reference toFIG. 26.FIG. 26 is a diagram showing a SOAP message showing the document edit request according to the first embodiment of the present invention. A SOAP message M18 shown inFIG. 26 shows a document edit request and requests to paste the confidential stamp by anXML sentence454.
Next, the SOAP message informed in step S110 inFIG. 22 will be described with reference toFIG. 27.FIG. 27 is a diagram showing a SOAP message showing the edit result notice according to the first embodiment of the present invention. A SOAP message M19 shown inFIG. 27 shows the edit result notice, and anXML sentence455 indicates a file name “content.tiff” of the document in which the confidential stamp is pasted. Actual document data following to the SOAP message M19 are sent to theWeb service control225.
Next, the SOAP message informed in step S112 inFIG. 22 will be described with reference toFIG. 28.FIG. 28 is a diagram showing the SOAP message for the document print accept result according to the first embodiment of the present invention. The SOAP message M20 shown inFIG. 28 shows the document print accept result, and includes a job ID “0987654321” as shown by anXML sentence456.
In the first embodiment described above, the document subject to edit or print out is in theclient PC213. Next, in a second embodiment, the document is stored in theclient PC213 similar to the first embodiment. However, different from the first embodiment, thedocument management service212 as a Web service managing the document is implemented in theclient PC213.
Second Embodiment A system configuration according to the second embodiment will be described with reference toFIG. 29.FIG. 29 is a diagram showing the system configuration according to the second embodiment of the present invention. InFIG. 29, aclient PC213, aprinting service210, animage editing service211, and adocument management service212, adocument DB214, anddocuments301 and302 are shown.
As shown inFIG. 29, different from the first embodiment, the number of document transmissions (sending and receiving the document) is reduced to two times (seeFIG. 5). By reducing the number of the document transmissions, it is possible to reduce the number of chances of attacking thedocuments301 and302 such as interception and falsification.
In a flow of the document transmission, thedocument301 is sent from thedocument management service212 of theclient PC213 to theimage editing service211, and is edited by theimage editing service211. Then, an edited document (document301) is sent from theimage editing service211 to theprinting service210, and is printed out by theprinting service210.
As described above, the second embodiment is different from the first embodiment in that thedocument301 is directly sent from theclient PC213 to theimage editing service211.
Next, a functional configuration according to the second embodiment will be described with reference toFIG. 30 in detail.FIG. 30 is a diagram showing the functional configuration according to the second embodiment of the present invention. InFIG. 30, theclient PC213, the MFP-A211, and the MFP-B222 are shown. Referring toFIG. 30, parts different from the first embodiment (seeFIG. 6) will be described. First, theclient PC213 includes arepository Web service231 as thedocument management service212, and a Webservice server engine232. The Webservice server engine232 is an engine to execute a server function of the Web services.
Moreover, in the MFP-B222, the Web service client (WSC)225, which is not used in the first embodiment, is used to function as a client of therepository Web service231.
The system configuration and the functional configuration according to the second embodiment are described above. Next, a sequence flow for obtaining the print condition property candidate will be described with reference toFIG. 31.FIG. 31 is a diagram showing the sequence flow of the process for obtaining the print condition property candidate according to the second embodiment of the present invention. In the sequence flow inFIG. 31, a sequential process, which is conducted among theclient PC213, the MFP-A221, and the MFP-B222, are shown. InFIG. 31, theprinting WS240 collectively represents the Web service server (WSS)224 and theprinting WSF226 in the MFP-A221 inFIG. 30. Also, theimage editing WS241 collectively represents the Web service server (WSS)224 and theimage editing WSF227 in the MFP-B222 inFIG. 30.
In addition, the sequential process in the sequence flow shown inFIG. 31 is a process for obtaining a print condition property candidate.
The sequence flow will be described. In step S601, theclient PC213 informs a print condition property candidate obtain request, which is an obtain request for obtaining the print condition property candidate, to theprinting WS240. In step S602, theprinting WS240 informs a WS request send request, which requests sending a WS request to an indicated Web service, to the Web service client (WSC)225. In this case, a URL (Uniform Resource Locater) of theimage editing WS241, and a method name showing an edit property candidate obtain request are informed with the WS request send request.
In step S603, the Web service client (WSC)225 informs the edit property candidate obtain request to theimage editing WS241 by a SOAP message. In step S604, in response to this SOAP message, theimage editing WS241 informs an edit property notice to the Web service client (WSC)225 by the SOAP message. By sending the edit property notice, the edit property is informed to the MFP-A221.
In step S605, the Web service client (WSC)225 informs a WS request result notice to theprinting WS240. In this case, the edit property candidate informed from the MFP-B222 is also informed to theprinting WS240. When the edit property candidate is informed to theprinting WS240, theprinting WS240 generates the print condition property candidate from the print property candidate held by theprinting WS240 and the edit property candidate informed from the MFP-B222. This process conducted by theprinting WS240 is the same as the process described in accordance with the flowcharts shown inFIG. 10 andFIG. 11.
In step S606, after theprinting WS240 generates the print condition property candidate, theprinting WS240 informs the print condition property candidate by the SOAP message.
By the above-described processes, theclient PC213 can obtain the print condition property candidate.
Next, a process concerning a print according to the second embodiment will be described with reference toFIG. 32 andFIG. 33.FIG. 32 andFIG. 33 are diagrams showing a sequence flow of the process concerning a print according to the second embodiment of the present invention. InFIG. 32, in step S607, theapplication229 of theclient PC213 informs a document ticket create request to therepository WS235 in thesame client PC213 with an array of document IDs. In step S608, therepository WS235 sends a response with respect to the document ticket create request to theapplication229 with a document ticket. In this case, the document ID uniquely indicates a document. The document ticket shows permission to edit or print out the document, and is required to edit or print out the document specified by the document ID.
In step S609, theclient PC213 informs a document print request to the MFP-A221. The document print request is informed by a SOAP message, which will be described later, and the document ticket and the print condition will be informed with the document print request. In this case inFIG. 31, theclient PC213 requests pasting a confidential stamp as a print condition property.
When the document print request is informed to theprinting WS240, theprinting WS240 executes a process flow of the printing service described inFIG. 24. Theprinting WS240 sends a WS request send request, which requests the Web service client (WSC)225 to send the WS request to the MFP-B222, to the Web service client (WSC)225 in step S610. This WS request send request informs a method name showing a document edit request, edit contents including a paste of the confidential, a URL of theimage editing WS241, and the document ticket, to the Web service client (WSC)255, by using the function shown inFIG. 25.
In step S611, the Web service client (WSC)225 sends the document edit request to the MFP-B222. A SOAP message for the document edit request is the same as the SOAP message M18 shown inFIG. 26. Also, the document ticket and the edit contents showing to paste the confidential stamp, which are previously informed, are informed by this SOAP message.
Next, in step S612, theimage editing WS241 sends the WS request send request to the Web service client (WSC)225 in the MFP-B222 to get back (retrieve) the document from therepository WS235. The function shown inFIG. 25 is used for this WS request send request, and a URL of therepository WS235, a method showing a document get back request, and the document ticket are informed to the Web service client (WSC)225.
In step S613, the Web service client (WSC)225 sends the document get back request to therepository WS235 with the document ticket. The process concerning a print is continued to the sequence flow shown inFIG. 33. Instep S614, therepository WS235 sends a response with respect to the document get back request. In this case, the document is returned to the MFP-B222. When the Web service client (WSC)225 gets back the document, the Web service client (WSC)225 sends a response including a request result with the document to theimage editing WS241 in step S615.
In step S616, theimage editing WS241 edits the document and sends an edit result with the edited document to the Web service client (WSC)225 of the MFP-A221. The edit result is sent by the SOAP message M19 shown inFIG. 27. Next, in step S617, the Web service client (WSC)225 sends the edit result with the edited document to theprinting WS240.
When the edited document is sent to theprinting WS240, theprinting WS240 prints out the document and sends a document print accept result to theclient PC213 in step S618. The document print accept result is sent by the SOAP message M20 described inFIG. 28.
Next, a SOAP message sent from theapplication229 to theprinting WS240 in step S609 will be described with reference toFIG. 34. The SOAP message shown M21 inFIG. 34 is a SOAP message for the document print request, but is different from the SOAP message M17 shown inFIG. 23 in the first embodiment and instead of the document name, the document ticket is indicated by anXML sentence459. “jfowfnofjofi” is the document ticket shown by theXML sentence459. The SOAP message M21 shown inFIG. 34 will be used in the following embodiments until an eighth embodiment.
Next, a third embodiment will be described. In the third embodiment, different from the second embodiment, thedocument management service212 is separately provided from theclient PC213.
Third EmbodimentFIG. 35 is a block diagram showing a system configuration according to the third embodiment of the present invention. InFIG. 35, aclient PC213, aprinting service210, animage editing service211, adocument management service211, adocument DB214, anddocuments301 and302 are shown.
In a flow of thedocuments301 and302 inFIG. 35, thedocument302 is sent from thedocument management service212 to theimage editing service211, and edited by theimage editing service211. Then, the edited document as thedocument301 is sent from theimage editing service211 to theprinting service210, and prints out thedocument301.
A functional configuration according to the third embodiment will be described with reference toFIG. 36 in detail.FIG. 36 is a block diagram showing the functional configuration according to the third embodiment of the present invention. InFIG. 36, theclient PC213, the MFP-A221, the MFP-B222, and a MFP-C233 are shown. InFIG. 36, parts different from the second embodiment will be described. First, theclient PC213 includes theapplication229 and thenetwork interface230, and has the same functional configuration as the first embodiment.
Moreover, the MFP-C233 is additionally provided as a repository service. The MFP-C233 includes theNCS31 having thehttpd223, the Web service server (WSS)224, the Web service client (WSC)225, a repository Web service function (WSF)234, theMCS36, and theHDD65.
Therepository WSF234 is a Web service function (WSF) for providing a document management function. TheMCS36 is used when therepository WSF234 accesses theHDD65. TheHDD65 stores the document. It should be noted that the Web service client (WSC)225 provided in the MFP-B222 is not used in the third embodiment.
The above-described system configuration and the functional configuration are implemented in the third embodiment. Next, a process concerning a print will be described with reference toFIG. 37 andFIG. 38.FIG. 37 andFIG. 38 are diagrams showing a sequence flow of the process concerning a print, according to the third embodiment of the present invention. In the sequence flow shown inFIG. 37 andFIG. 38, the process conducted among theclient PC213, the MFP-A221, the MFP-B222, and the MFP-C233 is shown. InFIG. 37 andFIG. 38, therepository WS235 collectively represents the Web service server (WSS)224 in the MFP-C233 and therepository WSF234.
The process shown inFIG. 37 andFIG. 38 is a process in that theclient PC213 obtains a document ticket and prints out the document.
In step S701, theapplication229 of theclient PC123 sends a document ticket create request with an array of document IDs to therepository WS235. Therepository WS235 creates the document ticket, and sends a response with respect to the document ticket create request with the document ticket, to theclient PC213 in step S702. SOAP messages used in step S701 and step S702 will be described later with reference toFIG. 39 andFIG. 40.
In step S703, theclient PC213 sends a document print request to the MFP-A221. The document print request is sent by the SOAP message described inFIG. 34, and the document ticket, the document, the print condition property are informed to theprinting WS240 of the MFP-A221. In this case inFIG. 37, theclient PC213 request pasting a confidential stamp as the print condition property.
When the document print request is informed to theprinting WS240, theprinting WS240 executes the process flow of the printing service described inFIG. 24. Theprinting WS240 sends a WS request send request, which requests sending a WS request to an indicated Web service, to the Web service client (WSC)225 in step S704. The function shown inFIG. 25 is used for the WS request send request, and a method name showing a document edit request, edit contents showing a paste of the confidential stamp, a URL of theimage editing WS241, and the document ticket are informed to the Web service client (WSC)225.
In step S705, the Web service client (WSC)225 sends the document edit request to the MFP-B222. A SOAP message for the document edit request is the same as the SOAP message M18 shown inFIG. 26. The SOAP message M18 informs the document ticket, and the edit contents showing the paste of the confidential stamp.
Next, theimage editing WS241 sends a WS request send request to the Web service client (WSC)225 to get back (retrieve) the document from therepository WS235 in step S706. The function shown inFIG. 25 is used for the WS request send request, and a URL of therepository WS235, a method name showing a document get back request, and the document ticket are informed to the Web service client (WSC)225.
Referring toFIG. 38, the Web service client (WSC)225 sends the document get back request with the document ticket to therepository WS235 in step S707. In step S708, therepository WS235 sends a response with respect to the document get back request. In this case, the document is returned to the MFP-B222. When the Web service client (WSC)225 receives the document, the Web service client (WSC)225 sends a response including a request result with the document to theimage editing WS241 in step S709.
Theimage editing WS241 edits the document, and sends an edit result notice showing an edit result with the edited document to the Web service client (WSC)225 of the MFP-A221 in step S710. A SOAP message for the edit result notice is the same as the SOAP message M19 shown inFIG. 27. Next, the Web service client (WSC)225 sends the edit result notice showing the edit result with the edited document to theprinting WS240 in step S711.
When theprinting WS240 receives the edited document, theprinting WS240 prints out the edited document, sends a document print accept result to theclient PC213 in step S712. A SOAP message for the document print accept result is the same as the SOAP message M20 shown inFIG. 28.
Next, a SOAP message informed in step S701 inFIG. 37 will be described with reference toFIG. 39.FIG. 39 is a diagram showing a SOAP message for the document ticket create request according to the third embodiment of the present invention. A SOAP message M22 shown inFIG. 39 shows two document IDs “1111” and “1112” as shown by anXML sentence457. The document ticket is created based on these two document IDs.
A SOAP message for the response with respect to the document ticket create request will be described with reference toFIG. 40.FIG. 40 is a diagram showing the SOAP message for the response with respect to the document ticket create request according to the third embodiment of the present invention. In the SOAP message M23 shown inFIG. 40, the response with respect to the document ticket create request includes the document ticket “jfowfnofjofi” as shown by anXML sentence458.
Next, a fourth embodiment will be described. In the fourth embodiment, different from the third embodiment, the document transmission (sending and receiving a document) is conducted between thedocument management service212 and theprinting service210.
Fourth EmbodimentFIG. 41 is a block diagram showing a system configuration according to the fourth embodiment of the present invention. InFIG. 41, a heclient PC213, aprinting service210, animage editing service211, adocument management service212, adocument DB214, anddocuments301,302, and303 are shown.
In a document flow inFIG. 41, thedocument301 is sent from thedocument management service212 to theprinting service210, and is sent from theprinting service210 to theimage editing service211 as thedocument302. Thedocument302 edited by theimage editing service211 is sent to theprinting service210 as thedocument303, and is printed out from theprinting service210.
Next, a functional configuration will be described with reference toFIG. 42 in detail.FIG. 42 is a block diagram showing the functional configuration according to the fourth embodiment of the present invention. InFIG. 42, theclient PC213, the MFP-A221, the MFP-B222, and the MFP-C233 are shown. InFIG. 42, parts different from the third embodiment will be described. In the fourth embodiment, different from the third embodiment, the Web service client (WSC)225 is not required since the MFP-B222 is not required to be a client of the Web service.
The system configuration and the functional configuration are described above. Next, a process concerning a print will be described in accordance with a sequence flow with respect toFIG. 43 andFIG. 44.FIG. 43 andFIG. 44 are diagrams showing a sequence flow of the process concerning a print according to the fourth embodiment of the present invention. In the sequence flow shown inFIG. 43 andFIG. 44, the process is conducted among theclient PC213, the MFP-A221, the MFP-B222, and the MFP-C233.
Also, in the process in accordance with the sequence flow shown inFIG. 43 andFIG. 44, theclient PC213 obtains a document ticket, and prints out a document specified by the document ticket.
In step S801, theapplication229 of theclient PC213 sends a document ticket create request with an array of document IDs to therepository WS235. Therepository235 creates a document ticket, and sends a response with the document ticket with respect to the document ticket create request in step S802. SOAP messages used in step S801 and step S802 are the same as the SOAP messages M22 and M23 described with reference toFIG. 39 andFIG. 40.
In step S803, theclient PC213 sends a document print request to the MFP-A221. In this case, the SOAP message M21 described inFIG. 34 is used, and the document ticket, the document, and the print condition property are informed. In a case inFIG. 43, theclient PC213 requests pasting the confidential stamp as the print condition property.
When the document print request is informed to theprinting WS240, theprinting WS240 executes the process flow of the printing service described inFIG. 24. In step S804, theprinting WS240 sends a WS request send request with respect to the Web service client (WSC)225. The function shown inFIG. 25 is used for the WS request send request, and a method name showing a document get back request, a URL of therepository WS235, and the document ticket are informed to the Web service client (WSC)225.
In step S805, the Web service client (WSC)225 sends the document get back request to therepository WS235. A SOAP message for the document get back request informs the document ticket. In step S806, therepository WS235 sends a response including the document to the Web service client (WSC)225. When the Web service client (WSC)225 receives the document, the Web service client (WSC)225 sends a response including a request result with the document to theimage editing WS241 in step S807.
Referring toFIG. 44, in step S808, theprinting WS240 sends a WS request send request to the Web service client (WSC)225. The function shown inFIG. 25 is used for the WS request send request, and a URL of theimage editing WS241 and the document are informed to the Web service client (WSC)225.
In step S809, the Web service client (WSC)225 sends the document edit request to the MFP-B222. A SOAP message for the document edit request informs the document, and the edit contents showing to paste the confidential stamp.
Theimage editing WS241 edits the document, and sends an edit result notice including an edit result with the edited document to the Web service client (WSC)225 in step S810. A SOAP message M19 shown inFIG. 27 is used for the edit result notice. Next, in step S811, the Web service client (WSC)225 sends the edit result notice including an edit result with the edited document to theprinting WS240.
When theprinting WS240 receives the edited document, theprinting WS240 prints out the document, and sends a document print accept result to theclient PC213 in step S812. A SOAP message for the document print accept result is the same as the SOAP message M20 described inFIG. 28.
The fourth embodiment is described above. Next, a fifth embodiment will be described. In the fifth embodiment, thedocument management service212 and theprinting service210 are implemented in a single MFP as themulti-functional apparatus1.
Fifth EmbodimentFIG. 45 is a diagram showing a system configuration according to the fifth embodiment of the present invention. InFIG. 45, aclient PC213, aprinting service210, adocument management service212, animage editing service211, adocument DB214, and adocuments301 and302 are shown.
In a document flow inFIG. 45, thedocument301 is sent from thedocument management service212 to theimage editing service211. Thedocument302, which is edited by theimage editing service211, is sent to theprinting service210, and printed out from theprinting service210.
Next, a functional configuration will be described with reference toFIG. 46 in detail.FIG. 46 is a block diagram showing the functional configuration according to the fifth embodiment of the present invention. InFIG. 46, theclient PC213, the MFP-A221, and the MFP-B222 are shown. Theimage editing service211 is implemented in the MFP-B222.
The system configuration and the functional configuration in the fifth embodiment are described above. Next, a process for obtaining a print condition property candidate will be described in accordance with a sequence flow with reference toFIG. 47, and a process concerning a print will be described in accordance with a sequence flow with reference toFIG. 48 andFIG. 49.FIG. 47 is a diagram showing the sequence flow of the process for obtaining a print condition property according to the fifth embodiment of the present invention.FIG. 48 andFIG. 49 are diagrams showing the sequence flow of the process concerning a print according to the fifth embodiment of the present invention. InFIG. 47,FIG. 48, andFIG. 49, the processes among theclient PC213, the MFP-A221, and the MFP-B222 are shown. InFIG. 47,FIG. 48, andFIG. 49, theprinting WS240 collectively represents the Web service server (WSS)224 in the MFP-A221 and theprinting WSF226 inFIG. 46. Similarly, therepository WS235 collectively represents the Web service server (WSS)224 in the MFP-A221 and therepository WSF234 inFIG. 46.
The process for obtaining the print condition property candidate shown inFIG. 47 is a process in that theclient PC213 obtains the print condition property candidate. The process concerning the print shown inFIG. 48 andFIG. 49 is a process in that theclient PC213 obtains a document ticket and prints out the document.
The sequence flow inFIG. 47 will be described. In step S901, theclient PC213 sends a print condition property candidate obtain request, which is an obtain request for obtaining the print condition property candidate, to theprinting WS240. In step S902, theprinting WS240 sends a WS request send request, which requests sending a WS request to an indicated Web service, to the Web service client (WSC)225. In this case, a URL of the image editing WS and a method name showing an edit property candidate obtain request are informed with the WS request send request.
In step S903, the Web service client (WSC)225 sends the edit property candidate obtain request to theimage editing WS241 by a SOAP message. In response to the edit property candidate obtain request, theimage editing WS241 sends an edit property notice to the Web service client (WSC)225 by a SOAP message in step S904. Accordingly, the edit property is informed to the MFP-A221.
In step S905, the Web service client (WSC)225 sends a WS request result notice to theprinting WS240. In this case, the edit property candidate informed from the MFP-B222 is also informed to theprinting WS240. When theprinting WS240 receives the edit property candidate, theprinting WS240 generates a print condition property candidate from the print property candidate possessed in theprinting WS240 itself and the edit property candidate. This process is the same as the process described in accordance with the flowchart inFIG. 11.
After theprinting WS240 generates the print condition property candidate, theprinting WS240 sends the print condition property candidate to theclient PC213 by a SOAP message in step S906.
Accordingly, theclient PC213 can obtain the print condition property candidate.
Next, the process concerning the print will be described in accordance with the sequence flow shown inFIG. 48 andFIG. 49. In step S907, theclient PC213 sends a document ticket create request with an array of document IDs to therepository WS235. In step S908, therepository WS235 sends a response with respect to the document ticket request with the document ticket to theclient PC213.
In step S909, theclient PC213 sends a document print request to the MFP-A221. The document print request is sent by the SOAP message M21 inFIG. 34, and the document ticket and the print condition are informed. In a case inFIG. 48, theclient PC213 requests to paste the confidential stamp as the print condition property.
When theprinting WS240 receives the document print request, theprinting WS240 executes the process flow of the printing service described inFIG. 24. Theprinting WS240 sends a WS request send request to the Web service client (WSC)225 in step S910. The function shown inFIG. 25 is used for the WS request send request, and a method name showing the document edit request, edit contents indicating to paste the confidential stamp, a URL of theimage editing WS241, and the document ticket are informed to the Web service client (WSC)225.
In step S911, the Web service client (WSC)225 sends a document edit request to the MFP-B222. A SOAP message for the document edit request is the same as the SOAP message M18 shown inFIG. 26. Also, the document ticket and the edit contents are informed by the SOAP message M18.
Next, in step S912, theimage editing WS241 sends a WS request send request to the Web service client (WSC)225 in the MFP-B222 to get back (retrieve) the document from therepository WS235. The function shown inFIG. 25 is used for the WS request send request, and a URL of therepository WS235, a method name showing a document get back request, and the document ticket are informed to the Web service client (WSC)225.
In step S913, the Web service client (WSC)225 sends the document get back request with the document ticket to therepository WS235. Subsequently, the sequence flow inFIG. 49 will be described. In step S914, therepository WS235 sends a response with respect to the document get back request to the Web service client (WSC)225 of the MFP-B222. In this case, the MFP-B222 gets back the document from therepository WS235. When the Web service client (WSC)225 of the MFP-B222 receives the document, the Web service client (WSC)225 sends a response including a request result with the document to theimage editing WS241 in step S915.
Theimage editing WS241 edits the document, and sends an edit result notice showing the edit result with the edited document to the Web service client (WSC)225 of the MFP-A221 in step S916. A SOAP message, which is the same as the SOAP message M19 shown inFIG. 27, is used for the edit result notice. Next, the Web service client (WSC)225 sends the edit result notice showing the edit result with the edited document to theprinting WS240 in step S917.
When theprinting WS240 receives the edited document, theprinting WS240 prints out the document, and sends a document print accept result to theclient PC213 in step S918. The document print accept result is sent by the SOAP message M20 described inFIG. 28.
The fifth embodiment is described above. Next, a sixth embodiment will be described. In the sixth embodiment, thedocument management service212 and theimage editing service211 are implemented in a single MFP as themulti-functional apparatus1.
Sixth EmbodimentFIG. 50 is a block diagram showing a system configuration according to the sixth embodiment of the present invention. InFIG. 50, aclient PC213, aprinting service210, adocument management service212, animage editing service211, adocument DB214, anddocument301.
In a document flow inFIG. 50, thedocument301 is sent from theimage editing service211 to theprinting service210, and is printed out from theprinting service210. Accordingly, the document transmission is conducted just once.
Next, a functional configuration will be described with reference toFIG. 51 in detail. InFIG. 51, theclient PC213, the MFP-A221, and the MFP-B222 are shown. InFIG. 51, theimage editing WSF227 and therepository WSF234 are implemented in the MFP-B222. Accordingly, the printingWSF226 is implemented in the MFP-A221.
The system configuration and the functional configuration in the sixth embodiment are described above. Next, a process for obtaining a print condition property candidate and a process concerning a print will be described in accordance with sequence flows. In the sequence flows shown inFIG. 52,FIG. 53, andFIG. 54, processes, which are conducted among theclient PC213, the MFP-A221, and the MFP-B222, are shown. InFIG. 52,FIG. 53, andFIG. 54, theimage editing WS241 collectively represents the Web service server (WSS)224 and theimage editing WSF227 inFIG. 51. Similarly, therepository WS235 collectively represents the Web service server (WSS)224 and therepository WSF234 inFIG. 51.
In the process shown inFIG. 52, theclient PC213 obtains the print condition property candidate. In the process shown inFIG. 53 andFIG. 54, theclient PC213 obtains a document ticket and prints out the document.
The sequence flow for obtaining the print condition property candidate will be described with reference toFIG. 52.FIG. 52 is a diagram showing the sequence flow of the process for obtaining the print condition property candidate according to the sixth embodiment of the present invention. InFIG. 52, in step S1001, theclient PC213 sends a print condition property candidate obtain request to theprinting WS240. In step S1002, theprinting WS240 sends a WS request send request to the Web service client (WSC)225 in the MFP-A221. In this case, a URL of theimage editing WS241 and a method name showing the edit property candidate obtain request are informed to the Web service client (WSC)225 of the MFP-A221.
In step S1003, the Web service client of the MFP-A221 sends an edit property candidate obtain request to theimage editing WS241 by a SOAP message. In step S1004, in response to the edit property candidate obtain request, theimage editing WS241 sends an edit property notice to the Web service client (WSC)225 of the MFP-A221. Accordingly, the edit property is informed to the MFP-A221.
In step S1005, the Web service client (WSC)225 of the MFP-A221 sends a WS request result notice to theprinting WS240. In this case, the edit property candidate, which is informed from the MFP-B222, is also informed to theprinting WS240. When theprinting WS240 receives the edit property candidate, theprinting WS240 generates the print condition property candidate from the print property candidate possessed in theprinting WS240 itself and the edit property candidate informed from the Web service client (WSC)225. This process is the same as the process described in accordance with the flowchart shown inFIG. 11.
After theprinting WS240 generates the print condition property candidate, theprinting WS240 sends the print condition property candidate to theclient PC213 by a SOAP message in step S1006.
By the above-described process, theclient PC213 can obtain the print condition property candidate.
Next, the process concerning the print will be described with reference toFIG. 53 andFIG. 54. In step S1007, theclient PC213 sends a document ticket create request with an array of document IDs to therepository WS235. In step S1008, therepository WS235 sends a response with a document ticket with respect to the document ticket create request to theclient PC213.
In step S1009, theclient PC213 sends a document print request to the MFP-A221. The document print request is sent by the SOAP message M21 shown inFIG. 34, and the document ticket and the print condition are informed to the MFP-A221. In a case inFIG. 53, theclient PC213 requests to paste the confidential stamp as the print condition property.
When theprinting WS240 receives the document print request, theprinting WS240 executes the process flow of the printing service described inFIG. 24. Theprinting WS240 sends a WS request send request to the Web service client (WSC)225 of the MFP-A221 in step S1010. The function shown inFIG. 25 is used for the WS request send request, and a method name showing the document edit request, edit contents indicating to paste the confidential stamp, a URL of theimage editing WS241, and the document ticket are informed to the Web service client (WSC)225 of the MFP-A221.
In step S1011, theWSC225 of the MFP-A221 sends the document edit request to the MFP-B222. A SOAP message for the document edit request is the same as the SOAP message M18 shown inFIG. 26, and the document ticket and the edit contents are informed by the SOAP message.
Next, in step S1012, theimage editing WS241 sends a document get back request with the document ticket to therepository WS235 in the MFP-B222 in order to get back (retrieve) the document from therepository WS235.
Subsequently, referring toFIG. 54, in step S1013, therepository WS235 sends a response including a request result and the document to theimage editing WS241.
Theimage editing WS241 edits the document, and sends an edit result with the edited document to the Web service client (WSC)225 of the MFP-A221 in step S1014. The edit result is sent by the SOAP message M19 shown inFIG. 27. Next, in step S1015, the Web service client (WSC)225 sends the edit result with the edited document to theprinting WS240.
When theprinting WS240 receives the edited document, theprinting WS240 prints out the edited document and sends a document print accept result to theclient PC213 in step S1016. The document print accept result is sent by the SOAP message M20 described inFIG. 28.
The sixth embodiment is described above. Next, a seventh embodiment will be described. In the seventh embodiment, theprinting service210 and theimage editing service211 are implemented in a single MFP as themulti-functional apparatus1.
Seventh EmbodimentFIG. 55 is a block diagram showing a system configuration according to the seventh embodiment of the present invention. InFIG. 55, aclient PC213, aprinting service210, adocument management service212, animage editing service211, adocument DB214, and adocument301 are shown.
In a document flow inFIG. 55, thedocument301 is sent from thedocument management service212 to theimage editing service211, and an edited document as thedocument301 is printed out from theprinting service210. Accordingly, the document transmission is conducted just once.
Next, a functional configuration will be described with reference toFIG. 56 in detail. InFIG. 56, theclient PC213, the MFP-A221, and the MFP-B222 are shown. InFIG. 56, the printingWSF226 as theprinting service210 and theimage editing WSF227 as theimage editing service211 are implemented in the MFP-A221. Moreover, therepository WSF234 as the repository service is implemented in the MFP-B222.
The system configuration and the functional configuration in seventh embodiment are described above. Next, a process for obtaining a print condition property candidate and a process concerning a print will be described in accordance with sequence flows. In the sequence flows shown inFIG. 57,FIG. 58, andFIG. 59, processes, which are conducted among theclient PC213, the MFP-A221, and the MFP-B222, are shown. InFIG. 57,FIG. 58, andFIG. 59, theprinting WS240 collectively represents the Web service server (WSS)224 and theprinting WSF226 in the MFP-A221 inFIG. 56. Similarly, theimage editing WS241 collectively represents the Web service server (WSS)224 and theimage editing WSF227 in the MFP-A221 inFIG. 56.
In the process shown inFIG. 57, theclient PC213 obtains the print condition property candidate. In the process shown inFIG. 58 andFIG. 59, theclient PC213 obtains a document ticket and prints out the document.
The sequence flow for obtaining the print condition property candidate will be described with reference toFIG. 57.FIG. 52 is a diagram showing the sequence flow of the process for obtaining the print condition property candidate according to the seventh embodiment of the present invention. InFIG. 57, in step S1101, theclient PC213 sends a print condition property candidate obtain request to theprinting WS240. In step S1102, theprinting WS240 sends a WS request send request to theimage editing WS241. In response to the WS request send request, theimage editing WS241 informs an edit property notice to theprinting WS240 in step S1103.
When theprinting WS240 receives the edit property candidate, theprinting WS240 generates the print condition property candidate from the print property possessed in theprinting WS240 itself and the edit property candidate informed from theimage editing WS241. This process is conducted as described in accordance with the flowchart shown inFIG. 11.
After theprinting WS240 generates the print condition property candidate, theprinting WS240 sends the print condition property candidate by a SOAP message to theclient PC213 in step S1104.
By the above-described process, theclient PC213 can obtain the print condition property candidate.
Next, the process concerning the print will be described with reference toFIG. 58 andFIG. 59. In step S1105, theclient PC213 sends a document ticket create request with an array of document IDs to therepository WS235. In step S1106, therepository WS235 sends a response with a document ticket with respect to the document ticket create request to theclient PC213.
In step S1107, theclient PC213 sends a document print request to the MFP-A221. The document print request is sent by the SOAP message M21 shown inFIG. 34, and the document ticket and the print condition are informed to the MFP-A221. In a case inFIG. 58, theclient PC213 requests to paste the confidential stamp as the print condition property.
When theprinting WS240 receives the document print request, theprinting WS240 executes the process flow of the printing service described inFIG. 24. In step S1108, theprinting WS240 sends a document edit request to theimage editing WS241. The document edit request informs the document ticket and the edit contents.
Next, in step S1109, theimage editing WS241 sends a WS request send request to the Web service client (WSC)225 in order to get back (retrieve) the document from therepository WS235. The function shown inFIG. 25 is used for the WS request send request, and a URL of therepository WS235, a method name showing a document get back request, and the document ticket to the Web service client (WSC)225 of the MFP-A221. The Web service client (WSC)225 sends the document get back request with the document ticket to the repository WS235 (step S1110).
Subsequently, referring toFIG. 54, in step S1111, therepository WS235 sends a response including a request result and the document with respect the document get back request. In this case, the document is returned to the MFP-A221. When the Web service client (WSC)225 receives the document, the Web service client (WSC)225 sends a response including a request result and the document in step S1112.
Theimage editing WS241 edits the document, and sends an edit result notice showing an edit result with the edited document to theprinting WS240 in step S1113. When theprinting WS240 receives the edited document, theprinting WS240 prints out the edited document, and sends a document print accept result to theclient PC213 in step S1114. The document print accept result is sent by the SOAP message M20 described inFIG. 28.
The seventh embodiment is described above. Next, an eighth embodiment will be described. In the eighth embodiment, all three services: aprinting service210, adocument management service212, and animage editing service211, are implemented in a single MFP as themulti-functional apparatus1.
Eighth EmbodimentFIG. 60 is a block diagram showing a system configuration according to the eighth embodiment of the present invention. InFIG. 60, theclient PC213, theprinting service210, thedocument management service212, theimage editing service211, thedocument DB214, and thedocument301 are shown.
In a document flow inFIG. 60, since the document is stored in an MFP that edits and/or prints out the document, the document transmission is not conducted.
Next, a functional configuration will be described with reference toFIG. 61 in detail. InFIG. 61, theclient PC213 and the MFP-A221 are shown. InFIG. 61, the printingWSF226 as theprinting service210, theimage editing WSF227 as theimage edit service211, and therepository WSF234 as thedocument management service212 are implemented in the MFP-A221.
The system configuration and the functional configuration in eighth embodiment are described above. a process for obtaining a print condition property candidate and a process concerning a print will be described in accordance with sequence flows. In the sequence flows shown inFIG. 62,FIG. 63, andFIG. 64, processes, which are conducted among theclient PC213, and the MFP-A221, are shown. InFIG. 62,FIG. 63, andFIG. 64, theimage editing WS241 collectively represents the Web service server (WSS)224 and theimage editing WSF227 in the MFP-A221 inFIG. 61. Similarly, therepository WS235 collectively represents the Web service server (WSS)224 and therepository WSF234 inFIG. 61. Moreover, theprinting WS240 collectively represents the Web service server (WSS)224 and theprinting WSF226 in the MFP-A221 inFIG. 61.
In the process shown inFIG. 62, theclient PC213 obtains the print condition property candidate. In the process shown inFIG. 63 andFIG. 64, theclient PC213 obtains a document ticket and prints out the document.
The sequence flow for obtaining the print condition property candidate will be described with reference toFIG. 62.FIG. 62 is a diagram showing the sequence flow of the process for obtaining the print condition property candidate according to the eighth embodiment of the present invention. InFIG. 62, in step S1201, theclient PC213 sends a print condition property candidate obtain request to theprinting WS240. In step S1102, theprinting WS240 sends an edit property candidate obtain request to theimage editing WS241. In response to the edit property candidate obtain request, theimage editing WS241 informs an edit property notice to theprinting WS240 in step S1203.
When theprinting WS240 receives the edit property candidate, theprinting WS240 generates the print condition property candidate from the print property possessed in theprinting WS240 itself and the edit property candidate informed from theimage editing WS241. This process is conducted as described in accordance with the flowchart shown inFIG. 11.
After theprinting WS240 generates the print condition property candidate, theprinting WS240 sends the print condition property candidate by a SOAP message to theclient PC213 in step S1204.
By the above-described process, theclient PC213 can obtain the print condition property candidate.
Next, the process concerning the print will be described with reference toFIG. 63 andFIG. 64. In step S1205, theclient PC213 sends a document ticket create request with an array of document IDs to therepository WS235. In step S1206, therepository WS235 sends a response with a document ticket with respect to the document ticket create request to theclient PC213.
In step S1207, theclient PC213 sends a document print request to the MFP-A221. The document print request is sent by the SOAP message M21 shown inFIG. 34, and the document ticket and the print condition are informed to the MFP-A221. In a case inFIG. 63, theclient PC213 requests to paste the confidential stamp as the print condition property.
When theprinting WS240 receives the document print request, theprinting WS240 executes the process flow of the printing service described inFIG. 24. In step S1208, theprinting WS240 sends a document edit request to theimage editing WS241. The document edit request informs the document ticket and the edit contents.
Next, in step S1209, theimage editing WS241 sends a document ID obtain request included in the document ticket to therepository WS235 in order to get back (retrieve) the document from therepository WS235. Theimage editing WS241 obtains the document ID since the document is stored in the MFP-A221 where theimage editing WS241 is implemented. Theimage editing WS241 can edit the document corresponding to the document ID by obtaining the document ID.
Referring toFIG. 64, in step S1210, therepository WS235 sends a document ID to theimage editing WS241. Theimage editing WS241 edits the document and sends an edit result with an edited document to the printing WS240 (step S1211).
When theprinting WS240 receives the edited document, theprinting WS240 prints out the edited document and sends a document print accept result to theclient PC213 in step S1212. The document print accept result is sent by the SOAP message described inFIG. 28.
The eighth embodiment is described above. Thus, the explanations from the first embodiment to the eighth embodiment are completed. From the first embodiment to the eighth embodiment, an outputting service part, an output condition property candidate obtain request receiving part, an output condition property candidate obtaining part, and an output condition property candidate obtaining part correspond to theprinting WSF226. An editing service part corresponds to theimage editing WSF227. A Web service part corresponds to a Web service including the Web service server (WSS)224, the printingWSF226, an theimage editing WSF227.
An output service client part corresponds to theprinting WSF226. An edit service client corresponds to theimage editing WSF227. A Web client part corresponds to a Web service client including the Web service client (WSC)225, the printingWSF226, and the image editing WSF.
FIG. 65 is a diagram showing a configuration in that a single Web service client (WSC) can use a plurality of Web services (WS), according to the present invention. Referring toFIG. 65, the configuration will be described in detail. The MFP-A221 includes theprinting WS240 and theimage editing WS241. Each of theprinting WS240 and theimage editing WS241 functions as a Web service server for Web service clients (WS clients)503 other than the MFP-A221. Even in this case, both theprinting WS240 and theimage editing WS241 can use the single Web service client (WSC)225, and each of theprinting WS240 and theimage editing WS241 can use therepository WS235 other than the MFP-A221 through theWeb service client225.
FIG. 66 is a diagram showing another configuration in that a single Web service can use a plurality of Web service client (WSC), according to the present invention. InFIG. 66, the MFP-B222, the Web service client (WS client)504, aUPnP repository WS507, and aBMLinkS repository WS508 are shown.
BMLinkS is a standard specification defining a search of OA devices, a data format for the OA devices to send and receive data, and a control of the OA devices.
In order to support theUPnP repository WS507 and theBMLinkS repository WS508, which have a different protocol each other, a WSC_A505 for supporting a UPnP protocol and aWSC_B506 for supporting a BMLinkS protocol are implemented in the MFP-B222. Accordingly, for example, theprinting WS240 being a server of theWS client504 can use any one of theUPnP repository WS507 and theBMLinkS repository WS508. In addition, by implementing a Web service client (WSC) to support each version of the SOAP, it is possible to support each version of the SOAP.
FIG. 67 is a diagram showing a configuration formed by the MFP-A described inFIG. 65 and the MFP-B described inFIG. 66, according to the present invention. InFIG. 67, explanations of the parts described above will be omitted.
In the MFP-A221 shown inFIG. 67, theprinting WSF226 and theimage editing WSF227 can use the Web service client (WSC)225 being a single Web service client. In addition, in the MFP-B222, theprinting WS226 can use two Web service clients: a Webservice A client501 and a Webservice B client502. As described above, the Web service client (WSC) may be implemented for each specification of the Web service parts.
In the present invention, the output property includes at least one of a capability of setting copies of the document, a capability of setting a sheet size to print out, a capability of printing both sides, a capability of collating copies, a capability of indicating a tray, a capability of printing multi-pages of the document on a single sheet, a capability of printing the document by a variable magnification, a capability of indicating a partial area in the document to print out, a capability of indicating a color print for the document, and a capability of setting a finisher.
In the present invention, the edit property includes as contents of the edit property, at lease one of a capability of pasting a stamp to the document, a capability of a drawing operation, a capability of deleting, copying, pasting, moving, or converting a color with respect to an indicated area, a capability of continuously editing multi-pages, and a capability of eliminating a stain of a ground color.
The present invention is not limited to the specifically disclosed embodiments, and variations and modifications may be made without departing from the scope of the present invention.
The present application is based on the Japanese Priority Applications No. 2003-376499 filed on Nov. 6, 2003, No. 2003-376500 filed on Nov. 6, 2003, No. 2003-376501 filed on Nov. 6, 2003, No. 2004-318292 filed on Nov. 1, 2004, No. 2004-318293 filed on Nov. 1, 2004, and No. 2004-318294 filed on Nov. 1, 2004, the entire contents of which are hereby incorporated by reference.