WO2000023912A1 - Systeme de livraison de documents sur reseau - Google Patents

Systeme de livraison de documents sur reseau Download PDF

Info

Publication number
WO2000023912A1
WO2000023912A1 PCT/US1999/024482 US9924482W WO0023912A1 WO 2000023912 A1 WO2000023912 A1 WO 2000023912A1 US 9924482 W US9924482 W US 9924482W WO 0023912 A1 WO0023912 A1 WO 0023912A1
Authority
WO
WIPO (PCT)
Prior art keywords
document
name
recipient
data stream
programmed
Prior art date
Application number
PCT/US1999/024482
Other languages
English (en)
Inventor
Dennis W. Hicks
Richard Newman
Gary Johnson
Lisa O'toole
David Hay
Chris Gyllenskog
Steven C. Johnson
Matt Stephenson
Frank Hartmann
Ray Asbury
Eric Luttmann
Original Assignee
Oce-Usa Inc.
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
Priority claimed from US09/175,905 external-priority patent/US7086001B1/en
Application filed by Oce-Usa Inc. filed Critical Oce-Usa Inc.
Priority to AU65211/99A priority Critical patent/AU6521199A/en
Publication of WO2000023912A1 publication Critical patent/WO2000023912A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/103—Formatting, i.e. changing of presentation of documents

