proj title of specification (acronym) -...

May 14, 2023Working Draft

The Printer Working Group

Common Use Cases

Status: Interim

Abstract: This document provides a repository of well-defined use cases, design requirements, internationalization considerations, security considerations, and references for use in PWG standards-track documents.

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

This document is available electronically at:

ftp://ftp.pwg.org/pub/pwg/general/wd/wd-commonusecases10-20110827.docx and ftp://ftp.pwg.org/pub/pwg/general/wd/wd-commonusecases10-20110827.pdf

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

12345678910

11

12

13

14

151617

1819

20

2122

Working Draft – PWG Common Use Cases May 14, 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: PWG Common Use Cases

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 19 Copyright © 2011 The Printer Working Group. All rights reserved.

12

23

24252627282930

31

32333435

363738

3940414243

44454647484950

51525354

55565758

34


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


56

59

606162636465

66

67

68

6970717273747576777879

808182

83

84

85

868788899091

78

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

http://standards.ieee.org/)

http://www.ieee.org/


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

2.1 Precondition Terminology..........................................................................................83. Use Cases.......................................................................................................................8

3.1 Select Device.............................................................................................................83.1.1 Select the Last Used Device...............................................................................83.1.2 Select Device Using Name or Address...............................................................93.1.3 Select Device Using URI.....................................................................................93.1.4 Select Device Using a Directory Service.............................................................93.1.5 Select Device Using a Cloud Service..................................................................93.1.6 Select Device Using a Discovery Protocol..........................................................93.1.7 Select Device Using Geo-Location....................................................................103.1.8 Select Device Using Out of Band Method.........................................................103.1.9 Select Device Using Properties.........................................................................10

3.2 Print..........................................................................................................................113.2.1 Print a Document...............................................................................................113.2.2 Print a Document by Reference........................................................................113.2.3 Print Using Loaded Media.................................................................................113.2.4 Print a Secure Form..........................................................................................123.2.5 Print with Special Formatting.............................................................................123.2.6 Print and Select at Device.................................................................................123.2.7 Print to a Service...............................................................................................133.2.8 Print to a Recipient............................................................................................133.2.9 Print with a Proof Copy......................................................................................13

3.3 Scan.........................................................................................................................143.3.1 Scan a Document..............................................................................................143.3.2 Scan a Photo.....................................................................................................143.3.3 Scan with Presets..............................................................................................143.3.4 Scan Using a Cloud Service..............................................................................143.3.5 Scan and Select at Device................................................................................14

3.4 Facsimile..................................................................................................................143.4.1 Fax a Document................................................................................................143.4.2 Fax a Photo.......................................................................................................143.4.3 Fax with Presets................................................................................................143.4.4 Fax Using a Cloud Service................................................................................143.4.5 Fax and Select at Device...................................................................................14

3.5 Transforms...............................................................................................................143.6 Status Monitoring.....................................................................................................143.7 Job Control and Management..................................................................................14

3.7.1 Release Job for Printing....................................................................................153.7.2 Reprint Job........................................................................................................15

3.8 Exceptions...............................................................................................................153.8.1 Select Device Canceled....................................................................................15


910

9293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135

1112


3.8.2 Device No Longer Visible after Selection..........................................................153.8.3 Not Authorized...................................................................................................153.8.4 Not Authenticated..............................................................................................153.8.5 Not Accepting Jobs............................................................................................153.8.6 Document Format Not Supported......................................................................153.8.7 Document Processing Failed.............................................................................153.8.8 Device Fault......................................................................................................153.8.9 Device Warning.................................................................................................153.8.10 Billing Error......................................................................................................15

3.9 Access Control.........................................................................................................153.9.1 Authenticated Guest Access.............................................................................153.9.2 Pre-Authorization of User..................................................................................163.9.3 Post-Authorization of User.................................................................................163.9.4 Authentication of User.......................................................................................16

3.10 Auditing..................................................................................................................163.11 Accounting.............................................................................................................16

3.11.1 Collect Detailed Job/Document Metrics...........................................................163.11.2 Query Device for Accounting Information Before Print....................................17

3.12 Regulatory Compliance..........................................................................................173.12.1 Copyright.........................................................................................................173.12.2 Privacy.............................................................................................................173.12.3 Identification....................................................................................................17

