PROJ Title of Specification (Acronym)€¦ · Web viewWorking Draft – PWG Common Use CasesMay 24, 2011

May 15, 2023Working Draft

The Printer Working Group

Common Use Cases

Status: Initial Draft

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

This is a PWG Best Practices document. For a definition of a "PWG Best Practices 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-20110524.docx

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

12345678910

11

12

13

14

151617

1819

20

21

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

Page 2 of 34 Copyright © 2011 The Printer Working Group. All rights reserved.

12

22

23242526272829

30

31323334

353637

3839404142

43444546474849

50515253

54555657

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

58

596061626364

65

66

67

6869707172737475767778

798081

82

83

84

858687888990

78

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

http://standards.ieee.org/)

http://www.ieee.org/


Table of Contents1. Introduction......................................................................................................................62. Terminology.....................................................................................................................63. Use Cases.......................................................................................................................7

3.1 Setup..........................................................................................................................73.1.1 Connection of a Printer to a Wired Network........................................................73.1.2 Connection of a Printer to a Wireless Network....................................................93.1.3 Connection of a Printer to a Cellular Network...................................................103.1.4 Connection of a Printer to a Directory Service..................................................113.1.5 Connection of a Printer to Cloud Service..........................................................123.1.6 PLACEHOLDER FOR MORE SETUP USE CASES.........................................13

3.2 Administration and Configuration.............................................................................133.2.1 PLACEHOLDER FOR ADMINISTRATION AND CONFIGURATION USE CASES.......................................................................................................................13

3.3 Selection..................................................................................................................143.3.1 Selection of Printer Using Address or URI........................................................143.3.2 Selection of Printer Using a Directory Service...................................................153.3.3 Selection of Printer Using a Cloud Service........................................................153.3.4 Selection of Printer Using Proximity..................................................................163.3.5 PLACEHOLDER FOR MORE SELECTION USE CASES.................................17

3.4 Printing.....................................................................................................................183.4.1 Print a Document...............................................................................................183.4.2 Print a Document by Reference........................................................................193.4.3 Print a Photo......................................................................................................213.4.4 Print a Form.......................................................................................................223.4.5 Special Formatting Printing...............................................................................233.4.6 Prescription Printing..........................................................................................243.4.7 PLACEHOLDER FOR MORE PRINTING USE CASES....................................25

3.5 Scanning..................................................................................................................253.5.1 Use Case Title...................................................................................................253.5.2 PLACEHOLDER FOR MORE SCANNING USE CASES..................................26

3.6 Facsimile..................................................................................................................263.6.1 Use Case Title...................................................................................................263.6.2 PLACEHOLDER FOR MORE FACSIMILE USE CASES..................................27

3.7 Status Monitoring.....................................................................................................273.7.1 Use Case Title...................................................................................................273.7.2 PLACEHOLDER FOR MORE STATUS MONITORING USE CASES...............28

3.8 Access Control.........................................................................................................283.8.1 Authenticated Guest Access.............................................................................283.8.2 PLACEHOLDER FOR MORE ACCESS CONTROL USE CASES....................30

3.9 Auditing....................................................................................................................303.9.1 Use Case Title...................................................................................................303.9.2 PLACEHOLDER FOR MORE AUDITING USE CASES....................................31

3.10 Accounting.............................................................................................................31


910

919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134

1112


3.10.1 Use Case Title.................................................................................................313.10.2 PLACEHOLDER FOR MORE ACCOUNTING USE CASES...........................32

4. References....................................................................................................................324.1 Normative References.............................................................................................324.2 Informative References............................................................................................33

5. Authors' Addresses........................................................................................................336. Change History..............................................................................................................34

6.1 May 24, 2011...........................................................................................................34


1314135136137138139140141142143

1516


1. IntroductionThis document provides a common repository of 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, and Internet Printing Protocol working groups so that a coherent view of Multifunction Devices and services can be adopted and appropriate (and necessary) standards written to address the common use cases

This document is organized into sections for setup, administration and configuration, selection, printing, scanning, facsimile, status monitoring, access control, auditing, and accounting. Each subsection contains a named use case with subsections for goals, preconditions, steps, postconditions, design requirements, internationalization considerations, security considerations, and references.

2. TerminologyThe following terms are used throughout this document:

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

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.

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

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


1718

144

145146147148149150151

152153154155156

157

158

159

160161

162

163

164

165

166167

168169

170171

172

1920


Imaging Device

Printer

Scanner

Service; Software providing access to physical or virtual resources.

User; A person or automata using a Service.

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

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.

3. Use Cases

3.1 Setup

3.1.1 Connection of a Printer to a Wired Network

A Printer is connected to a Wired Network. The Wired Network Settings for the Printer are configured manually through a User Interface or configured automatically using BOOTP, DHCP, or ZeroConf.


2122173

174

175

176

177

178179

180181

182183184185

186187

188189190191192

193194

195

196

197

198199200

2324


3.1.1.1 Goals

To connect a Printer to a Wired Network so that Clients may submit print jobs, initiate scan jobs, query Printer status, and so forth.

3.1.1.2 Preconditions

A Wired Network exists, has sufficient capacity/ports to allow the Printer to be connected, has the necessary infrastructure needed to allow the Printer to obtain Wired Network Settings, and the necessary cabling and/or adapters are available.

3.1.1.3 Steps

Manual configuration:

1. Connect the necessary cabling and adapters to the Printer and Network.2. Use the User Interface to configure the Wired Network Settings.

Automatic configuration:

1. Connect the necessary cabling and adapters to the Printer and Network.2. If necessary, use the User Interface to configure the auto-configuration protocol

to BOOTP or DHCP.

3.1.1.4 Postconditions

Printer is connected to the Wired Network and has been configured with the correct Wired Network Settings.

3.1.1.5 Design Requirements

The Printer must provide a User Interface to configure the Wired Network Settings and automatic configuration protocol.

3.1.1.6 Internationalization Considerations

The User Interface may require localization.

3.1.1.7 Security Considerations

Automatic configuration of Wired Network Settings may allow unauthorized Printers to connect to the Wired Network.


2526201

202203

204

205206207

208

209

210211

212

213214215

216

217218

219

220221

222

223

224

225226

2728


3.1.2 Connection of a Printer to a Wireless Network

A Printer is connected to a Wireless Network. The Wireless Network Settings for the Printer are configured manually through a User Interface or configured automatically using BOOTP, DHCP, WPS, or ZeroConf.

3.1.2.1 Goals

To connect a Printer to a Wireless Network so that Clients may submit print jobs, initiate scan jobs, query Printer status, and so forth.


A Wireless Network exists, has sufficient capacity/spectrum to allow the Printer to be connected, has the necessary infrastructure needed to allow the Printer to obtain Wireless Network Settings, and the necessary antennae and/or adapters are available.

3.1.2.3 Steps


3. Connect the necessary antennae and/or adapters to the Printer.4. Use the User Interface to configure the Wireless Network Settings.

Semi-automatic configuration:

5. Connect the necessary antennae and/or adapters to the Printer.6. Use the User Interface to enter WPS mode or select the Wireless Network name

and provide a password as needed.7. If necessary, use the User Interface to configure the auto-configuration protocol

to BOOTP or DHCP.


Printer is connected to the Wireless Network and has been configured with the correct Wireless Network Settings.


The Printer must provide a User Interface to configure the Wireless Network Settings and automatic configuration protocol.




2930227

228229230

231

232233

234

235236237

238

239

240241

242

243244245246247

248

249250

251

252253

254

255

3132



Automatic configuration of Wireless Network Settings may allow unauthorized Printers to connect to the Wireless Network.

3.1.3 Connection of a Printer to a Cellular Network

A Printer is connected to a Cellular Network. The Cellular Network Settings for the Printer are configured manually through a User Interface.

3.1.3.1 Goals

To connect a Printer to a Cellular Network so that Clients may submit print jobs, initiate scan jobs, query Printer status, and so forth.


A Cellular Network exists, has sufficient capacity/spectrum to allow the Printer to be connected, has the necessary infrastructure needed to allow the Printer to obtain Cellular Network Settings, and the necessary antennae and/or adapters are available.

3.1.3.3 Steps


1. Connect the necessary antennae and/or adapters to the Printer.2. Use the User Interface to configure the Cellular Network Settings.


Printer is connected to the Cellular Network and has been configured with the correct Cellular Network Settings.


The Printer must provide a User Interface to configure the Cellular Network Settings.




TBD.


3334256

257258

259

260261

262

263264

265

266267268

269

270

271272

273

274275

276

277

278

279

280

281

3536


3.1.4 Connection of a Printer to a Directory Service

A Printer is connected to a Directory Service automatically or through a User Interface. The Printer then advertises its presence and description information through the Directory Service.

3.1.4.1 Goals

To advertise a Printer through a shared Directory Service so that Clients may use the Printer.


A Directory Service exists, has sufficient capacity to allow the Printer to advertise its presence, and is accessible from one or more connected networks.

3.1.4.3 Steps


3. Use the User Interface to configure the Directory Service address and authentication information, if necessary.


4. Wait for the Printer to obtain network settings containing Directory Service configuration information.


Printer is connected to the Directory Service and has advertised its presence.


The Printer must provide a User Interface to configure the Directory Service address and authentication information. The Printer may also use service discovery protocols to automatically connect to the Directory Service or provide an "optimized" User Interface.




Automatic configuration of Directory Service connections may allow unauthorized access to the Printer and its services and object data.


3738282

283284285

286

287288

289

290291

292

293

294295

296

297298

299

300

301

302303304

305

306

307

308309

3940


3.1.5 Connection of a Printer to Cloud Service

A Printer is connected to a Cloud Service automatically or through a User Interface. The Printer then advertises its presence and processes Client requests through and provides responses and status to the Cloud Service.

3.1.5.1 Goals

To advertise a Printer through a shared Cloud Service so that Clients may use the Printer.


A Cloud Service exists, has sufficient capacity to allow the Printer to advertise its presence and process Client requests, and is accessible from one or more connected networks.

3.1.5.3 Steps


1. Use the User Interface to configure the Cloud Service address and authentication information, if necessary.


1. Wait for the Printer to obtain network settings containing Cloud Service configuration information.


Printer is connected to the Cloud Service, has advertised its presence, and is accepting Client requests through and providing responses and status to the Cloud Service.


The Printer must provide a User Interface to configure the Cloud Service address and authentication information. The Printer may also use service discovery protocols to automatically connect to the Cloud Service or provide an "optimized" User Interface.





4142310

311312313

314

315

316

317318319

320

321

322323

324

325326

327

328329

330

331332333

334

335

336

4344


Automatic configuration of Cloud Service connections may allow unauthorized access to the Printer and its services and object data.

3.1.6 PLACEHOLDER FOR MORE SETUP USE CASES

Description of use case.

3.1.6.1 Goals


3.1.6.3 Steps





3.2 Administration and Configuration

3.2.1 PLACEHOLDER FOR ADMINISTRATION AND CONFIGURATION USE CASES


3.2.1.1 Goals


3.2.1.3 Steps






4546337338339

340

341

342

343

344

345

346

347

348

349

350

351

352

353

354

355

356

357

358

359

360

4748


3.3 Selection

3.3.1 Selection of Printer Using Address or URI

A User selects a Printer by specifying the Printer's address or service URI. The Printer is then queried for capabilities and status information in preparation for submission of a print job, initiation of a scan job, and so forth.

3.3.1.1 Goals

To select a Printer for subsequent use.


Both the Client and Printer are connected to one or more networks that allow the Client to communicate with the Printer directly or through an intermediate Cloud Service.

3.3.1.3 Steps

Selection using address:

1. User provides Printer address through the Client user interface.2. Client user interface queries Printer for valid URIs and verifies access to the

Printer for the service required.

Selection using URI:

1. User provides Printer service URI through the Client user interface.2. Client user interface verifies access to the Printer.


The Printer is available for use by the Client.


The Printer must support access using an address or URI. The address and URI must support Unicode characters using UTF-8.


Printer addresses and URIs may contain Unicode characters.


Printers must provide access control through authentication or other accepted methods.Page 14 of 34 Copyright © 2011 The Printer Working Group. All rights reserved.

4950

361

362

363364365

366

367

368

369370

371

372

373374375

376

377378

379

380

381

382383

384

385

386

387

5152


3.3.2 Selection of Printer Using a Directory Service

A User selects a Printer by choosing it from a list provided by a Directory Service. The Printer is then queried for capabilities and status information in preparation for submission of a print job, initiation of a scan job, and so forth.

3.3.2.1 Goals




Both the Client and Printer are connected to a common Directory Service.

3.3.2.3 Steps

Selection using Directory Service:

1. Client user interface lists the accessible Printers connected to the Directory Service

2. User selects a Printer from the list.3. Client user interface verifies access to the Printer.




The Printer must support connection to a Directory Service.


Printer names may contain Unicode characters.


Printers must provide access control through authentication or other accepted methods.


5354388

389390391

392

393

394

395396

397

398

399

400401402403

404

405

406

407

408

409

410

411

5556


3.3.3 Selection of Printer Using a Cloud Service

A User selects a Printer by choosing it from a list provided by a Cloud Service. The Printer is then queried for capabilities and status information in preparation for submission of a print job, initiation of a scan job, and so forth.

3.3.3.1 Goals



Both the Client and Printer are connected to one or more networks that allow the Client to communicate with the Printer through an intermediate Cloud Service.

Both the Client and Printer are connected to a common Cloud Service.

3.3.3.3 Steps

Selection using Cloud Service:

1. Client user interface lists the accessible Printers connected to the Cloud Service2. User selects a Printer from the list.3. Client user interface verifies access to the Printer.




The Printer must support connection to a Cloud Service.





3.3.4 Selection of Printer Using Proximity

A User selects a Printer by choosing it from a list of nearby printers. The Printer is then queried for capabilities and status in preparation for submission of a print job, initiation of a scan job, and so forth.


5758412

413414415

416

417

418

419420

421

422

423

424425426

427

428

429

430

431

432

433

434

435

436437438

5960


3.3.4.1 Goals




Both the Client and Printer have access to geo-location, near-field communications, or other technologies to allow for proximity detection.

3.3.4.3 Steps

Selection using proximity:

1. User initiates a proximity detection of nearby Printers.2. Client user interface lists nearby Printers.3. User selects a Printer from a list of nearby Printers.4. Client user interface verifies access to the Printer.




The Printer must support geo-location, near-field communications, or other technologies to allow for proximity detection.

The Printer must advertise location information via Directory Service, Cloud Service, and discovery protocols to enable proximity detection by physical location.





3.3.5 PLACEHOLDER FOR MORE SELECTION USE CASES



6162439

440

441

442443

444445

446

447

448449450451

452

453

454

455456

457458

459

460

461

462

463

464

6364


3.3.5.1 Goals


3.3.5.3 Steps





3.4 Printing

3.4.1 Print a Document

User has a phone 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 phone. User initiates a print from the phone and chooses a Printer that has been associated with the phone 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.4.1.1 Goals

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


Printer is accessible from User’s phone.

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

3.4.1.3 Steps

Print a document:

5. User initiates a print from an application on her phone.6. Client user interface provides a list of available Printers.7. User selects an available Printer from the list.8. Client user interface provides controls for creating job ticket.


6566465

466

467

468

469

470

471

472

473

474

475476477478479

480

481

482

483

484485

486

487

488489490491

6768


9. User selects job ticket options such as duplex and media size.10.User submits the print job.11.Client user interface sends job ticket and document data to Printer in a job

creation request. 12.Printer validates job ticket and document data and returns job identifier and

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


Job is printed


Printer must supply capabilities and status information to Client

Printer must support validation of job tickets and document data.


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


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.4.2 Print a Document by Reference

User has a phone 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 phone and chooses a Printer that has been associated with the phone 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.4.2.1 Goals

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


Printer is accessible from User’s phone.

Printer has access to the User's document.Page 19 of 34 Copyright © 2011 The Printer Working Group. All rights reserved.

6970492493494495496497498

499

500

501

502

503

504

505

506

507

508509

510

511512513514515

516

517

518

519

520

7172


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

3.4.2.3 Steps

Print a document by reference:

14.User initiates a print from an application on her phone.15.Client user interface provides a list of available Printers.16.User selects an available Printer from the list.17.Client user interface provides controls for creating job ticket.18.User selects job ticket options such as duplex and media size.19.User submits the print job.20.Client user interface sends job ticket and document URI to Printer in a job

creation request. 21.Printer validates job ticket and document URI and returns job identifier and status

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


Job is printed


Printer must supply capabilities and status information to Client

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.



7374521522

523

524

525526527528529530531532533534535

536

537

538

539

540

541

542

543

544

545

546547

548549

7576


3.4.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.4.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.4.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.


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.Page 21 of 34 Copyright © 2011 The Printer Working Group. All rights reserved.

7778550

551552553

554

555

556

557

558

559

560

561562563564565566567568569570571572

573

574

575

576

577

578

579

7980






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


3.4.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.4.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.

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


8182580

581

582

583

584585

586587

588

589590591592593

594

595

596

597

598

599

600

601602603604605606607608609

8384



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.4.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.4.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.4.5.3 Steps

Special formatting printing:

1. Gofer creates the page descriptions on his word processor program.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.


8586610

611612

613

614

615

616

617618619620621622

623

624625

626

627628629

630

631

632633634635636

637

638

8788





3.4.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.4.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.4.6.3 Steps

Prescription printing:

1. User initiates a print command from an application that can generate print content

2. 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 Everywhere9. User gets confirmation of job submitted/completed by the Cloud Provider

Alternate steps:


8990639

640

641

642

643644645646647648

649

650651

652

653654

655

656

657

658659660661662663664665666667668669

670

9192


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.4.7 PLACEHOLDER FOR MORE PRINTING USE CASES


3.4.7.1 Goals


3.4.7.3 Steps






9394671672

673674

675676

677

678

679

680

681

682

683

684

685

686

687

688

689

690

691

692

693

9596


3.5 Scanning

3.5.1 Use Case Title


3.5.1.1 Goals


3.5.1.3 Steps





3.5.2 PLACEHOLDER FOR MORE SCANNING USE CASES


3.5.2.1 Goals


3.5.2.3 Steps





3.6 Facsimile




9798

694

695

696

697

698

699

700

701

702

703

704

705

706

707

708

709

710

711

712

713

714

715

716

99100


3.6.1.1 Goals


3.6.1.3 Steps





3.6.2 PLACEHOLDER FOR MORE FACSIMILE USE CASES


3.6.2.1 Goals


3.6.2.3 Steps





3.7 Status Monitoring




101102717

718

719

720

721

722

723

724

725

726

727

728

729

730

731

732

733

734

735

736

103104


3.7.1.1 Goals


3.7.1.3 Steps





3.7.2 PLACEHOLDER FOR MORE STATUS MONITORING USE CASES


3.7.2.1 Goals


3.7.2.3 Steps





3.8 Access Control

3.8.1 Authenticated Guest Access

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


105106737

738

739

740

741

742

743

744

745

746

747

748

749

750

751

752

753

754

755

756757758759760761762

107108


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.

3.8.1.1 Goals

To demonstrate rapid but temporary access to cloud print services and the necessary administrative services.


John and Steve both have cloud repositories accounts.

Steve has at least one cloud print account

Steve has some administrative privileges

3.8.1.3 Steps

1. Steve logs in to his cloud account

2. Steve adds John to the ‘friend’s’ list for his home printer

3. The cloud system updates the ‘friend’ access list.

4. The cloud system add the Steve’s home printer to John’s printer list.

1. John logs in to his cloud account

2. John selects his document and request a print.

3. John selects Steve’s home printer from his printer list.

4. The cloud system presents a print dialog using the capabilities for Steve’s home printer.

5. John sets his print options and presses the print button.

6. The print dialog generates a Print-Job-Ticket and records the URI for Steve’s document in the Print-Job-Ticket.

7. The print dialog passes the print request to the cloud repository print client manager.


109110763764

765766767

768

769770

771

772

773

774

775

776

777

778

779

780

781

782

783

784

785

786787

788

111112


8. The cloud repository print client manager checks the status of Steve’s printer.

9. The cloud repository print client manager sends the print job to Steve’s printer.

10. The cloud repository print client manager receive a print-complete.

11. The cloud repository print client manager updates John’s print status.

12. The cloud repository print client manager removes the job from its queue.





3.8.2 PLACEHOLDER FOR MORE ACCESS CONTROL USE CASES


3.8.2.1 Goals


3.8.2.3 Steps





3.9 Auditing




113114789

790

791

792

793

794

795

796

797

798

799

800

801

802

803

804

805

806

807

808

809

810

115116


3.9.1.1 Goals


3.9.1.3 Steps





3.9.2 PLACEHOLDER FOR MORE AUDITING USE CASES


3.9.2.1 Goals


3.9.2.3 Steps





3.9.2.8

3.10 Accounting




117118811

812

813

814

815

816

817

818

819

820

821

822

823

824

825

826

827

828

829

830

831

119120


3.10.1.1 Goals


3.10.1.3 Steps





3.10.1.8 References

3.10.2 PLACEHOLDER FOR MORE ACCOUNTING USE CASES


3.10.2.1 Goals


3.10.2.3 Steps





4. References

4.1 Normative References

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


121122832

833

834

835

836

837

838

839

840

841

842

843

844

845

846

847

848

849

850

851

852853

123124


4.2 Informative References

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

5. Authors' AddressesMichael SweetApple Inc.10431 N. De Anza Blvd.MS 38-$LPTCupertino, CA 95014 USA

Justin HutchinsMicrosoft Corporation

Glen PetrieEpson

Craig ShifmanKonica Minolta

William WagnerTechnical Information Consulting


125126

854

855856

857

858859860861862863864865866867868869870871872873874

127128


6. Change History

6.1 May 24, 2011

Initial revision.


129130

875

876

877

131132

Documents

PROJ Title of Specification (Acronym)€¦ · Web viewWorking Draft – PWG Common Use CasesMay 24, 2011