Definitions

  • Microfiche Appendix This specification has appended hereto a microfiche appendix tiavlng 17 flche containing approximately 4600 frames. 5
  • This invention generally relates to document handling on a computer network, and more particularly, this invention relates to a recipient based system for printing, faxing, storing and transmitting electronic documents !5 across networks.
  • this general end Is achieved by a system of networked computers, peripherals and document delivery software which provlde ⁇ the user with a familiar simple user interface, such as a print dialog box in a Windows® environment, to deliver documents to a variety of different destinations, both within the network, across networks and outside of the network via remote links
  • a document generation device participating In the system may be provided with a print driver which translates an electronic document into a non-specific, or printer independent, printer language file and appends to this file a job ticket containing any other rendering characteristics which may not be supported by the printer independent language.
  • Rendering characteristics include such things as color or monochrome output, duplex printing, number of original copies, stapling, collating, binding, recipient and destination information, etc. This entire file Is then transmitted to the system server which analyzes the file, including the rendering characteristics; determines the best output devlce(s); appends output device specific commands to the general printer language file; and transmits this file to the device(s).
  • the Job ticket and related flexibility of the software also enable recipient baaed delivery and result based delivery, both of which represent a paradigm shift away from device based printing Reoipient based delivery focuses upon the location of a particular reoipient and the medium through which that recipient prefers to receive information, as opposed to a particular printer in the general location of the recipient.
  • Result based delivery focuses on the presentation and medium for delivery of Information, as opposed to a particular device or device location
  • the software on the server assigns an affinity value to each print job based upon the job size, destination and rendering characteristics This affinity value Is then used to determine which output devlce( ⁇ ) will receive the document
  • the server must therefor be aware of what output devices are participating In the system, where they are located, what their specific characteristics are and w ether or not any particular device is currently available, This Information may be gathered automatically by having the server poll for network resources, the Information may be manually entered by a user or system administrator, or the Information may be input by a combination of the two methods.
  • the user may elect to bypass the invention by selecting a specific printer driver rather than that of the invention.
  • the invention software on the server
  • This system facilitates the ability to implement many other valuable and desirable features.
  • One such feature is the ability to distribute a large job over two or more output devices participating In the system, essentially defining multiple output devices as a single output device This Is most advantageous where a single job contains multiple original copies and each output device receives one or more entire copies to output, thereby decreasing output time by a factor of the number of output devices and not causing the user to collate pages from multiple output devices. Additionally, the Invention can distribute jobs over the output resources on the network to even distribute the workload.
  • an activity log or journal which can provide detailed Information concerning usage.
  • the log can provide such information as the size and number of print jobs requested by any combination of users for billing purposes; job completion verification; diagnostic Information to allow an operator to determine when and why Jobs failed; and resource utilization Information such as toner usage for a printer to plan for Inventory, expenses and maintenance.
  • the journal may be kept In a standard database format which may be easily Imported to accounting, database or other computer applications.
  • the invention can support virtually any output device such as: standard Image forming devices Including printers, plotters, and video; facsimile devices; email communications; data communications links; and archival devices.
  • output device such as: standard Image forming devices Including printers, plotters, and video; facsimile devices; email communications; data communications links; and archival devices.
  • banner and receipt pages can be generated.
  • Banner pages can be used to identify sets of > jobs on each printer and notify the operator of any finishing operations to be performed.
  • Receipt pages can be used to provide a short job summary and verify job completion.
  • Supported data communications can include serial telecommunications via data mode s, network communications using TCP/IP,
  • archival and storage of documents may be done in a platform Independent format such as ADOBE'S Portable Document Format (PDF).
  • PDF Portable Document Format
  • RDF allows a user of virtually any operating system to view and print archived 5 documents using a freely distributed viewing program, ADOBE ACROBAT READER.
  • the software on the server can be oonfigured so that a job sent to a specific port or by a particular type of printer driver Is always output the same way or according to a specific set of rules
  • a printer specific printer 0 .driver such as a HEWLETT PACKARD LASERJET driver, and still have the job output to one or more different devices.
  • FIG. 1 Is a schematic representation of a network document delivery system acoordlng to the Invention
  • Fig. 2 Is a block diagram illustrating the functional aspects of the ⁇ oftwar ⁇
  • Fig. 3 Is a graphic representation of the connections that may be made 5 to a representative hardware system;
  • Fig. 4 is a graphic representation of a high level system object model of the Invention;
  • Fig. 5 Is a graphic representation of a subordinate level object model showing the relationship between a task and a job
  • Fig 6 is a graphic representation of a subordinate level object model ) showing the relationship between users and objects
  • Fig. 7 Is a graphic representation of a subordinate level object model showing the relationship between the general product and different types of output
  • Fig. 10 Is a graphic representation of a subordinate level object model showing the hierarchical relationship between a system device and an atomic device; 0 Figs. 11 and 12 describe the general life cycle model and rely on the schemata Figs. 13 through 55;
  • Fig, 56 describes the Fusion notation used In Figs. 4 through 10;
  • Fig. 57 describes the Life Cycle Model notation used in Figs. 11 and
  • Fig. 62 Is an object interaction graph Illustrating how affinity Is determined
  • Fig. 63 Is an object interaction graph illustrating the submit Job 0 sequence
  • Fig. 64 is an object interaction graph illustrating the Instruct to job ticket sequenoe
  • Fig. 65 is an object interaction graph Illustrating the Instruct to Instruction set sequence
  • Fig 66 is an object Interaction graph illustrating the normal execute sequence
  • Figs. 67 through 81 Illustrate one possible graphical user Interface for the Job ticket and show some of the various delivery options.
  • the network shown includes at least one document generator 11, such as a networked personal computer, having a client user Interface 12 Installed therein; a server 13 having main job processing software 14 therein Including a server user Interface 15; and two or more document output devices 16.
  • Fig. 3 shows a representative hardware connection configuration or network on whloh the Invention may be implemented.
  • the simplified user model illustrated in Fig. 2 provides a procedural view Of system operation.
  • the overall system may Include a main program 14, multiple data sources, such as client print driver 17, and/or other Input clients, such as a manufacturer specific print driver 18, and multiple output devices 16.
  • a job is sent from a data source such as document generator 11 to main program 14 via a data port 19,
  • a Job must contain a data stream to be rendered, also referred to as image data, on some output device.
  • the job may also contain a job ticket, which is a coiiection of specific Information concerning the desired output presentation, such as a standard hard copy print job; a fax; an archival; an email; finishing features; routing information; and even billing Information, l ⁇ the case, where print driver 17 is used, here when the user selects "auto" as the print destination, job ticket information is provided by client print driver 17,
  • print driver 17 Includes a generic language translator 24 which translates an electronic document Into a non-specific, or printer independent, printer language file and appends to this file a job ticket containing any other rendering characteristics which may not be supported by the printer independent language.
  • the job information may be provided by 'default' Job tickets or port profiles associated with a data port, a user name which can be determined from the network name, or a
  • Job parser 20 examines the Incoming job for a job ticket and applies ) default job tickets as required, then sends the job to routing and affinity process 21 .
  • Routing and affinity process 21 determines the capabilities required to complete the job successfully and the affinity of each potential output device for the job, Routing and affinity process 21 assigns an affinity value to each print job based upon the job size, destination and rendering characteristics by comparing the requested features 3 with the available features logged in resource library 25. Available resources may be gathered and logged Into resource library 25 by server 13 automatically by polling the network for resources.
  • the information may be manually entered by a user or system administrator or It may be Input by a combination of the two methods,
  • the job is then routed to a device specific assembler 22, also sometimes 0 called the 'transform', to change the image data to a device specific form.
  • the Image data Is then sent to the appropriate output devlce(s) 16 via a communications channel 23,
  • the current status of each device can be monitored by the main program via communication channel 23.
  • output devices 16 are printers, but they can also be 5 fax machines, electronic storage media, such as a 'file' on diskette, removable media, hard disk, tape drive, network drive, etc., or even email.
  • the simplified model can be extended to Include multiple data ports with an associated default job ticket or port profile for each A combination of port and port profile is referred to as a 'virtual queue'
  • client print driver 17 '.0 can reside on the same host as main program 1 , so that the operator of main program 14 can also submit Jobs.
  • Fig. 2 provides a procedural view of system operation
  • the following Illustrative embodiment takes advantage of the multitasking nature of a host operating system, such as WINDOWS > NT and the capabilities of object oriented programming techniques. This embodiment is Illustrated in Fig. 4.
  • the main program Is actually a set of programs running simultaneously. Also, the Job parsing, routing, and assembling functions are spread out over a set of objects.
  • One possible set of object models are shown in Figs. 4 -
  • a job is a task, and a job includes at least one document. Tasks may have one or more parent/child relationships.
  • External agents such as the human operator, are also represented by objects, even though the object may
  • FIG. 4 Each of the objects shown in Fig. 4 can be decomposed or broken down into other objects as shown in the other figures.
  • the objects enclosed within dashed lines are programs The Operator, Recipient, and User are people as shown In Fig. 6.
  • a Product Is the output of the system as shown Fig. 7.
  • a job is created by a data source such as a document generator 1 1 and more specifically, usually by client print driver 17.
  • Fig. 8 shows a more detailed view of possible types of data sources and their relationships to data ports. Note that remote systems can send jobs Just like any local source. Likewise, a remote system may be configured as a device. This allows passing of a Job from system to
  • the purpose for configuring the Systems this way is to reduce phone charges by using local area network (LAN) communications between main systems. This allows jobs to be passed to LAN or phone connected printers, even though the printers are not available to the local " system.
  • LAN local area network
  • the job parsing function Is performed by the data port.
  • the port creates a job object In the system that includes a document, I.e. Image data, and job ticket as shown in Fig. 5.
  • the job ticket may need to be formed from an associated port
  • the job ticket Is designed to allow routing of the Job to the best device and storing of data for billing and management purposes,
  • the Job ticket allows separation of the job specific features, such as number of copies, finishing, recipient information, etc., from the image data.
  • job specific Information needs to be In a form unique to each printer or output device, depending on Its manufacturer and its configuration as it was Installed, as some finishing features such as sorters and staplers are optional.
  • the Specialization of the generic or device independent data stream to the actual production device data stream is done after the production device is chosen by the System,
  • the data port creates a job and passes it to the system device.
  • Fig. 9 shows the device hierarchy
  • Fig. 10 shows the device relationships.
  • the devices contain the routing function ⁇ jipwn in the simplified model. All devices are implemented as objects.
  • Device Objects are serialized meaning configuration parameters are stored to disk so that they rriay be restored after a system reset.
  • a key feature of the device design is the relationship between pool6, arrays, and atomic devices as Illustrated In Fig. 10, A pool Is generally a grouping of
  • Jlk ⁇ devices Jlk ⁇ devices.
  • the grouping can be by function such as faxes, printers, or archive , devices, or by some other criteria such as location, e.g. all printers on the second . floor, permissions, or routing.
  • An array Is a collection of like devices.
  • An atomic device represents the smallest whole constituent part. As far as the parent pool is conoerned, an array is an atomic device, and thus the array class is derived from the atomic device class. At the lowest level, an atomic device 'knows' that It is capable
  • Devices contain many of the unique features of the invention As an example, arrays are defined as collections of devices which are capable of receiving and producing the desired output. The device hierarchy and built in routing capability allow arrays to break a job down into tasks, one task per copy. The separate tasks are sent to each of the devices constituting the array as each device is ready to receive Jt. Another example of a unique feature is the intelligent routing accomplished through capabilities and affinities The logic for routing is built in to each atomic device. The pass/fall response on capabilities and affinity number for a task Is passed to the parent device, which then compares the responses from each child device and sends the task to the appropriate device.
  • Another unique feature of the invention is intelligent translation of a job defined for one type of output device into another. Incoming jobs are often In a data stream that is incompatible with the best fit output device.
  • the intelligent translation device performs the appropriate translation based upon a separate determination of the best fit output device.
  • a current embodiment is capable of translating from ROSTSCRlPT to various forms of HP-PCL and PDF
  • the resource library and activity log or journal are advantageously coded as separate systems running simultaneously with the main system.
  • the aotivity Journal may be a database containing various tables, entries, queries, and reports relevant to the system.
  • the database interface can be provided by the operating system.
  • the database and its schema, e g. tables, queries, etc., are created at system startup if they don't already exist.
  • Exemplary database tables might Include: an ActlonLog which contains system startup and configuration change information; a Billing log which contains originator billing Information; a Company log which contains company address information, a FaxLlst log which relates fax completion statistics to recipients; a Job log which contains Job Information, such as ⁇ tart tlme, Stop time, originator, etc.; an Originator log which contains originator Information such as address, phone number, etc ; a Recipient log which contains recipient address information; a Recipient list which relates jobs to recipients; a Task JPg which contains task information such as start time, stop time, production device, etc., and a device log which contains physical device information.
  • ActlonLog which contains system startup and configuration change information
  • Billing log which contains originator billing Information
  • Company log which contains company address information
  • FaxLlst log which relates fax completion statistics to recipients
  • Job log which contains Job Information, such as ⁇ tart tlme, Stop time, originator, etc.
  • the operator user Interface allows the operator to configure the main system for the needs of a particular installation, and is Implemented as a separate program from the main system.
  • the main system is capable of operating without the operator user interface running.
  • the operator user interface also saves and loads Job templates. Job templates are job tickets that have been saved for later use, and Pan p ⁇ edited before submitting a job.
  • the invention examines the job ticket Information to route print Jobs to the most effective printer. This feature may be disabled during configuration. If a specific printer is selected by the user, and the printer does not exist, then the Job remains unassignable.
  • Each job is routed to a printer depending on whether the Job can be printed at ail, printer capabilities, and the best fit of additional performance or postprocessing factors, I.e. the affinity of the job to a printer or printer to a job.
  • Devices have a subset of attributes that define the types of tasks that can ba processed. If a task requests a function that is outside the set defined by the device's attributes, then the device Is considered to be Incapable of processing the task.
  • the attributes include the range of number of pages allowed in a single task, the ability to print color or strictly back and white pages, the ability to print duplex, and the ability to support a requested paper size, color or weight. A task's requirements must fall within all of these restrictions A task for which no capable devices can be found Is considered "Unassignable".
  • Automatic Assignment Is device selection that is Insensitive to the device's name If Automatic Assignment is not allowed by a device, and the task does not request that device specifying its name specifically, than the device Is considered Incapable. If a task requests a specific device, all devices that do not have the name requested are also * cons ⁇ dered incapable. If no device by the requested name is present In the system, or if no direct path to the requested device Is present, then the task is changed to allow Automatic Assignment Without regard for originally requested device name If no device name is ever requested by the task, Automatic Assignment Is assumed
  • Devices have another subset of attributes that define the device's ability to automate a number of processing options which Include the device's processing performance, and the operator's preference toward device
  • the affinity value for a device is calculated by accumulating the individual affinities given by examining each of the individual attributes
  • the automation attributes include the device's ability to collate, to $taple, to fold, to drill, to bind, and to add covers If a task requests one of these functions, the devices that provide the function are given a higher affinity than those devices that do not provide the function. Additional automation functions supported by the device, that are not requested by the task, are simply ignored
  • the device's performanpe is given as a single Impressions Per Minute (IPM) value.
  • IPM Impressions Per Minute
  • the assumption Is made that one minute is the optimal average amount of time that a device should spend processing a single task, and that thirty seconds Is the standard deviation.
  • the affinity of an array can be determined by averaging all of the affinities of the capable and available subordinate devices. There Is only one adjustment to the standard affinity calculations performed by the sub-devices The device's performance Is not factored into the result because, again, the page count for each device Is not known. All other affinity factors are evaluated normally.
  • Fi ⁇ s. 11 through 55 describe a life cycle model of one embodiment of the Invention.
  • the life cycle model describes the order in which system operations may occur.
  • Alphabet Any input or output event may be used in an expression. Output events are prefixed with #.
  • Name may be used In other expressions, but substitutions must not be recursive.
  • the recipient and result based paradigms mentioned earlier can be belter understood making reference to Figs. 67 - 81.
  • a user simply selects the recipient from the recipient list as Is shown In Fig. 67.
  • the Information is then delivered to that recipient based upon the recipient's preferred device or devices.
  • New recipients can be defined by entering the new recipient's Information, such as that shown In Figs. 68 - 70, or possibly as a result of that particular recipient joining the system as a new user by entering new user Information, such as that shown in Figs. 71 - 73.
  • Printing and delivery options can be selected by entering in the desired characteristics on the job ticket such as those shown In Flg ⁇ . 74 - 81.
  • the result oriented delivery paradigm is more of an inherent result of the design of the invention and is directly related to the affinity feature and a device's capability to produce the requested output.
  • output characteristics beyond the capability of a particular output device either simply were not presented as available options to the user or were altered, usually by being eliminated altogether, by the device specific print driver as the job was output.
  • all or some of the paradigms can be Implemented to whatever degree Is desired.