4. Design Requirements....................................................................................................175. Security Considerations.................................................................................................176. Internationalization Considerations................................................................................177. References....................................................................................................................17

7.1 Normative References.............................................................................................177.2 Informative References............................................................................................17

8. Authors' Addresses........................................................................................................179. Change History..............................................................................................................19

9.1 July 31, 2011............................................................................................................199.2 May 24, 2011...........................................................................................................19


1314136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169

1516


1. IntroductionThis document provides a common repository of casual use cases, design requirements, internationalization considerations, security considerations, and references for PWG standards-track documents. It has been developed to consolidate the overlapping use cases and design requirements of the Cloud Imaging, Imaging Device Security, Internet Printing Protocol, and Multifunction Device working groups so that a coherent view of Devices and Services can be adopted and appropriate (and necessary) standards written to address the common use cases. This document specifically does not address administration, configuration, or setup of Imaging Devices or Services.

These job-related use cases are organized into subsections for selection, printing, scanning, facsimile, transforms, status monitoring, exception handling, access control, auditing, and accounting use cases. Each subsection contains a named use case with a casual use case definition.

2. TerminologyThe following terms are used throughout this document:

Billing; Remuneration for processing of a job

BOOTP; Network address auto-configuration using the Boot Protocol [RFC????].

Cellular Network; A restricted-access voice and data network connected using a combination of radio frequency signal "cells" with optical or electrical cabling.

Cellular Network Settings; .....

Client

Cloud

Cloud Service

Device; IPP definition; also see Logical Device and Physical Device

DHCP; Network address auto-configuration using the Dynamic Host Configuration Protocol [RFC2131].

Directory Service; A Service providing query and enumeration of information using names or other identifiers.

Discovery Protocol; A (typically) connectionless protocol for enumeration of local Devices.


1718

170

171172173174175176177178

179180181182

183

184

185

186

187188

189

190

191

192

193

194195

196197

198

1920


DNS; Network address and name resolution using the Domain Name Service [RFC1034????].

DNS-SD; Service Discovery using DNS-Based Service Discovery [DNS-SD].

Imaging Device;

Job; A queued unit of work such as a document for printing.

Logical Device;

Physical Device;

Device;

Scanner;

Service; Software providing access to physical, logical, or virtual resources and (typically) processing of queued Jobs.

User; A person or automata using a Service.

User Interface; A human interface to the Device provided through Client software, embedded web server, or the Device control panel, console, or touch screen.

Visible Device; A Device that can be directly accessed by a Client.

Wired Network; A traditional computer network connected using electrical or optical cabling.

Wired Network Settings; The IPv4 and/or IPv6 network addresses, network masks, and default router addresses combined with a host name. May also include domain, DNS server addresses, Directory Service name, address, and authentication information, Cloud Service name, address, and authentication information, and Syslog host addresses.

Wireless Network; A traditional computer network connected using antennae and radio frequency signals.

Wireless Network Settings; The IPv4 and/or IPv6 network addresses, network masks, and default router addresses combined with a network name and host name. May also include a network password, domain, DNS server addresses, Directory Service name, address, and authentication information, Cloud Service name, address, and authentication information, and Syslog host addresses.

ZeroConf; Automatic network address assignment using Dynamic Configuration of IPv4 Link-Local Addresses [RFC3927] and IPv6 Link Local addressing.


2122199200

201

202

203

204

205

206

207

208209

210

211212

213

214215

216217218219

220221

222223224225226

227228

2324


2.1 Precondition Terminology

The following terms are used as preconditions for the scenarios and use cases in this document:

Connected Network; An IP network to which a Client or Device has access.

Directory Device; A printer selected by query or enumeration of a directory such as LDAP.

Discovered Device; A printer selected through an ad-hoc Discovery Protocol such as DNS-SD, SNMP broadcast, and UPNP.

Service Device; A printer selected by query or enumeration of a Service such as an enterprise print server or Cloud Imaging Service.

Static Device; A printer selected using its IP address, URI, or other static identifier.

Visible/Visibility; Refers to the ability of one device to communicate directly with another, for example a Client is able to connect to a Device, query for supported attributes, submit print jobs, and so forth.

3. Use Cases

3.1 Select Device

Device selection is part of most Service use cases - the User selects a Device, implicitly or explicitly, and the remainder of the use case applies to the selected device. A Device can be a Logical Device such as a Scan Service or a Physical Device such as a Printer. Selection use cases can often be combined, for example Selection Using a Directory Service (section 3.1.4) with Selection Using Properties (section 3.1.9).

In order to simplify the selection use cases, common exceptions are listed as separate use cases in section 3.8. Similarly, access control and authentication use cases are listed separately in section 3.9.

Precondition: For all of the following use cases, the Device must be Visible to the Client to be selected, either directly or through an intermediate Service.

3.1.1 Select the Last Used Device

The Client User Interface displays the last used Device as a selection. The User then confirms the selection of the last used Device.

The last used Device may be automatically selected by the Client User Interface and may be affected by the current network topology or geo-location, for example the last used


2526

229

230231

232

233

234235

236237

238

239240241

242

243

244245246247248

249250251

252253

254

255256

257258

2728


Device may be tracked on a per-network (e.g. default router or other criteria), per-location (e.g. geo-location), or per-Service (e.g. current local server) basis.

3.1.2 Select Device Using Name or Address

The Client User Interface asks the User for a name or address for the Device. The User then provides a Device name or address through the Client User Interface. Finally, the Client User Interface queries the Device for valid Service URIs.

The Device name can be a DNS-SD Service name, a fully-qualified domain name, or other unique identifying name. The Device address can be a numeric IP address or other unique identifying number.

3.1.3 Select Device Using URI

The Client User Interface asks the User for a Service URI for the Device. The User then provides a URI through the Client User Interface or cancels selection.

For example, the user could supply an IPP URI: "ipp://example.com/port1" as reported by the Device's network configuration page.

3.1.4 Select Device Using a Directory Service

The Client obtains a list of Devices on behalf of the User from the Directory Service and validates that each Device supports one or more Client-supported Service protocols. The Client User Interface then asks the User to select one of the supported Devices. Finally, the User selects a Device.

Preconditions: One or more Devices are listed in a Directory Service and that Directory Service is Visible to the Client.

3.1.5 Select Device Using a Cloud Service

The Client obtains a list of Devices on behalf of the User from the Cloud Service(s). The Client User Interface then asks the User to select one of the Devices. Finally, the User selects a Device.

Preconditions: The Client and one or more Devices are registered with a Cloud Service, and that Cloud Service is Visible to both the Client and Devices. The Client and Devices may be registered with multiple Cloud Services, and both may maintain multiple identities for a particular Cloud Service.


2930259260

261

262263264

265266267

268

269270

271272

273

274

275276277278

279280

281

282

283284285

286287288289

3132

Michael Sweet, 09/26/11,

Reword this to make it clear that we filter the list of printers based on the supported service protocols


3.1.6 Select Device Using a Discovery Protocol

The Client initiates Discovery on behalf of the User and maintains a dynamic list of Visible Devices during selection. The Client User Interface asks the user to select one of the Visible Devices, updating those Devices as they come and go. Finally, the User selects a Device and the Client terminates Discovery.

Preconditions: The Device is Visible to the Client and supports a common Discovery Protocol.

3.1.7 Select Device Using Geo-Location

The Client initiates a proximity detection of nearby Devices using Services and/or Discovery Protocols, hiding duplicate Devices that are reported by multiple Service and/or Discovery Protocols. The Client User Interface asks the User to select one of the nearby Devices. Finally, the User selects a nearby Device.

Preconditions: Both the Client and Device have access to geo-location information to allow for proximity detection, and both support common Discovery Protocol(s).

3.1.8 Select Device Using Out of Band Method

The User asks the Client User Interface to identify the Device. The Client initiates identification to obtain a Service URI and descriptive information. The Client User Interface then asks the User to confirm the selection of the identified Device. Finally, the User confirms the selection.

Precondition: The Device and Client support a common identifying technology such as near-field communications, QRCodes, or bar codes.

3.1.9 Select Device Using Properties

A User selects a Device using properties such as Service, capability, or description properties of the Device. Service properties include the application protocol, security, or restrictions such as the maximum number of pages allowed in a job. Capability properties include values such as media, duplex, finishing, color support, and so forth, Description properties include values such as location, speed, color support, and job size. The properties may be provided by a combination of User input, policy, and/or software heuristic.


3334290

291

292293294295

