DPS usage of USB and PTP

1. DPS Usage of USB and PTP
Bear Lin
2009/04/28

2. Overview
This section describes how DSCs and Printers shall
implement DPS over the USB physical layer with the
Still Image Capture Device Class PTP protocol.

3. DSC PTP Implementation Requirements
When a DPS system operates under PTP, it shall
comply with [PTP].
PTP contain details of Operation, Response, Event,
and ObjectFormat codes required by the
initiator(Printer) and the responder(DSC).
The following list shows the necessary Operation,
Response, and Event codes for the system.

4. DSC PTP Implementation Requirements
PTP Operation Codes:

5. DSC PTP Implementation Requirements(cont.)
PTP Response Codes:

6. DSC PTP Implementation Requirements(cont.)
PTP Event Codes:

7. Details of DPS Discovery(cont.)

8. Special DSC PTP Implementations for DPS

9. Special DSC PTP Implementations for DPS(Cont.)

10. Implementation of DPS Actions Over PTP
DPS Special-Optimized Actions:
1. Most DPS action will be passed with XML format.
2. Some DPS actions either because they pass large amounts of binary
data or because they would be more efficient to implement using the
standard PTP operations are not passed through to the DPS layer on the
DSC.
3. The following table specifies which actions are “special optimized”
actions. All other actions are “pass-through” actions.

11. Implementation of DPS Actions Over PTP(cont.)
Printer-to-DSC DPS Pass-Through Actions:
notifyDeviceStatus,
notifyJobStatus

12. Implementation of DPS Actions Over PTP(cont.)
DSC-to-Printer DPS Pass-Through Actions:
configurePrintService,
getCapability,
startJob, …

13. Implementation of DPS Actions Over PTP(cont.)
DPS Special Optimized Actions:

14. Implementation of DPS Actions Over PTP(cont.)
DPS Special Optimized Actions:

15. Implementation of DPS Actions Over PTP(cont.)
DPS Special Optimized Actions:

16. Implementation of DPS Actions Over PTP(cont.)
DPS Special Optimized Actions:

17. Collision Situation