Abstract

L'invention se rapporte à un système d'ordinateurs et de périphériques en réseau et à un logiciel de livraison de documents qui offre à l'utilisateur une interface utilisateur (12) simple et classique pour délivrer des documents en une variété de destinations différentes. Chaque dispositif de production de document intégré au système est équipé d'un pilote d'impression unifié qui traduit un document électronique en un fichier en langage d'imprimante non spécifique ou indépendant de l'imprimante et ajoute audit fichier une fiche de travail contenant toutes les autres caractéristiques relatives au rendu qui peuvent ne pas être gérées par le langage indépendant de l'imprimante (24). Ce fichier est transmis dans sa totalité au serveur du système qui analyse le contenu de ce fichier, et en particulier les caractéristiques de rendu; détermine le meilleur dispositif de sortie possible (S); ajoute les commandes spécifiques du dispositif de sortie (18) au fichier de langage imprimante général; et transmet ledit fichier au(x) dispositif(s) en vue de l'impression finale.
PCT/US1999/024482 1998-10-20 1999-10-20 Systeme de livraison de documents sur reseau WO2000023912A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU65211/99A AU6521199A (en) 1998-10-20 1999-10-20 Network document delivery system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/175,905 US7086001B1 (en) 1997-10-22 1998-10-20 Automatic network device selection and document delivery system
US09/175,905 1998-10-20

