PictBridge 01 - PictBridge(DPS) Overview
?Download as PPTX, PDF?
0 likes?396 views
The document provides an overview of PictBridge (DPS), a standard that enables direct printing from any PictBridge-compliant digital camera to any PictBridge-compliant printer regardless of manufacturer. It discusses key terminology, introduces the architectural framework based on a client-server model using Picture Transfer Protocol (PTP) and USB, and provides an example job flow including XML scripts for operations and events. The main implementation efforts involve using PTP over USB and requiring XML parsers to handle the passing of DPS actions in XML format.
PictBridge 01 - PictBridge(DPS) Overview
- 2. Outline ?Terminology ?Introduction ?Architectural Framework ?Job Flow Example ?Main Efforts to Implement PictBridge
- 3. Terminology ?DPS(Digital Photo Solutions for Image Device) ?DSC(Digital Still Image Camera) ?PTP(Picture Transfer Protocol) ?XML(Extensible Markup Language) ?DPOF(Digital Print Order Format)
- 4. Introduction ?CIPA DC-001-2003: Digital Photo Solutions(DPS) for Imaging Devices, Standard of CIPA(Cameras & Imaging Products Association). ?＾PictBridge￣ is a promotion name of DPS standard. ?Main Site: http://www.cipa.jp/pictbridge/index_e.html
- 5. Introduction(cont.) ?PictBridge is a smart way to enable direct printing from any PictBridge compliant DSC to any PictBridge compliant printer, regardless of the manufacturer.
- 6. Introduction(cont.) ?PictBridge v.s. DPOF: DPOF 頁匯_慧議複万屶址參和匯乂双咫竃O崔 x馗槻孚頭勣双咫竃、 耽孚頭双咫議芸機 双咫沫哈D頭、 D駮D、 喘Y侖兆、仇峽吉吉、 D騙Y鮪}、f苧吉吉。 ?音^喇豢鬼aC才竃O箋腸隨來}參式匯乂撹云陣崙議咀殆е堕診 DPOF 議 喘峪児豢匯曳^児云議A粁載謹互議孔嬬o隈V刑噸式。 ?曳泌朕念鬼aC岷俊B俊咫燕C議孔嬬m隼辛參F徽頁s贋壓赤惶掴猗殪}軸 峪嬬揖匯瞳兎議鬼aC才咫燕C嘉嬬F岷双咫議孔嬬。 ?咀緩 F壓 DPOF 幟u壓記竃繁議匯畠仟議、寔屎睡瞳兎議、V刑議福！ PictBridge 屎幟u函旗 DPOF。 ?http://baike./view/65011.htm ?http://www.casio.com.tw/qv/dpof/index.html ?http://www.digital.idv.tw/DIGITAL/Classroom/MROH-CLASS/oh89/index-89.htm
- 7. Architectural Framework ?The DSC is USB Still Image Capture Class ＾Device￣, and the printer works as a USB ＾Host￣. USB Device USB I/F USB Host
- 8. Architectural Framework(cont.) ?DPS architecture is based on Client-Server model. ?The DSC and the printer must support the Picture Transfer Protocol(PTP) and the USB.
- 9. Architectural Framework(cont.) ?DPS actions = a request phase + a response phase, both request/response are well formed XML. ?DPS has two kinds of actions: DPS operations and DPS events. ?DPS operation: a transaction initiated by the DPS client and completed by the DPS server. ?DPS event: a notification from a DPS server to the DPS client. It is initiated when a state change occurs in the server.
- 10. Architectural Framework(cont.) ?DPS Action Results: For every DPS Action request, a DPS Action result shall be returned along with the DPS Action response.
- 11. Architectural Framework(cont.) ?DPS¨s actions and events are based on PTP. ?Each action or event is a sequence of PTP commands. ?PTP contains details of Operation, Response, Event and ObjectFormat codes required by the Printer and DSC.
- 12. Architectural Framework(cont.) ?DPS Print Service Actions:
- 13. Architectural Framework(cont.) ?DPS Storage Service Actions:
- 14. Job Flow Example
- 15. Job Flow Example(cont.) ?DPS Operation XML script example:
- 16. Job Flow Example(cont.) ?DPS Operation XML script example:
- 17. Job Flow Example(cont.) ?DPS Event XML script example:
- 18. Main Efforts to Implement PictBridge ?Implement DPS over the USB physical layer with the Still Image Capture Device Class PTP protocol. ?XML parsers are required because DPS actions will be passed over PTP/USB in their original XML format.