ftp.pwg.orgftp.pwg.org/pub/pwg/mfd/wd/wd-smcwmpprint10-201308… · Web viewAbstract: This document defines the requirements, implementation recommendations, proxy protocol mappings,

The Printer Working Group

31 August 2013Working Draft

CWMP Printer Data Model

Status: Interim

Abstract: This document defines the requirements, implementation recommendations, proxy protocol mappings, and XML structure of a Printer data model for use with Broadband Forum CPE WAN Management Protocol (CWMP) [TR-069]. This Printer data model is based on machine-translation of the PWG Semantic Model XML Schema into XML schema objects that conform to Broadband Forum Data Model Template for TR-069-Enabled Devices [TR-106].

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

This document is available electronically at:

ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-smcwmpprint10-20130831.docxftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-smcwmpprint10-20130831.pdf

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

12345678910

11

12

13

141516171819

2021

22

2324

Working Draft – CWMP Printer Data Model 31 August 2013

Copyright © 2011-2013 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: CWMP Printer Data Model

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

12

25

26272829303132

33

343536

373839

4041424344

45464748495051

52535455

56575859

3


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


45

60

6162636465

66

67

68

6970717273747576777879

808182

83

84

85

868788899091

6

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

http://standards.ieee.org/)

http://www.ieee.org/


About the Semantic Model Working Group

The Semantic Model Working Group is responsible for the modeling of the services - Print, Copy, Scan, Fax, Email, Resource, System Control, and Transform hosted on Multifunction Devices (MFDs) and other Imaging Systems. Standardization of the Imaging System model and semantics will support interoperability of devices and services in local and enterprise networks enabling improved job submission, job management, remote administration, and support. The goal of the project is to define a unified semantic model and set of abstract operations for the most common and essential service and device features of Imaging Systems.

For additional information regarding SM visit:

http://www.pwg.org/sm/

Implementers of this specification are encouraged to join the SM mailing list in order to participate in any discussions of the specification. Suggested additions, changes, or clarification to this specification, should be sent to the SM mailing list for consideration.


78

92

93949596979899100

101

102

103104105

9


Table of Contents1. Introduction.......................................................................................................................72. Terminology......................................................................................................................9

2.1 Conformance Terminology..........................................................................................92.2 Printing Terminology...................................................................................................92.3 Telecommunications Terminology..............................................................................92.4 Other Terminology....................................................................................................112.5 Acronyms and Organizations....................................................................................11

3. Requirements.................................................................................................................123.1 Rationale for CWMP Printer Data Model..................................................................12

3.1.1 Rationale from PWG Perspective.......................................................................123.1.2 Rationale from Broadband Forum Perspective..................................................13

3.2 Use Cases................................................................................................................143.2.1 Printers managed by Telecom Providers...........................................................143.2.2 Printers managed by MPS Providers.................................................................143.2.3 Printers managed by Enterprise IT Staff............................................................153.2.4 Print Kiosks managed by Telecom Providers.....................................................15

3.3 Deployment Scenarios..............................................................................................163.4 Out of Scope.............................................................................................................173.5 Design Requirements...............................................................................................17

4. CWMP Printer Data Model.............................................................................................184.1 Technical Approach..................................................................................................18

4.1.1 XML Format of BBF CWMP and PWG SM Data Models...................................184.1.2 Translation of PWG SM into CWMP Printer Data Model....................................184.1.3 Simple CWMP Parameter Datatypes.................................................................194.1.4 Short CWMP Parameter Qualified Names.........................................................19

4.2 PWG Semantic Model...............................................................................................214.3 CWMP Printer Data Model Sketch............................................................................32

5. CWMP Proxy Implementation Guidance........................................................................385.1 PWG PrintService to IPP Proxy Guidance................................................................385.2 PWG SM PrintService to SNMP Proxy Guidance.....................................................50

6. Conformance Requirements...........................................................................................517. Internationalization Considerations.................................................................................518. Security Considerations..................................................................................................519. IANA and PWG Considerations......................................................................................5210. References...................................................................................................................52

10.1 Normative References............................................................................................5210.2 Informative References...........................................................................................54

11. Editors’ Addresses........................................................................................................5512. Change History.............................................................................................................56

12.1 31 August 2013 – Interim........................................................................................5612.2 14 September 2011 to 4 June 2012 – Whitepaper.................................................56


1011

106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149

12


List of FiguresFigure 1 – Broadband Forum CWMP End-to-End Architecture..........................................13Figure 2 – Print Kiosks and Secure Cloud Print Providers.................................................15Figure 3 – PWG SM System Object...................................................................................21Figure 4 – PWG SM PrintService Object............................................................................22Figure 5 – PWG SM PrintServiceCapabilities Group..........................................................22Figure 6 – PWG SM PrintServiceConfiguration Group (subunits)......................................23Figure 7 – PWG SM PrintServiceDefaults Group...............................................................23Figure 8 – PWG SM PrintServiceDescription Group (excerpt)...........................................24Figure 9 – PWG SM PrintServiceStatus group...................................................................26Figure 10 – PWG SM Print JobTable Group (w/ history)....................................................27Figure 11 – PWG SM InputTray Object (subunit)...............................................................28Figure 12 – PWG SM Console Object (subunit).................................................................29Figure 13 – PWG SM Marker Object (subunit)...................................................................30Figure 14 – PWG SM MarkerSupply Object (subunit)........................................................31

List of TablesTable 1 – PWG SM PrintService to IPP Proxy Mapping.....................................................38Table 2 – PWG SM Subunits to SNMP Proxy Mapping.....................................................50


1314

150151152153154155156157158159160161162163164

165166

167168169170

15


1. IntroductionThis document defines the requirements, implementation recommendations, proxy protocol mappings, and XML structure of a Printer data model for use with Broadband Forum CPE WAN Management Protocol (CWMP) [TR-069]. This Printer data model is based on machine-translation of the PWG Semantic Model XML Schema into XML schema objects that conform to Broadband Forum Data Model Template for TR-069-Enabled Devices [TR-106].

In this document, the term “Print Service” means a network service supports one or more standard or vendor-specific protocols which allow users to submit print jobs that include one or more documents by value (inline) or by reference (URI) – see section 2.2 below.

This document is strongly influenced by the ongoing evolution in the Managed Print Services (MPS) and broadband telecommunications (Telecom) industries. The primary goals of this document are to support automatic, remote, secure configuration of newly installed printers and to then securely manage them throughout their lifecycle.

Since the mid-1990s, high-quality digital printing technologies have become widespread. This has led to the convergence of traditional copiers and printers and the subsequent development of a new class of multifunction devices (MFDs). Older stand-alone office equipment typically performed a single copy, print, scan, or fax function. Newer MFDs have evolved to support all of these basic functions and also often include email, resource management, document transform, document storage, and other imaging services. In recent years, managed print service (MPS) providers have offered proactive supplies and maintenance service contracts to business, government, and university customers. The key limitation for MPS market growth has been the lack of a single, comprehensive monitoring and management interface across the current generation of MFDs.

Currently, print device status and diagnostic information is typically collected via SNMP using IETF MIB-II [RFC1213], IETF Host Resources MIB v2 [RFC2790], PWG Job Monitoring MIB [RFC2707], IETF Printer MIB v2 [RFC3805], IETF Finisher MIB [RFC3806], PWG Imaging System State and Counter MIB v2 [PWG5106.3], PWG Imaging System Power MIB [PWG5106.5], PWG Printer Port Monitor MIB [PWG5107.1], and PWG Printer MIB and IPP MFD Alerts [PWG5107.3].

Currently, print service status and print job information is typically collected via IPP/1.1 [RFC2911] and newer IPP versions 2.0, 2.1, and 2.2 [PWG5100.12].

Currently, information about other imaging services and MFDs overall is typically not available via open standard interfaces (i.e., the suite of PWG Semantic Model abstract services and WSDL/SOAP bindings).


1617

171

172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212

18


Meanwhile, Telecom service providers have also evolved dramatically. High-speed Internet and other data communications customer endpoints have become widespread, affordable, and reliable. Older single-function telecom customer premise equipment [CPE] such as land line telephones, set-top boxes (STBs), and mobile phones have converged and given rise to multifunction high-speed media offerings.

In the past, telecom infrastructure devices such as routers, bridges, cable modems, and DSL modems were monitored and managed via SNMP and TELNET/SSH. More recently, the telecom industry has migrated to the use of Broadband Forum CPE WAN Management Protocol (CWMP) [TR-069]. And the current generation of CPE devices are typically also managed using CWMP.

Telecom providers have now joined MPS providers as suppliers of printers and MFDs under service contracts in homes and businesses. Note that current telecom CPE device have more complex life-cycles than current printers and MFDs. A telecom CPE device is typically installed with entirely automatic initial configuration and is subsequently frequently updated with new firmware and new services, again via automatic configuration.


1920213214215216217218219220221222223224225226227228229

21


2. Terminology

2.1 Conformance Terminology

Capitalized terms, such as MUST, MUST NOT, RECOMMENDED, REQUIRED, SHOULD, SHOULD NOT, MAY, and OPTIONAL, have special meaning relating to conformance as defined in Key words for use in RFCs to Indicate Requirement Levels [RFC2119]. The term CONDITIONALLY REQUIRED is additionally defined for a conformance requirement that applies to a particular capability or feature.

2.2 Printing Terminology

Normative definitions and semantics of printing terms are imported from the Printer MIB v2 [RFC3805], Printer Finishings MIB [RFC3806], and Internet Printing Protocol/1.1: Model and Semantics [RFC2911]. This document also defines the following protocol roles in order to specify unambiguous conformance requirements:

IPP Client – Initiator of outgoing IPP session requests and sender of outgoing IPP operation requests (Hypertext Transfer Protocol -- HTTP/1.1 [RFC2616] User Agent).

IPP Printer – Listener for incoming IPP session requests and receiver of incoming IPP operation requests (Hypertext Transfer Protocol -- HTTP/1.1 [RFC2616] Server) that represents one or more Physical Devices or a Logical Device.

Managed Print Service (MPS) – A service model that adds value to MFDs and printers by combining provisioning, maintenance, and supplies into Service Level Agreements (SLAs).

Print Service – A network service supports one or more standard or vendor-specific protocols which allow users to submit print jobs that include one or more documents by value (inline) or by reference (URI).

SNMP MIB Agent – Listener for incoming SNMP Get and Set management requests and sender of optional outgoing SNMP notifications for a Printer or MFD (i.e., an SNMP Agent).

SNMP MIB Client – Initiator of outgoing SNMP Get and Set management requests and receiver of optional incoming SNMP notifications for a Printer or MFD (i.e., an SNMP Manager).

2.3 Telecommunications Terminology

Normative definitions and semantics of telecommunications management terms are imported from Broadband Forum CPE WAN Management Protocol [TR-069], including the following:


2223

230

231

232233234235236

237

238239240241

242243

244245246

247248

249250251

252253

254255256

257

258259260

24


Applied – A change to the Customer Premise Equipment (CPE) configuration has been applied when the CPE has stopped using the previous configuration and begun using the new Subunits.

Auto-Configuration Server (ACS) – This is a component in the broadband network responsible for auto-configuration of the Customer Premise Equipment (CPE) for advanced services.

Committed – A change to the Customer Premise Equipment (CPE) configuration has been committed when the change has been fully validated, the new configuration appears in the configuration data model for subsequent Auto-Configuration Server (ACS) operations to act on, and the change will definitely be applied in the future, as required by the protocol specification.

Customer Premises Equipment (CPE) – Refers to any TR-069-compliant device and therefore covers both Internet Gateway Devices (IGDs) and LAN-side end devices.

Data Model – A hierarchical set of CWMP parameters (i.e., elements) that define the managed objects accessible via [TR-069] for a particular device or service.

Deployment Unit (DU) – An entity that can be individually deployed on the Execution Environment. A Deployment Unit can consist of functional Execution Units and/or configuration files and/or other resources.

Device – Used interchangeably with CPE in [TR-069].

Execution Environment (EE) – A software platform that enables the dynamic loading and unloading of Software Modules. Typical examples include Linux, OSGi, .NET, and Java ME. Some Execution Environments enable the sharing of resources amongst modules.

Execution Unit (EU) – A functional entity that, once started, initiates processes to perform tasks or provide services, until it is stopped. Execution Units are deployed by Deployment Units. The following list of concepts could be considered Execution Units: services, scripts, software components, libraries, etc.

Internet Gateway Device (IGD) – A Customer Premise Equipment (CPE) device, typically a broadband router, that acts as a gateway between the WAN and the LAN.

Parameter – A name-value pair representing a manageable CPE parameter made accessible to an ACS for reading and/or writing.

Residential Gateway (RGW) – A gateway between the end user premise and the broadband service network (i.e., the Telecom network, not the Internet) that is introduced for architectural clarity in [TR-196].

Set Top Box (STB) – A television set top box that supports multimedia and Internet access by the end user.


2526261262263

264265266

267268269270271

272273

274275

276277278

279

280281282

283284285286

287288

289290

291292293

294295

27


Session – A contiguous sequence of CWMP transactions between a Customer Premise Equipment (CPE) and an Auto-Configuration Server (ACS). Note that a Session may span multiple TCP connections.

Software Module – The common term for all software (except firmware) that will be installed on an Execution Environment, including the concepts of Deployment Units and Execution Units.

Transaction – A message exchange between a Customer Premise Equipment (CPE) and an Auto-Configuration Server (ACS) consisting of a single request followed by a single response, initiated either by the CPE or ACS.

2.4 Other Terminology

Capitalized Term In Italics: defininition of the term with any references as appropriate.

2.5 Acronyms and Organizations

BBF – Broadband Forum, http://www.broadband-forum.org/

IANA – Internet Assigned Numbers Authority, http://www.iana.org/

IETF – Internet Engineering Task Force, http://www.ietf.org/

ISO – International Organization for Standardization, http://www.iso.org/

PWG – Printer Working Group, http://www.pwg.org/


2829296297298

299300301

302303304

305

306

307

308

309

310

311

312

313

30


3. Requirements

3.1 Rationale for CWMP Printer Data Model

3.1.1 Rationale from PWG Perspective

IETF and PWG standards for the printing industry define:

a) A rationale for an abstract model of printing (to support alternate encodings and protocols) in section 3 of the IETF IPP Rationale [RFC2568];

b) A set of design goals for status monitoring in a printing protocol in section 3.1.3 'Viewing the status and capabilities of a printer' (for End User), section 3.2.1 'Alerting' (for Operator), and section 3.3 'Administrator' (the bullet requirement to 'administrate billing or other charge-back mechanisms') of the IETF IPP Design Goals [RFC2567];

c) An abstract model of a Print Service (i.e., ISO DPA Logical Printer) and a Print Device (i.e., ISO DPA Physical Printer) in section 2.1 of IETF IPP/1.1 [RFC2911];

d) An abstract model of a Print Device and contained Subunits in section 2.2 of the IETF Printer MIB v2 [RFC3805];

e) An abstract model of Finishing Subunits integrated into the Printer Model (from [RFC3805]) in section 3 of the IETF Finisher MIB [RFC3806];

f) A set of Finishing Subunit types in the 'FinDeviceTypeTC' textual convention in IANA Finisher MIB [IANAFIN], originally published in section 7 of the IETF Finisher MIB [RFC3806]; and

g) An abstract model of a Multifunction Device in section 2 of the PWG MFD Model and Common Semantics [PWG5108.01].

When deploying printers and MFDs in home and office CPE environments based on telecom service agreements, initial configuration via SNMP and Embedded Web Server is neither feasible nor scalable.

Therefore a CWMP Printer Data Model should:

a) Standardize native CWMP support for secure operations on network printers;

b) Standardize CWMP capabilities to manage, provision, and service these network printers;

c) Encourage adoption of IPP-based printing infrastructures;


3132

314

315

316

317

318319

320321322323324

325326

327328

329330

331332333

334335

336337338

339

340

341342

343

33


d) Encourage adoption of PWG Semantic Model-based objects and elements.

3.1.2 Rationale from Broadband Forum Perspective

The Broadband Forum CPE WAN Management Protocol (CWMP) standard [TR-069] defines a set of standard interfaces between the Auto-Configuration Server (ACS) of a service provider and all customer premise equipment (CPE) devices in a customer's network that supports the CWMP device data model.

Figure 1 below is excerpted from section 1.2 of Broadband Forum CWMP [TR-069] and depicts the scope of CWMP in an end-to-end WAN network architecture.

Figure 1 – Broadband Forum CWMP End-to-End Architecture

Implementation of CWMP-based printers would enable a service provider to offer the following advantages throughout the lifecycle of the printer:

a) Ease of Deployment: Web-based remote selection, activation, and control of pay-per-use services;

b) Touchless Installation: Automatic discovery, secure configuration, and policy-based setup of network printers that is scalable to support thousands or millions of users according to each user’s/group's profile and service contract and the customer's business policies (e.g., access control and monetization of print services based on time, volume, user ID, features, payment models, etc.). This is similar to the way mobile phones can be remotely identified, configured, and setup on a broadband network today;

c) Remote Device Management: Automatic and secure firmware/software downloads, upgrades, patches, performance/status monitoring, and new value-add services for network printers; and


3435344

345

346347348349

350351

352

353

354355

356357

358359360361362363364

365366367

36


d) Remote Diagnostics/Troubleshooting: Improved problem resolution capability – eliminates unnecessary and costly device replacement – enhances customer support process.

Broadband Forum CWMP current standards for the Telecom industry include:

a) A broadband management architecture for CPE devices in CWMP [TR-069];

b) A data model template for all devices that support CWMP in [TR106];

c) A common device data model in [TR-181];

d) An Internet Gateway Device (IGD) data model in [TR-098]; and

e) A series of device-specific CWMP data models based on [TR-106] for DSLHomeTM for VoIP [TR-104], Set Top Boxes [TR-135], Storage Service enabled devices [TR-140], and Femto access points [TR-196].

This document defines the first standard TR-069 data model defined for network printers.

3.2 Use Cases

The use cases below are written from the perspective of the End User or local Admin of the network printer being managed as a CPE device.

3.2.1 Printers managed by Telecom Providers

Customers in home and enterprise environments can use CWMP Printers that are deployed and maintained by Telecom providers. Because the PWG Semantic Model is supported in this CWMP Printer data model, Telecom providers will be able to add these imaging device products into their value added services as part of their managed services portfolios. A user could purchase or lease a CWMP Printer, plug it into their network, and have the device automatically securely configured by the Telecom provider’s ACS (management server). Based on which services the user has already subscribed to, the device will be appropriately provisioned. Telecom providers could negotiate marketing and support contracts with printer manufacturers for technical support, field service, and toner/supplies replenishment – this would create a whole new revenue stream through a different channel for the printer manufacturers.

3.2.2 Printers managed by MPS Providers

Customers in enterprise environments can use Printers that have been pre-configured and shipped with the domain address of the ACS (management server) used by the MPS provider. When the CWMP Printer is plugged into the enterprise network, the device will automatically contact the ACS, using its pre-configured credentials. Based on the services that have been purchased by the customer, the ACS will automatically securely configure the device (including any firmware updates if necessary). The device will then be under


3738368369370371372

373

374

375

376

377378379380381

382

383384

385

386387388389390391392393394395396

397

398399400401402403

39


the control of the MPS provider, who can maintain the SLAs, perform toner/supplies replenishment, schedule service calls, and perform metering for control of service levels as well as billing. Through the lifecycle of the product or the service contract, the device will be managed remotely by the MPS provider. If the customer fails to pay or does not renew the service contract, then the device and its services can be remotely disabled by the MPS provider.

3.2.3 Printers managed by Enterprise IT Staff

Enterprise communications infrastructure devices – routers, bridges, VoIP switches, video telephony servers, etc. – are already typically managed using Broadband Forum CWMP [TR-069]. By adding CWMP clients to network Printers, manufacturers can ship devices that can all be managed from a single ACS. When these CWMP Printers are physically moved between departments or policies are deployed for usage of these devices – e.g., able to print only black/white but not color or restrictions of usage by page count – or certain departments require stronger security than others, this will necessitate remote configuration and provisioning of these devices. Once a set of policies has been created, configuration of these CWMP Printers will become automatic instead of based on extensive manual work for enterprise IT network operators. This would save time, improve enterprise security and ensure adherence to policy.

3.2.4 Print Kiosks managed by Telecom Providers

Figure 2 below shows the deployment environment for these use cases.

Figure 2 – Print Kiosks and Secure Cloud Print Providers

In the Cloud Print use cases below, the mobile phones and print kiosks are managed by Telecom providers using CWMP. The mobile phones are managed via Telecom cellular networks, while the print kiosks are managed via Telecom broadband networks. The print


4041404405406407408409

410

411412413414415416417418419420421

422

423

424

425

426427428

42


kiosks are monitored for status, provisioned with new services, and verified with remote diagnostics using CWMP.

3.2.4.1 Cloud Print via IPP Everywhere

Mobile phone users can access any bundled or 3rd party application (Email, Dropbox, Photoapp, etc.) that shares their desired document (MS Word, PDF, JPEG, etc.) and press the Print button. Using geolocation or other means (default device, last used device, etc.) a list of available Print Kiosks from their Telecom’s secure Cloud Print Service is displayed to the user, who then chooses a “nearby” location (same city, neighborhood, building, etc.). The user’s print client submits the selected document via PWG IPP Everywhere [PWG5100.14] to their Telecom’s secure Cloud Print Service specifying the target Print Kiosk device.

3.2.4.2 Cloud Print via Pull Print

Mobile phone users can access any bundled or 3rd party application (Email, Dropbox, Photoapp, etc.) that shares their desired document (MS Word, PDF, JPEG, etc.) and press the Print button. The user chooses delayed printing and the user’s client submits the selected document via PWG IPP Everywhere [PWG5100.14] to their Telecom’s secure Cloud Print Service specifying delayed printing. The user receives a secure job identifier and associated PIN via email, instant messaging, or in-band from their application. At a later time, the user queries for a list of available Print Kiosks from their Telecom’s secure Cloud Print Service and then chooses a “nearby” location (same city, neighborhood, building, etc.). The user walks up to their chosen Print Kiosk and enters their job identifier and secure PIN information. The Print Kiosk displays the price for the print job which the user accepts (adding to their monthly bill). The user’s job is securely pulled from their Telecom’s secure Cloud Print Service via PWG IPP Everywhere [PWG5100.14] and is printed with the requested processing options.

3.3 Deployment Scenarios

Because the architecture of the Broadband Forum CWMP [TR-069] is highly scalable and is designed to provide secure remote services in a firewall-friendly manner, several deployment scenarios can be envisioned. No special ports need to be opened up in corporate firewalls, nor is reverse VPN tunneling required for service management – both of which are nightmares for IT security staff.

An ACS could be deployed as a service in a public cloud, or in a private cloud for an enterprise network, or as a private self- deployment by IT staff. Telecom providers could manage printers in homes, enterprises, and government agencies. MPS providers could manage multiple enterprises (each of which might have multiple physical sites). Printer manufacturers could manage printers in SOHO networks, production printing facilities, or graphic arts companies. Corporate IT staff could deploy CWMP on an in-house server and then manage devices within their Intranets.


4344429430

431

432433434435436437438439

440

441442443444445446447448449450451452453

454

455456457458459

460461462463464465466

45


3.4 Out of Scope

The CWMP Printer data model should not:

a) Define any new content outside the PWG Semantic Model XML schema;

b) Define any semantics for workflow applications;

c) Define any semantics for document repositories; and

d) Define any application-specific semantics for printer monitoring using CWMP.

3.5 Design Requirements

The CWMP Printer data model should:

a) Be based on the PWG Semantic Model XML schema definitions;

b) Include all content from the PWG Semantic Model XML schema when possible, e.g., within the limitations of the BBF data model language [TR-106] and XML schema definitions;

c) Follow the naming conventions of the PWG Semantic Model XML schema when possible, e.g., within the limitations of BBF data model parameter object and parameter names and name lengths; and

d) Preserve the access control semantics of the PWG Semantic Model XML schema, e.g., PrintServiceStatus abstract elements are read-only.


4647

467

468

469

470

471

472

473

474

475

476477478

479480481

482483

484

48


4. CWMP Printer Data ModelThis section proposes an outline approach for a Broadband Forum [TR-106] data model for a CWMP Printer that is technically equivalent to the PWG Semantic Model [PWG5108.01]. The top-level PrintService object, named according to the [TR-106] data model conventions, contains the PWG PrintService object.

4.1 Technical Approach

4.1.1 XML Format of BBF CWMP and PWG SM Data Models

Each specific Broadband Forum CWMP data model is defined as a single XML document instance (.xml) file that uses CWMP data model structural elements (model, object, parameter, etc.) and a fixed set of datatypes pre-defined in a separate CWMP XML document schema (.xsd). Complex datatypes (choices, unions, sequences, etc.) cannot be used in CWMP parameter definitions (i.e., elements). Instead such PWG SM complex datatypes can be translated as CWMP data model: (a) strings; (b) lists (comma-separated list of strings); or (c) sub-objects (sequences of parameters).

The PWG Semantic Model is defined in a set of WSDL and XML document schema (.xsd) files that define elements using native XML schema [W3C-XSD] datatypes and PWG SM defined complex datatypes (e.g., element groups, choices, unions, etc.). Therefore, the element dictionary defined in “PwgCommon.xsd” can’t be converted to a directly equivalent CWMP data model (e.g., in sequence clauses) because a CWMP object can only contain simple parameters.

Note: BBF CWMP data models do allow both object and parameter (element) imports by reference – this will be considered for CWMP Printer data model compactness.

4.1.2 Translation of PWG SM into CWMP Printer Data Model

The PWG Semantic Model System and PrintService objects (at least) should be translated into a corresponding CWMP Printer data model as follows:

Define translation rules for the PWG complex datatypes and element groups;

Machine-translate keyword PWG datatypes in “PwgWellKnownValues.xsd” and “MediaWellKnownValues.xsd” into simple CWMP ‘string’ and save in control files. Note: The complete and authoritative list of standard values is contained in the IANA IPP Registry[IANAIPP] and the corresponding PWG SM XML Schema files.

Machine-translate other PWG datatypes in “ServiceTypes.xsd”, “JobTypes.xsd”, “DocumentTypes.xsd”, and “WimsType.xsd” into simple CWMP types when possible and save in control files – convert ‘choice’ and ‘union’ types into simple CWMP ‘string’ or ‘list’ or CWMP sub-objects – convert ‘sequence’ types into CWMP sub-objects.


4950

485

486487488489

490

491

492493494495496497498

499500501502503504

505506

507

508509

510

511512513514

515516517518

51


Machine-translate the PWG elements dictionary in PwgCommon.xsd into a BBF parameter dictionary and save in control files – preserve integer ranges, string lengths, etc.

Machine-translate PWG SM System and PrintService objects (and their contained objects), using the above control files into an equivalent CWMP Printer data model – convert PWG SM simple elements one-to-one into CWMP parameters – convert PWG SM element groups into CWMP sub-objects – flatten names to shorten fully qualified CWMP parameter names – do not translate JobTable.ActiveJobs (for security) and PrintServiceCapabilitiesReady (too volatile).

Hand-edit this machine-translated CWMP Printer data model in order to fix artifacts and add XML documentation (annotations, comments, etc.).

4.1.3 Simple CWMP Parameter Datatypes

Parameters (elements) in CWMP data models cannot be defined with syntaxes of sequences or complex types, so these PWG Semantic Model datatypes should be flattened whenever possible, to improve efficiency over limited bandwidth WAN connections to the ACS. For example:

PrintServiceCapabilities.PrintDocumentTicketCapabilites.PrintDocumentProcessingCapabilities.NumberUp (list of integers)

PrintService.Capabilities.DocumentProcessing.NumberUp (string)

– comma-separated list of integer values in a string datatype

PrintServiceStatus.AccessModes (list of keywords)

PrintService.Status.AccessModes (string)

– comma-separated list of keyword values in a string datatype

4.1.4 Short CWMP Parameter Qualified Names

CWMP requests always reference (or pass) parameters (elements) in CWMP data models as fully qualified names (similar to XPath), so redundancy in PWG Semantic Model path names should be eliminated whenever possible, to improve efficiency over limited bandwidth WAN connections to the ACS. For example:

PrintService.Configuration.Subunits.InputTrays.InputTray

PrintService.Subunits.InputTray

PrintService.Capabilities.PrintJobTicketCapabilities.PrintJobProcessingCapabilities

PrintService.Capabilities.JobProcessing


5253519520

521522523524525526

527528

529

530531532533

534535

536

537

538

539

540

541

542543544545

546

547

548

549

54


Note: Each CWMP parameter has an explicit access mode (readOnly vs. readWrite), so the PWG SM MarkerSupplyDescription and MarkerSupplyStatus element groups can be safely folded together into the base CWMP PrintService.Subunits.Marker.MarkerSupply object, while preserving the access control distinctions of the PWG Semantic Model.


5556550551552553554

57


4.2 PWG Semantic Model

The PWG Semantic Model root is the System Object shown in Figure 3 below, which contains the Services group, which in turn contains the PrintServices group. The CWMP Printer data model is derived from a translation of the PWG SM System Object in Figure 3 and the PWG SM PrintService in Figure 4 below.

Figure 3 – PWG SM System Object


5859

555

556557558559

560

561

562

60


Figure 4 – PWG SM PrintService Object

Figure 5 – PWG SM PrintServiceCapabilities Group


6162

563

564

565

566

567

568

63


Figure 6 – PWG SM PrintServiceConfiguration Group (subunits)

Figure 7 – PWG SM PrintServiceDefaults Group


6465

569

570

571

572

573

574

66


Figure 8 – PWG SM PrintServiceDescription Group (excerpt)


6768

575

576

69



7071577

72


Figure 9 – PWG SM PrintServiceStatus group


7374

578

579

580

75


Figure 10 – PWG SM Print JobTable Group (w/ history)


7677

581

582

583

78


Figure 11 – PWG SM InputTray Object (subunit)


7980

584

585

586

81


Figure 12 – PWG SM Console Object (subunit)


8283

587

588

589

84


Figure 13 – PWG SM Marker Object (subunit)


8586

590

591

592

87


Figure 14 – PWG SM MarkerSupply Object (subunit)


8889

593

594

595

90


4.3 CWMP Printer Data Model Sketch

The following XML sketch of a CWMP Printer data model illustrates the proposed approach and some of the challenges in transforming the existing PWG Semantic Model XML document schema into a CWMP Printer data model conformant to [TR-106].

ISSUE: Need to add PWG SM System object, System Control Service, and Resource Service to CWMP Printer data model. Need support for SystemTotals, Power Management, Configured Resources, and Configured Services per feedback from Thinxtream.

<?xml version="1.0" encoding="UTF-8"?><dm:document xmlns:dm="urn:broadband-forum-org:cwmp:datamodel-1-1"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="urn:broadband-forum-org:cwmp:datamodel-1-1 cwmp-datamodel-1-1.xsd"spec="urn:broadband-forum-org:tr-999-1-0-0"> <import file="tr-069-biblio.xml" spec="urn:broadband-forum-org:tr-069-biblio"/> <import file="tr-106-1-0-types.xml" spec="urn:broadband-forum-org:tr-106-1-0"> <dataType name="IPAddress"/> </import> <bibliography> <!—- Set of references here --> <reference id="TR-135"> <name>TR-135</name> <title>Data Model for a TR-069 Enabled STB</title> <organization>BBF</organization> <category>TR</category> </reference> </bibliography>

 <model name="PrintService:1.0" isService="true"> <parameter name="PrintServiceNumberOfEntries" access="readOnly"> <description>Number of entries in the {{PrintService}} table. </description> <syntax> <unsignedInt/> </syntax> </parameter>

 <object name="PrintService.{i}." access="readOnly" minEntries="0" maxEntries="unbounded" numEntriesParameter="PrintServiceNumberOfEntries"> <description>PWG PrintService in Services in the CPE.</description> <parameter name="Enable" access="readWrite"> <description>Enables or disables this {{object}} instance.</description> <syntax> <boolean/> </syntax> </parameter> </object>

<object name="PrintService.{i}.Subunits." access="readOnly" minEntries="1" maxEntries="1"> <description>PWG PrintServiceConfiguration in the CPE.</description>


9192

596

597598599

600601602603

605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650

93


<parameter name="InputTrayNumberOfEntries" access="readOnly"> <description>Number of entries in the {{InputTray}} table.</description> <syntax> <unsignedInt/> </syntax> </parameter> <parameter name="MarkerNumberOfEntries" access="readOnly"> <description>Number of entries in the {{Marker}} table.</description> <syntax> <unsignedInt/> </syntax> </parameter> <parameter name="ProcessorNumberOfEntries" access="readOnly"> <description>Number of entries in the {{Processor}} table.</description> <syntax> <unsignedInt/> </syntax> </parameter>  </object>

<object name="PrintService.{i}.Subunits.InputTray.{i}." access="readOnly" minEntries="1" maxEntries="unbounded" numEntriesParameter="InputTrayNumberOfEntries"> <description>PWG InputTray in the CPE.</description> <parameter name="Enable" access="readWrite"> <description>Enables or disables this {{object}} instance.</description> <syntax> <boolean/> </syntax> </parameter>

 <parameter name="Description" access="readWrite"> <syntax> <string/> </syntax> </parameter>

 <parameter name="DeviceErrors" access="readOnly"> <syntax> <int/> </syntax> </parameter> <parameter name="Id" access="readOnly"> <syntax> <int/> </syntax> </parameter>  </object>

<object name="PrintService.{i}.Subunits.Marker.{i}." access="readOnly" minEntries="1" maxEntries="unbounded" numEntriesParameter=”MarkerNumberOfEntries”> <description>PWG Marker in the CPE.</description> <parameter name="Enable" access="readWrite"> <description>Enables or disables this {{object}} instance.</description> <syntax> <boolean/> </syntax>


9495651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712

96


</parameter> <parameter name="ColorantNumberOfEntries" access="readOnly"> <description>Number of entries in the {{Colorant}} table.</description> <syntax> <unsignedInt/> </syntax> </parameter> <parameter name="SupplyNumberOfEntries" access="readOnly"> <description>Number of entries in the {{Supply}} table.</description> <syntax> <unsignedInt/> </syntax> </parameter>

 <parameter name="Description" access="readWrite"> <syntax> <string/> </syntax> </parameter>

 <parameter name="DeviceErrors" access="readOnly"> <syntax> <int/> </syntax> </parameter> <parameter name="Id" access="readOnly"> <syntax> <int/> </syntax> </parameter> </object>

<object name="PrintService.{i}.Subunits.Marker.{i}.Supply.{i}." access="readOnly" minEntries="1" maxEntries="unbounded" numEntriesParameter="SupplyNumberOfEntries"> <description>PWG MarkerSupplies in the CPE.</description> <parameter name="Enable" access="readWrite"> <description>Enables or disables this {{object}} instance.</description> <syntax> <boolean/> </syntax> </parameter>

 <parameter name="Description" access="readWrite"> <syntax> <string/> </syntax> </parameter>

 <parameter name="Id" access="readOnly"> <syntax> <int/> </syntax> </parameter>  </object>

<object name="PrintService.{i}.Subunits.Processor.{i}."


9798713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774

99


access="readOnly" minEntries="1" maxEntries="unbounded" numEntriesParameter=”ProcessorNumberOfEntries”> <description>PWG Processor in the CPE.</description> <parameter name="Enable" access="readWrite"> <description>Enables or disables this {{object}} instance.</description> <syntax> <boolean/> </syntax> </parameter> <parameter name="PowerCalendarNumberOfEntries" access="readOnly"> <description>Number of entries in the {{PowerCalendar}} table.</description> <syntax> <unsignedInt/> </syntax> </parameter> <parameter name="PowerEventNumberOfEntries" access="readOnly"> <description>Number of entries in the {{PowerEvent}} table.</description> <syntax> <unsignedInt/> </syntax> </parameter> <parameter name="PowerTimeoutNumberOfEntries" access="readOnly"> <description>Number of entries in the {{PowerTimeout}} table.</description> <syntax> <unsignedInt/> </syntax> </parameter> </object>

<object name="PrintService.{i}.Subunits.Processor.{i}.PowerCalendar.{i}." access="readOnly" minEntries="1" maxEntries="unbounded" numEntriesParameter="PowerCalendarNumberOfEntries"> <description>PWG ProcessorDescription.PowerCalendar in the CPE.</description> <parameter name="Id" access="readOnly"> <syntax> <int/> </syntax> </parameter> <parameter name="RequestPowerState" access="readWrite"> <syntax> <string/> </syntax> </parameter> <parameter name="CalendarRunOnce" access="readWrite"> <syntax> <boolean/> </syntax> </parameter> </object>

<object name="PrintService.{i}.Capabilities." access="readOnly" minEntries="1" maxEntries="1"> <description>PWG PrintServiceCapabilities in the CPE.</description> <parameter name="Enable" access="readWrite"> <description>Enables or disables this {{object}} instance.</description> <syntax> <boolean/> </syntax> </parameter> </object>


100101775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836

102


<object name="PrintService.{i}.Capabilities.JobDescription." access="readOnly" minEntries="1" maxEntries="1"> <description>PWG PrintJobDescriptionCapabilities in the CPE.</description> <parameter name="ElementsNaturalLanguage" access="readWrite"> <syntax> <string/> </syntax> </parameter>  </object>

<object name="PrintService.{i}.Capabilities.JobProcessing." access="readOnly" minEntries="1" maxEntries="1"> <description>PWG PrintJobProcessingCapabilities in the CPE.</description> <parameter name="JobDelayOutputUntil" access="readWrite"> <syntax> <string/> </syntax> </parameter>  </object>

<object name="PrintService.{i}.Capabilities.DocumentDescription." access="readOnly" minEntries="1" maxEntries="1"> <description>PWG PrintDocumentDescriptionCapabilities in the CPE.</description> <parameter name="DocumentDigitalSignature" access="readWrite"> <syntax> <string/> </syntax> </parameter>  </object>

<object name="PrintService.{i}.Capabilities.DocumentProcessing." access="readOnly" minEntries="1" maxEntries="1"> <description>PWG PrintDocumentProcessingCapabilities in the CPE.</description> <parameter name="NumberUp" access="readWrite"> <description>Comma-separated list of allowed integer values</description> <syntax> <list/>

<int/> </syntax> </parameter>  </object>



<object name="PrintService.{i}.Defaults." access="readOnly" minEntries="1" maxEntries="1"> <description>PWG PrintServiceDefaults in the CPE.</description> <parameter name="Enable" access="readWrite"> <description>Enables or disables this {{object}} instance.</description> <syntax> <boolean/> </syntax> </parameter> </object>

<object name="PrintService.{i}.Defaults.JobDescription." access="readOnly" minEntries="1" maxEntries="1"> <description>PWG PrintJobDescription in the CPE.</description>


103104837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898

105


<parameter name="ElementsNaturalLanguage" access="readWrite"> <syntax> <string/> </syntax> </parameter>  </object>

<object name="PrintService.{i}.Description." access="readOnly" minEntries="1" maxEntries="1"> <description>PWG PrintServiceDescription in the CPE.</description> <parameter name="CharsetConfigured" access="readWrite"> <syntax> <string/> </syntax> </parameter>  </object>

<object name="PrintService.{i}.Status." access="readOnly" minEntries="1" maxEntries="1"> <description>PWG PrintServiceStatus in the CPE.</description> <parameter name="AccessModes" access="readOnly"> <description>Comma-separated list of access mode keywords</description> <syntax> <list/>

<string/> </syntax> </parameter> <parameter name="ConditionNumberOfEntries" access="readOnly"> <description>Number of entries in the {{Condition}} table.</description> <syntax> <unsignedInt/> </syntax> </parameter> <parameter name="CreateDate" access="readOnly"> <syntax> <string/> </syntax> </parameter>  </object>

 </model></dm:document>


106107899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944

945946

108


5. CWMP Proxy Implementation Guidance

5.1 PWG PrintService to IPP Proxy Guidance

Table 1 – PWG SM PrintService to IPP Proxy Mapping

PWG PrintService Group/Element IPP Printer/Job Attribute IETF/PWGReference

PrintServiceCapabilitiesPrintDocumentTicketCapabilitiesPrintDocumentDescriptionCapabilities

Printer RFC2911

(ImagingDocumentDescriptionCapabilities)DocumentDigitalSignature document-digital-signature-

supportedPWG5100.7

DocumentMessage (none – ‘true’ for PWG5100.7) PWG5100.7DocumentName (none – ‘true’ for PWG5100.7) PWG5100.7DocumentNaturalLanguage document-natural-language-

supportedPWG5100.7

(PrintService specific elements)CompressionSupplied compression-supported RFC2911DocumentCharsetSupplied document-charset-supported PWG5100.7DocumentDigitalSignatureSupplied document-digital-signature-

supportedPWG5100.7

DocumentFormatDetailsSupplied document-format-details-supported

PWG5100.7

DocumentFormatSupplied document-format-supported RFC2911DocumentFormatVersionSupplied document-format-version-

supportedPWG5100.7

DocumentMessageSupplied (none – ‘true’ for PWG5100.7) PWG5100.7DocumentMetadata (none – ‘true’ for JPS3) JPS3DocumentNameSupplied (none – ‘true’ for PWG5100.7) PWG5100.7DocumentUri (none – ‘true’ for PWG5100.5) PWG5100.5Impressions (none – ‘true’ for PWG5100.5) PWG5100.5KOctets (none – ‘true’ for PWG5100.5) PWG5100.5MediaSheets (none – ‘true’ for PWG5100.5) PWG5100.5PageOrderReceived (none – ‘true’ for PWG5100.5) PWG5100.5

PrintServiceCapabilitiesPrintDocumentTicketCapabilitiesPrintDocumentProcessingCapabilities

Printer RFC2911

(ImagingDocumentProcessingCapabilities)


109110

947

948

949

111



NumberUp (none – ‘true’ for PWG5100.5) PWG5100.5PresentationDirectionNumberUp (none – ‘true’ for PWG5100.5) PWG5100.5

(PrintService specific elements)Copies (none – ‘true’ for PWG5100.5) PWG5100.5CoverBack (none – ‘true’ for PWG5100.5) PWG5100.5CoverFront (none – ‘true’ for PWG5100.5) PWG5100.5DocumentPassword document-password-

supportedJPS3

FeedOrientation feed-orientation-supported PWG5100.11Finishings (none – ‘true’ for PWG5100.5) PWG5100.5FinishingsCol (none – ‘true’ for PWG5100.5) PWG5100.5FontNameRequested (none – ‘true’ for PWG5100.5) PWG5100.5FontSizeRequested (none – ‘true’ for PWG5100.5) PWG5100.5ForceFrontSize (none – ‘true’ for PWG5100.5) PWG5100.5ImpositionTemplate (none – ‘true’ for PWG5100.5) PWG5100.5InsertSheets (none – ‘true’ for PWG5100.5) PWG5100.5Media (none – ‘true’ for PWG5100.5) PWG5100.5MediaType (none – ‘true’ for PWG5100.5) PWG5100.5MediaColDatabase (none – not in CWMP model) PWG5100.11MediaColSupported (none – ‘true’ for PWG5100.5) PWG5100.5MediaInputTrayCheck (none – ‘true’ for PWG5100.5) PWG5100.5OrientationRequested (none – ‘true’ for PWG5100.5) PWG5100.5OutputBin (none – not in CWMP model)OutputDevice (none – not in CWMP model)PageDelivery (none – ‘true’ for PWG5100.5) PWG5100.5PageRanges (none – ‘true’ for PWG5100.5) PWG5100.5PagesPerSubset (none – not in CWMP model)PrintColorMode (none – not in CWMP model)PrintContentOptimize (none – not in CWMP model)PrintRenderingIntent print-rendering-intent-

supportedJPS3

Quality (none – ‘true’ for PWG5100.5) PWG5100.5Resolution (none – ‘true’ for PWG5100.5) PWG5100.5SeparatorSheets (none – ‘true’ for PWG5100.5) PWG5100.5SheetCollate (none – ‘true’ for PWG5100.5) PWG5100.5Sides (none – ‘true’ for PWG5100.5) PWG5100.5XImagePosition (none – ‘true’ for PWG5100.5) PWG5100.5XImageShift (none – ‘true’ for PWG5100.5) PWG5100.5XSide1ImageShift (none – ‘true’ for PWG5100.5) PWG5100.5XSide2ImageShift (none – ‘true’ for PWG5100.5) PWG5100.5YImagePosition (none – ‘true’ for PWG5100.5) PWG5100.5


112113

114



YImageShift (none – ‘true’ for PWG5100.5) PWG5100.5YSide1ImageShift (none – ‘true’ for PWG5100.5) PWG5100.5YSide2ImageShift (none – ‘true’ for PWG5100.5) PWG5100.5

PrintServiceCapabilitiesPrintJobTicketCapabilitiesPrintDocumentProcessingCapabilities

Printer RFC2911

(see PrintDocumentTicketCapabilities)

PrintServiceCapabilitiesPrintJobTicketCapabilitiesPrintJobDescriptionCapabilities

Printer RFC2911

(ImagingJobDescriptionCapabilities)ElementsNaturalLanguage generated-natural-language-

supportedRFC2911

JobAccountingID job-account-id-supported PWG5100.3JobAccountingUserID job-accounting-user-id-

supportedPWG5100.3

JobMandatoryElements (none – ‘true’ for PWG5100.7) PWG5100.7JobMessageFromOperator (none – ‘true’ for RFC2911) RFC2911JobMessageToOperator job-message-to-operator-

supportedPWG5100.3

JobMoreInfo (none – ‘true’ for PWG5100.8) PWG5100.8JobName (none – ‘true’ for RFC2911) RFC2911JobOriginatingUserName (none – ‘true’ for RFC2911) RFC2911JobOriginatingUserUri requesting-user-uri-supported JPS3JobPassword job-password-supported PWG5100.11JobPasswordEncryption job-password-encryption-

supportedPWG5100.11

KOctets job-k-octets-supported RFC2911TemplateCreatorUserName (none)TemplateId (none)TemplateInfo (none)TemplateName (none)TemplateType (none)

(PrintService specific elements)CompressionSupplied (none – ‘true’ for PWG5100.7) PWG5100.7DocumentCharsetSupplied (none – ‘true’ for PWG5100.7) PWG5100.7DocumentDigitalSignatureSupplied (none – ‘true’ for PWG5100.7) PWG5100.7DocumentFormatDetailsSupplied (none – ‘true’ for PWG5100.7) PWG5100.7DocumentFormatSupplied (none – ‘true’ for PWG5100.7) PWG5100.7


115116

117



DocumentFormatVersionSupplied (none – ‘true’ for PWG5100.7) PWG5100.7DocumentMessageSupplied (none – ‘true’ for PWG5100.7) PWG5100.7DocumentNameSupplied (none – ‘true’ for PWG5100.7) PWG5100.7Impressions job-impressions-supported RFC2911MediaSheets job-media-sheets-supported RFC2911PageOrderReceived page-order-received-

supportedPWG5100.3

PrintServiceCapabilitiesPrintJobTicketCapabilitiesPrintJobProcessingCapabilities

Printer RFC2911

(ImagingJobProcessingCapabilities)JobDelayOutputUntil job-delay-output-until-

supportedPWG5100.11

JobDelayOutputUntilTime job-delay-output-until-time-supported

PWG5100.11

JobHoldUntil job-hold-until-supported RFC2911JobHoldUntilTime job-hold-until-time-supported PWG5100.11JobMandatoryElements (none – ‘true’ for RFC2911) RFC2911JobPhoneNumber job-phone-number-supported PWG5100.11JobPriority job-priority-supported RFC2911JobRecipientName job-recipient-name-supported PWG5100.11

(PrintService specific elements)JobAccountingSheets job-accounting-sheets-

supportedPWG5100.3

JobCopies job-copies-supported PWG5100.5JobCoverBack job-cover-back-supported PWG5100.5JobCoverFront job-cover-front-supported PWG5100.5JobErrorSheet job-error-sheet-supported PWG5100.3JobFinishings job-finishings-supported PWG5100.5JobFinishingsCol job-finishings-col-supported PWG5100.5JobSaveDisposition save-disposition-supported PWG5100.11JobSheetMessage job-sheet-message-supported PWG5100.3JobSheetsCol job-sheets-col-supported PWG5100.3MultipleDocumentHandling multiple-document-handling-

supportedRFC2911

OutputBin output-bin-supported PWG5100.2OutputDevice output-device-supported PWG5100.7Overrides overrides-supported PWG5100.6PagesPerSubset (none – ‘true’ for PWG5100.8) PWG5100.8ProofPrint proof-print-supported PWG5100.11


118119

120



PrintServiceDefaultsDefaultPrintDocumentTicketPrintDocumentDescription

Printer RFC2911

(ImagingDocumentDescription)DocumentDigitalSignature document-digital-signature PWG5100.5DocumentMessage document-message PWG5100.5DocumentName document-name PWG5100.5DocumentNaturalLanguage document-natural-language PWG5100.5LastDocument last-document PWG5100.5

(PrintService specific elements)CompressionSupplied compression-supplied PWG5100.7DocumentCharsetSupplied document-charset-supplied PWG5100.7DocumentDigitalSignatureSupplied document-digital-signature-

suppliedPWG5100.7

DocumentFormatDetailsSupplied document-format-details- supplied

PWG5100.7

DocumentFormatSupplied document-format- supplied PWG5100.7DocumentFormatVersionSupplied document-format-version-

suppliedPWG5100.7

DocumentMessageSupplied document-message-supplied PWG5100.7DocumentMetadata document-metadata-supplied JPS3DocumentNameSupplied document-name-supplied PWG5100.7DocumentUri document-uri PWG5100.5Impressions impressions PWG5100.5KOctets k-octets PWG5100.5MediaSheets media-sheets PWG5100.5PageOrderReceived page-order-received PWG5100.5

PrintServiceDefaultsDefaultPrintDocumentTicketPrintDocumentProcessing

Printer RFC2911

(ImagingDocumentProcessing)NumberUp number-up PWG5100.5PresentationDirectionNumberUp presentation-direction-

number-upPWG5100.5

(PrintService specific elements)Copies copies PWG5100.5CoverBack cover-front PWG5100.5


121122

123



CoverFront cover-back PWG5100.5FeedOrientation feed-orientation PWG5100.11Finishings finishings PWG5100.5FinishingsCol finishings-col PWG5100.5FontNameRequested font-name-requested PWG5100.5FontSizeRequested font-size-requested PWG5100.5ForceFrontSize force-front-side PWG5100.5ImpositionTemplate imposition-template PWG5100.5InsertSheets insert-sheet PWG5100.5Media media PWG5100.5MediaType media-type PWG5100.5MediaColDatabase (none – not in CWMP model) PWG5100.11MediaColSupported media-col PWG5100.5MediaInputTrayCheck media-input-tray-check PWG5100.5OrientationRequested orientation-requested PWG5100.5OutputBin (none – not in CWMP model)OutputDevice (none – not in CWMP model)PageDelivery page-delivery PWG5100.5PageRanges page-ranges PWG5100.5PagesPerSubset (none – not in CWMP model)PrintColorMode (none – not in CWMP model)PrintContentOptimize (none – not in CWMP model)PrintRenderingIntent print-rendering-intent JPS3Quality print-quality PWG5100.5Resolution printer-resolution PWG5100.5SeparatorSheets separator-sheets PWG5100.5SheetCollate sheet-collate PWG5100.5Sides sides PWG5100.5XImagePosition x-image-position PWG5100.5XImageShift x-image-shift PWG5100.5XSide1ImageShift x-side1-image-shift PWG5100.5XSide2ImageShift x-side2-image-shift PWG5100.5YImagePosition y-image-position PWG5100.5YImageShift y-image-shift PWG5100.5YSide1ImageShift y-side1-image-shift PWG5100.5YSide2ImageShift y-side2-image-shift PWG5100.5

PrintServiceDefaultsDefaultPrintJobTicketPrintDocumentProcessing

Printer RFC2911

(see DefaultPrintDocumentTicket)


124125

126



PrintServiceDefaultsDefaultPrintJobTicketPrintJobDescription

Printer RFC2911

(ImagingJobDescription)ElementsNaturalLanguage natural-language-configured RFC2911JobAccountingID job-account-id-default PWG5100.3JobAccountingUserID job-accounting-user-id-default PWG5100.3JobMandatoryElements job-mandatory-attributes PWG5100.7JobMessageFromOperator (none)JobMessageToOperator job-message-to-operator-

defaultPWG5100.3

JobMoreInfo (none)JobName (none)JobOriginatingUserName (none)JobOriginatingUserUri (none)JobPassword (none)JobPasswordEncryption (none)KOctets (none)TemplateCreatorUserName (none)TemplateId (none)TemplateInfo (none)TemplateName (none)TemplateType (none)

(PrintService specific elements)CompressionSupplied (none)DocumentCharset document-charset-default RFC2911DocumentDigitalSignature document-digital-signature-

defaultPWG5100.7

DocumentFormatDetails document-format-details-default

PWG5100.7

DocumentFormat document-format-default RFC2911DocumentFormatVersion document-format-version-

defaultPWG5100.7

DocumentMessage (none)DocumentName (none)Impressions (none)MediaSheets (none)PageOrderReceived (none)


127128

129



PrintServiceDefaultsDefaultPrintJobTicketPrintJobProcessingDefault

Printer RFC2911

(ImagingJobProcessing)JobDelayOutputUntil job-delay-output-until-default PWG5100.11JobDelayOutputUntilTime (none)JobHoldUntil job-hold-until-default RFC2911JobHoldUntilTime (none)JobMandatoryElements (none – ‘true’ for RFC2911) RFC2911JobPhoneNumber job-phone-number-default PWG5100.11JobPriority job-priority-default RFC2911JobRecipientName job-recipient-name-default PWG5100.11

