PSI 1.0 Usage 20030327 An overview of usage models enabled by the PSI set of interfaces

PSI 1.0 Usage 20030327

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.


Service Based Portal Printing

1. Client interacts with a Portal or Enterprise Gateway (for example RIM’s Blackberry Enterprise Server).

2. Portal retrieves source document.3. Portal initiates print job and

delivers source document to Print Service JobControl.


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.


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.


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. Client informs TargetDevice of job a Print Service

4. Target Device behind an enterprises firewall contacts Print Service utilizing TargetDeviceSupport interface.

5. Target Device pulls data and prints users Job.

PSI Interface Deployment Model

Print Service

QueryEndpointsInterface

JobControlInterface

TargetDeviceSupportInterface

JobControlInterface

Client

Target Device Mobile

Client

Client

QueryEndpointsInterface

ServiceCapabilitiesInterface


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

Job and Document retrieval Target Device, 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 End Points and

WSDL definitions


GetTargetDeviceElements– Enables direct and proxied Target Device

capabilities discovery.– Aligned with PWG Common Semantic Model Printer

object – Supported, Ready, Default and Actual options

GetKnownTargetDevices– Exposes the 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 Target Device for the Job.– Allows specification of Job Processing and Default Document

Processing options.– 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. CloseJob

– Informs Service or Target Device that client is done submitting Documents for Job


AddDocumentByReference– Allows specification of Document Processing options. Unsupported

options are returned to client.– Rich reference definition: URL, FTP, File, eMail, Pop3, Imap, UNC, -

extensible to other references AddDocumentByPush

– 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. PushDocumentDataDelivered

– Informs that the document data for the AddDocumentByPush call as been completely delivered.

AddDocumentByValue– Allows base64Binary encoding of data in method call.


GetJobElements, GetDocumentElements– Allows a client to query the status of Jobs and Documents in

detail.

GetJobs, GetDocuments– Allows a client to get a list of Jobs or Documents

CancelJob, CancelDocument– Allows the client to cancel the Job, or individual Documents

within the Job

FetchJobs– Informs TargetDevice that it is to fetch a job from a particular

print service.


RegisterTargetDevice– Allows a Target Device to register with a Print

Service

UnregisterTargetDevice– Allows TargetDevice to un-register itself with a Print

Service


FetchNextJob– Allows Target Device to query for the availability of Jobs.

CloseJob– Allows Target Device to inform service that it has completed

processing of the Job. FetchNextDocumentByPull

– Allows Target Device to query for the availability of a document, and to retrieve the document data.

PullDocumentDataFetched– Allows Target Device to inform service that the data has been

completely retrieved. FetchNextDocumentByValue

– Allows Target Device to query for the availability of a document, and to retrieve the document data in-band.


SendTargetDeviceNotification, SendJobNotification, SendDocumentNotification– Allows Target Device to inform Print Service of

changes in Printer, Job and Document Status