Transcript Presentation Title

Imaging Status
Shivaun Albright
Imaging Committee Chair
Hewlett Packard
Agenda

UPnP v1 Printing and Imaging Use Cases

UPnP v1 Imaging Update – Where are
we?

UPnP v1 Deficiencies

UPnP v2 Requirements

UPnP v2 Use Scenarios

Schedule for UPnP v2 Imaging

Next Steps
Discovery and Installation
Imaging devices are
Plug Printer/Scanner directly
into any available network
port
discovered and can
immediately be used (no
drivers installation or setup )
UPnP Network
WiFi (802.11b)
 End User Benefits
New wireless devices enter
network and have instant
access to printer/scanner
o No need to manually install or share printer on the network
(no networking knowledge needed)
o Automatically discover printer/scanner and no need to
search for new imaging devices added to the network.
o Ability to print and scan from an extended range of devices
(Pocket PCs, Cell Phones, Web Tablets)
Service-Enabled Imaging
Distributes
through services
Photos captured
and distributed
Services
Grandma’s TV
Print Subcommittee Status UPnP v1

Printer Service Specifications Approved



Minimal Data Format – XHTML-Print



IEEE-ISTO PWG Proposed Standard document

XHTML-Print
Required Embedded Image Format

JPEG (JFIF) – PrintBasic
Sample Implementers


Printer:1 Device
PrintBasic:1 Service
HP, Oak Technologies, Canon, Microsoft
Printer Specifications published as Approved
Standards – July 2002
Scan Subcommittee Status –
UPnP V1

Scanner Service Definitions Complete





Scanner Device
Scanner Service
ExternalActivity Service
Feeder Service
Minimal Data Format – XHTML-Print

Required Image Format

JPEG (JFIF) Support

Sample Implementers: Canon, Ricoh, HP

Scanner Specifications published as Approved
Standards – September 2002
UPnP Version 1 Deficiencies

Data types


Action Extensibility


Need to be able to specify whether arguments are
optional/required or whether it should just use
device settings (defaults)
Service Inheritance


Missing Arrays and complex structures
Data inheritance may work here
Eventing


SOAP-based eventing instead of GENA so that
secured eventing could be supported
Event filtering and grouping at the device level
Imaging WC Architecture
Requirements

Utilize standard web services to develop a
standard service for:



Eventing
Discovery - Scalability of discovery for enterprise
support
Security

Ability to extend Actions/Operations

Simple way to designate “Default” values


Outside of the SCPD
Run-time parsing of the SCPD is too much of a
burden
Use Scenarios (Printer) for v2

Location-based Printing – “print to the near-by
printer” (hotel, home, airport, etc.)




Microsoft desktop printing for the mobile client

Driver-centric model using a PDL
PDA, cell phone (e.g., XHTML-Print) printing

Job Ticket Model + XHTML-Print
“Client operates the same—regardless of the
location”
Secure Printing
Use Scenarios (Scan) for v2

Scan



Scan to a service (e.g., storage,
application)
 Scan to a fax
 Scan to e-mail
Scan to Print (copy function)
Scan with user intervention
UPnP v2 Imaging Schedule










Complete Use cases

Prioritize
Identify Requirements
Complete Device Model (MFD vs. Print & Scan)
Provide Architecture input
Complete Detailed service interfaces

Design Complete – tbd
Complete Prototypes
PlugFests (minimum of 2) – tbd

Possible Hosts: Lexmark, Oak Tech., MS, HP
Incorporate feedback from Plugfests
Technical review, forum review, SC review
“Approved” specification - tbd
Next Steps

Forward progress required on the UPnP
v2 architecture
For the interconnected lifestyle