proj title of specification (acronym) · web view3/19/2012 · the ieee-isto takes no position...

May 26, 2023Working Draft

The Printer Working Group

Cloud Imaging Requirements and Model

Status: Preliminary

Abstract: This document contains new specifications to support Cloud based printing and multifunction imaging using the PWG semantic model.

This document is a PWG Working Draft. For a definition of a "PWG Working Draft", see: ftp://ftp.pwg.org/pub/pwg/general/pwg-process30.pdf

This document is available electronically at:

ftp://ftp.pwg.org/pub/pwg/cloud/wd-cloudmodel10.docx

Copyright © 2011 The Printer Working Group. All rights reserved.

12345678910

12

13

14

15

1617

1819

20

21

Working Draft – Cloud Imaging May 26, 2023

Copyright © 2011 The Printer Working Group. All rights reserved.

This document may be copied and furnished to others, and derivative works that comment on, or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice, this paragraph and the title of the Document as referenced below are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the IEEE-ISTO and the Printer Working Group, a program of the IEEE-ISTO.

Title: Cloud Imaging Requirements and Model

The IEEE-ISTO and the Printer Working Group DISCLAIM ANY AND ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED INCLUDING (WITHOUT LIMITATION) ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

The Printer Working Group, a program of the IEEE-ISTO, reserves the right to make changes to the document without further notice. The document may be updated, replaced or made obsolete by other documents at any time.

The IEEE-ISTO takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights.

The IEEE-ISTO invites any interested party to bring to its attention any copyrights, patents, or patent applications, or other proprietary rights which may cover technology that may be required to implement the contents of this document. The IEEE-ISTO and its programs shall not be responsible for identifying patents for which a license may be required by a document and/or IEEE-ISTO Industry Group Standard or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. Inquiries may be submitted to the IEEE-ISTO by e-mail at: [email protected].

The Printer Working Group acknowledges that the IEEE-ISTO (acting itself or through its designees) is, and shall at all times, be the sole entity that may authorize the use of certification marks, trademarks, or other special designations to indicate compliance with these materials.

Use of this document is wholly voluntary. The existence of this document does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to its scope.

of 20 Copyright © 2011 The Printer Working Group. All rights reserved.

12

22

23242526272829

30

31323334

353637

3839404142

43444546474849

50515253

54555657

3


About the IEEE-ISTO

The IEEE-ISTO is a not-for-profit corporation offering industry groups an innovative and flexible operational forum and support services. The IEEE-ISTO provides a forum not only to develop standards, but also to facilitate activities that support the implementation and acceptance of standards in the marketplace. The organization is affiliated with the IEEE (http://www.ieee.org/) and the IEEE Standards Association (http://standards.ieee.org/).

For additional information regarding the IEEE-ISTO and its industry programs visit:

http://www.ieee-isto.org

About the IEEE-ISTO PWG

The Printer Working Group (or PWG) is a Program of the IEEE Industry Standards and Technology Organization (ISTO) with member organizations including printer manufacturers, print server developers, operating system providers, network operating systems providers, network connectivity vendors, and print management application developers. The group is chartered to make printers and the applications and operating systems supporting them work together better. All references to the PWG in this document implicitly mean “The Printer Working Group, a Program of the IEEE ISTO.” In order to meet this objective, the PWG will document the results of their work as open standards that define print related protocols, interfaces, procedures and conventions. Printer manufacturers and vendors of printer related software will benefit from the interoperability provided by voluntary conformance to these standards.

In general, a PWG standard is a specification that is stable, well understood, and is technically competent, has multiple, independent and interoperable implementations with substantial operational experience, and enjoys significant public support.

For additional information regarding the Printer Working Group visit:

http://www.pwg.org

Contact information:

The Printer Working Groupc/o The IEEE Industry Standards and Technology Organization445 Hoes LanePiscataway, NJ 08854USA


45

58

596061626364

65

66

67

6869707172737475767778

798081

82

83

84

858687888990

6

http://www.ieee-isto.org/

http://standards.ieee.org/)

http://www.ieee.org/


About the Cloud Imaging Work Group

Description of Cloud Imaging.

Cloud-based applications and solutions are increasingly common, and Cloud-based printing, scanning, and facsimile (collectively called "Cloud Imaging") are emerging in several different forms. Adopting standard protocols and schemas now will help interoperability, speed adoption, and address privacy, security, and legal issues involved in Cloud Imaging.

For additional information regarding Cloud Imaging visit:

http://www.pwg.org/Cloud/

Implementers of this specification are encouraged to join the Cloud Imaging mailing list in order to participate in any discussions of the specification. Suggested additions, changes, or clarification to this specification, should be sent to the Cloud Mailing list for consideration.


78

91

92

9394959697

98

99

100101102103

9


Table of Contents1. Introduction......................................................................................................................62. Terminology.....................................................................................................................6

2.1 Conformance Terminology.........................................................................................62.2 Other Terminology.....................................................................................................7

3. Requirements..................................................................................................................73.1 Rationale for Title of Standard...................................................................................73.2 Use Cases.................................................................................................................83.3 Design Requirements..............................................................................................14

4. First Specification Section.............................................................................................155. Internationalization Considerations................................................................................156. Security Considerations.................................................................................................157. IANA Considerations.....................................................................................................158. References....................................................................................................................15

8.1 Normative References.............................................................................................158.2 Informative References............................................................................................15

9. Author's Addresses........................................................................................................15

List of FiguresFigure 1 - Cloud Print Model................................................................................................4

List of TablesTable 1 - An Example Table................................................................................................4


1011

104105106107108109110111112113114115116117118119120121122

123124

125126

127128129

12


1. Introduction

Cloud-based applications and solutions are increasingly common, and Cloud-based printing, scanning, and facsimile (collectively called "Cloud Imaging") are emerging in several different forms. Adopting standard protocols and schemas now will help interoperability, speed adoption, and address privacy and security issues involved in Cloud Imaging.

A basic functional model including a Client, Cloud Print Provider, Cloud Print Manager, and Printer was developed in Cloud Printing BOF sessions. This model revealed several new requirements beyond the existing PWG Semantic Model including registration, enumeration/selection, use of late transforms to preserve fidelity, additional notification events, strict privacy and security policies, and reliable logging.

2. Terminology

2.1 Conformance Terminology

Capitalized terms, such as MUST, MUST NOT, RECOMMENDED, REQUIRED, SHOULD, SHOULD NOT, MAY, and OPTIONAL, have special meaning relating to conformance as defined in RFC 2119 [RFC2119].]. The term CONDITIONALLY REQUIRED is additionally defined for a conformance requirement that applies to a particular capability or feature.

