proj title of specification (acronym) … · web viewworking draft – pwg common use casesjune 19,...
TRANSCRIPT
May 15, 2023Working Draft
The Printer Working Group
Common Use Cases
Status: Interim
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-20110619.docx and ftp://ftp.pwg.org/pub/pwg/general/wd/wd-commonusecases10-20110619.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 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 42 Copyright © 2011 The Printer Working Group. All rights reserved.
12
23
24252627282930
31
32333435
363738
3940414243
44454647484950
51525354
55565758
34
Working Draft – PWG Common Use Cases May 15, 2023
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
Page 3 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
56
59
606162636465
66
67
68
6970717273747576777879
808182
83
84
85
868788899091
78
Working Draft – PWG Common Use Cases May 15, 2023
Table of Contents1. Introduction......................................................................................................................62. Terminology.....................................................................................................................6
2.1 Precondition Terminology..........................................................................................83. Scenarios.........................................................................................................................9
3.1 Setup..........................................................................................................................93.2 Administration and Configuration...............................................................................93.3 Selection....................................................................................................................93.4 Printing.......................................................................................................................93.5 Scanning....................................................................................................................93.6 Facsimile....................................................................................................................93.7 Transforms.................................................................................................................93.8 Status Monitoring.......................................................................................................93.9 Exception Handling....................................................................................................93.10 Access Control.........................................................................................................93.11 Auditing....................................................................................................................93.12 Billing....................................................................................................................... 9
4. Basic Use Cases.............................................................................................................94.1 Setup..........................................................................................................................9
4.1.1 Connection of a Printer to a Wired Network........................................................94.1.2 Connection of a Printer to a Wireless Network..................................................114.1.3 Connection of a Printer to a Cellular Network...................................................124.1.4 Connection of a Printer to a Directory Service..................................................134.1.5 Connection of a Printer to Cloud Service..........................................................144.1.6 PLACEHOLDER FOR MORE SETUP USE CASES.........................................15
4.2 Administration and Configuration.............................................................................154.2.1 PLACEHOLDER FOR ADMINISTRATION AND CONFIGURATION USE CASES.......................................................................................................................15
4.3 Select Printer...........................................................................................................164.3.1 Select the Last Used Printer..............................................................................164.3.2 Select Printer Using Name or Address..............................................................164.3.3 Select Printer Using URI....................................................................................174.3.4 Select Printer Using a Directory Service...........................................................184.3.5 Select Printer Using a Cloud Service................................................................194.3.6 Select Printer Using a Discovery Protocol.........................................................204.3.7 Select Printer Using Proximity...........................................................................214.3.8 Select Printer Using Identifying Technology......................................................224.3.9 Select Printer Using Criteria..............................................................................224.3.10 PLACEHOLDER FOR MORE SELECTION USE CASES...............................23
4.4 Print..........................................................................................................................244.4.1 Print a Document...............................................................................................244.4.2 Print a Document by Reference........................................................................254.4.3 Print a Photo......................................................................................................274.4.4 Print a Form.......................................................................................................28
Page 4 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
910
9293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135
1112
Working Draft – PWG Common Use Cases May 15, 2023
4.4.5 Special Formatting Printing...............................................................................294.4.6 Prescription Printing..........................................................................................304.4.7 PLACEHOLDER FOR MORE PRINTING USE CASES....................................31
4.5 Scanning..................................................................................................................324.5.1 Use Case Title...................................................................................................324.5.2 PLACEHOLDER FOR MORE SCANNING USE CASES..................................32
4.6 Facsimile..................................................................................................................324.6.1 Use Case Title...................................................................................................324.6.2 PLACEHOLDER FOR MORE FACSIMILE USE CASES..................................33
4.7 Transforms...............................................................................................................334.7.1 Use Case Title...................................................................................................334.7.2 PLACEHOLDER FOR TRANSFORM USE CASES..........................................34
4.8 Status Monitoring.....................................................................................................344.8.1 Use Case Title...................................................................................................344.8.2 PLACEHOLDER FOR MORE STATUS MONITORING USE CASES...............35
4.9 Exception Handling..................................................................................................354.9.1 Use Case Title...................................................................................................354.9.2 PLACEHOLDER FOR MORE EXCEPTION HANDLING USE CASES.............36
4.10 Access Control.......................................................................................................364.10.1 Authenticated Guest Access...........................................................................364.10.2 PLACEHOLDER FOR MORE ACCESS CONTROL USE CASES..................38
4.11 Auditing..................................................................................................................384.11.1 Use Case Title.................................................................................................384.11.2 PLACEHOLDER FOR MORE AUDITING USE CASES..................................39
4.12 Accounting.............................................................................................................394.12.1 Use Case Title.................................................................................................394.12.2 PLACEHOLDER FOR MORE ACCOUNTING USE CASES...........................40
5. References....................................................................................................................405.1 Normative References.............................................................................................405.2 Informative References............................................................................................41
6. Authors' Addresses........................................................................................................417. Change History..............................................................................................................42
7.1 May 24, 2011...........................................................................................................42
Page 5 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
1314136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170
1516
Working Draft – PWG Common Use Cases May 15, 2023
1. IntroductionThis document provides a common repository of scenarios, basic 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 scenarios and basic use cases of setup, administration and configuration, selection, printing, scanning, facsimile, transforms, status monitoring, exception handling, access control, auditing, and accounting. Each subsection contains a named use case with subsections for goals, preconditions, steps, post-conditions, design requirements, internationalization considerations, security considerations, and references.
Scenarios are composed of one or more use cases and may address multiple sets of preconditions, decision paths, and outcomes. Use cases provide the basic framework with a set of preconditions, steps involved in the use case, and one or more outcomes or post-conditions. Preconditions can be use cases or defined terminology for items that are outside the scope of a PWG standard such as network cabling, strategies for choosing a baby name, and so forth. Scenarios, use cases, and precondition terminology are given unique (durable) names that may be referenced by PWG standards.
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
Page 6 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
1718
171
172173174175176177178
179180181182183184
185186187188189190191
192
193
194
195
196197
198
199
200
201
1920
Working Draft – PWG Common Use Cases May 15, 2023
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].
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.
Page 7 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
2122202203
204205
206207
208
209
210
211
212
213
214215
216217
218219220221
222223
224225226227228
229230
2324
Working Draft – PWG Common Use Cases May 15, 2023
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 Printer has access.
Directory Printer; A printer selected by query or enumeration of a directory such as LDAP.
Discovered Printer; A printer selected through an ad-hoc discovery protocol such as DNS-SD, SNMP broadcast, and UPNP.
Service Printer; A printer selected by query or enumeration of a service such as an enterprise print server or Cloud Imaging service.
Static Printer; A printer selected using its IP address, URI, other 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 Printer, query for supported attributes, submit print jobs, and so forth.
Page 8 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
2526
231
232233
234
235
236237
238239
240
241242243
2728
Working Draft – PWG Common Use Cases May 15, 2023
3. Scenarios
3.1 Setup
3.2 Administration and Configuration
3.3 Selection
3.4 Printing
3.5 Scanning
3.6 Facsimile
3.7 Transforms
3.8 Status Monitoring
3.9 Exception Handling
3.10 Access Control
3.11 Auditing
3.12 Billing
4. Basic Use Cases
4.1 Setup
4.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.
Page 9 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
2930
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261262263
3132
Working Draft – PWG Common Use Cases May 15, 2023
4.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.
4.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.
4.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.
4.1.1.4 Post-Conditions
Printer is connected to the Wired Network and has been configured with the correct Wired Network Settings.
4.1.1.5 Design Requirements
The Printer must provide a User Interface to configure the Wired Network Settings and automatic configuration protocol.
4.1.1.6 Internationalization Considerations
The User Interface may require localization.
4.1.1.7 Security Considerations
Automatic configuration of Wired Network Settings may allow unauthorized Printers to connect to the Wired Network.
Page 10 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
3334264
265266
267
268269270
271
272
273274
275
276277278
279
280281
282
283284
285
286
287
288289
3536
Working Draft – PWG Common Use Cases May 15, 2023
4.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.
4.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.
4.1.2.2 Preconditions
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.
4.1.2.3 Steps
Manual configuration:
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.
4.1.2.4 Post-Conditions
Printer is connected to the Wireless Network and has been configured with the correct Wireless Network Settings.
4.1.2.5 Design Requirements
The Printer must provide a User Interface to configure the Wireless Network Settings and automatic configuration protocol.
4.1.2.6 Internationalization Considerations
The User Interface may require localization.
Page 11 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
3738290
291292293
294
295296
297
298299300
301
302
303304
305
306307308309310
311
312313
314
315316
317
318
3940
Working Draft – PWG Common Use Cases May 15, 2023
4.1.2.7 Security Considerations
Automatic configuration of Wireless Network Settings may allow unauthorized Printers to connect to the Wireless Network.
4.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.
4.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.
4.1.3.2 Preconditions
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.
4.1.3.3 Steps
Manual configuration:
1. Connect the necessary antennae and/or adapters to the Printer.2. Use the User Interface to configure the Cellular Network Settings.
4.1.3.4 Post-Conditions
Printer is connected to the Cellular Network and has been configured with the correct Cellular Network Settings.
4.1.3.5 Design Requirements
The Printer must provide a User Interface to configure the Cellular Network Settings.
4.1.3.6 Internationalization Considerations
The User Interface may require localization.
4.1.3.7 Security Considerations
TBD.
Page 12 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
4142319
320321
322
323324
325
326327
328
329330331
332
333
334335
336
337338
339
340
341
342
343
344
4344
Working Draft – PWG Common Use Cases May 15, 2023
4.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.
4.1.4.1 Goals
To advertise a Printer through a shared Directory Service so that Clients may use the Printer.
4.1.4.2 Preconditions
A Directory Service exists, has sufficient capacity to allow the Printer to advertise its presence, and is accessible from one or more connected networks.
4.1.4.3 Steps
Manual configuration:
3. Use the User Interface to configure the Directory Service address and authentication information, if necessary.
Automatic configuration:
4. Wait for the Printer to obtain network settings containing Directory Service configuration information.
4.1.4.4 Post-Conditions
Printer is connected to the Directory Service and has advertised its presence.
4.1.4.5 Design Requirements
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.
4.1.4.6 Internationalization Considerations
The User Interface may require localization.
4.1.4.7 Security Considerations
Automatic configuration of Directory Service connections may allow unauthorized access to the Printer and its services and object data.
Page 13 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
4546345
346347348
349
350351
352
353354
355
356
357358
359
360361
362
363
364
365366367
368
369
370
371372
4748
Working Draft – PWG Common Use Cases May 15, 2023
4.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.
4.1.5.1 Goals
To advertise a Printer through a shared Cloud Service so that Clients may use the Printer.
4.1.5.2 Preconditions
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.
4.1.5.3 Steps
Manual configuration:
1. Use the User Interface to configure the Cloud Service address and authentication information, if necessary.
Automatic configuration:
1. Wait for the Printer to obtain network settings containing Cloud Service configuration information.
4.1.5.4 Post-Conditions
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.
4.1.5.5 Design Requirements
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.
4.1.5.6 Internationalization Considerations
The User Interface may require localization.
Page 14 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
4950373
374375376
377
378
379
380381382
383
384
385386
387
388389
390
391392
393
394395396
397
398
5152
Working Draft – PWG Common Use Cases May 15, 2023
4.1.5.7 Security Considerations
Automatic configuration of Cloud Service connections may allow unauthorized access to the Printer and its services and object data.
4.1.6 PLACEHOLDER FOR MORE SETUP USE CASES
Description of use case.
4.1.6.1 Goals
4.1.6.2 Preconditions
4.1.6.3 Steps
4.1.6.4 Post-Conditions
4.1.6.5 Design Requirements
4.1.6.6 Internationalization Considerations
4.1.6.7 Security Considerations
4.2 Administration and Configuration
4.2.1 PLACEHOLDER FOR ADMINISTRATION AND CONFIGURATION USE CASES
Description of use case.
4.2.1.1 Goals
4.2.1.2 Preconditions
4.2.1.3 Steps
Page 15 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
5354399
400401402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
5556
Working Draft – PWG Common Use Cases May 15, 2023
4.2.1.4 Post-Conditions
4.2.1.5 Design Requirements
4.2.1.6 Internationalization Considerations
4.2.1.7 Security Considerations
4.3 Select Printer
4.3.1 Select the Last Used Printer
A User selects the last used Printer. The last used Printer may be automatically selected by the Client user interface and may be colored by the current network topology or geo-location, for example the last used Printer may be tracked on a per-network or per-location basis. 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.
4.3.1.1 Goals
To select a Printer for subsequent use.
4.3.1.2 Preconditions
The Printer is Visible to the Client, either directly or through an intermediate Service.
4.3.1.3 Steps
1. Client user interface displays the last used Printer as a selection.2. User confirms the selection of the last used Printer or cancels selection.
4.3.1.4 Post-Conditions
Printer and associated service URI or other identifier is selected, or printer selection is canceled.
4.3.1.5 Design Requirements
The Printer must have a reusable, persistent, and unique identifier such as a URI.
4.3.1.6 Internationalization Considerations
Printer identifiers may contain Unicode characters.
Page 16 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
5758419
420
421
422
423
424
425
426427428429430
431
432
433
434
435
436437
438
439440
441
442
443
444
5960
Working Draft – PWG Common Use Cases May 15, 2023
4.3.1.7 Security Considerations
Printers should provide access control through authentication or other accepted methods.
4.3.2 Select Printer Using Name or Address
A User selects a Printer by specifying the Printer's name or address. The Printer is then probed to determine the available service URIs.
4.3.2.1 Goals
To select a Printer for subsequent use.
4.3.2.2 Preconditions
The Printer is Visible to the Client, either directly or through an intermediate Service.
4.3.2.3 Steps
1. Client user interface requests a name or address.2. User provides Printer name or address through the Client user interface or
cancels selection.3. Client user interface queries Printer for valid service URIs.
4.3.2.4 Post-Conditions
Printer and associated service URI or other identifier is selected, or printer selection is canceled.
4.3.2.5 Design Requirements
The Printer must support access using a name or address. The name and address must support Unicode characters using UTF-8.
4.3.2.6 Internationalization Considerations
Printer names and addresses may contain Unicode characters.
4.3.2.7 Security Considerations
Printers should provide access control through authentication or other accepted methods.
4.3.3 Select Printer Using URI
A User selects a Printer by specifying the Printer's service URI.
Page 17 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
6162445
446
447
448449
450
451
452
453
454
455456457458
459
460461
462
463464
465
466
467
468
469
470
6364
Working Draft – PWG Common Use Cases May 15, 2023
4.3.3.1 Goals
To select a Printer for subsequent use.
4.3.3.2 Preconditions
The Printer is Visible to the Client, either directly or through an intermediate Service.
4.3.3.3 Steps
4. Client user interface requests a Printer service URI.5. User provides Printer service URI through the Client user interface or cancels
selection.
4.3.3.4 Post-Conditions
Printer and associated service URI or other identifier is selected, or printer selection is canceled.
4.3.3.5 Design Requirements
The Printer must support access using a URI.
4.3.3.6 Internationalization Considerations
Printer URIs may contain Unicode characters.
4.3.3.7 Security Considerations
Printers should provide access control through authentication or other accepted methods.
4.3.4 Select Printer Using a Directory Service
A User selects a Printer by choosing it from a list provided by a Directory Service.
4.3.4.1 Goals
To select a Printer for subsequent use.
4.3.4.2 Preconditions
The Printer is Visible to the Client, either directly or through an intermediate Service. The Printer has a listing in the Directory Service, and the Directory Service is Visible to the Client.
Page 18 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
6566471
472
473
474
475
476477478
479
480481
482
483
484
485
486
487
488
489
490
491
492
493494495
6768
Working Draft – PWG Common Use Cases May 15, 2023
4.3.4.3 Steps
1. Client obtains a list of Printers for the User from the Directory Service.2. Client validates supported protocols for each Printer in the list.3. Client user interface presents the supported Printers to the User for selection.4. User selects a Printer or cancels selection.
4.3.4.4 Post-Conditions
Printer and associated service URI or other identifier is selected, or printer selection is canceled.
4.3.4.5 Design Requirements
The Directory Service must support listing of Printers, their service URIs, and other descriptive information. The Client must support communication with the Directory Service.
4.3.4.6 Internationalization Considerations
Printer names and descriptive information may contain Unicode characters.
4.3.4.7 Security Considerations
Printers and Directory Services should provide access control through authentication or other accepted methods.
4.3.5 Select Printer Using a Cloud Service
A User selects a Printer by choosing it from a list provided by a Cloud Service. The User and Printer may be registered with multiple Cloud Services and maintain multiple identities.
4.3.5.1 Goals
To select a Printer for subsequent use.
4.3.5.2 Preconditions
The Cloud Service is Visible to the Client. The Client and Printer are registered with the Cloud Service.
4.3.5.3 Steps
1. Client obtains a list of Printers for the User from the Cloud Service.
Page 19 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
6970496
497498499500
501
502503
504
505506507
508
509
510
511512
513
514515516
517
518
519
520521
522
523
7172
Working Draft – PWG Common Use Cases May 15, 2023
Client user interface present the available Printers to the User for selection.
2. User selects a Printer or cancels selection.
4.3.5.4 Post-Conditions
Printer and associated service URI or other identifier is selected, or printer selection is canceled.
4.3.5.5 Design Requirements
The Cloud Service must provide Printer services and enumeration of Printers. The Client and Printer must support communication with a Cloud Service.
4.3.5.6 Internationalization Considerations
Printer names and descriptive information may contain Unicode characters.
4.3.5.7 Security Considerations
Printers must provide access control through authentication or other accepted methods.
4.3.6 Select Printer Using a Discovery Protocol
A User selects a Printer by choosing it from a list of discovered printers.
4.3.6.1 Goals
To select a Printer for subsequent use.
4.3.6.2 Preconditions
The Printer is Visible to the Client and supports a common discovery protocol.
4.3.6.3 Steps
1. User initiates a discovery of local Printers.2. Client software browses for local Printers.3. Client user interface presents the discovered Printers.4. User selects a discovered Printer or cancels selection.5. Client software stops browsing for local Printer.
4.3.6.4 Post-Conditions
Printer and associated service URI or other identifier is selected, or printer selection is canceled.
Page 20 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
7374524
525
526
527528
529
530531
532
533
534
535
536
537
538
539
540
541
542
543544545546547
548
549550
7576
Working Draft – PWG Common Use Cases May 15, 2023
4.3.6.5 Design Requirements
The Printer must provide location information to Services or support local discovery protocols.
4.3.6.6 Internationalization Considerations
Printer names and descriptive information may contain Unicode characters.
4.3.6.7 Security Considerations
Printers should provide access control through authentication or other accepted methods.
4.3.7 Select Printer Using Proximity
A User selects a Printer by choosing it from a list of nearby printers.
4.3.7.1 Goals
To select a Printer for subsequent use.
4.3.7.2 Preconditions
The Printer is Visible to the Client, either directly or through an intermediate Service.
Both the Client and Printer have access to location information to allow for proximity detection. The location information may be implied by the network topology.
4.3.7.3 Steps
1. User initiates a proximity detection of nearby Printers.2. Client obtains a list of Printers nearby the Client using Services and/or discovery
protocols, hiding duplicate Printers that are reported by multiple Service and/or discovery procotols.
3. Client user interface presents the nearby Printers.4. User selects a nearby Printer or cancels selection.
4.3.7.4 Post-Conditions
Printer and associated service URI or other identifier is selected, or printer selection is canceled.
4.3.7.5 Design Requirements
The Printer must provide location and globally-unique identifying information to Services and/or support local discovery protocols with globally-unique identifying information.
Page 21 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
7778551
552553
554
555
556
557
558
559
560
561
562
563
564565
566
567568569570571572
573
574575
576
577578
7980
Working Draft – PWG Common Use Cases May 15, 2023
4.3.7.6 Internationalization Considerations
Printer names and descriptive information may contain Unicode characters.
4.3.7.7 Security Considerations
Printers should provide access control through authentication or other accepted methods.
4.3.8 Select Printer Using Identifying Technology
A User selects a Printer using identifying technology such as near-field communications, QRCodes, and bar codes.
4.3.8.1 Goals
To select a Printer for subsequent use.
4.3.8.2 Preconditions
The Printer is Visible to the Client, either directly or through an intermediate Service.
4.3.8.3 Steps
5. User initiates selection using identifying technology.6. Client scans the identifying technology to obtain a service URI and printer
descriptive information.7. Client user interface presents selection to the User.8. User confirms or cancels selection.
4.3.8.4 Post-Conditions
Printer and associated service URI or other identifier is selected, or printer selection is canceled.
4.3.8.5 Design Requirements
The Printer and Client must support a common identifying technology, and the Printer must support access using a URI.
4.3.8.6 Internationalization Considerations
Printer URIs may contain Unicode characters.
4.3.8.7 Security Considerations
Printers should provide access control through authentication or other accepted methods.
Page 22 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
8182579
580
581
582
583
584585
586
587
588
589
590
591592593594595
596
597598
599
600601
602
603
604
605
8384
Working Draft – PWG Common Use Cases May 15, 2023
4.3.9 Select Printer Using Criteria
A User selects a Printer using criteria such as protocol, limits such as the number of pages allowed, job ticket capabilities such as duplex printing support, printer description elements such as location, speed, and color support, and job size. The criteria may be provided by a combination of User input, policy, and/or software heuristic.
4.3.9.1 Goals
To select a Printer for subsequent use.
4.3.9.2 Preconditions
The Printer is Visible to the Client, either directly or through an intermediate Service.
4.3.9.3 Steps
1. Client obtains a list of Printers for the User that meet the given Job Ticket and Printer Description criteria provided by the Client software, policy, and/or User.
2. Client validates supported protocols for each Printer in the list3. Client user interface presents the supported Printers to the User for selection4. User selects a Printer or cancels selection
4.3.9.4 Post-Conditions
Printer and associated service URI or other identifier is selected, or printer selection is canceled.
4.3.9.5 Design Requirements
The Printer or Service must provide sufficient descriptive and capability information to support selection using criteria.
4.3.9.6 Internationalization Considerations
Printer names and descriptive information may contain Unicode characters.
4.3.9.7 Security Considerations
Printers and Directory Services should provide access control through authentication or other accepted methods.
4.3.10 PLACEHOLDER FOR MORE SELECTION USE CASES
Description of use case.
Page 23 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
8586606
607608609610
611
612
613
614
615
616617618619620
621
622623
624
625626
627
628
629
630631
632
633
8788
Working Draft – PWG Common Use Cases May 15, 2023
4.3.10.1 Goals
4.3.10.2 Preconditions
4.3.10.3 Steps
4.3.10.4 Post-Conditions
4.3.10.5 Design Requirements
4.3.10.6 Internationalization Considerations
4.3.10.7 Security Considerations
4.4 Print
4.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.
4.4.1.1 Goals
User obtains a high-quality print with good performance from her phone.
4.4.1.2 Preconditions
Printer is accessible from User’s phone.
Printer supports the document format or Client can convert to Printer's supported document formats.
4.4.1.3 Steps
Print a document:
9. User initiates a print from an application on her phone.10.Client user interface provides a list of available Printers.11.User selects an available Printer from the list.12.Client user interface provides controls for creating job ticket.
Page 24 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
8990634
635
636
637
638
639
640
641
642
643
644645646647648
649
650
651
652
653654
655
656
657658659660
9192
Working Draft – PWG Common Use Cases May 15, 2023
13.User selects job ticket options such as duplex and media size.14.User submits the print job.15.Client user interface sends job ticket and document data to Printer in a job
creation request. 16.Printer validates job ticket and document data and returns job identifier and
status to Client user interface.17.Client user interface presents status to User.
4.4.1.4 Post-Conditions
Job is printed
4.4.1.5 Design Requirements
Printer must supply capabilities and status information to Client
Printer must support validation of job tickets and document data.
4.4.1.6 Internationalization Considerations
Job ticket information such as the job name can contain Unicode characters.
4.4.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.
4.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.
4.4.2.1 Goals
User obtains a high-quality print with good performance from her phone.
4.4.2.2 Preconditions
Printer is accessible from User’s phone.
Printer has access to the User's document.Page 25 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
9394661662663664665666667
668
669
670
671
672
673
674
675
676
677678
679
680681682683684
685
686
687
688
689
9596
Working Draft – PWG Common Use Cases May 15, 2023
Printer supports the document format or Client can convert to Printer's supported document formats.
4.4.2.3 Steps
Print a document by reference:
18.User initiates a print from an application on her phone.19.Client user interface provides a list of available Printers.20.User selects an available Printer from the list.21.Client user interface provides controls for creating job ticket.22.User selects job ticket options such as duplex and media size.23.User submits the print job.24.Client user interface sends job ticket and document URI to Printer in a job
creation request. 25.Printer validates job ticket and document URI and returns job identifier and status
to Client user interface.26.Client user interface presents status to User.
4.4.2.4 Post-Conditions
Job is printed
4.4.2.5 Design Requirements
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.
4.4.2.6 Internationalization Considerations
Job ticket information such as the job name can contain Unicode characters.
4.4.2.7 Security Considerations
Unlimited print jobs can cause a denial of service.
Document URIs may require authentication or have other security requirements for access from the Printer.
Document data can contain executable code or may exploit known Printer software vulnerabilities such as buffer overflows.
Page 26 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
9798690691
692
693
694695696697698699700701702703704
705
706
707
708
709
710
711
712
713
714
715716
717718
99100
Working Draft – PWG Common Use Cases May 15, 2023
4.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.
4.4.3.1 Goals
To produce a high-quality photographic print on borderless media.
4.4.3.2 Preconditions
Printer is accessible from Client.
Printer supports photo printing and offers borderless media sizes.
4.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.
4.4.3.4 Post-Conditions
Photo is printed.
4.4.3.5 Design Requirements
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 27 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
101102719
720721722
723
724
725
726
727
728
729
730731732733734735736737738739740741
742
743
744
745
746
747
748
103104
Working Draft – PWG Common Use Cases May 15, 2023
4.4.3.6 Internationalization Considerations
Job ticket information such as the job name can contain Unicode characters.
4.4.3.7 Security Considerations
Unlimited print jobs can cause a denial of service.
Document URIs may require authentication or have other security requirements for access from the Printer.
Document data can contain executable code or may exploit known Printer software vulnerabilities such as buffer overflows.
4.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.
4.4.4.1 Goal
To print checks for all meeting personnel at the conclusion of the meeting.
4.4.4.2 Preconditions
Printer is accessible from Client.
Printer supports printing on forms such as check blanks.
4.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.
Page 28 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
105106749
750
751
752
753754
755756
757
758759760761762
763
764
765
766
767
768
769
770771772773774775776777778
107108
Working Draft – PWG Common Use Cases May 15, 2023
4.4.4.4 Post-Conditions
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.
4.4.4.5 Design Requirements
4.4.4.6 Internationalization Considerations
4.4.4.7 Security Considerations
4.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
4.4.5.1 Goals
Gofer must provide paper slips of the specified size with legible text, promptly and cheaply.
4.4.5.2 Preconditions
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.
4.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
4.4.5.4 Post-Conditions
Gofer will be charged for printing two single sided sheets.
Page 29 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
109110779
780781
782
783
784
785
786787788789790791
792
793794
795
796797798
799
800
801802803804805
806
807
111112
Working Draft – PWG Common Use Cases May 15, 2023
4.4.5.5 Design Requirements
4.4.5.6 Internationalization Considerations
4.4.5.7 Security Considerations
4.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.
4.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
4.4.6.2 Preconditions
User’s mobile device is capable of interacting with a Cloud Provider supporting the IPP Everywhere protocol.
User’s mobile device supports prescription generation.
4.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:
Page 30 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
113114808
809
810
811
812813814815816817
818
819820
821
822823
824
825
826
827828829830831832833834835836837838
839
115116
Working Draft – PWG Common Use Cases May 15, 2023
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.
4.4.6.4 Post-Conditions
The IPP Everywhere printer has printed the job the user sent.
The IPP everywhere printer is available to accept additional print jobs.
4.4.6.5 Design Requirements
4.4.6.6 Internationalization Considerations
4.4.6.7 Security Considerations
4.4.7 PLACEHOLDER FOR MORE PRINTING USE CASES
Description of use case.
4.4.7.1 Goals
4.4.7.2 Preconditions
4.4.7.3 Steps
4.4.7.4 Post-Conditions
4.4.7.5 Design Requirements
4.4.7.6 Internationalization Considerations
4.4.7.7 Security Considerations
Page 31 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
117118840841
842843
844845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
119120
Working Draft – PWG Common Use Cases May 15, 2023
4.5 Scanning
4.5.1 Use Case Title
Description of use case.
4.5.1.1 Goals
4.5.1.2 Preconditions
4.5.1.3 Steps
4.5.1.4 Post-Conditions
4.5.1.5 Design Requirements
4.5.1.6 Internationalization Considerations
4.5.1.7 Security Considerations
4.5.2 PLACEHOLDER FOR MORE SCANNING USE CASES
Description of use case.
4.5.2.1 Goals
4.5.2.2 Preconditions
4.5.2.3 Steps
4.5.2.4 Post-Conditions
4.5.2.5 Design Requirements
4.5.2.6 Internationalization Considerations
4.5.2.7 Security Considerations
4.6 Facsimile
4.6.1 Use Case Title
Description of use case.
Page 32 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
121122
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
123124
Working Draft – PWG Common Use Cases May 15, 2023
4.6.1.1 Goals
4.6.1.2 Preconditions
4.6.1.3 Steps
4.6.1.4 Post-Conditions
4.6.1.5 Design Requirements
4.6.1.6 Internationalization Considerations
4.6.1.7 Security Considerations
4.6.2 PLACEHOLDER FOR MORE FACSIMILE USE CASES
Description of use case.
4.6.2.1 Goals
4.6.2.2 Preconditions
4.6.2.3 Steps
4.6.2.4 Post-Conditions
4.6.2.5 Design Requirements
4.6.2.6 Internationalization Considerations
4.6.2.7 Security Considerations
4.7 Transforms
4.7.1 Use Case Title
Description of use case.
Page 33 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
125126886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
127128
Working Draft – PWG Common Use Cases May 15, 2023
4.7.1.1 Goals
4.7.1.2 Preconditions
4.7.1.3 Steps
4.7.1.4 Post-Conditions
4.7.1.5 Design Requirements
4.7.1.6 Internationalization Considerations
4.7.1.7 Security Considerations
4.7.2 PLACEHOLDER FOR TRANSFORM USE CASES
Description of use case.
4.7.2.1 Goals
4.7.2.2 Preconditions
4.7.2.3 Steps
4.7.2.4 Post-Conditions
4.7.2.5 Design Requirements
4.7.2.6 Internationalization Considerations
4.7.2.7 Security Considerations
4.8 Status Monitoring
4.8.1 Use Case Title
Description of use case.
Page 34 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
129130906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
131132
Working Draft – PWG Common Use Cases May 15, 2023
4.8.1.1 Goals
4.8.1.2 Preconditions
4.8.1.3 Steps
4.8.1.4 Post-Conditions
4.8.1.5 Design Requirements
4.8.1.6 Internationalization Considerations
4.8.1.7 Security Considerations
4.8.2 PLACEHOLDER FOR MORE STATUS MONITORING USE CASES
Description of use case.
4.8.2.1 Goals
4.8.2.2 Preconditions
4.8.2.3 Steps
4.8.2.4 Post-Conditions
4.8.2.5 Design Requirements
4.8.2.6 Internationalization Considerations
4.8.2.7 Security Considerations
4.9 Exception Handling
4.9.1 Use Case Title
Description of use case.
Page 35 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
133134926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
135136
Working Draft – PWG Common Use Cases May 15, 2023
4.9.1.1 Goals
4.9.1.2 Preconditions
4.9.1.3 Steps
4.9.1.4 Post-Conditions
4.9.1.5 Design Requirements
4.9.1.6 Internationalization Considerations
4.9.1.7 Security Considerations
4.9.2 PLACEHOLDER FOR MORE EXCEPTION HANDLING USE CASES
Description of use case.
4.9.2.1 Goals
4.9.2.2 Preconditions
4.9.2.3 Steps
4.9.2.4 Post-Conditions
4.9.2.5 Design Requirements
4.9.2.6 Internationalization Considerations
4.9.2.7 Security Considerations
4.10 Access Control
4.10.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
Page 36 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
137138946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965966967968969970971
139140
Working Draft – PWG Common Use Cases May 15, 2023
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.
4.10.1.1 Goals
To demonstrate rapid but temporary access to cloud print services and the necessary administrative services.
4.10.1.2 Preconditions
John and Steve both have cloud repositories accounts.
Steve has at least one cloud print account
Steve has some administrative privileges
4.10.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.
Page 37 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
141142972973
974975976
977
978979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995996
997
143144
Working Draft – PWG Common Use Cases May 15, 2023
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.
4.10.1.4 Post-Conditions
4.10.1.5 Design Requirements
4.10.1.6 Internationalization Considerations
4.10.1.7 Security Considerations
4.10.2 PLACEHOLDER FOR MORE ACCESS CONTROL USE CASES
Description of use case.
4.10.2.1 Goals
4.10.2.2 Preconditions
4.10.2.3 Steps
4.10.2.4 Post-Conditions
4.10.2.5 Design Requirements
4.10.2.6 Internationalization Considerations
4.10.2.7 Security Considerations
4.11 Auditing
4.11.1 Use Case Title
Description of use case.
Page 38 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
145146998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
147148
Working Draft – PWG Common Use Cases May 15, 2023
4.11.1.1 Goals
4.11.1.2 Preconditions
4.11.1.3 Steps
4.11.1.4 Post-Conditions
4.11.1.5 Design Requirements
4.11.1.6 Internationalization Considerations
4.11.1.7 Security Considerations
4.11.2 PLACEHOLDER FOR MORE AUDITING USE CASES
Description of use case.
4.11.2.1 Goals
4.11.2.2 Preconditions
4.11.2.3 Steps
4.11.2.4 Post-Conditions
4.11.2.5 Design Requirements
4.11.2.6 Internationalization Considerations
4.11.2.7 Security Considerations
4.11.2.8
4.12 Accounting
4.12.1 Use Case Title
Description of use case.
Page 39 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
1491501020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
151152
Working Draft – PWG Common Use Cases May 15, 2023
4.12.1.1 Goals
4.12.1.2 Preconditions
4.12.1.3 Steps
4.12.1.4 Post-Conditions
4.12.1.5 Design Requirements
4.12.1.6 Internationalization Considerations
4.12.1.7 Security Considerations
4.12.1.8 References
4.12.2 PLACEHOLDER FOR MORE ACCOUNTING USE CASES
Description of use case.
4.12.2.1 Goals
4.12.2.2 Preconditions
4.12.2.3 Steps
4.12.2.4 Post-Conditions
4.12.2.5 Design Requirements
4.12.2.6 Internationalization Considerations
4.12.2.7 Security Considerations
5. References
5.1 Normative References
[REFERENCE] F. Last author list or standards body, "Title of referenced document", Document Number, Month YYYY, URL (if any)
Page 40 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
1531541041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
10611062
155156
Working Draft – PWG Common Use Cases May 15, 2023
5.2 Informative References
[REFERENCE] F. Last author list or standards body, "Title of referenced document", Document Number, Month YYYY, URL (if any)
6. 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
Page 41 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
157158
1063
10641065
1066
10671068106910701071107210731074107510761077107810791080108110821083
159160
Working Draft – PWG Common Use Cases May 15, 2023
7. Change History
7.1 May 24, 2011
Initial revision.
Page 42 of 42 Copyright © 2011 The Printer Working Group. All rights reserved.
161162
1084
1085
1086
163164