Publications (1)

Publication Number Publication Date
WO2000023912A1 true WO2000023912A1 (fr) 2000-04-27

Family

ID=22642157

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1999/024482 WO2000023912A1 (fr) 1998-10-20 1999-10-20 Systeme de livraison de documents sur reseau

Country Status (2)

Country Link
AU (1) AU6521199A (fr)
WO (1) WO2000023912A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1014272A2 (fr) * 1998-12-23 2000-06-28 Nortel Networks Corporation Interface périphérique universelle
GB2379055A (en) * 2001-06-05 2003-02-26 Hewlett Packard Co Configuring Access to Services or a Database Using a Job Ticket
GB2382174A (en) * 2001-11-20 2003-05-21 Hewlett Packard Co Data formatting in a platform independent manner
GB2385693A (en) * 2001-06-05 2003-08-27 Hewlett Packard Co Database Comprising Job Ticket Service for Managing Tasks
US7349869B2 (en) 2001-06-05 2008-03-25 Hewlett-Packard Development Company, L.P. Use of a job ticket service to store bid information

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5384620A (en) * 1992-08-31 1995-01-24 Xerox Corporation Scheduling page parameter variations for discrete job elements
US5402527A (en) * 1993-04-23 1995-03-28 Xerox Corporation Apparatus and method for determining the page description language in which a print job is written
US5701500A (en) * 1992-06-02 1997-12-23 Fuji Xerox Co., Ltd. Document processor
US5715379A (en) * 1995-10-30 1998-02-03 Xerox Corporation Architecture for a digital printer with multiple independent decomposers

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5701500A (en) * 1992-06-02 1997-12-23 Fuji Xerox Co., Ltd. Document processor
US5384620A (en) * 1992-08-31 1995-01-24 Xerox Corporation Scheduling page parameter variations for discrete job elements
US5402527A (en) * 1993-04-23 1995-03-28 Xerox Corporation Apparatus and method for determining the page description language in which a print job is written
US5715379A (en) * 1995-10-30 1998-02-03 Xerox Corporation Architecture for a digital printer with multiple independent decomposers

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1014272A2 (fr) * 1998-12-23 2000-06-28 Nortel Networks Corporation Interface périphérique universelle
EP1014272A3 (fr) * 1998-12-23 2002-01-30 Nortel Networks Limited Interface périphérique universelle
GB2379055A (en) * 2001-06-05 2003-02-26 Hewlett Packard Co Configuring Access to Services or a Database Using a Job Ticket
GB2385693A (en) * 2001-06-05 2003-08-27 Hewlett Packard Co Database Comprising Job Ticket Service for Managing Tasks
GB2385694A (en) * 2001-06-05 2003-08-27 Hewlett Packard Co Controlling Tasks in a Networked Environment Using Job Tickets
GB2385693B (en) * 2001-06-05 2003-11-19 Hewlett Packard Co Use of a job ticket as a generic XML database
GB2385694B (en) * 2001-06-05 2003-12-17 Hewlett Packard Co Use of a job ticket as a generic XML database
GB2379055B (en) * 2001-06-05 2004-07-07 Hewlett Packard Co Use of a job ticket as a generic xml database
US7349869B2 (en) 2001-06-05 2008-03-25 Hewlett-Packard Development Company, L.P. Use of a job ticket service to store bid information
DE10224744B4 (de) * 2001-06-05 2010-07-29 Hewlett-Packard Development Co., L.P., Houston Verwendung eines Auftragsetikettdienstes, um Angebotsinformationen zu speichern
GB2382174A (en) * 2001-11-20 2003-05-21 Hewlett Packard Co Data formatting in a platform independent manner

