US20130132486A1 - Service processing system and service processing method - Google Patents

Service processing system and service processing method Download PDF

Info

Publication number
US20130132486A1
US20130132486A1 US13/745,014 US201313745014A US2013132486A1 US 20130132486 A1 US20130132486 A1 US 20130132486A1 US 201313745014 A US201313745014 A US 201313745014A US 2013132486 A1 US2013132486 A1 US 2013132486A1
Authority
US
United States
Prior art keywords
processing
script
service
information
document
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US13/745,014
Inventor
Yuji Hikawa
Yukio Tajima
Kazuko Kirihara
Akihiro Enomoto
Hidekazu Ozawa
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujifilm Business Innovation Corp
Original Assignee
Fuji Xerox Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fuji Xerox Co Ltd filed Critical Fuji Xerox Co Ltd
Priority to US13/745,014 priority Critical patent/US20130132486A1/en
Publication of US20130132486A1 publication Critical patent/US20130132486A1/en
Priority to US15/019,542 priority patent/US10291683B2/en
Priority to US16/372,755 priority patent/US20190230145A1/en
Priority to US16/372,737 priority patent/US11201905B2/en
Priority to US17/525,500 priority patent/US11546407B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/02Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60PVEHICLES ADAPTED FOR LOAD TRANSPORTATION OR TO TRANSPORT, TO CARRY, OR TO COMPRISE SPECIAL LOADS OR OBJECTS
    • B60P1/00Vehicles predominantly for transporting loads and modified to facilitate loading, consolidating the load, or unloading
    • B60P1/04Vehicles predominantly for transporting loads and modified to facilitate loading, consolidating the load, or unloading with a tipping movement of load-transporting element
    • B60P1/26Means for controlling movement of tailboards or sideboards
    • B60P1/273Providing interdependence between tipping movement and the latching or unlatching of a freely-swingable tailboard or sideboard
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/04817Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance using icons
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/04845Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range for image manipulation, e.g. dragging, rotation, expansion or change of colour
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/0486Drag-and-drop
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1097Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N1/00Scanning, transmission or reproduction of documents or the like, e.g. facsimile transmission; Details thereof
    • H04N1/0035User-machine interface; Control console
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N1/00Scanning, transmission or reproduction of documents or the like, e.g. facsimile transmission; Details thereof
    • H04N1/0035User-machine interface; Control console
    • H04N1/00405Output means
    • H04N1/00477Indicating status, e.g. of a job
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N1/00Scanning, transmission or reproduction of documents or the like, e.g. facsimile transmission; Details thereof
    • H04N1/0035User-machine interface; Control console
    • H04N1/00501Tailoring a user interface [UI] to specific requirements
    • H04N1/00503Customising to a particular machine or model, machine function or application
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N1/00Scanning, transmission or reproduction of documents or the like, e.g. facsimile transmission; Details thereof
    • H04N1/00912Arrangements for controlling a still picture apparatus or components thereof not otherwise provided for
    • H04N1/00957Compiling jobs, e.g. for batch processing
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60YINDEXING SCHEME RELATING TO ASPECTS CROSS-CUTTING VEHICLE TECHNOLOGY
    • B60Y2200/00Type of vehicle
    • B60Y2200/10Road Vehicles
    • B60Y2200/14Trucks; Load vehicles, Busses
    • B60Y2200/142Heavy duty trucks
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60YINDEXING SCHEME RELATING TO ASPECTS CROSS-CUTTING VEHICLE TECHNOLOGY
    • B60Y2200/00Type of vehicle
    • B60Y2200/10Road Vehicles
    • B60Y2200/14Trucks; Load vehicles, Busses
    • B60Y2200/146Silo or fluid transporting vehicles

Definitions

  • the present invention relates to a service processing system in which a service for performing specified multiple processings of document data is processed in a cooperative manner on a network, and a service processing method.
  • a network system is proposed in which a scanner, a facsimile machine (hereinafter referred to as a FAX), a copying machine, a composite machine in which these are combined, a personal computer, a mail server and the like are mutually connected to each other through a network, so that paper documents and electronic information are shared.
  • a FAX facsimile machine
  • a composite machine in which these are combined
  • a personal computer a mail server and the like
  • the network system as stated above is configured such that for example, a document file is captured from an input system such as a scanner for reading a manuscript or a paperless FAX, and is processed by a processing system of image manipulation, character recognition or the like, and then, the document file is delivered to the outside through an output system such as a printer or a mail server.
  • an input system such as a scanner for reading a manuscript or a paperless FAX
  • a processing system of image manipulation, character recognition or the like the document file is delivered to the outside through an output system such as a printer or a mail server.
  • the capture of the document file the manipulation processing of the captured data, and the delivery after the manipulation processing are independently carried out.
  • the operator uses a client terminal for collectively managing the above processing devices to open, on a display part, instruction windows relating to the capture of the document file, the manipulation processing of the captured data, and the delivery processing after the manipulation processing, and must perform specified input operations, and therefore, the operation efficiency has been very poor.
  • a work flow system is conventionally introduced in which a series of processings from input to output are linked on a network and are carried out in previously defined order.
  • the present invention has been made in view of the above circumstance and provides a service processing system and a service processing method, in which in a case where a service for performing specified multiple processings of document data as one job is processed in a cooperative manner on a network, a service processing state is exhibited in a proper notice form in each job unit and in each processing unit in the job, so that the processing state can be properly recognized from the viewpoint of accounting, security and privacy.
  • a service processing system in which a service for performing specified multiple processings of document data is processed in a cooperative manner on a network, the system includes: an indication data creation part for creating, for each job as a unit of the associated processings, indication data to indicate a processing procedure of the job, and notice condition data to indicate a notice event and a notice form thereof at each processing stage in the job; a management control part for managing progress of each of the processings in the job on the basis of contents recited in the indication data created by the indication data creation part; and a notice part for sending a notice during the progress of each of the processings in the job on the basis of contents recited in the notice condition data.
  • a service processing method in which a service for performing specified multiple processings of document data is processed in a cooperative manner on a network, the method includes the steps of: creating, for each job as a unit of the associated processings, indication data to indicate a processing procedure of the job, and notice condition data to indicate a notice event and a notice form thereof at each processing stage in the job; managing progress of each of the processings in the job on the basis of contents recited in the created indication data; and sending a notice during the progress of each of the processings in the job on the basis of contents recited in the notice condition data.
  • a job management device for managing progress of each of processings in a service processing system in which a service for performing specified multiple processings of document data is processed in a cooperative manner on a network
  • the device includes: an indication data creation part for creating, for each job as a unit of the associated processings, indication data to indicate a processing procedure of the job, and notice condition data to indicate a notice event and a notice form thereof at each processing stage in the job; a management control part for managing progress of each of the processings in the job on the basis of contents recited in the indication data created by the indication data creation part; and a notice part for sending a notice during the progress of each of the processings in the job on the basis of contents recited in the notice condition data.
  • a job management device for managing progress of each of processings in a service processing system in which a service for performing specified multiple processings of document data is processed in a cooperative manner on a network
  • the device includes: an indication data reception part for receiving, for each job as a unit of the associated processings, indication data to indicate a processing procedure of the job, and notice condition data to indicate a notice event and a notice form thereof at each processing stage in the job; a management control part for managing progress of each of the processings in the job on the basis of contents recited in the indication data received by the indication data reception part; and a notice part for sending a notice during the progress of each of the processings in the job on the basis of contents recited in the notice condition data.
  • a service processing device for processing a service in a service processing system in which the service for performing specified multiple processings of document data is processed in a cooperative manner on a network
  • the device includes: an indication data reception part for receiving, for each job as a unit of the associated processings, indication data to indicate a processing procedure of the job, and notice condition data to indicate a notice event and a notice form thereof at each processing stage in the job; a management control part for managing progress of each of the processings in the job on the basis of contents recited in the indication data received by the indication data reception part; and a notice part for sending a notice during the progress of each of the processings in the job on the basis of contents recited in the notice condition data.
  • FIG. 1 is a block diagram showing the outline of a document processing system according to a first embodiment of the invention
  • FIG. 2 is a block diagram for explaining the mutual relation of service processing devices configuring the document processing system according to the first embodiment of the invention
  • FIG. 3 is a schematic view showing a structure of I/F information according to the first embodiment of the invention.
  • FIG. 4 is a front view of a script creation screen as a GUI screen for defining a job flow according to the first embodiment of the invention
  • FIG. 5 is a schematic view showing a script formed in an XML format according to the first embodiment of the invention.
  • FIG. 6 is a front view of a script creation screen displaying a notice processing condition setting screen according to the first embodiment of the invention
  • FIG. 7 is a front view of a script creation screen when a service of setting a notice processing condition according to the first embodiment of the invention is selected;
  • FIG. 8 is a front view of a script creation screen after the notice processing condition according to the first embodiment of the invention is set;
  • FIG. 9 is a flowchart showing a processing procedure of a client terminal and a script creation server at the time of script creation according to the first embodiment of the invention.
  • FIG. 10 is a flowchart showing a processing of the client terminal, a script management server and a cooperative processing server according to the first embodiment of the invention
  • FIG. 11 is an explanatory view showing an example of a service cooperative processing selection screen 110 displaying a script list according to the first embodiment of the invention
  • FIG. 12 is a flowchart showing a notice processing selection control routine interrupting at the time of notice event occurrence according to the first embodiment of the invention.
  • FIG. 13 is a block diagram showing the mutual relation of service processing devices configuring a document processing system according to a second embodiment.
  • FIG. 1 is a block diagram showing the configuration of a document processing system 1 according to a first embodiment of the invention.
  • the document processing system 1 is such that various services and applications are connected through a network 5 .
  • the service is a function usable on a document in accordance with a request from the outside.
  • the service is equivalent to, for example, copy, print, scan, facsimile transmission and reception, mail delivery, storing into repository and readout from repository, OCR (Optical Character Recognition) processing, noise removal processing, and the like, and is not particularly limited.
  • the document processing system 1 specifically includes a client terminal 10 provided with a user interface and for linking plural services with each other to indicate a desired processing of a user, a service retrieval server 20 for retrieving a desired service of the user, a script creation server 30 for creating a script from information relating to the service cooperation indicated by the client terminal 10 , a script management server 40 for managing the script, and a cooperative processing server 50 for executing a cooperative processing of the respective services in accordance with the script.
  • the document processing system 1 includes an image processing device 61 for performing an image processing such as a noise removal processing of an image document, an image rotation processing, an OCR processing, and binding of images, a document management server 62 for managing documents, a document delivery server 63 for delivering documents, a first service processing device 64 for performing a first service processing, and a second service processing device 65 for performing a second service processing.
  • an image processing device 61 for performing an image processing such as a noise removal processing of an image document, an image rotation processing, an OCR processing, and binding of images
  • a document management server 62 for managing documents
  • a document delivery server 63 for delivering documents
  • a first service processing device 64 for performing a first service processing
  • a second service processing device 65 for performing a second service processing.
  • the document processing system 1 has the configuration in which the plural servers for performing specific service processings are connected through the network 5 , as long as the plural services are connected through the network 5 , the configuration is not particularly limited.
  • the script is data containing, in a case where a series of processings are decomposed into plural functional processings, information expressing a relation among the respective functions, interface (I/F) information for invoking the respective functions, and information for configuring a graphical user interface (GUI) relating to the series of processings.
  • I/F interface
  • GUI graphical user interface
  • FIG. 2 is a block diagram for explaining the mutual relation of the respective service processing devices configuring the document processing system 1 .
  • Each of the service processing devices stores I/F information expressing the contents of the service provided by itself.
  • FIG. 3 is a view showing the structure of the I/F information.
  • the I/F information is constituted by ⁇ Service Class>, ⁇ Service Name>, ⁇ Service Icon>, ⁇ Service Location Information>, ⁇ Input>, ⁇ Output>, ⁇ Parameter Restriction Rules>, ⁇ Service Location>, ⁇ Method Name>, ⁇ Invocation Scheme>, ⁇ Implicit Elements> and ⁇ Notice Information>.
  • the ⁇ Service Class> is a class of the service provided by the service processing device. Incidentally, what is previously defined is used as the ⁇ Service Class> and is equivalent to, for example, scan, print, repository, flow and the like.
  • the ⁇ Service Name> is a name of the service provided by the service processing device.
  • the ⁇ Service Icon> is position information of an icon displayed on the GUI of the client terminal 10 .
  • the ⁇ Service Location Information> is a URL which the script creation server 30 uses for acquiring the I/F information.
  • the ⁇ Input> is an input to the service.
  • the ⁇ Output> is an output from the service.
  • the ⁇ Parameter Restriction Rules> are restriction rules applied to the ⁇ Input> and the ⁇ Output>.
  • the ⁇ Service Location> is position information when the service is actually used.
  • the ⁇ Method Name> is a provision method of a service processing.
  • the ⁇ Invocation Scheme> is a scheme for invoking and starting the service processing.
  • SOAP Simple Object Access Protocol
  • SMTP Simple Mail Transfer Protocol
  • the ⁇ Implicit Elements> are not data which are explicitly delivered as the output to a later stage processing, however, they are data which can be consulted at the later stage processing.
  • the ⁇ Notice Information> is information concerning the progress state of a processing in each service, and for example, a notice form as described below is recited.
  • the client terminal 10 has the function of a graphical user interface (GUI) for performing a screen display and for performing a specific operation in order to instruct the creation of a script or to select a script to be invoked.
  • GUI graphical user interface
  • the service retrieval server 20 retrieves a service corresponding to a retrieval condition from plural services connected to the network 5 .
  • the service retrieval server 20 previously stores part of the I/F information (hereinafter referred to as “partial I/F information”) (see FIG. 3 ) of various service processing devices, such as the image processing device 61 , the document management server 62 , the document delivery server 63 , the first service processing device 64 , and the service processing device 65 .
  • the partial I/F information is the information of ⁇ Service Class>, ⁇ Service Name>, ⁇ Service Location Information>, ⁇ Input>, and ⁇ Output> in the elements of the I/F information.
  • the service retrieval server 20 uses the partial I/F information of the respective service processing devices to retrieve the service. For example, when a service similar to a specific service is retrieved, the service retrieval server 20 may retrieve services which are coincident to each other in the ⁇ Service Class>, or may retrieve services which are coincident to each other in the ⁇ Input> and ⁇ Output>, or may retrieve services which are coincident to each other in all of these.
  • the script creation server 30 acquires the I/F information from the respective service processing devices, and creates the script for linking the services provided by the respective service processing devices with each other.
  • the script creation server 30 specifically executes the following processing to create the script.
  • the script creation server 30 requests specific service processing devices dispersed on the network 5 to transmit the I/F information relating to the respective services on the basis of the ⁇ Service Location Information>.
  • the script creation server 30 instructs the service retrieval server 20 to retrieve another service processing device performing the same service as the specific service processing device. Then, the script creation server 30 has only to acquire the ⁇ Service Location Information> of the another service processing device from the service retrieval server 20 .
  • the script creation server 30 manages the retrieval result from the service retrieval server 20 and the I/F information received from the respective service processing devices.
  • the script creation server 30 creates an HTML file which becomes a GUI screen for defining a job flow on the basis of the I/F information acquired from the respective service processing devices.
  • the script creation server 30 transmits the HTML file which becomes the GUI screen to the client terminal 10 .
  • FIG. 4 is a view showing a script creation screen 100 as the GUI screen for defining the job flow.
  • the script creation screen 100 is constituted by a service window 101 , a flow window 102 , a logic window 103 , and a property window 104 .
  • the service window 101 displays various usable service processing devices.
  • the logic window 103 displays the job flow showing cooperation patterns among the services.
  • the property window 104 displays detailed setting parameters of respective icons displayed on the service window 101 and the logic window 103 .
  • the user can define the job flow on the flow window 102 by dragging and dropping icons of the service window 101 and icons of the logic window 103 to the flow window 102 .
  • the user further edits the contents displayed on the property window 104 and can set services and logics in detail.
  • a notice condition menu 200 B is set on a tool menu 200 A of a pull-down menu 200 of the script creation screen 100 .
  • the notice condition menu 200 B is a menu which functions when any one of the icons in the service window 101 , which was dragged and dropped on the flow window 102 , is selected (reverse display) ( FIG. 7 shows, as an example, a state in which a FAX icon is selected).
  • a notice setting screen 202 as shown in FIG. 6 is displayed.
  • Two check boxes of “set” and “not set” are provided on the notice setting screen 202 , and it is possible to select whether or not a notice condition is especially set for the selected icon (service).
  • a condition item setting screen 208 in the notice setting screen 202 becomes effective, notice information of the selected icon is displayed, and the notice information is successively selected, so that a special notice condition as a script is inputted (set) to a notice condition setting screen 210 .
  • the notice information For example, in the case where the selected icon is FAX, as the notice information, “Transmission report is outputted at the time of transmission completion”, “Notice is sent when unreadable document data exists”, and the like are displayed as a list. As one of them, “Transmission report is outputted at the time of transmission completion” is selected, and as the notice condition added to the indication data, “Mail transmission is made to client terminal at the time of transmission completion (report output is not made)” can be set.
  • the notice condition may be set in a job unit (that is, common to plural services), not for each service (FAX, etc.).
  • the notice condition is set in the document form, however, similarly to the flow window 102 (GUI), it is internally processed in a program language.
  • a mark (“#” mark with a circle in FIG. 8 ) 212 indicating that a special notice condition is set is attached to the pertinent icon in the flow window 102 , so that it can be judged whether or not the special notice condition is set.
  • the client terminal 10 transmits the job flow information defined by the operation of the user to the script creation server 30 in accordance with a CGI (Common Gateway Interface) format.
  • CGI Common Gateway Interface
  • the script creation server 30 creates the script defining the contents of the processing requested to the respective services, input parameters, the way (job flow) of cooperation of the respective services, and information for specifying a document as a processing object, such as a document name and storage location information, on the basis of the job flow information relating to the indication of the service cooperation from the user and the I/F information of the respective services.
  • the script is constituted by files of an XML format.
  • FIG. 5 is a view showing the script composed in the XML format. Since the cooperative processing itself of the plural services is also regarded as one service, the script has the structure in which ⁇ Flow> is added to the I/F information shown in FIG. 3 .
  • the ⁇ Flow> is an element for describing the cooperation between services and includes ⁇ Invoke>, control structure and logic operation, elements such as ⁇ if> for sending a notice, and information for specifying a document as a processing object.
  • the ⁇ Invoke> expresses a specific method of a service processing device, and executes invocation of a service.
  • the element of the ⁇ Invoke> includes ⁇ Map> expressing the position information of a parameter, and ⁇ Method> of an invocation method name.
  • the ⁇ if>, ⁇ and>, ⁇ eq> and ⁇ gt> expressing the control structure, the logic operation and the like carry out condition branching at the time of the cooperative processing and the adjustment of parameters delivered between the services.
  • the script describes all information relating to the control of the cooperative processing of the services in the element of the ⁇ flow>.
  • the cooperative processing itself expressed by the script is also regarded as one service.
  • the script is not limited to the structure shown in FIG. 5 , and it is sufficient if the respective services can be linked with each other.
  • the script creation server 30 transmits the script of the XML format as stated above to the script management server 40 . Besides, in the case where the execution of the service cooperative processing is instructed by the user, the script creation server 30 may directly transmit the script to the cooperative processing server 50 .
  • the script management server 40 holds the script transmitted from the script creation server 30 , and transmits the script to the cooperative processing server 50 in accordance with the request from the client terminal 10 .
  • the cooperative processing server 50 is a server for interpreting and executing the specified script.
  • the cooperative processing server 50 interprets the script, sequentially invokes the respective service processing devices, such as the image processing device 61 , the document management server 62 , and the document delivery server 63 in accordance with the order and the use method described in the script, and executes the cooperative processing.
  • the cooperative processing server 50 stores the state of the cooperative processing under execution and the information of the result of the completed cooperative processing, and notifies the state of the cooperative processing and the result in accordance with a request from the outside.
  • the cooperative processing server 50 interprets the script, and when making a request to the respective service processing devices, the cooperative processing server creates individual indication information having the contents of the processing request, input parameters and information for specifying the document as the processing object.
  • the cooperative processing server 50 may describe the relation to a processing before or after a processing performed by the respective service processing devices, or the processing request may be made in an information exchange form intrinsic to each service processing device, not the form of the script.
  • the image processing device 61 is a computer in which a software program for performing an image processing function is installed.
  • the image processing device 61 performs the processing of the document on the basis of the contents of the service processing request contained in the processing request from the cooperative processing server 50 , the input parameters, and the information of the processing object document. Besides, the image processing device 61 notifies the service retrieval server 20 of the partial I/F information at the time of invocation. Further, in accordance with the request from the script creation server 30 , the image processing device 61 transmits the I/F information expressing the use method of the image processing service. The I/F information is used when the script is created.
  • the document management server 62 has a document storage function.
  • the document management server 62 carries out the storage, retrieval, and readout of the document, the change of attribute relating to the document, and various processings on the basis of the information contained in the request from the cooperative processing server 50 .
  • the document management server 62 notifies the service retrieval server 20 of the partial I/F information at the time of invocation. Further, the document management server 62 transmits the I/F information expressing the use method of the document management service in accordance with the request from the script creation server 30 .
  • the document delivery server 63 has functions to store the acquired document into the indicated document management server, to perform mail transmission or FAX transmission to an indicated transmission destination, and to perform a print output processing to an indicated printer. In accordance with the request from the cooperative processing server 50 , the document delivery server 63 performs the delivery processing of the document on the basis of the document indicated by the client terminal 10 and the information of the delivery destination. Besides, the document delivery server 63 notifies the service retrieval server 20 of the partial I/F information at the time of invocation. Further, the document delivery server 63 transmits the I/F information expressing the use method of the document delivery service in accordance with the request from the script creation server 30 .
  • the first service processing device 64 is a device for performing a specific service processing relating to the document in accordance with the instruction from the outside.
  • the first service processing device 64 carries out the service processing to be executed by itself on the basis of information such as the contents of the processing request from the cooperative processing server 50 , the input parameters, and the information for specifying the document as the processing object.
  • the first service processing device 64 notifies the service retrieval server 20 of the partial I/F information at the time of invocation.
  • the first service processing device 64 transmits the I/F information expressing the use method of the service processing in accordance with the request from the script creation server 30 .
  • the second service processing device 65 operates similarly to the first service processing device 64 except for the contents of the service processing.
  • the service processing devices notify the service retrieval server 20 of the partial I/F information containing the information expressing the respective service summaries and addresses at the invocation processing.
  • the service retrieval server 20 stores the partial I/F information transmitted from the respective service processing devices such as the image processing device 61 , the document management server 62 and the document delivery server 63 .
  • the service retrieval server 20 can perform retrieval by using the partial I/F information.
  • FIG. 9 is a flowchart showing a processing procedure of the client terminal 10 and the script creation server 30 at the time of creating the script.
  • the client terminal 10 accesses a URL (Uniform Resource Locator) of an HTML file created for the user interface screen provided by the script creation server 30 through an installed browser in accordance with the operation of the user (step 250 ).
  • a URL Uniform Resource Locator
  • the script creation server 30 transmits the HTML file of the user interface screen to the client terminal 10 in accordance with the browse request from the client terminal 10 (step 252 ).
  • the client terminal 10 displays the user interface screen on the basis of the HTML file transmitted from the script creation server 30 (step 254 ). At this time, the user can define a desired service cooperation job flow by using the user interface screen displayed on the client terminal 10 .
  • the client terminal 10 judges whether or not the job flow is defined through the user interface screen, and stands by until the job flow is defined (step 256 ).
  • step 258 it is judged whether or not a notice condition definition exists.
  • the procedure proceeds to step 260 , and it is added as an additional element of the definition of the job flow so that this specified notice condition becomes effective in the pertinent service.
  • the setting of the notice condition is performed in the following procedure.
  • a service is selected from the job flow defined on the completed flow window 102 in order to set the notice condition. For example, in the case where FAX is selected, a pointer is placed on the FAX icon and selection is made by a specific operation (for example, one click of a mouse). The selected FAX icon is highlighted (see FIG. 7 ).
  • the notice processing condition menu 200 B is selected from the tool menu 200 A of the pull-down menu 200 .
  • the notice setting screen 202 shown in FIG. 6 is displayed.
  • the condition item setting screen 208 in the notice setting screen 202 becomes effective, the notice condition of the selected icon is displayed, and notice conditions are successively selected, so that a special notice condition as a script is inputted (set) to the notice condition setting screen 210 .
  • the “#” mark 212 indicating that the special notice condition is set is attached to the icon in the flow window 102 , so that it is possible to visually judge whether or not the special notice condition is set.
  • the client terminal 10 When judging that the job flow is created, the client terminal 10 transmits the job flow information relating to the service cooperation defined by the user to the script creation server 30 .
  • the script creation server 30 creates the script defining the contents of the processing to be requested to the respective services, input parameters, the way of cooperation of the respective services, and information for specifying a document as a processing object, such as a document name and storage location information, on the basis of the information relating to the job flow transmitted from the client terminal 10 and the I/F information acquired from the respective service processing devices (step 262 ).
  • the script creation server 30 transmits the script of the XML format to the script management server 40 .
  • the script management server 40 stores the script created by the script creation server 30 .
  • the script management server 40 stores plural scripts created by the script creation server 30 , and reads out a selected script when a selection instruction of a script is issued from the client terminal 10 .
  • the user selects a desired script among the plural scripts stored in the script management server 40 , and can invoke the cooperative processing. Specifically, this is as follows:
  • FIG. 10 is a flowchart showing the processing of the client terminal 10 , the script management server 40 and the cooperative processing server 50 .
  • the client terminal 10 accesses the script management server 40 and acquires the script list managed by the script management server 40 (step 270 ).
  • FIG. 11 is a view showing an example of a service cooperation processing selection screen 110 expressing the script list.
  • the service cooperation processing selection screen 110 has buttons 111 to 116 for selecting scripts for the respective scripts. The user can select the script by clicking a desired button from the service cooperation processing selection screen 110 .
  • the client terminal 10 selects the script expressing the specific service cooperation processing from the service cooperation processing selection screen 110 on the basis of the operation instruction of the user, and instructs the invocation of the script.
  • the script management server 40 transmits the script indicated by the client terminal 10 to the cooperative processing server 50 (step 272 ). As a result, the cooperative processing server 50 starts the execution of the cooperative processing.
  • the cooperative processing server 50 interprets the script transmitted from the script management server 40 , and requests the image processing device 61 as the first processing described in the script to execute the first service processing (step 274 ). Specifically, the cooperative processing server 50 extracts the location of the service processing device to which the processing request is made, the input parameter and output parameter form necessary for the processing request, the method name for the processing request, the invocation scheme, and the information for specifying the processing object document on the basis of the information described in the script, and creates individual indication information. The cooperative processing server 50 transmits the individual indication information to the image processing device 61 as the first processing request destination.
  • the image processing device 61 copies the processing object document and acquires the document on the basis of the location information of the storage destination of the processing object document described in the transmitted script.
  • the image processing device 61 interprets the contents of the service processing request with respect to the acquired document image, performs the image processing such as noise removal or OCR processing, and performs a processing to bind it to the extracted text document.
  • the image processing device 61 again stores into the original storage destination the document in which the image document obtained by the image processing and the text document are bound.
  • the image processing device 61 transmits the processing result, such as the status information (completion) of the processing, the output parameters, and the document storage destination information after the processing, to the cooperative processing server 50 .
  • the cooperative processing server 50 When receiving the processing result from the image processing device 61 , the cooperative processing server 50 manages the result of the first processing request as a log. Then, the cooperative processing server 50 specifies a second processing request destination on the basis of the script, and requests the document management server 62 to perform a second service processing (step 276 ). Similarly to the first service processing request, the cooperative processing server 50 transmits individual indication information (information of storing a document as information relating to the processing request, information of a storage destination of the document, and information to specify the processing object document) to the document management server 62 .
  • the document management server 62 On the basis of the contents of the request of the cooperative processing server 50 , the document management server 62 performs, on the basis of the storage destination information described in the request content, a storage processing of the document processed and stored in the former processing (first service processing). When the processing as stated above is completed, the document management server 62 transmits the processing result, such as the status information (completion) of the processing, the output parameter, and document storage destination information after the processing, to the cooperative processing server 50 .
  • the processing result such as the status information (completion) of the processing, the output parameter, and document storage destination information after the processing
  • the cooperative processing server 50 When receiving the processing result of the second service processing (document storage processing), the cooperative processing server 50 manages the result of the second processing request as a log.
  • the cooperative processing server 50 specifies a third processing request destination on the basis of the script, and requests the document delivery server 63 to carry out a third service processing (step 278 ).
  • the cooperative processing server 50 transmits individual indication information (information of storing a document as information relating to the processing request, information of a storage destination of the document, and information to specify the processing object document) to the document delivery server 63 .
  • the document delivery server 63 On the basis of the contents of the request of the cooperative processing server 50 , with respect to the document processed and stored in the former processing (second service processing), the document delivery server 63 reads out the document file on the basis of the information (storage destination information) to specify the document, and performs the processing described in the contents of the request.
  • the document delivery server 63 mails only a text document to a mail address specified as a delivery destination in the document in which the text document and the image document are bound, and faxes only the image document to a FAX number.
  • the document delivery server 63 transmits the processing result, such as the status information (completion) of the processing, the output parameter, and document storage destination information after the processing, to the cooperative processing server 50 .
  • the document delivery server 63 transmits the status information “mail transmission; completed, FAX transmission: non-transmission” to the cooperative processing server 50 .
  • the cooperative processing server 50 receives the processing result from the third service processing, and when judging that a next processing is not described in the script, the cooperative processing server 50 notifies the client terminal 10 that all processings are completed, and ends the cooperative processing (step 280 ).
  • the service retrieval server 20 acquires part (partial I/F information) of the I/F information from the respective service processing devices, all of the I/F information may be acquired.
  • the cooperative processing server 50 recognizes notice information in the respective services as a piece of information in the partial I/F information shown in FIG. 5 .
  • a notice event occurrence origin service is judged, and when the judgment is completed, the procedure proceeds to step 302 , and the notice condition previously set for the notice event is read out from the partial I/F information of the notice event occurrence origin service and is made a first notice processing.
  • step 304 it is judged whether or not the definition of the notice condition corresponding to the notice event exists in the script data, and in the case of negative judgment, that is, in the case where it does not exist in the script data, the procedure proceeds to step 306 , and an instruction to carry out the first notice processing is issued.
  • step 304 in the case of affirmative judgment, that is, in the case where the definition of the notice condition exists in the script data, the procedure proceeds to step 308 , this defined notice processing is read out and is made a second notice processing, and it proceeds to step 310 .
  • the notice at the time of processing completion of the respective services has been mainly described as the notice event, other various conditions can be set as the notice condition. Examples of the notice condition will be described below.
  • any method may be used as long as a user can clearly recognize, for example, a message transmission, a mail transmission, a FAX transmission, a log record, a report output (print), a display to a user interface or the like is used, or two or more of them may be combined and executed.
  • a notice event occurs, in the case where a notice condition concerning the notice event is defined in the indication data, a notice is made on the basis of the notice condition defined in the indication data, to which a higher priority is given than to the previously set notice condition, and therefore, in the case where accounting is necessary over all jobs, or in the case where importance is attached to security or privacy, a notice most suitable for the job can be selected.
  • FIG. 13 is a block diagram for explaining the mutual relation among respective service processing devices configuring a document processing system 10 A according to the second embodiment.
  • the document processing system 10 A according to the second embodiment can carry out the cooperative processing of plural services without using the cooperative processing server 50 shown in FIGS. 1 and 2 .
  • FIG. 13 shows only the service processing devices relating to the cooperative processing.
  • a user selects a desired script among plural scripts stored in a script management server 40 and can invoke the cooperative processing. Specifically, this is as follows.
  • a client terminal 10 selects a script expressing a desired service cooperation processing from a service cooperation processing selection screen in accordance with the operation of the user, and instructs the invocation of the script.
  • the script management server 40 transmits the script indicated by the client terminal 10 to an image processing device 61 .
  • the image processing device 61 acquires a document as a processing object on the basis of storage destination location information of the processing object document described in the transmitted script.
  • the image processing device 61 interprets the contents of a service processing request with respect to the acquired document image, performs the image processing such as noise removal and OCR processing, and performs a processing to bind it to the extracted text document. After the specific image processing is ended, the image processing device 61 deletes the service processing request described in the script.
  • the image processing device 61 transmits the document in which the image document obtained by the image processing and the text document are bound, and the script including the processing result such as the status information (completion) of the processing, the output parameter, and document storage destination information after the processing, to a document management server 62 for providing a next service processing.
  • the document management server 62 temporarily stores the document transmitted from the image processing device 61 into a storage destination described in the script. Then, the document management server 62 deletes the service processing request described in the script, and transmits the document and the script to a document delivery server 63 for performing a next service processing.
  • the document delivery server 63 mails only the text document to a mail address specified as a delivery destination in the document in which the text document and the image document are bound, and faxes only the image document to a specified FAX number. Then, when judging that a next processing is not described in the script, the document delivery server 63 notifies the client terminal 10 that all processings are completed, and ends the cooperative processing.
  • the addition of a notice to the script data as described in the first embodiment is performed, so that a notice processing most suitable for the job can be carried out in the respective services.
  • the notice in the case where the notice condition is defined in the indication data, the notice is always carried out on the basis of the notice condition defined in this indication data, however, in the case where some condition is satisfied, a higher priority is given to a notice mode set for the respective services than to the notice data recited in the script, and the notice mode may be applied.
  • a service processing state is exhibited in a proper notice form in each job unit and each processing unit in the job, and therefore, it is possible to obtain an excellent effect that the processing state can be properly recognized from the viewpoint of accounting, security, and privacy.

Abstract

In a case where a service for performing specified processings of document data as one job is processed in a cooperative manner on a network, a service processing state is exhibited in a proper notice form in each job unit and in each processing unit in the job, so that the processing state can be properly recognized from the viewpoint of accounting, security and privacy.

Description

  • This is a Continuation of application Ser. No. 12/458,359 filed Jul. 9, 2009, which in turn is a Divisional of application Ser. No. 10/661,503 filed Sep. 15, 2003, which claims the benefit of Japanese Application No. 2003-081453 filed Mar. 24, 2003. The disclosure of the prior applications is hereby incorporated by reference herein in its entirety.
  • BACKGROUND OF THE INVENTION
  • 1. Field of the Invention
  • The present invention relates to a service processing system in which a service for performing specified multiple processings of document data is processed in a cooperative manner on a network, and a service processing method.
  • 2. Description of the Related Art
  • A network system is proposed in which a scanner, a facsimile machine (hereinafter referred to as a FAX), a copying machine, a composite machine in which these are combined, a personal computer, a mail server and the like are mutually connected to each other through a network, so that paper documents and electronic information are shared.
  • The network system as stated above is configured such that for example, a document file is captured from an input system such as a scanner for reading a manuscript or a paperless FAX, and is processed by a processing system of image manipulation, character recognition or the like, and then, the document file is delivered to the outside through an output system such as a printer or a mail server.
  • Here, in general, the capture of the document file, the manipulation processing of the captured data, and the delivery after the manipulation processing are independently carried out.
  • Thus, in the case where the capture operation of the document file, the manipulation processing operation of the captured data, and the delivery operation after the manipulation processing are continuously performed, an operator must make a specified setting for each of the operations.
  • For example, the operator uses a client terminal for collectively managing the above processing devices to open, on a display part, instruction windows relating to the capture of the document file, the manipulation processing of the captured data, and the delivery processing after the manipulation processing, and must perform specified input operations, and therefore, the operation efficiency has been very poor.
  • In order to solve this, a work flow system is conventionally introduced in which a series of processings from input to output are linked on a network and are carried out in previously defined order.
  • In the work flow system, consideration is given to a work flow generally used in an office, such as approval and circulation, and the system is developed by computerizing an existing paper-based transaction system as it is (see patent document 1, patent document 2, and patent document 3).
  • [Patent Document 1]
    • JP-A-2002-99686
  • [Patent Document 2]
    • JP-A-2001-325389
  • [Patent Document 3]
    • JP-A-2001-195295
  • However, although the conventional work flow system is a very effective system from the viewpoint of operation efficiency, it has not been perfect from the viewpoint of accounting and security.
  • That is, in the case where the processing along the work flow is carried out, since it is impossible to confirm by a client terminal that the processing by plural processing devices has been carried out, it has been difficult to grasp the progress of a job set as the work flow.
  • Thus, it is conceivable that a setting is made in such a fixed way that each of the processing devices reports the progress thereof when the processing of the processing device is carried out. However, for example, in the case where a document or the like handled by the processing device is a document or the like permitted to be read out only in the work flow, a report is also made under the situation in which it is not permitted, and this can be a problem from the viewpoint of security or privacy.
  • Besides, although it is also conceivable to relegate the output of the report of the processing situation set for the respective processing devices, this also becomes a problem from the viewpoint of security or privacy.
  • Further, with respect to the processing carried out by a system administrator (Key Operator), a CE (Customer Engineer) or the like, since there is also information which is desired not to be known to a general user (Casual User), the setting in the fixed way causes trouble.
  • SUMMARY OF THE INVENTION
  • The present invention has been made in view of the above circumstance and provides a service processing system and a service processing method, in which in a case where a service for performing specified multiple processings of document data as one job is processed in a cooperative manner on a network, a service processing state is exhibited in a proper notice form in each job unit and in each processing unit in the job, so that the processing state can be properly recognized from the viewpoint of accounting, security and privacy.
  • According to an aspect of the invention, a service processing system in which a service for performing specified multiple processings of document data is processed in a cooperative manner on a network, the system includes: an indication data creation part for creating, for each job as a unit of the associated processings, indication data to indicate a processing procedure of the job, and notice condition data to indicate a notice event and a notice form thereof at each processing stage in the job; a management control part for managing progress of each of the processings in the job on the basis of contents recited in the indication data created by the indication data creation part; and a notice part for sending a notice during the progress of each of the processings in the job on the basis of contents recited in the notice condition data.
  • Besides, according to another aspect of the invention, a service processing method in which a service for performing specified multiple processings of document data is processed in a cooperative manner on a network, the method includes the steps of: creating, for each job as a unit of the associated processings, indication data to indicate a processing procedure of the job, and notice condition data to indicate a notice event and a notice form thereof at each processing stage in the job; managing progress of each of the processings in the job on the basis of contents recited in the created indication data; and sending a notice during the progress of each of the processings in the job on the basis of contents recited in the notice condition data.
  • Besides, according to another aspect of the invention, a job management device for managing progress of each of processings in a service processing system in which a service for performing specified multiple processings of document data is processed in a cooperative manner on a network, the device includes: an indication data creation part for creating, for each job as a unit of the associated processings, indication data to indicate a processing procedure of the job, and notice condition data to indicate a notice event and a notice form thereof at each processing stage in the job; a management control part for managing progress of each of the processings in the job on the basis of contents recited in the indication data created by the indication data creation part; and a notice part for sending a notice during the progress of each of the processings in the job on the basis of contents recited in the notice condition data.
  • Besides, according to another aspect by the invention, a job management device for managing progress of each of processings in a service processing system in which a service for performing specified multiple processings of document data is processed in a cooperative manner on a network, the device includes: an indication data reception part for receiving, for each job as a unit of the associated processings, indication data to indicate a processing procedure of the job, and notice condition data to indicate a notice event and a notice form thereof at each processing stage in the job; a management control part for managing progress of each of the processings in the job on the basis of contents recited in the indication data received by the indication data reception part; and a notice part for sending a notice during the progress of each of the processings in the job on the basis of contents recited in the notice condition data.
  • Besides, according to another aspect of the invention, a service processing device for processing a service in a service processing system in which the service for performing specified multiple processings of document data is processed in a cooperative manner on a network, the device includes: an indication data reception part for receiving, for each job as a unit of the associated processings, indication data to indicate a processing procedure of the job, and notice condition data to indicate a notice event and a notice form thereof at each processing stage in the job; a management control part for managing progress of each of the processings in the job on the basis of contents recited in the indication data received by the indication data reception part; and a notice part for sending a notice during the progress of each of the processings in the job on the basis of contents recited in the notice condition data.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • Preferred embodiments of the present invention will be described in detail based on the following figure, wherein:
  • FIG. 1 is a block diagram showing the outline of a document processing system according to a first embodiment of the invention;
  • FIG. 2 is a block diagram for explaining the mutual relation of service processing devices configuring the document processing system according to the first embodiment of the invention;
  • FIG. 3 is a schematic view showing a structure of I/F information according to the first embodiment of the invention;
  • FIG. 4 is a front view of a script creation screen as a GUI screen for defining a job flow according to the first embodiment of the invention;
  • FIG. 5 is a schematic view showing a script formed in an XML format according to the first embodiment of the invention;
  • FIG. 6 is a front view of a script creation screen displaying a notice processing condition setting screen according to the first embodiment of the invention;
  • FIG. 7 is a front view of a script creation screen when a service of setting a notice processing condition according to the first embodiment of the invention is selected;
  • FIG. 8 is a front view of a script creation screen after the notice processing condition according to the first embodiment of the invention is set;
  • FIG. 9 is a flowchart showing a processing procedure of a client terminal and a script creation server at the time of script creation according to the first embodiment of the invention;
  • FIG. 10 is a flowchart showing a processing of the client terminal, a script management server and a cooperative processing server according to the first embodiment of the invention;
  • FIG. 11 is an explanatory view showing an example of a service cooperative processing selection screen 110 displaying a script list according to the first embodiment of the invention;
  • FIG. 12 is a flowchart showing a notice processing selection control routine interrupting at the time of notice event occurrence according to the first embodiment of the invention; and
  • FIG. 13 is a block diagram showing the mutual relation of service processing devices configuring a document processing system according to a second embodiment.
  • DETAILED DESCRIPTION OF THE INVENTION
  • Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the drawings.
  • First Embodiment System Configuration
  • FIG. 1 is a block diagram showing the configuration of a document processing system 1 according to a first embodiment of the invention.
  • The document processing system 1 is such that various services and applications are connected through a network 5. Here, the service is a function usable on a document in accordance with a request from the outside. The service is equivalent to, for example, copy, print, scan, facsimile transmission and reception, mail delivery, storing into repository and readout from repository, OCR (Optical Character Recognition) processing, noise removal processing, and the like, and is not particularly limited.
  • The document processing system 1 specifically includes a client terminal 10 provided with a user interface and for linking plural services with each other to indicate a desired processing of a user, a service retrieval server 20 for retrieving a desired service of the user, a script creation server 30 for creating a script from information relating to the service cooperation indicated by the client terminal 10, a script management server 40 for managing the script, and a cooperative processing server 50 for executing a cooperative processing of the respective services in accordance with the script.
  • Further, the document processing system 1 includes an image processing device 61 for performing an image processing such as a noise removal processing of an image document, an image rotation processing, an OCR processing, and binding of images, a document management server 62 for managing documents, a document delivery server 63 for delivering documents, a first service processing device 64 for performing a first service processing, and a second service processing device 65 for performing a second service processing.
  • Incidentally, in this embodiment, although the document processing system 1 has the configuration in which the plural servers for performing specific service processings are connected through the network 5, as long as the plural services are connected through the network 5, the configuration is not particularly limited.
  • Here, the script is data containing, in a case where a series of processings are decomposed into plural functional processings, information expressing a relation among the respective functions, interface (I/F) information for invoking the respective functions, and information for configuring a graphical user interface (GUI) relating to the series of processings.
  • FIG. 2 is a block diagram for explaining the mutual relation of the respective service processing devices configuring the document processing system 1. Each of the service processing devices stores I/F information expressing the contents of the service provided by itself.
  • FIG. 3 is a view showing the structure of the I/F information. The I/F information is constituted by <Service Class>, <Service Name>, <Service Icon>, <Service Location Information>, <Input>, <Output>, <Parameter Restriction Rules>, <Service Location>, <Method Name>, <Invocation Scheme>, <Implicit Elements> and <Notice Information>.
  • The <Service Class> is a class of the service provided by the service processing device. Incidentally, what is previously defined is used as the <Service Class> and is equivalent to, for example, scan, print, repository, flow and the like. The <Service Name> is a name of the service provided by the service processing device. The <Service Icon> is position information of an icon displayed on the GUI of the client terminal 10.
  • The <Service Location Information> is a URL which the script creation server 30 uses for acquiring the I/F information. The <Input> is an input to the service. The <Output> is an output from the service. The <Parameter Restriction Rules> are restriction rules applied to the <Input> and the <Output>. The <Service Location> is position information when the service is actually used. The <Method Name> is a provision method of a service processing.
  • The <Invocation Scheme> is a scheme for invoking and starting the service processing. Incidentally, as the <Invocation Scheme>, for example, SOAP (Simple Object Access Protocol) as the protocol of message exchange, SMTP (Simple Mail Transfer Protocol), or the like can be used. The <Implicit Elements> are not data which are explicitly delivered as the output to a later stage processing, however, they are data which can be consulted at the later stage processing.
  • The <Notice Information> is information concerning the progress state of a processing in each service, and for example, a notice form as described below is recited.
  • (1) In the respective servers (the service retrieval server 20, the script creation server 30, the script management server 40, etc.), in the case where an access occurs, contact with an administrator of the server is made.
  • (2) In the respective services (copy, print, scan, facsimile transmission/reception, etc.), in the case where a paper jam at the time of manuscript feed, a copy paper jam, or the like occurs at the time of point when the processing is completed, the processing is suspended.
  • The client terminal 10 has the function of a graphical user interface (GUI) for performing a screen display and for performing a specific operation in order to instruct the creation of a script or to select a script to be invoked.
  • The service retrieval server 20 retrieves a service corresponding to a retrieval condition from plural services connected to the network 5. The service retrieval server 20 previously stores part of the I/F information (hereinafter referred to as “partial I/F information”) (see FIG. 3) of various service processing devices, such as the image processing device 61, the document management server 62, the document delivery server 63, the first service processing device 64, and the service processing device 65. Here, the partial I/F information is the information of <Service Class>, <Service Name>, <Service Location Information>, <Input>, and <Output> in the elements of the I/F information.
  • When the retrieval condition is transmitted from the script creation server 30 or the cooperative processing server 50, the service retrieval server 20 uses the partial I/F information of the respective service processing devices to retrieve the service. For example, when a service similar to a specific service is retrieved, the service retrieval server 20 may retrieve services which are coincident to each other in the <Service Class>, or may retrieve services which are coincident to each other in the <Input> and <Output>, or may retrieve services which are coincident to each other in all of these.
  • At the time of creation of the script, the script creation server 30 acquires the I/F information from the respective service processing devices, and creates the script for linking the services provided by the respective service processing devices with each other. The script creation server 30 specifically executes the following processing to create the script.
  • The script creation server 30 requests specific service processing devices dispersed on the network 5 to transmit the I/F information relating to the respective services on the basis of the <Service Location Information>. Incidentally, in the case where the specific service processing device does not exist, the script creation server 30 instructs the service retrieval server 20 to retrieve another service processing device performing the same service as the specific service processing device. Then, the script creation server 30 has only to acquire the <Service Location Information> of the another service processing device from the service retrieval server 20.
  • The script creation server 30 manages the retrieval result from the service retrieval server 20 and the I/F information received from the respective service processing devices. The script creation server 30 creates an HTML file which becomes a GUI screen for defining a job flow on the basis of the I/F information acquired from the respective service processing devices. When receiving a browse request for services from the client terminal 10, the script creation server 30 transmits the HTML file which becomes the GUI screen to the client terminal 10.
  • FIG. 4 is a view showing a script creation screen 100 as the GUI screen for defining the job flow. The script creation screen 100 is constituted by a service window 101, a flow window 102, a logic window 103, and a property window 104.
  • The service window 101 displays various usable service processing devices. The logic window 103 displays the job flow showing cooperation patterns among the services. The property window 104 displays detailed setting parameters of respective icons displayed on the service window 101 and the logic window 103.
  • The user can define the job flow on the flow window 102 by dragging and dropping icons of the service window 101 and icons of the logic window 103 to the flow window 102. The user further edits the contents displayed on the property window 104 and can set services and logics in detail.
  • Here, as shown in FIG. 6, a notice condition menu 200B is set on a tool menu 200A of a pull-down menu 200 of the script creation screen 100.
  • The notice condition menu 200B is a menu which functions when any one of the icons in the service window 101, which was dragged and dropped on the flow window 102, is selected (reverse display) (FIG. 7 shows, as an example, a state in which a FAX icon is selected).
  • That is, when the notice condition menu 200B is selected in the state where some icon is selected, a notice setting screen 202 as shown in FIG. 6 is displayed.
  • Two check boxes of “set” and “not set” are provided on the notice setting screen 202, and it is possible to select whether or not a notice condition is especially set for the selected icon (service).
  • In the case where “not set” is selected (the check box 204 is checked), notice recognized by the I/F information is executed.
  • In the case where “set” is selected (the check box 206 is checked), a condition item setting screen 208 in the notice setting screen 202 becomes effective, notice information of the selected icon is displayed, and the notice information is successively selected, so that a special notice condition as a script is inputted (set) to a notice condition setting screen 210.
  • For example, in the case where the selected icon is FAX, as the notice information, “Transmission report is outputted at the time of transmission completion”, “Notice is sent when unreadable document data exists”, and the like are displayed as a list. As one of them, “Transmission report is outputted at the time of transmission completion” is selected, and as the notice condition added to the indication data, “Mail transmission is made to client terminal at the time of transmission completion (report output is not made)” can be set. Incidentally, with respect to such setting, the notice condition may be set in a job unit (that is, common to plural services), not for each service (FAX, etc.).
  • Besides, as a matter of course, since the setting is made in an interactive manner with the user in the above, the notice condition is set in the document form, however, similarly to the flow window 102 (GUI), it is internally processed in a program language.
  • As described above, when the notice condition different from the notice information (I/F information) previously set in the respective services is set, as shown in FIG. 8, a mark (“#” mark with a circle in FIG. 8) 212 indicating that a special notice condition is set is attached to the pertinent icon in the flow window 102, so that it can be judged whether or not the special notice condition is set.
  • The client terminal 10 transmits the job flow information defined by the operation of the user to the script creation server 30 in accordance with a CGI (Common Gateway Interface) format.
  • The script creation server 30 creates the script defining the contents of the processing requested to the respective services, input parameters, the way (job flow) of cooperation of the respective services, and information for specifying a document as a processing object, such as a document name and storage location information, on the basis of the job flow information relating to the indication of the service cooperation from the user and the I/F information of the respective services. The script is constituted by files of an XML format.
  • FIG. 5 is a view showing the script composed in the XML format. Since the cooperative processing itself of the plural services is also regarded as one service, the script has the structure in which <Flow> is added to the I/F information shown in FIG. 3.
  • The <Flow> is an element for describing the cooperation between services and includes <Invoke>, control structure and logic operation, elements such as <if> for sending a notice, and information for specifying a document as a processing object.
  • The <Invoke> expresses a specific method of a service processing device, and executes invocation of a service. The element of the <Invoke> includes <Map> expressing the position information of a parameter, and <Method> of an invocation method name. The <if>, <and>, <eq> and <gt> expressing the control structure, the logic operation and the like carry out condition branching at the time of the cooperative processing and the adjustment of parameters delivered between the services.
  • The script describes all information relating to the control of the cooperative processing of the services in the element of the <flow>. By this, the cooperative processing itself expressed by the script is also regarded as one service. Incidentally, the script is not limited to the structure shown in FIG. 5, and it is sufficient if the respective services can be linked with each other.
  • The script creation server 30 transmits the script of the XML format as stated above to the script management server 40. Besides, in the case where the execution of the service cooperative processing is instructed by the user, the script creation server 30 may directly transmit the script to the cooperative processing server 50.
  • The script management server 40 holds the script transmitted from the script creation server 30, and transmits the script to the cooperative processing server 50 in accordance with the request from the client terminal 10.
  • The cooperative processing server 50 is a server for interpreting and executing the specified script. When the script is transmitted, the cooperative processing server 50 interprets the script, sequentially invokes the respective service processing devices, such as the image processing device 61, the document management server 62, and the document delivery server 63 in accordance with the order and the use method described in the script, and executes the cooperative processing. Besides, the cooperative processing server 50 stores the state of the cooperative processing under execution and the information of the result of the completed cooperative processing, and notifies the state of the cooperative processing and the result in accordance with a request from the outside.
  • The cooperative processing server 50 interprets the script, and when making a request to the respective service processing devices, the cooperative processing server creates individual indication information having the contents of the processing request, input parameters and information for specifying the document as the processing object. Incidentally, the cooperative processing server 50 may describe the relation to a processing before or after a processing performed by the respective service processing devices, or the processing request may be made in an information exchange form intrinsic to each service processing device, not the form of the script.
  • The image processing device 61 is a computer in which a software program for performing an image processing function is installed. The image processing device 61 performs the processing of the document on the basis of the contents of the service processing request contained in the processing request from the cooperative processing server 50, the input parameters, and the information of the processing object document. Besides, the image processing device 61 notifies the service retrieval server 20 of the partial I/F information at the time of invocation. Further, in accordance with the request from the script creation server 30, the image processing device 61 transmits the I/F information expressing the use method of the image processing service. The I/F information is used when the script is created.
  • The document management server 62 has a document storage function. The document management server 62 carries out the storage, retrieval, and readout of the document, the change of attribute relating to the document, and various processings on the basis of the information contained in the request from the cooperative processing server 50. Besides, the document management server 62 notifies the service retrieval server 20 of the partial I/F information at the time of invocation. Further, the document management server 62 transmits the I/F information expressing the use method of the document management service in accordance with the request from the script creation server 30.
  • The document delivery server 63 has functions to store the acquired document into the indicated document management server, to perform mail transmission or FAX transmission to an indicated transmission destination, and to perform a print output processing to an indicated printer. In accordance with the request from the cooperative processing server 50, the document delivery server 63 performs the delivery processing of the document on the basis of the document indicated by the client terminal 10 and the information of the delivery destination. Besides, the document delivery server 63 notifies the service retrieval server 20 of the partial I/F information at the time of invocation. Further, the document delivery server 63 transmits the I/F information expressing the use method of the document delivery service in accordance with the request from the script creation server 30.
  • The first service processing device 64 is a device for performing a specific service processing relating to the document in accordance with the instruction from the outside. Here, the first service processing device 64 carries out the service processing to be executed by itself on the basis of information such as the contents of the processing request from the cooperative processing server 50, the input parameters, and the information for specifying the document as the processing object. Besides, the first service processing device 64 notifies the service retrieval server 20 of the partial I/F information at the time of invocation. Further, the first service processing device 64 transmits the I/F information expressing the use method of the service processing in accordance with the request from the script creation server 30. Incidentally, the second service processing device 65 operates similarly to the first service processing device 64 except for the contents of the service processing.
  • In the document processing system 1 configured as described above, when application programs for executing specific services are installed in the respective service processing devices such as the image processing device 61, the document management server 62, and the document delivery server 63, they operate as follows.
  • The service processing devices, such as the image processing device 61, the document management server 62, and the document delivery server 63, notify the service retrieval server 20 of the partial I/F information containing the information expressing the respective service summaries and addresses at the invocation processing.
  • The service retrieval server 20 stores the partial I/F information transmitted from the respective service processing devices such as the image processing device 61, the document management server 62 and the document delivery server 63. By this, when a specific service retrieval request is issued from, for example, the script creation server 30 or the cooperative processing server 50, the service retrieval server 20 can perform retrieval by using the partial I/F information.
  • (Creation of Script)
  • FIG. 9 is a flowchart showing a processing procedure of the client terminal 10 and the script creation server 30 at the time of creating the script.
  • The client terminal 10 accesses a URL (Uniform Resource Locator) of an HTML file created for the user interface screen provided by the script creation server 30 through an installed browser in accordance with the operation of the user (step 250).
  • The script creation server 30 transmits the HTML file of the user interface screen to the client terminal 10 in accordance with the browse request from the client terminal 10 (step 252).
  • The client terminal 10 displays the user interface screen on the basis of the HTML file transmitted from the script creation server 30 (step 254). At this time, the user can define a desired service cooperation job flow by using the user interface screen displayed on the client terminal 10.
  • The client terminal 10 judges whether or not the job flow is defined through the user interface screen, and stands by until the job flow is defined (step 256).
  • When it is judged that the job flow is defined, at next step 258, it is judged whether or not a notice condition definition exists.
  • That is, in the case where the notice condition defined in the job flow, which is different from notice conditions previously set for the individual services, is specified, the procedure proceeds to step 260, and it is added as an additional element of the definition of the job flow so that this specified notice condition becomes effective in the pertinent service.
  • Incidentally, the setting of the notice condition is performed in the following procedure.
  • First, a service is selected from the job flow defined on the completed flow window 102 in order to set the notice condition. For example, in the case where FAX is selected, a pointer is placed on the FAX icon and selection is made by a specific operation (for example, one click of a mouse). The selected FAX icon is highlighted (see FIG. 7).
  • In the above selection state, the notice processing condition menu 200B is selected from the tool menu 200A of the pull-down menu 200.
  • When the notice processing condition menu 200B is selected, the notice setting screen 202 shown in FIG. 6 is displayed.
  • On the notice setting screen 202, when “set” is selected (the check box 206 is checked), the condition item setting screen 208 in the notice setting screen 202 becomes effective, the notice condition of the selected icon is displayed, and notice conditions are successively selected, so that a special notice condition as a script is inputted (set) to the notice condition setting screen 210.
  • When the above setting is completed and the notice setting screen 202 is closed, as shown in FIG. 8, the “#” mark 212 indicating that the special notice condition is set is attached to the icon in the flow window 102, so that it is possible to visually judge whether or not the special notice condition is set.
  • When judging that the job flow is created, the client terminal 10 transmits the job flow information relating to the service cooperation defined by the user to the script creation server 30.
  • The script creation server 30 creates the script defining the contents of the processing to be requested to the respective services, input parameters, the way of cooperation of the respective services, and information for specifying a document as a processing object, such as a document name and storage location information, on the basis of the information relating to the job flow transmitted from the client terminal 10 and the I/F information acquired from the respective service processing devices (step 262). The script creation server 30 transmits the script of the XML format to the script management server 40.
  • The script management server 40 stores the script created by the script creation server 30. The script management server 40 stores plural scripts created by the script creation server 30, and reads out a selected script when a selection instruction of a script is issued from the client terminal 10.
  • (Invocation and Execution of Cooperative Processing)
  • The user selects a desired script among the plural scripts stored in the script management server 40, and can invoke the cooperative processing. Specifically, this is as follows:
  • FIG. 10 is a flowchart showing the processing of the client terminal 10, the script management server 40 and the cooperative processing server 50.
  • The client terminal 10 accesses the script management server 40 and acquires the script list managed by the script management server 40 (step 270).
  • FIG. 11 is a view showing an example of a service cooperation processing selection screen 110 expressing the script list. The service cooperation processing selection screen 110 has buttons 111 to 116 for selecting scripts for the respective scripts. The user can select the script by clicking a desired button from the service cooperation processing selection screen 110.
  • The client terminal 10 selects the script expressing the specific service cooperation processing from the service cooperation processing selection screen 110 on the basis of the operation instruction of the user, and instructs the invocation of the script.
  • The script management server 40 transmits the script indicated by the client terminal 10 to the cooperative processing server 50 (step 272). As a result, the cooperative processing server 50 starts the execution of the cooperative processing.
  • The cooperative processing server 50 interprets the script transmitted from the script management server 40, and requests the image processing device 61 as the first processing described in the script to execute the first service processing (step 274). Specifically, the cooperative processing server 50 extracts the location of the service processing device to which the processing request is made, the input parameter and output parameter form necessary for the processing request, the method name for the processing request, the invocation scheme, and the information for specifying the processing object document on the basis of the information described in the script, and creates individual indication information. The cooperative processing server 50 transmits the individual indication information to the image processing device 61 as the first processing request destination.
  • The image processing device 61 copies the processing object document and acquires the document on the basis of the location information of the storage destination of the processing object document described in the transmitted script. The image processing device 61 interprets the contents of the service processing request with respect to the acquired document image, performs the image processing such as noise removal or OCR processing, and performs a processing to bind it to the extracted text document. The image processing device 61 again stores into the original storage destination the document in which the image document obtained by the image processing and the text document are bound. When the processing as stated above is completed, the image processing device 61 transmits the processing result, such as the status information (completion) of the processing, the output parameters, and the document storage destination information after the processing, to the cooperative processing server 50.
  • When receiving the processing result from the image processing device 61, the cooperative processing server 50 manages the result of the first processing request as a log. Then, the cooperative processing server 50 specifies a second processing request destination on the basis of the script, and requests the document management server 62 to perform a second service processing (step 276). Similarly to the first service processing request, the cooperative processing server 50 transmits individual indication information (information of storing a document as information relating to the processing request, information of a storage destination of the document, and information to specify the processing object document) to the document management server 62.
  • On the basis of the contents of the request of the cooperative processing server 50, the document management server 62 performs, on the basis of the storage destination information described in the request content, a storage processing of the document processed and stored in the former processing (first service processing). When the processing as stated above is completed, the document management server 62 transmits the processing result, such as the status information (completion) of the processing, the output parameter, and document storage destination information after the processing, to the cooperative processing server 50.
  • When receiving the processing result of the second service processing (document storage processing), the cooperative processing server 50 manages the result of the second processing request as a log. The cooperative processing server 50 specifies a third processing request destination on the basis of the script, and requests the document delivery server 63 to carry out a third service processing (step 278). Similarly to the second service processing request, the cooperative processing server 50 transmits individual indication information (information of storing a document as information relating to the processing request, information of a storage destination of the document, and information to specify the processing object document) to the document delivery server 63.
  • On the basis of the contents of the request of the cooperative processing server 50, with respect to the document processed and stored in the former processing (second service processing), the document delivery server 63 reads out the document file on the basis of the information (storage destination information) to specify the document, and performs the processing described in the contents of the request. Here, the document delivery server 63 mails only a text document to a mail address specified as a delivery destination in the document in which the text document and the image document are bound, and faxes only the image document to a FAX number. When the processing is completed, the document delivery server 63 transmits the processing result, such as the status information (completion) of the processing, the output parameter, and document storage destination information after the processing, to the cooperative processing server 50.
  • In this processing, for example, in the FAX transmission processing, in the case where the opposite party was engaged on the phone, and even if a retry was performed a predetermined number of times, the connection with the opposite party could not be established, the document delivery server 63 transmits the status information “mail transmission; completed, FAX transmission: non-transmission” to the cooperative processing server 50.
  • The cooperative processing server 50 receives the processing result from the third service processing, and when judging that a next processing is not described in the script, the cooperative processing server 50 notifies the client terminal 10 that all processings are completed, and ends the cooperative processing (step 280).
  • Incidentally, in this embodiment, although the service retrieval server 20 acquires part (partial I/F information) of the I/F information from the respective service processing devices, all of the I/F information may be acquired.
  • Here, in this embodiment, although there is no problem in the case where the cooperative processing as stated above is properly carried out, in the case where a notice event occurs in some service, a measure to the notice event is simultaneously managed.
  • That is, the cooperative processing server 50 recognizes notice information in the respective services as a piece of information in the partial I/F information shown in FIG. 5.
  • On the other hand, there is a case where a definition of a notice condition different from notice conditions previously set for the respective services is added to the script data.
  • Then, when the notice event occurs in some service, it is judged whether or not the definition of the notice condition of the service exists in the script data, and a proper notice processing is carried out.
  • Hereinafter, a notice processing selection control interrupting at the time of a notice event occurrence will be described with reference to a flowchart of FIG. 12.
  • At step 300, a notice event occurrence origin service is judged, and when the judgment is completed, the procedure proceeds to step 302, and the notice condition previously set for the notice event is read out from the partial I/F information of the notice event occurrence origin service and is made a first notice processing.
  • At next step 304, it is judged whether or not the definition of the notice condition corresponding to the notice event exists in the script data, and in the case of negative judgment, that is, in the case where it does not exist in the script data, the procedure proceeds to step 306, and an instruction to carry out the first notice processing is issued.
  • On the other hand, at the step 304, in the case of affirmative judgment, that is, in the case where the definition of the notice condition exists in the script data, the procedure proceeds to step 308, this defined notice processing is read out and is made a second notice processing, and it proceeds to step 310.
  • At the step 310, an instruction to carry out the second notice processing is issued, and this routine is ended.
  • Incidentally, in the above first embodiment, although the notice at the time of processing completion of the respective services has been mainly described as the notice event, other various conditions can be set as the notice condition. Examples of the notice condition will be described below.
  • (1) Notice Condition Common in Job Units
  • When the processing of each service is completed, a notice is made to the client terminal.
  • (2) Execution of a Processing Different from Indication Data
  • When a processing is being performed in accordance with the indication data, and when the pertinent service operates, a notice is made to the client terminal.
  • (3) Processing Different from Indication Data by a Specific User
  • Since a processing carried out by a system administrator (Key Operator), a CE (Customer Engineer) or the like includes information which is desired not to be known to a general user (Casual User), any notice is not made.
  • (4) Login to a Specific Server, and Access to a Secret Document File
  • In the case where login to a specific server occurs, or there occurs an access to a secret document file stored in a server or a HDD of each service, a notice is made to the CE.
  • (5) Access to a Pay Server or Execution of Service
  • In the case where there is a charge for use, a notice is made to a client terminal before the use.
  • Besides, as a specific method of notice, any method may be used as long as a user can clearly recognize, for example, a message transmission, a mail transmission, a FAX transmission, a log record, a report output (print), a display to a user interface or the like is used, or two or more of them may be combined and executed.
  • As described above, in the first embodiment, when a notice event occurs, in the case where a notice condition concerning the notice event is defined in the indication data, a notice is made on the basis of the notice condition defined in the indication data, to which a higher priority is given than to the previously set notice condition, and therefore, in the case where accounting is necessary over all jobs, or in the case where importance is attached to security or privacy, a notice most suitable for the job can be selected.
  • Second Embodiment
  • Next, a second embodiment of the invention will be described. Incidentally, the same parts as those of the first embodiment are denoted by the same reference numerals and the detailed description will be omitted.
  • FIG. 13 is a block diagram for explaining the mutual relation among respective service processing devices configuring a document processing system 10A according to the second embodiment. The document processing system 10A according to the second embodiment can carry out the cooperative processing of plural services without using the cooperative processing server 50 shown in FIGS. 1 and 2.
  • Incidentally, although the document processing system 10A includes the service processing devices (except for the cooperative processing server 50) shown in FIG. 1, FIG. 13 shows only the service processing devices relating to the cooperative processing.
  • (Invocation and Execution of Cooperative Processing)
  • A user selects a desired script among plural scripts stored in a script management server 40 and can invoke the cooperative processing. Specifically, this is as follows.
  • A client terminal 10 selects a script expressing a desired service cooperation processing from a service cooperation processing selection screen in accordance with the operation of the user, and instructs the invocation of the script. The script management server 40 transmits the script indicated by the client terminal 10 to an image processing device 61.
  • The image processing device 61 acquires a document as a processing object on the basis of storage destination location information of the processing object document described in the transmitted script. The image processing device 61 interprets the contents of a service processing request with respect to the acquired document image, performs the image processing such as noise removal and OCR processing, and performs a processing to bind it to the extracted text document. After the specific image processing is ended, the image processing device 61 deletes the service processing request described in the script. Then, the image processing device 61 transmits the document in which the image document obtained by the image processing and the text document are bound, and the script including the processing result such as the status information (completion) of the processing, the output parameter, and document storage destination information after the processing, to a document management server 62 for providing a next service processing.
  • The document management server 62 temporarily stores the document transmitted from the image processing device 61 into a storage destination described in the script. Then, the document management server 62 deletes the service processing request described in the script, and transmits the document and the script to a document delivery server 63 for performing a next service processing.
  • On the basis of the script, the document delivery server 63 mails only the text document to a mail address specified as a delivery destination in the document in which the text document and the image document are bound, and faxes only the image document to a specified FAX number. Then, when judging that a next processing is not described in the script, the document delivery server 63 notifies the client terminal 10 that all processings are completed, and ends the cooperative processing.
  • Also in the second embodiment, the addition of a notice to the script data as described in the first embodiment is performed, so that a notice processing most suitable for the job can be carried out in the respective services.
  • Incidentally, in the first and the second embodiments, in the case where the notice condition is defined in the indication data, the notice is always carried out on the basis of the notice condition defined in this indication data, however, in the case where some condition is satisfied, a higher priority is given to a notice mode set for the respective services than to the notice data recited in the script, and the notice mode may be applied.
  • As described above, according to the invention, in the case where a service for performing specified multiple processings of document data as one job is processed in a cooperative manner on a network, a service processing state is exhibited in a proper notice form in each job unit and each processing unit in the job, and therefore, it is possible to obtain an excellent effect that the processing state can be properly recognized from the viewpoint of accounting, security, and privacy.

Claims (9)

What is claimed is:
1. A script creation apparatus comprising:
a script creation unit that creates a script, the script configured to cause a plurality of processing units to perform a plurality of processes in coordination, the script including relation information expressing relations among the respective processes, and location information expressing locations of the processing units that perform the plurality of processes; and
a transmitting unit that transmits the script to a script management apparatus.
2. The script creation apparatus according to claim 1,
wherein at least one of the processes is for a document or document data.
3. The script creation apparatus according to claim 1,
wherein the script is written in XML format.
4. The script creation apparatus according to claim 1,
wherein the relation information comprises linkage patterns that define a sequence in which the processes are performed.
5. A script creation apparatus comprising:
a receiving unit that receives flow information of a plurality of services;
a management unit that manages an interface information of the services; and
a script creation unit that creates a script to perform processes by using the services according to the flow information and the interface information.
6. The script creation apparatus according to claim 5, further comprising:
an HTML file creation unit that creates an HTML file of a GUI screen which is used to define the flow information of the services according to the interface information.
7. The script creation apparatus according to claim 6,
wherein the HTML file displays services which are available to use.
8. The script creation apparatus according to claim 5, wherein the flow information defines a process flow among the plurality of services.
9. The script creation apparatus according to claim 5, wherein the interface information comprises information including one or more of a service name, a service icon, service location information, or notice information.
US13/745,014 2003-03-24 2013-01-18 Service processing system and service processing method Abandoned US20130132486A1 (en)

Priority Applications (5)

Application Number Priority Date Filing Date Title
US13/745,014 US20130132486A1 (en) 2003-03-24 2013-01-18 Service processing system and service processing method
US15/019,542 US10291683B2 (en) 2003-03-24 2016-02-09 Service processing system and service processing method
US16/372,755 US20190230145A1 (en) 2003-03-24 2019-04-02 Service processing system and service processing method
US16/372,737 US11201905B2 (en) 2003-03-24 2019-04-02 Service processing system and service processing method
US17/525,500 US11546407B2 (en) 2003-03-24 2021-11-12 Service processing system and service processing method

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
JP2003-081453 2003-03-24
JP2003081453A JP4232499B2 (en) 2003-03-24 2003-03-24 INSTRUCTION DATA GENERATION DEVICE, INSTRUCTION DATA GENERATION METHOD, AND INSTRUCTION DATA GENERATION PROGRAM
US10/661,503 US20040205758A1 (en) 2003-03-24 2003-09-15 Service processing system and service processing method
US12/458,359 US20090276493A1 (en) 2003-03-24 2009-07-09 Service processing system and service processing method
US13/745,014 US20130132486A1 (en) 2003-03-24 2013-01-18 Service processing system and service processing method

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US12/458,359 Continuation US20090276493A1 (en) 2003-03-24 2009-07-09 Service processing system and service processing method

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/019,542 Continuation US10291683B2 (en) 2003-03-24 2016-02-09 Service processing system and service processing method

Publications (1)

Publication Number Publication Date
US20130132486A1 true US20130132486A1 (en) 2013-05-23

Family

ID=33127229

Family Applications (8)

Application Number Title Priority Date Filing Date
US10/661,503 Abandoned US20040205758A1 (en) 2003-03-24 2003-09-15 Service processing system and service processing method
US12/458,359 Abandoned US20090276493A1 (en) 2003-03-24 2009-07-09 Service processing system and service processing method
US13/745,071 Abandoned US20130139086A1 (en) 2003-03-24 2013-01-18 Service processing system and service processing method
US13/745,014 Abandoned US20130132486A1 (en) 2003-03-24 2013-01-18 Service processing system and service processing method
US15/019,542 Expired - Lifetime US10291683B2 (en) 2003-03-24 2016-02-09 Service processing system and service processing method
US16/372,755 Abandoned US20190230145A1 (en) 2003-03-24 2019-04-02 Service processing system and service processing method
US16/372,737 Expired - Lifetime US11201905B2 (en) 2003-03-24 2019-04-02 Service processing system and service processing method
US17/525,500 Expired - Lifetime US11546407B2 (en) 2003-03-24 2021-11-12 Service processing system and service processing method

Family Applications Before (3)

Application Number Title Priority Date Filing Date
US10/661,503 Abandoned US20040205758A1 (en) 2003-03-24 2003-09-15 Service processing system and service processing method
US12/458,359 Abandoned US20090276493A1 (en) 2003-03-24 2009-07-09 Service processing system and service processing method
US13/745,071 Abandoned US20130139086A1 (en) 2003-03-24 2013-01-18 Service processing system and service processing method

Family Applications After (4)

Application Number Title Priority Date Filing Date
US15/019,542 Expired - Lifetime US10291683B2 (en) 2003-03-24 2016-02-09 Service processing system and service processing method
US16/372,755 Abandoned US20190230145A1 (en) 2003-03-24 2019-04-02 Service processing system and service processing method
US16/372,737 Expired - Lifetime US11201905B2 (en) 2003-03-24 2019-04-02 Service processing system and service processing method
US17/525,500 Expired - Lifetime US11546407B2 (en) 2003-03-24 2021-11-12 Service processing system and service processing method

Country Status (4)

Country Link
US (8) US20040205758A1 (en)
JP (1) JP4232499B2 (en)
KR (1) KR100592101B1 (en)
CN (1) CN1312598C (en)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7890573B2 (en) * 2005-11-18 2011-02-15 Toshiba Medical Visualization Systems Europe, Limited Server-client architecture in medical imaging
US20090006989A1 (en) * 2007-06-27 2009-01-01 Samsung Electronics Co., Ltd Image forming method and apparatus, and host
US8848213B2 (en) * 2008-03-18 2014-09-30 Microsoft Corporation Object-based network scanning
US20100017430A1 (en) * 2008-07-21 2010-01-21 Kodimer Marianne L System and method for document processing job management based on user login
CN101938460B (en) * 2010-06-22 2014-04-09 北京中兴网安科技有限公司 Coordinated defense method of full process and full network safety coordinated defense system
JP2012053511A (en) * 2010-08-31 2012-03-15 Canon Inc Server device, information processor, service processing apparatus, network system, job management method, and program
JP5803452B2 (en) * 2010-09-30 2015-11-04 ブラザー工業株式会社 Image processing system, image processing method, relay device, and relay program
EP2668571B1 (en) * 2011-01-26 2020-10-14 Hewlett-Packard Development Company, L.P. Document workflow architecture
CN104081381B (en) * 2012-03-29 2017-08-04 企业服务发展公司有限责任合伙企业 Method and apparatus for implementing concept service
USD766957S1 (en) * 2015-05-01 2016-09-20 Microsoft Corporation Display screen with graphical user interface
USD768172S1 (en) * 2015-05-01 2016-10-04 Microsoft Corporation Display screen with animated graphical user interface

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5815152A (en) * 1995-04-18 1998-09-29 Logical Software Solutions Corporation Method and apparatus for defining and evaluating a graphic rule
US20020161462A1 (en) * 2001-03-05 2002-10-31 Fay Todor J. Scripting solution for interactive audio generation
US20030131075A1 (en) * 2001-05-08 2003-07-10 Narad Networks, Inc. Language and interface for unified network service creation, provision and deployment
US6701366B1 (en) * 1999-11-09 2004-03-02 Nortel Networks Corporation Providing communications services
US6966029B1 (en) * 1999-12-08 2005-11-15 Koninklijke Philips Electronics N.V. Script embedded in electronic documents as invisible encoding
US7007275B1 (en) * 1999-10-21 2006-02-28 Unisys Corporation Method and apparatus for automatic execution of concatenated methods across multiple heterogeneous data sources
US7069536B2 (en) * 2001-06-28 2006-06-27 International Business Machines Corporation Method, system, and program for executing a workflow
US7363377B1 (en) * 2002-10-09 2008-04-22 Unisys Corporation Method for protecting the program environment of a microsoft component object model (COM) client
US7398237B2 (en) * 2001-06-26 2008-07-08 International Business Machines Corporation Rule based engine for validating financial transactions

Family Cites Families (81)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5220674A (en) 1987-07-17 1993-06-15 Digital Equipment Corporation Local area print server for requesting and storing required resource data and forwarding printer status message to selected destination
US6683697B1 (en) 1991-03-20 2004-01-27 Millenium L.P. Information processing methodology
US5589625A (en) 1992-03-18 1996-12-31 Kemira Oy, Biotech Transgenic plants displaying multiple virus resistance and a process for their production
FR2692058B1 (en) * 1992-06-09 1994-07-29 Bull Sa TRANSACTIONAL PROCESSING SYSTEM BETWEEN A COMPUTER SERVER AND A PLURALITY OF WORKSTATIONS.
US5467434A (en) 1992-08-28 1995-11-14 Xerox Corporation Apparatus and method for determining printer option availability and representing conflict resolution in a combination of print job selections
US5625757A (en) 1993-12-24 1997-04-29 Hitachi, Ltd. Printing system
JPH07271699A (en) 1994-03-31 1995-10-20 Canon Inc Peripheral processor and information processor connected through network, and control method in peripheral processor and control method for peripheral processor
KR100289826B1 (en) * 1994-05-31 2001-05-15 아끼구사 나오유끼 Job execution system and method between different operating systems
JP2666755B2 (en) * 1995-01-11 1997-10-22 日本電気株式会社 Workflow system
US5774661A (en) 1995-04-18 1998-06-30 Network Imaging Corporation Rule engine interface for a visual workflow builder
US6401150B1 (en) 1995-06-06 2002-06-04 Apple Computer, Inc. Centralized queue in network printing systems
US6657741B1 (en) 1995-08-07 2003-12-02 Tr Systems, Inc. Multiple print engine system with selectively distributed ripped pages
US5760775A (en) 1995-10-30 1998-06-02 Xerox Corporation Apparatus and method for programming a job ticket in a document processing system
US5761396A (en) 1995-11-28 1998-06-02 Xerox Corporation Document server for processing a distribution job in a document processing system
JPH09231280A (en) * 1996-02-22 1997-09-05 Casio Comput Co Ltd Data processing method and its processor
US8162125B1 (en) * 1996-05-29 2012-04-24 Cummins-Allison Corp. Apparatus and system for imaging currency bills and financial documents and method for using the same
US7187795B2 (en) * 2001-09-27 2007-03-06 Cummins-Allison Corp. Document processing system using full image scanning
JPH09325928A (en) 1996-06-06 1997-12-16 Fuji Xerox Co Ltd Method and equipment for communicating message
JP3559656B2 (en) 1996-09-09 2004-09-02 キヤノン株式会社 Image forming apparatus and image processing method
US6604124B1 (en) 1997-03-13 2003-08-05 A:\Scribes Corporation Systems and methods for automatically managing work flow based on tracking job step completion status
US5974234A (en) 1997-04-15 1999-10-26 Xerox Corporation Centralized print server for interfacing one or more network clients with a plurality of printing devices
US6122633A (en) * 1997-05-27 2000-09-19 International Business Machines Corporation Subscription within workflow management systems
JP3201514B2 (en) 1997-06-09 2001-08-20 セイコーエプソン株式会社 Print data generation device, print data generation method, printing device, and printing system
JPH11184649A (en) 1997-07-25 1999-07-09 Seiko Epson Corp System and method for printing, and printer
US5960404A (en) * 1997-08-28 1999-09-28 International Business Machines Corp. Mechanism for heterogeneous, peer-to-peer, and disconnected workflow operation
US6708189B1 (en) * 1997-09-30 2004-03-16 Desknet, Inc. Computer file transfer system
EP0910010A3 (en) 1997-10-14 2001-01-31 Canon Kabushiki Kaisha Apparatus and method for performing a specific process based on a setup condition, and a storage medium for such a program
JPH11196125A (en) 1997-12-27 1999-07-21 Hitachi Ltd Device and method for automatic operation reporting and storage medium stored with program regarding the method
JPH11224296A (en) 1998-02-05 1999-08-17 Nec Corp Image workflow system
JP3857409B2 (en) * 1998-03-17 2006-12-13 富士通株式会社 Distributed processing system, distributed processing method, and computer-readable recording medium recording distributed processing program
JPH11289419A (en) * 1998-04-01 1999-10-19 Ricoh Co Ltd Combined device
JP3689564B2 (en) * 1998-07-31 2005-08-31 キヤノン株式会社 OA device, OA system, control method, and storage medium
US6775023B1 (en) * 1999-07-30 2004-08-10 Canon Kabushiki Kaisha Center server, information processing apparatus and method, and print system
JP2000105678A (en) 1998-07-31 2000-04-11 Canon Inc Image gathering device, print controller, image gathering method, print control method, and storage medium storing computer-readable program
JP4026960B2 (en) 1998-07-31 2007-12-26 キヤノン株式会社 Image position management apparatus, image position management method, and storage medium storing computer-readable program
US6182136B1 (en) 1998-09-08 2001-01-30 Hewlett-Packard Company Automated service elements discovery using core service specific discovery templates
JP2000099686A (en) 1998-09-17 2000-04-07 Nippon Telegr & Teleph Corp <Ntt> Pattern recognition and vehicle recognition method and storage medium recording its program
JP3997013B2 (en) 1998-10-30 2007-10-24 キヤノン株式会社 Information processing apparatus and information processing method
JP3931941B2 (en) 1999-01-26 2007-06-20 富士ゼロックス株式会社 Work process management apparatus and work process management method
JP4809968B2 (en) * 1999-04-09 2011-11-09 キヤノン株式会社 Information processing apparatus, information processing method, and computer-readable recording medium
US6549516B1 (en) 1999-07-02 2003-04-15 Cisco Technology, Inc. Sending instructions from a service manager to forwarding agents on a need to know basis
US6941465B1 (en) * 1999-07-26 2005-09-06 Microsoft Corporation Method of enforcing a policy on a computer network
US6483524B1 (en) 1999-10-01 2002-11-19 Global Graphics Software Limited Prepress workflow method using raster image processor
US6785015B1 (en) 1999-11-12 2004-08-31 Hewlett-Packard Development Company, L.P. System and method for monitoring a computer system process or peripheral
US7099027B1 (en) * 1999-11-12 2006-08-29 Electronics For Imaging, Inc. Method and apparatus for distributing print jobs
JP2001195295A (en) * 2000-01-12 2001-07-19 Ricoh Co Ltd Integral technical document managing device
US20050060059A1 (en) * 2003-09-15 2005-03-17 Klein Robert J. System and method for processing batches of documents
US7120910B2 (en) * 2000-03-29 2006-10-10 Canon Kabushiki Kaisha Control method for image processing apparatus connectable to computer network
JP2001325389A (en) * 2000-05-16 2001-11-22 Canon Inc Device and method for information processing and program storage medium
US6772216B1 (en) * 2000-05-19 2004-08-03 Sun Microsystems, Inc. Interaction protocol for managing cross company processes among network-distributed applications
JP3605700B2 (en) 2000-06-06 2004-12-22 ノーリツ鋼機株式会社 Image data transmitting apparatus and method, computer-readable recording medium storing a program for transmitting image data, and image data transmitting / receiving system and method
US20020055849A1 (en) * 2000-06-30 2002-05-09 Dimitrios Georgakopoulos Workflow primitives modeling
US7251728B2 (en) * 2000-07-07 2007-07-31 Message Secure Corporation Secure and reliable document delivery using routing lists
US6970261B1 (en) 2000-07-11 2005-11-29 Hewlett-Packard Development Company, L.P. Printing system and method with print job distribution among a number of printers
US8086508B2 (en) * 2000-07-24 2011-12-27 Cashedge, Inc. Method and apparatus for delegating authority
JP2002073576A (en) 2000-08-31 2002-03-12 Toshiba Corp Batch job control system
JP4299447B2 (en) * 2000-09-12 2009-07-22 インターナショナル・ビジネス・マシーンズ・コーポレーション Workflow system, information processing apparatus, and storage medium
US20020030840A1 (en) 2000-09-12 2002-03-14 Fuji Xerox Co., Ltd. Image output system, and device and method applicable to the same
JP2002108632A (en) 2000-09-28 2002-04-12 Dainippon Printing Co Ltd Controller working with existing system
US7196805B1 (en) * 2000-12-29 2007-03-27 Cisco Technology, Inc. Consumer level device for automatically transferring digital images to an internet-based service provider
US20020111841A1 (en) 2001-02-09 2002-08-15 International Business Machines Corporation Controlling commands in workflow management systems
US20020135816A1 (en) * 2001-03-20 2002-09-26 Masahiro Ohwa Image forming apparatus
US7315389B2 (en) 2001-03-23 2008-01-01 Toshiba Tec Kabushiki Kaisha Electronic document assembly, proofing and printing system
US7051119B2 (en) * 2001-07-12 2006-05-23 Yahoo! Inc. Method and system for enabling a script on a first computer to communicate and exchange data with a script on a second computer over a network
US20030061266A1 (en) * 2001-09-27 2003-03-27 Norman Ken Ouchi Project workflow system
US6934932B2 (en) * 2001-10-16 2005-08-23 Sharp Laboratories Of America, Inc. System and method for managing workflow using a plurality of scripts
US7171468B2 (en) * 2001-11-10 2007-01-30 Kabushiki Kaisha Toshiba System and method for accessing a document management repository
US7408658B2 (en) 2001-12-04 2008-08-05 Hewlett-Packard Development Company, L.P. Generation and usage of workflows for processing data on a printing device
US6898625B2 (en) * 2001-12-18 2005-05-24 Hewlett-Packard Development Company, L.P. Document tracking methods and system therefor
US20030142128A1 (en) 2002-01-30 2003-07-31 Benefitnation User interface for a document component management and publishing system
US7111024B2 (en) 2002-04-19 2006-09-19 Kabushiki Kaisha Toshiba Document management system for automating operations performed on documents in data storage areas
US20070146781A1 (en) * 2002-05-28 2007-06-28 Garg Man M Method and implementation of capturing print data from heterogeneous networked clients
US7146413B2 (en) 2002-06-14 2006-12-05 Hewlett-Packard Development Company, L.P. Remote updating of printer settings on a client device in a networked environment
DE10348563B4 (en) * 2002-10-22 2014-01-09 Fisher-Rosemount Systems, Inc. Integration of graphic display elements, process modules and control modules in process plants
US7146231B2 (en) * 2002-10-22 2006-12-05 Fisher-Rosemount Systems, Inc.. Smart process modules and objects in process plants
US7134150B2 (en) 2002-11-25 2006-11-14 Steve Stewart Foot-operated toilet seat
US7136941B2 (en) 2002-12-04 2006-11-14 Microsoft Corporation Print management architecture for computing devices having a set of filters functions wherein the functions are prevented from conflicting with one another
US20040148271A1 (en) * 2003-01-28 2004-07-29 Stephen Wood System and method for defining and processing decision processes
US7168077B2 (en) * 2003-01-31 2007-01-23 Handysoft Corporation System and method of executing and controlling workflow processes
US7200860B2 (en) * 2003-03-05 2007-04-03 Dell Products L.P. Method and system for secure network service
GB2486832A (en) * 2007-03-09 2012-06-27 Cummins Allison Corp Document processing system using blind balancing

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5815152A (en) * 1995-04-18 1998-09-29 Logical Software Solutions Corporation Method and apparatus for defining and evaluating a graphic rule
US7007275B1 (en) * 1999-10-21 2006-02-28 Unisys Corporation Method and apparatus for automatic execution of concatenated methods across multiple heterogeneous data sources
US6701366B1 (en) * 1999-11-09 2004-03-02 Nortel Networks Corporation Providing communications services
US6966029B1 (en) * 1999-12-08 2005-11-15 Koninklijke Philips Electronics N.V. Script embedded in electronic documents as invisible encoding
US20020161462A1 (en) * 2001-03-05 2002-10-31 Fay Todor J. Scripting solution for interactive audio generation
US20030131075A1 (en) * 2001-05-08 2003-07-10 Narad Networks, Inc. Language and interface for unified network service creation, provision and deployment
US7398237B2 (en) * 2001-06-26 2008-07-08 International Business Machines Corporation Rule based engine for validating financial transactions
US7069536B2 (en) * 2001-06-28 2006-06-27 International Business Machines Corporation Method, system, and program for executing a workflow
US7363377B1 (en) * 2002-10-09 2008-04-22 Unisys Corporation Method for protecting the program environment of a microsoft component object model (COM) client

Also Published As

Publication number Publication date
CN1532752A (en) 2004-09-29
US20090276493A1 (en) 2009-11-05
US20040205758A1 (en) 2004-10-14
KR100592101B1 (en) 2006-06-21
US20190230145A1 (en) 2019-07-25
US20190230144A1 (en) 2019-07-25
US11546407B2 (en) 2023-01-03
US20160173562A1 (en) 2016-06-16
US20220078225A1 (en) 2022-03-10
JP2004288054A (en) 2004-10-14
US10291683B2 (en) 2019-05-14
KR20040086512A (en) 2004-10-11
CN1312598C (en) 2007-04-25
US11201905B2 (en) 2021-12-14
JP4232499B2 (en) 2009-03-04
US20130139086A1 (en) 2013-05-30

Similar Documents

Publication Publication Date Title
US11546407B2 (en) Service processing system and service processing method
US7551303B2 (en) Service processing device and method
US7496233B2 (en) Service processing apparatus and service processing method
US8223370B2 (en) Information processing system, program, recording medium, and history information displaying method
KR100711837B1 (en) Apparatus and method for processing service
US8610922B2 (en) Information processing apparatus, image input apparatus, document distribution system, and control method therefor
US7418632B2 (en) Service processing system, processing result management device and processing result checking method of service processing system
JP4055618B2 (en) Image processing device
JP4745866B2 (en) Device management system and control method thereof
JP2002200827A (en) Imaging apparatus, imaging method and program for executing that method by computer
JP4985318B2 (en) Image processing apparatus and method
US7844910B2 (en) Linking information making device, linking information making method, recording medium having recorded a linking information making program, and document processing system therewith
US6704775B1 (en) Facsimile image information managing system and method
JP4501723B2 (en) Image processing apparatus, image processing method, and program
JP2004288055A (en) Service processing system, service processing method and service processing program
JP2005262675A (en) Service processing device
JP2008005518A (en) Image processing system
JP2005258626A (en) Service processing device and program
JP2005258545A (en) Service processing device

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION