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.
Bajaj Allianz Life Insurance Company - Insurer Innovation Award 2024
Giving RFID a REST: Web-enabled EPCIS
1. Giving RFID a REST:Building a Web-Enabled EPCIS Dominique Guinard, Auto-ID Labs, MIT / ETH Zurich / SAP Research Mathias Mueller, Jacques Pasquier-RochaSoftware Engineering Group, University of Fribourg Switzerland
3. The Web Era Web Rise of the WoT: Ubiquitous & Scalable The new universalintegrationbus Machines, appliances, sensors, mobile phones consumer electronics are in Full of apps, widgets and mashups Whereis RFID? Dominique Guinard 3 IoT 2010
4. EPC Network in a Nutshell Integration Interface 4 IoT 2010 Dominique Guinard
5. Towards a mashable EPC Network Classical SOAP Web Services adequate for business integration (e.g., ERP): Not so much for more light-weight, ad-hoc integration Requirements for new API: Low entry barrier for developements(easier/cheaper) Direct data access to users Lightweight (embedded/mobile devices) Easyto scale (cloud) Pautasso, Cesare, Olaf Zimmermann, and Frank Leymann. “Restful web services vs. "big" web services: making the right architectural decision.” WWW '08 Pautasso, Cesare, and Erik Wilde. “Why is the Web Loosely Coupled? A Multi-Faceted Metric for Service Design.” WWW’09 5 IoT 2010 Dominique Guinard
6. How do we Web-enable the EPC Network? [flickr.com/photos/julianbleecker ] Architecture Dominique Guinard 6 IoT 2010
7. Recap: The Web of Things D. Guinard, V. Trifa, E. Wilde: " A Resource Oriented Architecture for the Web of Things” IoT 2010 7 IoT 2010 Dominique Guinard
8. API Design: Addressability & Connectedness Resources: Locations, Readers, Tagged objects (EPC), etc. Links: Every resource is linked to its children. And to relevant resources. http://.../location/migros:basel/reader/warehouse:incoming/time/2009-12-21T13:22:04.000Z/event/EPC Dominique Guinard 8 IoT 2010
9. Wait, the EPCIS is not Hierachical! The EPCIS data isn‘t really hierachical: Complex queries become cumbersome: all events occurring in 2010 for urn:epc:id:sgtin: 0057000.123430.2025 Query-based interface http://.../eventquery/result?param1=value1&..¶mN=valueN http://.../eventquery/result?reader=sap:regensdorf:frc:storage&epc=urn:epc:id:sgtin:200057000.* Dominique Guinard 9 IoT 2010
10. Design: Representations Several representations: XML: EPCIS standard JSON: Web integration HTML: browsability CSS for browser CSS for mobile (IUI) Selected through “HTTP content negotiation” Atom feeds for subscription to queries. Dominique Guinard 10 IoT 2010
20. LeveragingOther Web Platforms: Sharing D.Guinard, M. Fischer, V. Trifa . Sharing Using Social Networks in a Composable Web of Things. WoT 2010 16 IoT 2010 Dominique Guinard
21.
22. Challenges & outlook Incentive for companies to share data… Sharing mechanism: EPC Discovery standard Social Access Controller / Friends and Things We are currentlyworking on: Adaptingother standards to the Web (E.g., TDT) Creating a mashupplatform for common EPC applications. 18 IoT 2010 Dominique Guinard
23. Thanks a lot for your attention EPCIS REST-adapter is Open Source (LGPL) Module of the Fosstrak EPCIS Contact: Dominique Guinard www.guinard.org 19 www.webofthings.com/rfid
Editor's Notes
Benchmarkedlocally (one hop away)Can beexplainedmainly by the processing time for SOAP on the client-side vs simple JSON/jDOMunmarshalling