Also Published As

Publication number Publication date
AU6521199A (en) 2000-05-08

Similar Documents

Publication Publication Date Title
US7086001B1 (en) Automatic network device selection and document delivery system
JP4954368B2 (ja) 複写センタへジョブを提出する方法及びシステム
US5974234A (en) Centralized print server for interfacing one or more network clients with a plurality of printing devices
US6020973A (en) Centralized print server for interfacing one or more network clients with a plurality of printing devices
US6246487B1 (en) Multi-function unit, server and network system having multi-function unit
US5778183A (en) Apparatus and method of automatically transmitting event-related information to a user of a network printing system
JP3904422B2 (ja) プロダクション・スキャナに接続するためのシステムおよび方法
US6453129B1 (en) System and method for providing job assurance
CN100476712C (zh) 信息处理装置、打印系统、打印设备、及其控制方法
EP1865409A2 (fr) Appareil de traitement des informations, procédé de commande d'impression et support lisible sur un ordinateur
US20010035972A1 (en) Adaptive interface for digital printing systems
US6535297B1 (en) Programmable auditron for multifunctional printing system
US7461069B2 (en) Log information management device, log information generation device, and computer-readable medium storing log information management program therein
JPH09234853A (ja) 電子的画像処理装置の動作方法
US7464134B2 (en) Mechanism and method for sharing imaging information from an enterprise resource planning computing environment
EP1710694A2 (fr) Appareil de communication, produit de programme de mécanisme de communication ajouté à l'appareil de communication fournissant l'usage amélioré et l'efficacité de la communication et produit de stockage du programme de support d'enregistrement
JP4666849B2 (ja) 印刷ジョブ管理方法および装置
JPH09226212A (ja) 電子的画像処理装置におけるコントローラの動作方法
US6909519B2 (en) Method and system for printer suggested upgrades
JPH11327861A (ja) 画像形成装置、方法および記録媒体
JPH07175603A (ja) プリント処理システム
JPH09207413A (ja) 電子的画像処理装置の駆動方法
WO2000023912A1 (fr) Systeme de livraison de documents sur reseau
US7196803B1 (en) System and method for printing to a printer without the use of a print driver
US6865564B2 (en) Method and system for printer suggested training

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref country code: AU

Ref document number: 1999 65211

Kind code of ref document: A

Format of ref document f/p: F

AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase