Giving RFID a REST: Web-enabled EPCIS


Published on

In the EPCIS REST-Adapter project, we propose seamlessly integrating this network into the Web by designing a RESTful (REpresentational State Transfer) architecture for the EPCIS. Using this approach, each query, tagged object, location or RFID reader gets a unique URL that can be linked to, exchanged in emails, browsed for, bookmarked, etc. Additionally, this paradigm shift allows Web languages like HTML and JavaScript to directly use RFID data to fast-prototype light-weight applications such as mobile applications or Web mashups. We illustrate these benefits with a JavaScript mashup platform that integrates several services on the Web (e.g., Twitter, Wikipedia, etc.) with RFID data to allow managers along the supply chain and customers to get comprehensive data about their products.

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Benchmarkedlocally (one hop away)Can beexplainedmainly by the processing time for SOAP on the client-side vs simple JSON/jDOMunmarshalling
  • Giving RFID a REST: Web-enabled EPCIS

    1. 1. Giving RFID a REST:Building a Web-Enabled EPCIS <br />Dominique Guinard, Auto-ID Labs, MIT / ETH Zurich / SAP Research<br />Mathias Mueller, Jacques Pasquier-RochaSoftware Engineering Group, University of Fribourg Switzerland<br />
    2. 2. Whatis the EPCIS / EPC Network?<br />[]<br />Background & Motivation<br />Dominique Guinard<br />2<br />IoT 2010<br />
    3. 3. The Web Era<br />Web<br />Rise of the WoT:<br />Ubiquitous & Scalable<br />The new universalintegrationbus<br />Machines, appliances, sensors, mobile phones consumer electronics are in<br />Full of apps, widgets and mashups<br />Whereis RFID?<br />Dominique Guinard<br />3<br />IoT 2010<br />
    4. 4. EPC Network in a Nutshell<br />Integration Interface<br />4<br />IoT 2010<br />Dominique Guinard<br />
    5. 5. Towards a mashable EPC Network<br />Classical SOAP Web Services adequate for business integration (e.g., ERP):<br />Not so much for more light-weight, ad-hoc integration<br />Requirements for new API:<br />Low entry barrier for developements(easier/cheaper)<br />Direct data access to users<br />Lightweight (embedded/mobile devices)<br />Easyto scale (cloud)<br />Pautasso, Cesare, Olaf Zimmermann, and Frank Leymann. “Restful web services vs. "big" web services: making the right architectural decision.” WWW '08<br />Pautasso, Cesare, and Erik Wilde. “Why is the Web Loosely Coupled? A Multi-Faceted Metric for Service Design.” WWW’09<br />5<br />IoT 2010<br />Dominique Guinard<br />
    6. 6. How do we Web-enable the EPC Network? <br />[ ]<br />Architecture<br />Dominique Guinard<br />6<br />IoT 2010<br />
    7. 7. Recap: The Web of Things<br />D. Guinard, V. Trifa, E. Wilde: " A Resource Oriented Architecture for the Web of Things” IoT 2010<br />7<br />IoT 2010<br />Dominique Guinard<br />
    8. 8. API Design: Addressability & Connectedness<br />Resources:<br />Locations, Readers, Tagged objects (EPC), etc.<br />Links:<br />Every resource is linked to its children.<br />And to relevant resources.<br />http://.../location/migros:basel/reader/warehouse:incoming/time/2009-12-21T13:22:04.000Z/event/EPC<br />Dominique Guinard<br />8<br />IoT 2010<br />
    9. 9. Wait, the EPCIS is not Hierachical!<br /> The EPCIS data isn‘t really hierachical:<br />Complex queries become cumbersome:<br />all events occurring in 2010 for urn:epc:id:sgtin: 0057000.123430.2025<br />Query-based interface<br />http://.../eventquery/result?param1=value1&..&paramN=valueN<br />http://.../eventquery/result?reader=sap:regensdorf:frc:storage&epc=urn:epc:id:sgtin:200057000.*<br />Dominique Guinard<br />9<br />IoT 2010<br />
    10. 10. Design: Representations<br />Several representations:<br />XML: EPCIS standard<br />JSON: Web integration<br />HTML: browsability<br />CSS for browser<br />CSS for mobile (IUI)<br />Selected through “HTTP content negotiation”<br />Atom feeds for subscription to queries.<br />Dominique Guinard<br />10<br />IoT 2010<br />
    11. 11. IntegrationStrategy for WS-* / REST<br />Woven REST:<br /><ul><li>Integrated to the core
    12. 12. Resource-orientedobject model
    13. 13. no overhead</li></ul>REST Adapter:<br /><ul><li>Independant module
    14. 14. Hot-pluggable on any EPCIS implementation
    15. 15. Full legacy support</li></ul>Dominique Guinard<br />11<br />IoT 2010<br />
    16. 16. Implementation: EPCIS REST-adapter <br />12<br />IoT 2010<br />Dominique Guinard<br />
    17. 17. Performance Evaluation<br />13<br />IoT 2010<br />Dominique Guinard<br />
    18. 18. Whatisit good for?<br />[]<br />Prototype APPLIcation<br />Dominique Guinard<br />14<br />IoT 2010<br />
    19. 19. EPC Mashup Dashboard<br />Javascriptmashup (GWT).<br />Uses the REST API.<br />Extensible widget base.<br />Dominique Guinard<br />15<br />IoT 2010<br />
    20. 20. LeveragingOther Web Platforms: Sharing<br />D.Guinard, M. Fischer, V. Trifa . Sharing Using Social Networks in a Composable Web of Things. WoT 2010 <br />16<br />IoT 2010<br />Dominique Guinard<br />
    21. 21. Take Home Notes<br />Making the EPC Network part of the WoT:<br />unlocks new types of app (mobile, mashups, …)<br />allowsfor easy: scaling (cloud), browsing, sharing and bookmarking of RFID data<br /><ul><li>REST and SOAP-based Web Servicesinterfaces cancohabit</li></ul>17<br />IoT 2010<br />Dominique Guinard<br />
    22. 22. Challenges & outlook<br />Incentive for companies to share data…<br />Sharing mechanism:<br />EPC Discovery standard<br />Social Access Controller / Friends and Things<br />We are currentlyworking on:<br />Adaptingother standards to the Web (E.g., TDT)<br />Creating a mashupplatform for common EPC applications.<br />18<br />IoT 2010<br />Dominique Guinard<br />
    23. 23. Thanks a lot for your attention<br />EPCIS REST-adapter is Open Source (LGPL)<br />Module of the Fosstrak EPCIS<br />Contact:<br />Dominique Guinard<br /><br />19<br /><br />