2.2 Other Terminology

Cloud Printing - any solution that connects a Client to a Printer through a shared Cloud Print Provider.

Cloud Print Provider - the software component that manages printing between Clients and Cloud Printer Managers.

Cloud Printer Manager - the software component that implements the interface between the Cloud Print Provider and Printer.

Client - standard IPP definition.

Device – A physical or logical output device that can return status and capabilities


1314

130

131

132133134135136

137138139140141

142143

144

145

146147148149150

151

152153

154155

156157

158

159

15


Printer - standard IPP definition.

Registration - process by which a Client or Cloud Printer Manager associates itself with the Cloud Print Provider.

3. Requirements

3.1 Rationale for Cloud Imaging

Cloud-based applications and solutions are increasingly common, and Cloud-based printing, scanning, and facsimile (collectively called "Cloud Imaging") are emerging in several different forms. Adopting standard protocols and schemas now will help interoperability, speed adoption, and address privacy, security, and legal issues involved in Cloud Imaging.

Cloud printing has many potential implementation methods to comply with the need for security, and that the components can be located or contained within different locations.

The cloud can be a private cloud, a hybrid model, or a public cloud. The actual print device may be located at the users location, part of the service provider, at a remote user location, or remotely as a pay to print destination.

3.2 Use Cases

3.1 Print

Printing is a common (perhaps the most common) use case for Devices. Each of the use

cases in this section begin by initiating a print, selecting a Device (section 3.1), querying

the Device status, capabilities, and status information, and displaying of any status

information important to the User. Each use case generally ends with the User collecting

the printout from the Device.

Preconditions: For all of the following use cases, the Device must be Visible to the Client

in order to be selected, either directly or through an intermediate Service. Also, the

document to be printed must be Visible to the Device and in a format suitable for the

Device or converted by the Client (or Service) into a suitable format.


1617160

161162

163

164

165166167168169

170171

172173174

175

176

177

178

179

180

181

182

183

184

185

186

18


3.1.1 Print a Document

User has a mobile device connected to the Wi-Fi network in her business. User has a document to print prior to a meeting and has it available from her mobile device. User initiates a print from the mobile device and chooses a Printer that has been associated with the mobile device previously. User submits the print job. Once the Printer determines that the settings are valid, the job is printed. User picks up her job at the Printer.

3.1.1.1 Goals

User obtains a high-quality print with good performance from her mobile device.

3.1.1.2 Preconditions

Printer is accessible from User’s mobile device.

Printer supports the document format or Client can convert to Printer's supported document formats.

3.1.1.3 Steps

Print a document:

1. User initiates a print from an application on her mobile device.2. Client user interface provides a list of available Printers.3. User selects an available Printer from the list.4. Client user interface provides controls for creating job ticket.5. User selects job ticket options such as duplex and media size.6. User submits the print job.7. Client user interface sends job ticket and document data to Printer in a job creation request. 8. Printer validates job ticket and document data and returns job identifier and status to Client user

interface.9. Client user interface presents status to User.

3.1.1.4 Post-Conditions

Job is printed

3.1.1.5 Design Requirements

Printer must supply capabilities and status information to Client

Printer must support validation of job tickets and document data.

3.1.1.6 Internationalization Considerations

Job ticket information such as the job name can contain Unicode characters.


1920187

188189190191192

193

194

195

196

197198

199

200

201202203204205206207208209210

211

212

213

214

215

216

217

21


3.1.1.7 Security Considerations

Unlimited print jobs can cause a denial of service.

Document data can contain executable code or may exploit known Printer software vulnerabilities such as buffer overflows.

3.1.2 Print a Document by Reference

User has a mobile device connected to the Wi-Fi network in her business. User is viewing a document on a server and would like to print it. User initiates a print from the mobile device and chooses a Printer that has been associated with the mobile device previously. User submits the print job. Once the Printer determines that the settings are valid, the job is printed. User picks up her job at the Printer.

3.1.2.1 Goals

User obtains a high-quality print with good performance from her mobile device.


Printer is accessible from User’s mobile device.

Printer has access to the User's document.

Printer supports the document format or Client can convert to Printer's supported document formats.

3.1.2.3 Steps

Print a document by reference:

10. User initiates a print from an application on her mobile device.11. Client user interface provides a list of available Printers.12. User selects an available Printer from the list.13. Client user interface provides controls for creating job ticket.14. User selects job ticket options such as duplex and media size.15. User submits the print job.16. Client user interface sends job ticket and document URI to Printer in a job creation request. 17. Printer validates job ticket and document URI and returns job identifier and status to Client user

interface.18. Client user interface presents status to User.


Job is printed


Printer must supply capabilities and status information to Client


2223218

219

220221

222

223224225226227

228

229

230

231

232

233234

235

236

237238239240241242243244245246

247

248

249

250

24


Printer must support validation of job tickets and document URIs.

Printer must support printing of remote documents via URI.





Document URIs may require authentication or have other security requirements for access from the Printer.


3.1.3 Print a Photo

User is viewing a photo and would like to print the photo on the largest borderless photographic media available on her Printer. User selects a printer with the necessary capabilities and submits the photo for printing.

3.1.3.1 Goals

To produce a high-quality photographic print on borderless media.


Printer is accessible from Client.

Printer supports photo printing and offers borderless media sizes.

3.1.3.3 Steps

Printing a photo:

1. User initiates a print from an application.2. Client user interface provides a list of available Printers offering photo printing support.3. User selects an available Printer from the list.4. Client user interface provides controls for creating job ticket.5. User selects job ticket options such as print quality and media size.6. User submits the print job.7. Client user interface sends job ticket and photo to Printer in a job creation request. 8. Printer validates job ticket and photo and returns job identifier and status to Client user interface.9. Client user interface presents status to User.


2526251

252

253

254

255

256

257258

259260

261

262263264

265

266

267

268

269

270

271

272273274275276277278279280

27



Photo is printed.


Printer must advertise photo printing capabilities.

Printer must supply capabilities and status information to Client.

Printer must support validation of job ticket and photo.

Printer must support printing of borderless photos.





Document URIs may require authentication or have other security requirements for access from the Printer.


3.1.4 Print a Form

The treasurer of a small training company that is holding a meeting and seminar at a resort needs to print out 20 checks for training personnel. He uses an accounting program to enter the hours worked, bonuses, reimbursable expenses, and so forth and prints the checks on a printer provided by the resort using check blanks he brought to the meeting.

3.1.4.1 Goal

To print checks for all meeting personnel at the conclusion of the meeting.


Printer is accessible from Client.

Printer supports printing on forms such as check blanks.


2829281

282

283

284

285

286

287

288

289

290

291

292293

294295

296

297298299300301

302

303

304

305

306

30


3.1.4.3 Steps

Print a Form:

1. User updates his accounting grogram, determines what checks need to be printed and insures that checks amounts, payees and signature are correct.

2. User locates an available printer3. User ensures that printer is free, locks out other jobs and loads the check blanks.4. User initiates check printing. (put in a validate job operation?)5. The system (or the application) submits the job to the printer.6. Checks are printed and immediately taken off the printer.7. Cost of printing (not including media) is calculated and sent to treasurer’s account.


The accounting program properly reflects all outstanding checks. The treasurer has a stack of properly printed checks. The Treasurer will be charged for the use of the printer.




3.1.5 Special Formatting Printing

At a seminar located at a country resort, a factotum and general gofer has been asked to provide 80 sets of ten keywords/phrases, clearly printed on 2-inch by 1-inch paper slips for use in a get acquainted exercise. Costs are to be minimized. Gofer has a laptop with a word processer program. Resort has a wi-fi network available to users and a networked MFD at the business centre. Attendant at business center will charge for any printed sheets removed from premises

3.1.5.1 Goals

Gofer must provide paper slips of the specified size with legible text, promptly and cheaply.


TBD – to an extent, this is part of solution since at the present time site does not have advanced capabilities that we which to define. However, we can note that security is one of many concerns.

3.1.5.3 Steps

Special formatting printing:

1. Gofer creates the page descriptions on his word processor program.


3132307

308

309310311312313314315316

317

318319

320

321

322

323

324325326327328329

330

331332

333

334335336

337

338

339

33


2. Gofer locates an available printer3. User initiates printing. (put in a validate job operation?)4. The system (or the application) submits the job to the printer.5. Two sheets are printed with 80 phrases. User must then use scissors to cut part


Gofer will be charged for printing two single sided sheets.




3.1.6 Prescription Printing

Doctor has a mobile device and wants to send a prescription to a particular drug store for a patient in off hours. The Doctor selects a target printer based on the Cloud Provider’s information regarding the geographic location of the printer. The user configures the print job, and once the Cloud Provider determines that the settings are valid, the job is sent to the targeted device and printed. The third party receives the print job at the targeted printer.

3.1.6.1 Goals

User sends a hand written prescription print job from their mobile device to the geographically located printer through a Cloud Provider


User’s mobile device is capable of interacting with a Cloud Provider supporting the IPP Everywhere protocol.

User’s mobile device supports prescription generation.

3.1.6.3 Steps

Prescription printing:

1. User initiates a print command from an application that can generate print content2. User queries Cloud Provider for printers in a specific geographic location that supports the

features needed for their print job. (example: prescription printing)3. User chooses an available printer from the available devices4. User configures the print job, setting options5. User submits the job6. The mobile device validates the print job through the Cloud Provider using IPP Everywhere to talk

to the Cloud Provider7. The mobile device submits the job to the Cloud Provider8. The Cloud Provider submits the job to the target printer through IPP Everywhere


3435340341342343

344

345

346

347

348

349

350351352353354355

356

357358

359

360361

362

363

364

365366367368369370371372373374

36


9. User gets confirmation of job submitted/completed by the Cloud Provider

Alternate steps:

6a. The Cloud Provider could deem the job settings invalid and return the job to the user for correction.

6b. The IPP Everywhere printer could deem the job settings invalid and return the job to the Cloud Provider who in turn returns the job to the user for correction

9a. An error could be encountered, in which case the user would be notified by the Cloud Provider on how to proceed.


The IPP Everywhere printer has printed the job the user sent.

The IPP everywhere printer is available to accept additional print jobs.




3.1.7 Print and Select at Device

One or more Devices are integrated with a Service to provide "follow me" printing. The

User may release a job at a given Device by providing a PIN and/or other unique identification/authorization information such as a username and password or ID card. After initiating a print and selecting a Service, the User specifies the processing intent and PIN for the Job and confirms the print action. The Client sends a print job request to the service with the Job Ticket and local document. The Service validates the Job Ticket and document data and then holds the document until released by the User at the Device.

Precondition: The Client and Device support a common authorization or identification system.

3.1.8 Print to a Service

John is flying to New York for a presentation and doesn't want to carry the presentations.

John arrives in New York and goes online from his mobile phone. He selects a local print provider after reviewing the provider web pages and submits his document for printing. He specifies that he needs 10 color copies, printed duplex and stapled on the left side. He also specifies the covers to be 80lb. stock, and the internal pages to be 24lb. stock. John


3738375

376

377378

379380

381382

383

384

385

386

387

388

389

390

391392393394395396

397398

399

400

401402403404

39


arrives at the provider and picks up his presentations, paying with his corporate credit card.

3.1.9 Print with a Proof Copy