296297

298

299

300301302303

304305

306

307

308309310311

312313

314

315316317318319320321

3536


The User asks the Client User Interface to select using properties. The Client obtains a list of Devices for the User that meet the given properties provided by the Client software, policy, and/or User and validates that each Device supports one or more Client-supported Service protocols. The Client User Interface then asks the User to select one of the supported Devices. Finally, the User selects a Device.

3.2 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.

3.2.1 Print a Document

User has a Client connected to the Wi-Fi network in her business and has a document to print prior to a meeting that is stored on her phone.

After the user User initiates a print and selects a Device, the User specifies the processing intent for the Job 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 the document.

3.2.2 Print a Document by Reference

User has a Client connected to the Wi-Fi network in her business and is viewing a document on a server that she would like to print.

After the user initiates a print and selects a Device, the User specifies the processing intent for the Job and confirms the print action. The Client sends a print job request to the Device with the Job Ticket and remote document URI. The Device validates the Job Ticket and document URI and then prints the document.

3.2.3 Print Using Loaded Media

User is viewing a photo and would like to print the photo on the largest borderless photographic media loaded on her Device.


3738322323324325326

327

328329330331332

333334335336

337

338339

340341342343

344

345346

347348349350

351

352353

3940


After the User initiates a print from the phone and selects a Device, the Client automatically selects the largest borderless photographic media loaded on the Selected Device and the highest print quality. The User selects additional processing intent for the Job and confirms the print action. The Client sends a print job request to the Device with the Job Ticket and local photo. The Device validates the Job Ticket and document data and then prints the photo.

Preconditions: Device can report loaded media information such as size, type, coating, and weight. This may be detected automatically or manually entered by the User or Operation when loading the media.

3.2.4 Print a Secure 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.

The User loads check blanks into the Device and configured the loaded media as necessary at the Device. After the User initiates a print from his accounting program, selects a Device for printing, and selects checks to be printed, the Client User Interface displays a preview of the printed checks and the User confirms that checks amounts, payees and signature are correct. The Client automatically selects the check blank media. The User selects additional processing intent for the Job and confirms the print action. The Client sends a print job request to the Device with the Job Ticket and document data containing the checks, correctly oriented for the check blank media. The User waits for the checks to be printed and removes any excess media from the Device.

3.2.5 Print with Special Formatting

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 center. Attendant at business center will charge for any printed sheets removed from premises.

After the User initiates a print from his word processor and selects a Device, the User selects the processing intent for the Job and confirms the print action. The Client produces document data using the media information (size and margins) in the Job Ticket so that 2-inch by 1-inch slips are spread evenly over each page and sends a print job request to the Device with the Job Ticket and document. The Device validates the Job Ticket and document data and then prints the document.


4142354355356357358359

360361362

363

364365366367368

369370371372373374375376377

378

379380381382383384

385386387388389390

4344


3.2.6 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.2.7 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 arrives at the provider and picks up his presentations, paying with his corporate credit card.

3.2.8 Print to a Recipient

The recipient 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 Device, the User specifies the processing intent, specifies a recipient, 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 holds the document until released by the recipient. Finally, the recipient collects the printout from the Device.

3.2.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.


4546391

392393394

395396397398

399400

401

402403404405406407408

409

410411

412413414415416

417

418419420421422423

4748


3.3 Scan

3.3.1 Scan a Document

3.3.2 Scan a Photo

3.3.3 Scan with Presets

3.3.4 Scan Using a Cloud Service

3.3.5 Scan and Select at Device

"Follow me" scanning use case.

3.4 Facsimile

3.4.1 Fax a Document

3.4.2 Fax a Photo

3.4.3 Fax with Presets

3.4.4 Fax Using a Cloud Service

3.4.5 Fax and Select at Device

"Follow me" fax use case.

3.5 Transforms

TBD

3.6 Status Monitoring

TBD

3.7 Job Control and Management

For general Operator use cases.


4950

424

425

426

427

428

429

430

431

432

433

434

435

436

437

438

439

440

441

442

443

5152


3.7.1 Release Job for Printing

3.7.2 Reprint Job

3.8 Exceptions

3.8.1 Select Device Canceled

3.8.2 Device No Longer Visible after Selection

3.8.3 Not Authorized

3.8.4 Not Authenticated

