MFD: Scan Service September 181, 2007
September 181, 2007
wd-mfdscan10-2007 Working Draft
The Printer Working Group
Network Scan Service
Semantic Model And Service Interface
Status: Interim
Abstract: Network print devices have evolved to support additional multifunction services, in particular scan service. When network scan devices are installed in local office or enterprise networks, they need remote service, device, and job management capabilities so that administrators, operators, and end users can monitor their health and status. In addition, such network scan devices need remote job submission capabilities so that operators and end users can create scan jobs without depending entirely on local console interfaces. This document defines a semantic model and requirements for service, device, and job management and job submission for these network scan devices.
Copyright (C) 2007, 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 Printer Working Group, a program of the IEEE-ISTO.
Title: Network Scan Service Semantic Model and Service Interface
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 and the Printer Working Group, a program of the IEEE-ISTO take 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 and the Printer Working Group, a program of the IEEE-ISTO invite 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:
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.
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 Industry Standards and Technology Organization member organizations include printer manufacturers, print server developers, operating system providers, network operating systems providers, network connectivity vendors, and print management application developers. 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 Printer Working Group
The Printer Working Group (or PWG) is a Program of the IEEE-ISTO. All references to the PWG in this document implicitly mean “The Printer Working Group, a Program of the IEEE ISTO.” The PWG is chartered to make printers and the applications and operating systems supporting them work together better. In order to meet this objective, the PWG will document the results of their work as open standards that define print related protocols, interfaces, data models, procedures and conventions. Printer manufacturers and vendors of printer related software would 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.
Contact information:
The Printer Working Group
c/o The IEEE Industry Standards and Technology Organization
445 Hoes Lane
Piscataway, NJ 08854
USA
MFD Web Page: http://www.pwg.org/mfd MFD Mailing List:
Instructions for subscribing to the MFD mailing list can be found at the following link:
http://www.pwg.org/mailhelp.html
Members of the PWG and interested parties are encouraged to join the PWG and MFD WG mailing lists in order to participate in discussions, clarifications and review of the WG product.
Contents
1 Introduction 6
2 Terminology 6
2.1 Conformance Terminology 6
2.2 Scan Service Terminology 6
3 Requirements 7
3.1 Rationale of the Requirements for Scan Service 7
3.2 Out of Scope for Scan Service 7
3.3 Use Cases 8
The following usage scenarios have been considered for support by the scan service model: 8
3.3.1 Create Scan Job Template from a Remote Scan Client 8
3.3.2 Walk-up User Creates Scan Templates 9
3.3.3 Walk-Up Scan – Pre-Created Scan Job Template 10
3.3.4 Walk-up Scan and Store Document - 12
3.3.5 Scan from PC, Multiple Sets of Originals, and Store Document in Repository 14
3.3.6 Walk-up Scan and Select Storage Destination - 17
3.3.7 Walk-up Scan with Pre-Selected, Non-Over-Writable Template 18
3.3.8 Walk-Up Batch Scan 20
1. The Scan Service shall support a “batch scan” mode of operation that is different from the normal scan mode as described in the Processing Flow Step requirements (3.3.8.1). 21
3.3.9 Finding a Previously Scanned Document Location 21
3.3.10 Disable Scan Service for Copying 22
3.3.11 Interrupt a Scan Job for Printing 23
3.3.12 Scan Service Discovery via LDAP or DNS 24
3.3.13 Scan Service Capability Discovery 26
4 Scan Service Object Model 27
4.1 Scan Job Ticket Life Cycle 27
4.1.1 Scan Job Ticket Life Cycle Diagram 27
4.1.2 Scan Job Ticket Life Cycle Description 27
4.2 Scan Service Model Overview 28
4.3 Scan Service Model Diagram 29
4.4 Scan Service Model Description 29
4.4.1 Service Status 29
4.4.2 Service Description 35
4.4.3 Service Processing Elements 36
4.5 Scan Job Model Diagram 36
4.6 Scan Job Model Description 37
4.6.1 Scan Job Status 37
5 Scan Service Theory of Operation 40
6 Scan Service Interfaces 40
6.1 Basic Scan Service Operations 40
6.2 Administrative Scan Service Operations 41
6.3 Scan Job Template Manager Operations 41
7 Conformance Requirements 41
8 PWG and IANA Registration Considerations 41
9 Internalization Considerations 41
10 Security Considerations 41
11 References 42
11.1 Normative References 42
11.2 Informative References 42
12 Author’s Address 42
13 Change Log 43
1 Introduction 6
2 Terminology 6
2.1 Conformance Terminology 6
2.2 Scan Service Terminology 6
3 Requirements 7
3.1 Rationale of the Requirements for Scan Service 7
3.2 Out of Scope for Scan Service 7
3.3 Use Cases 8
The following usage scenarios have been considered for support by the scan service model: 8
3.3.1 Create Scan Job Template from a Remote Scan Client 8
3.3.2 Walk-up User Creates Scan Templates 9
3.3.3 Walk-Up Scan – Pre-Created Scan Job Template 10
3.3.4 Walk-up Scan and Store Document - 12
3.3.5 Scan from PC, Multiple sets of Originals, and Store Document in Repository 14
3.3.6 Walk-up Scan and Discover Storage Destination - 16
3.3.7 Walk-Up Scan, with Pre-selected Scan Template and Policy Template Overwrite 18
3.3.8 Walk-Up Batch Scan 20
3.3.9 Workflow On-Ramp Scanning 22
3.3.10 Finding Scan Job Storage Location 23
3.3.11 Disable Scan Service for Copying 24
3.3.12 Interrupt a Scan Job for Printing 25
3.3.13 Scan Service Discovery via LDAP or DNS 26
3.3.14 Scan Service Capability Discovery 27
4 Scan Service Object Model 28
4.1 Scan Job Ticket Life Cycle 28
4.1.1 Scan Job Ticket Life Cycle Diagram 28
4.1.2 Scan Job Ticket Life Cycle Description 28
4.2 Scan Service Model Overview 29
4.3 Scan Service Model Diagram 30
4.4 Scan Service Model Description 30
4.4.1 Service Status 30
4.4.2 Service Description 36
4.4.3 Service Processing Elements 37
4.5 Scan Job Model Diagram 37
4.6 Scan Job Model Description 38
4.6.1 Scan Job Status 38
5 Scan Service Theory of Operation 41
6 Scan Service Interfaces 41
6.1 Basic Scan Service Operations 41
6.2 Administrative Scan Service Operations 42
6.3 Scan Job Template Manager Operations 42
7 Conformance Requirements 42
8 PWG and IANA Registration Considerations 42
9 Internalization Considerations 42
10 Security Considerations 42
11 References 43
11.1 Normative References 43
11.2 Informative References 43
12 Author’s Address 43
13 Change Log 44
Figures
Figure 1 Create Template from Remote Scan Client 9
Figure 2 Walk-up User Creates Scan Templates 10
Figure 3 Walk-up Scan with Pre-created Scan Job Template 11
Figure 4 Walk-up Scan and Store Document 13
Figure 5 Scan from PC, Mutiple Set of Originals and Store Document 15
Figure 6 Walk-up Scan and Select Storage Destination 17
Figure 7 Walk-up Scan with Pre-selected, Non-Over-Writable Scan Template 18
Figure 8 Walk-Up Batch Scan 20
Figure 9 Finding Scan Job Storage Location 21
Figure 10 Disable Scan Service for Copying 22
Figure 11 Intgerrupt a Scan Job for Printing or Copying 23
Figure 12 Scan Service discovery via LDAP or DNS 24
Figure 13 Service Capability Discovery 26
Figure 14 Scan Job Ticket Lifecycle Diagram 27
Figure 15 High level Scan Service Schema 29
Figure 16 Scan Service Status 30
Figure 17 Top-Level Service State Transition Diagram 31
Figure 18 Detailed Service Transition Diagram 34
Figure 19 Scan Service Description 36
Figure 20 High level Scan Job view 37
Figure 21 Scan Job Status 38
Figure 22 Job State Transition Diagram 40
Figure 1 Create Job Template from Client 9
Figure 2 Walk-up User Creates Scan Templates 10
Figure 3 Walk-up Scan with Pre-created Scan Job Template 11
Figure 4 Walk-up Scan and Store Document 13
Figure 5 Scan from PC and Store Document 15
Figure 6 Walk-up Scan and Discover a Storage Destination 16
Figure 7 Walk-up Scan with Pre-selected Scan Template and Template Policy Overwrite 18
Figure 8 Walk-Up Batch Scan 20
Figure 9 Workflow On-Ramp Scanning 22
Figure 10 Finding Scan Job Storage Location 23
Figure 11 Disable Scan Service for Copying 24
Figure 12 Interrupt a Scan Job for Printing or Copying 25
Figure 13 Scan Service discovery via LDAP or DNS 26
Figure 14 Service Capability Discovery 27
Figure 15 Scan Job Ticket Lifecycle Diagram 28
Figure 16 High level Scan Service Schema 30
Figure 17 Scan Service Status 31
Figure 18 Top-Level Service State Transition Diagram 32
Figure 19 Detailed Service Transition Diagram 35
Figure 20 Scan Service Description 37
Figure 21 High level Scan Job view 38
Figure 22 Scan Job Status 39
Figure 23 Job State Transition Diagram 41
Copyright © 2007, Printer Working Group. All rights reserved. Page 5 of 43
MFD: Scan Service September 181, 2007
1 Introduction
This document specifies the PWG abstract model of the scan service of a multifunction device (MFD). The model includes requirements and definitions of the data and functional architectural elements and the service interface and operation model for the usage of the scan service and device of a multifunction device (MFD) installed either in a local or enterprise network environment.
The scan service semantic model supports both walk-up scan from MFD’s front panel, and remote scan from a client PC or workstation without operating the front panel. The model also supports document on-ramp scanning for enterprise workflow applications that may store scanned images internally or to a remote server/repository. When shared by a workgroup using different functions of the MFD, the model supports interruption of a large scan job to perform a higher priority job. For batch scanning (single or multiple documents), the model supports automated scanning of a stack of documents separated by a scan instruction sheet (a physical scan job ticket) for each document. The model will support security services that protects against unauthorized use of the scan service or access of scanned image data.
This document focuses on the specification of job submission and job management abstract semantics for MFD scan service in network environment. Service, device, and job management and job submission protocols for these network MFDs are currently fragmented and proprietary. This standard for scan service, device, and job management and job submission for these network MFDs will benefit both the imaging industry and the user community.
2 Terminology
This section defines terminology used throughout this document.
2.1 Conformance Terminology
Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, MAY, RECOMMENDED and OPTIONAL, have special meaning relating to conformance as defined in RFC 2119 [RFC2119].
2.2 Scan Service Terminology
Scan Job Parameters – The set of values the Scan Service inputs from the end user, each value is to realize a property or attribute of an instance of the Scan Job Template.
Scan Job Ticket (digital) – A data object that contains processing and description properties of a scan job such as source, destination, image processing, image format, and image compression parameters and settings. The content of a scan job ticket is configured by user through a scan client UI or created from a Scan Job Template.
Scan Job Ticket (physical) – An encoded sheet of paper that contains processing and description properties of a scan job such as source, destination, image processing, image format, and image compression parameters and settings. The content of the physical scan job ticket is configured by the user through direct markings on the encoded sheet of paper.