After initiating a print and selecting a Device, the User specifies the processing intent, requests a proof print, and confirms the print action. The Client sends a print job request to the Device with the Job Ticket and local document. The Device validates the Job Ticket and document data and then prints a proof copy of the document. The User collects the proof printout from the Device and verifies correct output. The User then initiates a full print of the document from the Client or Device to produce the final printout.

3.2 Out of Scope

Provide a list of use cases that are out-of-scope and the reasons.

Defining Cloud federation interfaces and associated protocols and technologies.

Defining the interface between the Cloud Imaging Manager and Imaging Device, specifically the interface for device and job status and job submission.

Defining new protocols for authentication, authorization, and access control (AAA), enumeration, transport, notification, and device management.

Defining new document file formats.

Defining new abstract job tickets.

3.3 Design Requirements

3.3.1 Registration

Process by which a Client or Cloud Print Manager associates itself with the Cloud Print Provider

3.3.2 Enumeration/selection

Process by which a Client finds candidate devices and selects one for a subsequent print job


4041405406

407

408409410411412413

414

415

416

417

418419

420421

422

423

424

425

426427

428

429430

42


3.3.3 Bindings

3.3.3.1 IPP binding documents for Cloud Print and Cloud 60 Multifunction services.

3.3.3.2 SOAP binding documents for Cloud Print and Cloud Multifunction services with associated XML schemas/WSDL definitions and equivalent informative REST bindings.

3.3.4 Transforms

3.3.5 Notification events

3.3.5.1 Cloud Print Provider to Client

3.3.5.2 Cloud Print Provider to Cloud Print Manager

3.3.5.3 Cloud Print Manager to Printer

3.3.5.4 Printer to Cloud Print Manager

3.3.5.5 Cloud Print Manager to Cloud Print Provider

3.3.5.6 Cloud Print Provider to Cloud Print Provider

3.3.6 Privacy and security policies

3.3.6.1 Encryption for privacy/security

3.3.6.1.1 X.509 authentication/authorization

3.3.6.1.2 Encryption of all data between Client, Cloud Print Provider, Cloud Print Manager, and potentially Printer

3.3.6.2 Firewall/router/network traversal

All connections between Client, Cloud Print Provider, Cloud Print Manager, and Printer need to be considered

3.3.7 Logging

3.3.7.1Security auditing

3.3.7.2 Maintenance

3.3.7.3 Billing


4344431

432

433434435

436

437

438

439

440

441

442

443

444

445

446

447448

449

450451

452

453

454

455

456

45


4. Model

4.1 Top Level model

In a cloud environment, an individual client may not be aware of the components and services needed to enable printing to a device that may be located at an external location, including appropriate tracking, security, and transforms required to produce and deliver the requested output.

4.1.1 Client

The client is responsible for supply information including the document to be printed, the attributes associated with the appearance of the document, and the location and method of where the document will be delivered.

4.1.2 Cloud Print Provider

Acting as a gateway the cloud print provider will provide the client with a single point of contact. The cloud print provider will be responsible for providing the client with print devices available for selection, job and device status, and tracking/logging of print job details. The cloud print provider will also interface with the cloud print manager supplying the cloud print manager with print data and job ticket information while maintaining status information.

4.1.3 Cloud Print Manager

The software component that implements the interface between the Cloud Print Provider and Printer is responsible for delivering the print data and returning status and tracking information to the cloud print provider.


4647

457

458

459460461462

463

464465466

467

468469470471472473

474

475476477

478

48


5. Conformance RequirementsProvide a list of conformance requirements for the document.

6. Internationalization ConsiderationsFor interoperability and basic support for multiple languages, conforming implementations MUST support the UTF-8 [RFC3629] encoding of Unicode [UNICODE] [ISO10646].

7. Security ConsiderationsProvide security considerations for this specification.

8. IANA ConsiderationsProvide IANA registration information for this specification.

Subsections include IANA registration templates using the Example style:

Some IANA registration text.


4950

479

480

481

482

483484

485

486

487

488

489

490

51


9. References

9.1 Normative References

[REFERENCE] F. Last author list or standards body, "Title of referenced document", Document Number, Month YYYY, URL (if any)

9.2 Informative References

[REFERENCE] F. Last author list or standards body, "Title of referenced document", Document Number, Month YYYY, URL (if any)

10. Authors' AddressesLarry Upthegrove4605 Goldcrest WayAntioch, CA [email protected]

The authors would also like to thank the following individuals for their contributions to this standard:


5253

491

492

493494

495

496497

498

499500501502

503504

505

54


11. Change History

11.1 Month, DD, YYYY

Initial revision.


5556

506

507

508

57

proj title of specification (acronym) · web view3/19/2012 · the ieee-isto takes no position...

Documents