PSI Usage 0.94b An overview of usage models enabled by the PSI set of interfaces.

Use Models PSI Enables Service Based Printing – Mobile Printing – Portal Printing – Enterprise Printing Direct Printing – Mobile Printing – Desktop Printing Secure, Authenticated Printing Firewall Traversal

Service Based Mobile Printing Mobile clients (PDAs, cell phones, cameras, etc.) can use PSI to render and print local content stored on the client. 1.Client initiates print job and delivers source document to Print Service JobControl 2.Print Service renders document to printer specific format and delivers it to PSI Target Device (printer) 1.Client initiates print job and delivers source document to Target Device JobControl 2.Target Device forwards document to Print Service JobControl. 3.Print Service renders document to printer specific format and delivers it to PSI Target Device (printer)

Service Based Portal Printing 1.Client interacts with a Portal or Enterprise Gateway (for example RIMs Blackberry Enterprise Server). 2.Portal retrieves source document. 3.Portal initiates print job and delivers source document to Print Service JobControl. 4.Print Service renders document to printer specific format and delivers it to PSI Target Device (printer)

Service Based Enterprise Printing 1.Client initiates print job and delivers a content reference to Print Service JobControl 2.Print Service resolves content reference and retrieves the source document. 3.Print Service renders document to printer specific format and delivers it to PSI Target Device (printer) 1.Client initiates print job and delivers a content reference to Target Device JobControl 2.Target Device forwards content reference to Print Service JobControl. 3.Print Service resolves content reference and retrieves the source document. 4.Print Service renders document to printer specific format and delivers it to PSI Target Device (printer) Mobile clients (PDAs, cell phones, cameras, etc.) can use PSI to render and print remote content by reference.

Direct Mobile and Desktop Printing Clients can render data that the device can consume directly. 1.Client connects directly to Target Device. 2.Client determines capabilities of Target Device, and device PDL format utilizing ServiceCapabilitiesInterface. 3.Client renders to document data to PDL of Target Device, and delivers utilizing JobControlInterface.

Secure, Authenticated Printing All models can utilize standard HTTPS for secure, authenticated printing.

Firewall Traversal 1.Target Device registers itself with Print Service utilizing TargetDeviceSupport Interface. 2.Client initiates Print Job with the Print Service utilizing JobControlInterface. 3.Target Device behind an enterprises firewall contacts Print Service utilizing TargetDeviceSupport interface. 4.Target Device pulls data and prints users Job.

PSI Interface Deployment Model

PSI Interfaces QueryEndPointsInterface – Extensible discovery of all interfaces that a Print Service and a Target Device support. ServiceCapabilitiesInterface – TargetDevice and Print Service capabilities discovery. JobControlInterface – Transform and Deliver Workflow multi-document Job creation and control. – PWG Common Semantic Model Job and Document processing options. – By Value and By Reference document data submission. TargetDeviceSupportInterface – Firewall traversal from Target Device to Print Service Document retrieval Job and Document status eventing – Target Device registration with Print Service

QueryEndPointsInterface QuerySupportedInterfaces – Allows a client to determine the interfaces that a service supports – Services can advertise additional interfaces beyond the required PSI set. This enables vendor extensibility. QueryInterfaceDefinition – Allows client to retrieve interface HTTP End Points and WSDL definitions

ServiceCapabilitiesInterface GetTargetDeviceElements – Enables direct and proxied Target Device capabilities discovery. – Aligned with PWG Common Semantic Model Printer object – Supported, Ready and Default options GetKnownTargetDevices – Exposes Target Devices a print service has discovered, or that have registered ValidateReference – Reference and credential validation

JobControlInterface (1) CreateJob – Allows a client to create a Job on a Print Service, or on a Target Device for direct print. – Allows specification of Job Processing and Default Document Processing options. – Allows specification of Target Device for Job. – Service and Target Device can inform client about which requested options it does not support. – Client can specify if service is to attempt to deliver transformed data, or if Target Device is going to retrieve the data. – Multiple documents allowed in a Job. Both By Value and By Reference.

JobControlInterface (2) AddDocumentByReference – Allows specification of Document Processing options. Unsupported options are returned to client. – Rich reference definition: URL, FTP, File, , Pop3, Imap, UNC, - extensible to other references AddDocumentByPost – Enables a push of the document data from the client to the service. – Allows specification of Document Processing options. Unsupported options are returned to client. GetJobElements, GetDocumentElements – Allows a client to query the status of Jobs and Documents in detail. CancelJob, CancelDocument – Allows the client to cancel the Job, or individual Documents within the Job

TargetDeviceSupportInterface AssociateTargetDevice – Allows a Target Device to associate itself with a particular Job, or a particular user. – Target Device can specify its data type. GetNextJob, GetNextDocument – Allows Target Device to query for the availability of Jobs and Documents. SendJobNotification, SendDocumentNotification – Allows Target Device to inform Print Service of changes in Job and Document Status RegisterTargetDevice, UnregisterTargetDevice – Allows TargetDevice to register itself with a Print Service