3.8.5 Not Accepting Jobs

3.8.6 Document Format Not Supported

and any other job creation errors due to the document or Job Ticket.

3.8.7 Document Processing Failed

and any other job processing errors that are reported to the User or Operator.

3.8.8 Device Fault

Out of Paper and any other "something has happened that requires your attention" errors at the Device. Reported to User and/or Operator depending on use case.

3.8.9 Device Warning

Low Toner and any other advisory messages from the Device. Reported to User and/or Operator depending on use case.

3.8.10 Billing Error

Credit card denied and other failure to pay for services?

3.9 Access Control

3.9.1 Authenticated Guest Access

John and Steve both have cloud repositories accounts. Steve has at least one cloud print account and has some administrative privileges


5354444

445

446

447

448

449

450

451

452

453

454

455

456

457458

459

460461

462

463

464

465

466467

5556


John, a high-school student, rushes out of the house on his way to his friend’s (Steve) house and, then, to school. In less than 5 minutes he arrives at Steve house. Steve waves his history report at John to show him it is done and printed. John reaches in his backpack to realize he has forgotten his printed copy. John tells Steve he has a copy of his report on his cloud and could he print it at his house. Steve agrees. Steve ask John for his cloud user name and adds John as a ‘friend’ to his cloud aware printer. John promptly logs into his cloud account and finds his history report. Invoking a print request, John sees that Steve’s printer has been added to this printer list. Selecting Steve’s printer, John prints his report and they are both off to school.

Optional: Steve’s system administrator (dad) does not want the ‘friend’s’ list for the printer to be to long; so, Steve removes John from the ‘friend’s’ list and John see the printer disappear from this printer list.

Steve logs in to his cloud account and adds John to the ‘friend’s’ list for his home printer. The cloud system updates the ‘friend’ access list and adds Steve’s home printer to John’s printer list.

John logs in to his cloud account and selects his document and request a print. John selects Steve’s home printer from his printer list. The cloud system presents a print dialog using the capabilities for Steve’s home printer. John sets his print options and presses the print button. The print dialog generates a Print-Job-Ticket and records the URI for Steve’s document in the Print-Job-Ticket. The print dialog passes the print request to the cloud repository print client manager. The cloud repository print client manager checks the status of Steve’s printer. The cloud repository print client manager sends the print job to Steve’s printer. The cloud repository print client manager receive a print-complete. The cloud repository print client manager updates John’s print status. The cloud repository print client manager removes the job from its queue.

3.9.2 Pre-Authorization of User

3.9.3 Post-Authorization of User

3.9.4 Authentication of User

3.10 Auditing

TBD

3.11 Accounting

3.11.1 Collect Detailed Job/Document Metrics

including pages/sheets, color usage, media, finishing, job receipt, date/time info, owner of 19 Copyright © 2011 The Printer Working Group. All rights reserved.

5758468469470471472473474475476

477478479

480481482

483484485486487488489490491492

493

494

495

496

497

498

499

500

5960


3.11.2 Query Device for Accounting Information Before Print

including charge info URI and summary/info text

3.12 Regulatory Compliance

3.12.1 Copyright

3.12.2 Privacy

3.12.3 Identification

4. Design RequirementsThe Device must have a reusable, persistent, and unique identifier such as a URI.

5. Security ConsiderationsDevices should provide access control through authentication or other accepted methods.

6. Internationalization Considerations

7. References

7.1 Normative References

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

7.2 Informative References

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

8. Authors' AddressesMichael SweetApple Inc.


6162501

502

503

504

505

506

507

508

509

510

511

512

513

514

515516

517

518519

520

521522

6364


10431 N. De Anza Blvd.MS 38-$LPTCupertino, CA 95014 USA

Justin HutchinsMicrosoft Corporation

Glen PetrieEpson

Craig ShifmanKonica Minolta

Larry UpthegroveEnd-User

William WagnerTechnical Information Consulting


6566523524525526527528529530531532533534535536537538539540

6768


9. Change History

9.1 July 31, 2011

1. Major revision to casual use case format, break out selection and exceptions from use cases, and drop scenarios.

2. Incorporated new use cases from Larry Upthegrove.

9.2 May 24, 2011

Initial revision.


6970

541

542

543544545

546

547

7172

proj title of specification (acronym) -...

Documents