(PrintService specific elements)JobAccountingSheets job-accounting-sheets-default PWG5100.3JobCopies job-copies-default PWG5100.5JobCoverBack job-cover-back-default PWG5100.5JobCoverFront job-cover-front-default PWG5100.5JobErrorSheet job-error-sheet-default PWG5100.3JobFinishings job-finishings-default PWG5100.5JobFinishingsCol job-finishings-col-default PWG5100.5JobSaveDisposition (none)JobSheetMessage job-sheet-message-default PWG5100.3JobSheetsCol job-sheets-col-default PWG5100.3MultipleDocumentHandling multiple-document-handling-

defaultRFC2911

OutputBin output-bin-default PWG5100.2OutputDevice (none)Overrides (none)PagesPerSubset (none)ProofPrint proof-print-default PWG5100.11

PrintServiceDescription Printer RFC2911(ImagingServiceDescription)CharsetConfigured charset-configured RFC2911CharsetSupported charset-supported RFC2911DeviceID printer-device-id PWG5107.2MakeAndModel printer-make-and-model RFC2911MessageFromOperator printer-message-from-

operatorRFC2911


130131

132



MoreInfoManufacturerUri printer-more-info-manufacturer

RFC2911

MoreInfoUri printer-more-info RFC2911NaturalLanguageConfigured natural-language-configured RFC2911NaturalLanguageSupported natural-language-supported RFC2911OperationsSupported operations-supported RFC2911OwnerUri (none)OwnerVCard (none)ServiceChargeInfo printer-charge-info PWG5100.13ServiceChargeInfoUri printer-charge-info-uri PWG5100.13ServiceGeoLocation printer-geo-location PWG5100.13ServiceInfo printer-info RFC2911ServiceOrganization printer-organization PWG5100.13ServiceOrganizationalUnit printer-organizational-unit PWG5100.13ServiceLocation printer-location RFC2911ServiceName printer-name RFC2911ServiceStringsLanguageSupported (none)ServiceStringsUri (none)ServiceXriSupported printer-xri-supported RFC3380ServiceVersionsSupported ipp-versions-supported RFC2911

(PrintService specific elements)ColorSupported color-supported RFC2911CompressionDefault (none)CompressionSupported compression-supported RFC2911DocumentFormatDefault document-format-default RFC2911DocumentFormatSupported document-format-supported RFC2911DocumentFormatDetailsDefault document-format-details-

defaultPWG5100.7

DocumentFormatDetailsSupported document-format-details-supported

PWG5100.7

DocumentFormatVersionDefault document-format-version-default

PWG5100.7

DocumentFormatVersionSupported document-format-version-supported

PWG5100.7

DocumentPasswordSupported document-password-supported

PWG5100.13

FeaturesSupported ipp-features-supported PWG5100.13GetEventLife ippget-event-life RFC3396IdentifyActionsDefault identify-actions-default PWG5100.13IdentifyActionsSupported identify-actions-supported PWG5100.13ImpressionsSupported job-impressions-supported RFC2911


133134

135



JobConstraintsSupported job-constraints-supported PWG5100.13JobCreationElementsSupport job-creation-attributes-

supportedPWG5100.11

JobPasswordEncryptionSupported job-password-encryption-supported

PWG5100.11

JobPasswordSupported job-password-supported PWG5100.11PreferredElementsSupported preferred-attributes-supported PWG5100.13ResolversSupported job-resolvers-supported PWG5100.13JobSettableElementsSupported job-settable-attributes-

supportedRFC3380

JobSpoolingSupported job-spooling-supported PWG5100.11KOctetsSupported job-k-octets-supported RFC2911MaxSaveInfoSupported max-save-info-supported PWG5100.11MaxStitchingLocationsSupported max-stitching-locations-

supportedPWG5100.3

MediaBottomMarginSupported media-bottom-margin-supported

PWG5100.13

MediaLeftMarginSupported media-left-margin-supported PWG5100.13MediaRightMarginSupported media-right-margin-supported PWG5100.13MediaSheetsSupported job-media-sheets-supported RFC2911MediaSourceSupported media-source-supported PWG5100.13MediaTopMarginSupported media-top-margin-supported PWG5100.13MultipleDocumentJobsSupported multiple-document-jobs-

supportedRFC2911

MultipleOperationTimeout multiple-operation-time-out RFC2911MultipleOperationTimeoutAction multiple-operation-time-out-

actionPWG5100.13

PagesPerMinute pages-per-minute RFC2911PagesPerMinuteColor pages-per-minute-color RFC2911ParentPrintersSupported parent-printers-supported RFC3998PdlOverrideSupported pdl-override-supported RFC2911PrinterDetailedStatusMessages printer-detailed-status-

messagesPWG5100.11

PrinterSettableElementsSupported printer-settable-attributes-supported

RFC3380

PwgRasterDocumentResolutionSupported pwg-raster-document-resolution-supported

PWG5102.4

PwgRasterDocumentSheetBack pwg-raster-document-sheet-back

PWG5102.4

PwgRasterDocumentTypeSupported pwg-raster-document-type-supported

PWG5102.4

ReferenceUriSchemesSupported reference-uri-schemes- RFC2911


136137

138



supportedRepertoiresSupported repertoire-supported PWG5101.2ServiceConfigChangeDateTime (none)ServiceConfigChangeTime (none)ServiceIccProfiles printer-icc-profiles PWG5100.13ServiceIcons printer-icons PWG5100.13ServiceMandatoryJobElements printer-mandatory-job-

attributesPWG5100.13

SubordinatePrintersSupported subordinate-printers-supported

RFC3998

UserDefinedValuesSupported user-defined-values-supported

PWG5100.3

PrintServiceStatus Printer RFC2911(ImagingServiceStatus)AccessModes (none)ConditionTable (none) (use IPP Get-

Notifications)RFC3996

CreateDate (none)CurrentTime printer-current-time RFC2911DeviceServiceCount device-service-count PWG5100.13Id printer-device-id PWG5107.2ServiceUuid printer-uuid PWG5100.13MessageDateTime printer-message-date-time RFC3380MessageTime printer-message-time RFC3380NaturalLanguage natural-language-configured RFC2911SerialNumber (none)State printer-state RFC2911StateMessages printer-state-message RFC2911StateReasons printer-state-reasons RFC2911UpTime printer-up-time RFC2911

(PrintService specific elements)ImpressionsCompleted (none)IsAcceptingJobs printer-is-accepting-jobs RFC2911PrintServiceCounters (none)QueuedJobCount queued-job-count RFC2911

JobTable (none – use IPP Get-Jobs) (RFC2911)

(*** the end ***)


139140

141



142143950

951

144


5.2 PWG SM PrintService to SNMP Proxy Guidance

Table 2 – PWG SM Subunits to SNMP Proxy Mapping

PWG Subunit Group/Element IETF/PWG MIB Attribute IETF/PWGReference

ConsoleConsoleDescription

Printer MIB v2Imaging System Power MIB

RFC3805PWG5106.5

Description prtConsoleDescription RFC3805PowerCalendar powCalendarEntry PWG5106.5PowerEvent powEventEntry PWG5106.5PowerTimeout powTimeoutEntry PWG5106.5

ConsoleConsoleStatus

Host Resources MIB v2 Printer MIB v2Imaging System Power MIB

RFC2790RFC3805PWG5106.5

DeviceErrors hrDeviceErrors or (none) RFC2790Id hrDeviceIndex or (none) RFC2790PowerCounters powCounterEntry PWG5106.5PowerMeters powMeterEntry PWG5106.5PowerMonitor powMonitorEntry PWG5106.5PowerSupport powSupportEntry PWG5106.5PowerTransition powTransitionEntry PWG5106.5ProductId hrDeviceID RFC2790SubunitStates hrDeviceStatus

prtConsoleDisableRFC2790RFC3805

CoverCoverDescription

Printer MIB v2 RFC3805

Description prtCoverDescription RFC3805

CoverCoverStatus

Host Resources MIB v2 Printer MIB v2

RFC2790RFC3805

CoverIsOpen hrDeviceStatus prtCoverStatus

RFC2790RFC3805

CoverSubunitType prtCoverStatus RFC3805DeviceErrors hrDeviceErrors or (none) RFC2790Id hrDeviceIndex

prtCoverIndexRFC2790RFC3805


145146

952

953

954

147


6. Conformance Requirements[TBD]

7. Internationalization ConsiderationsFor interoperability and basic support for multiple languages, conforming implementations MUST support the Universal Character Set (UCS) Transformation Format -- 8 bit (UTF-8) [RFC3629] encoding of Unicode [UNICODE] [ISO10646] and the Unicode Format for Network Interchange [RFC5198].

8. Security ConsiderationsThis extension poses no additional security threats or burdens than those in IPP/1.1 [RFC2911, RFC2910] and Printer MIB v2 [RFC3805]. However, implementations MAY support different access control to various features, depending on the identity of the Admin user.


148149

955

956

957

958959960961

962

963964965966967

150


9. IANA and PWG ConsiderationsNo new IANA or PWG registrations are defined in this document.

10. References

10.1 Normative References

[IANAFIN] IANA Finisher MIB Registryhttps://www.iana.org/assignments/ianafinisher-mib/ianafinisher-mib

[IANAIPP] IANA IPP Registryhttp://www.iana.org/assignments/ipp-registrations/ipp-registrations.xhtml

[IANAPRT] IANA Printer MIB Registryhttp://www.iana.org/assignments/ianaprinter-mib/ianaprinter-mib

[PWG5100.12] R. Bergman, H. Lewis, I. McDonald, M. Sweet, "PWG Internet Printing Protocol Version 2.0 Second Edition", PWG 5100.12, February 2011, ftp://ftp.pwg.org/pub/pwg/candidates/cs-ipp20-20110214-5100.12.pdf

[PWG5100.14] I. McDonald, M. Sweet, "PWG IPP Everywhere", PWG 5100.14, January 2013, ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippeve10-20130128-5100.14.pdf

[PWG5106.3] I. McDonald, "PWG Imaging System State and Counter MIB v2.0", PWG 5106.3, March 2008, ftp://ftp.pwg.org/pub/pwg/candidates/cs-wimscountmib20-20080318-5106.3.pdf

[PWG5106.5] I. McDonald, "PWG Imaging System Power MIB v1.0", PWG 5106.5, February 2011,ftp://ftp.pwg.org/pub/pwg/candidates/cs-wimspowermib10-20110214-5106.5.pdf

[PWG5107.1] R. Bergman, M. Fenelon, I. McDonald, I. Pavicevic, "PWG Printer Port Monitor MIB v1.0", PWG 5107.1, October 2005,ftp://ftp.pwg.org/pub/pwg/candidates/cs-pmpportmib10-20051025-5107.1.pdf

[PWG5107.3] R. Bergman, I. McDonald, "PWG Printer MIB and IPP MFD Alerts", PWG 5107.3, June 2012,


151152

968

969

970

971

972973

974975976

977978

979980981

982983984985

986987988989

990991992993

994995996997

998999

153

ftp://ftp.pwg.org/pub/pwg/candidates/cs-wimscountmib20-20080318-5106.3.pdf

ftp://ftp.pwg.org/pub/pwg/candidates/cs-wimscountmib20-20080318-5106.3.pdf


ftp://ftp.pwg.org/pub/pwg/candidates/cs-pmpmfdalerts10-20120629-5107.3.pdf

[PWG5108.01] W. Wagner and P. Zehler, "MFD Model and Common Semantics”, PWG 5108.01, May 2011,ftp://ftp.pwg.org/pub/pwg/candidates/cs-sm20-mfdmodel10-20110415-5108.01.pdf

[RFC2707] R. Bergman, T. Hastings, S. Isaacson, H. Lewis, "Job Monitoring MIB v1.0", IETF RFC 2707, November 1999,ftp://ftp.ietf.org/rfc/rfc2707.txt

[RFC2911] T. Hastings, R. Herriot, R. deBry, S. Isaacson, P. Powell, "Internet Printing Protocol/1.1: Model and Semantics", IETF RFC 2911, September 2000,ftp://ftp.ietf.org/rfc/rfc2911.txt

[RFC3805] R. Bergman, H. Lewis, I. McDonald, "Printer MIB v2", IETF RFC 3805, June 2004,ftp://ftp.ietf.org/rfc/rfc3805.txt

[RFC3806] R. Bergman, H. Lewis, I. McDonald, "Printer Finishing MIB", IETF RFC 3806, June 2004,ftp://ftp.ietf.org/rfc/rfc3806.txt

[TR-069] Broadband Forum, "CPE WAN Management Protocol Amendment 3", BBF Technical Report 069 Release 3.2, November 2010,http://www.broadband-forum.org/technical/trlist.php

[TR-098] Broadband Forum, "Internet Gateway Device Data Model for TR-069 Amendment 2", BBF Technical Report 098 Release 3.0, September 2008, http://www.broadband-forum.org/technical/trlist.php

[TR-106] Broadband Forum, "Data Model Template for TR-069-Enabled Devices Amendment 5", BBF Technical Report 106 Release 3.2, November 2010, http://www.broadband-forum.org/technical/trlist.php

[TR-157] Broadband Forum, "Component Objects for CWMP Amendment 3", BBF Technical Report 157 Release 3.2, November 2010, http://www.broadband-forum.org/technical/trlist.php

[TR-181] Broadband Forum, "Device Data Model for TR-069 Amendment 2", BBF Technical Report 181 Release 4.0, February 2011,http://www.broadband-forum.org/technical/trlist.php


15415510001001

1002100310041005

100610071008

1009101010111012

101310141015

101610171018

101910201021

1022102310241025

1026102710281029

103010311032

103310341035

156

http://www.broadband-forum.org/technical/trlist.php





ftp://ftp.ietf.org/rfc/rfc3806.txt




ftp://ftp.pwg.org/pub/pwg/candidates/cs-sm20-mfdmodel10-20110415-5108.01.pdf

ftp://ftp.pwg.org/pub/pwg/candidates/cs-sm20-mfdmodel10-20110415-5108.01.pdf


10.2 Informative References

[MR-230] Broadband Forum, "TR-069 Deployment Scenarios", BBF Marketing Report 230, August 2010, http://www.broadband-forum.org/marketing/marketingdocuments.php

[MR-239] Broadband Forum, "Broadband Forum Value Proposition for Connected Home", BBF Marketing Report 239, April 2011, http://www.broadband-forum.org/marketing/marketingdocuments.php

[RFC2567] F.D. Wright, "Design Goals for an Internet Printing Protocol", IETF RFC 2567, April 1999,ftp://ftp.ietf.org/rfc/rfc2567.txt

[RFC2568] S. Zilles, "Rationale for the Structure of the Model and Protocol for the Internet Printing Protocol", IETF RFC 2568, April 1999,ftp://ftp.ietf.org/rfc/rfc2568.txt

[TR-104] Broadband Forum, "DSLHomeTM Provisioning Parameters for VoIP CPE", BBF Technical Report 131 Release 3.2, November 2009, http://www.broadband-forum.org/technical/trlist.php

[TR-131] Broadband Forum, "ACS Northbound Interface Requirements", BBF Technical Report 131 Release 3.2, November 2009, http://www.broadband-forum.org/technical/trlist.php

[TR-135] Broadband Forum, "Data Model for a TR-069 Enabled STB Amendment 1", BBF Technical Report 135 Release 3.0, November 2010, http://www.broadband-forum.org/technical/trlist.php

[TR-140] Broadband Forum, "TR-069 Data Model for Storage Service Enabled Devices Amendment 1", BBF Technical Report 140 Release 3.0, April 2010, http://www.broadband-forum.org/technical/trlist.php

[TR-143] Broadband Forum, "Enabling Network Throughput Performance Tests and Statistical Monitoring", BBF Technical Report 143 Release 3.0, May 2008, http://www.broadband-forum.org/technical/trlist.php

[TR-196] Broadband Forum, "Femto Access Point Service Data Model Amendment 1", BBF Technical Report 196, May 2011, http://www.broadband-forum.org/technical/trlist.php


157158

1036

103710381039

104010411042

104310441045

104610471048

104910501051

105210531054

1055105610571058

1059106010611062

1063106410651066

106710681069

159









http://www.broadband-forum.org/marketing/marketingdocuments.php

http://www.broadband-forum.org/marketing/marketingdocuments.php


11. Editors’ AddressesNancy ChenIndependentEmail: [email protected]

Ira McDonaldHigh North IncPO Box 221Grand Marais, MI 49839Phone: +1-906-494-2434Email: [email protected]

The editors would also like to thank the following individuals for their contributions to this document:

Laxman J Bhat – CelstreamNagaraj Ghatigar – CelstreamSubramanyan Krishnan – CelstreamRanga Raj – Thinxtream TechnologiesAnil Thakkar – Thinxtream Technologies


160161

1070

10711072107310741075107610771078107910801081

10821083

10841085108610871088

162

mailto:[email protected]

mailto:[email protected]


12. Change History

12.1 31 August 2013 – Interim

- Updated to use current PWG template and logo

- Changed title to ‘CWMP Printer Data Model’ (removing MFD reference)

- Revised and clarified sections 1 through 4

- Completed PWG PrintService to IPP Proxy mapping table in section 5.1

- Started PWG Subunits to SNMP Proxy mapping table in section 5.2

- Revised normative and informative references in section 10

12.2 14 September 2011 to 4 June 2012 – Whitepaper

- Seven previous drafts as a CWMP BOF whitepaper

- Initial content from Nancy Chen, Ira McDonald, and Ranga Raj

- Rationale from Nancy Chen

- Uses cases from Ranga Raj

- Print Kiosks management from Laxman J. Bhat

- Deployment scenarios from Ranga Raj

- Partial PWG PrintService to IPP Proxy mapping from Ira McDonald


163164

1089

1090

1091

1092

1093

1094

1095

1096

1097

1098

1099

1100

1101

1102

1103

1104

1105

165

Documents

ftp.pwg.orgftp.pwg.org/pub/pwg/mfd/wd/wd-smcwmpprint10-201308… · Web viewAbstract: This document defines the requirements, implementation recommendations, proxy protocol mappings,