1 / 10

IoT /FI Architecture – Some Thoughts

IoT /FI Architecture – Some Thoughts. Stephan Haller, SAP Research. Breakout Session: Internet of Things and the Future Internet Panel on IoT /FI Architecture and Integration Future Internet Assembly May 17-19, 2011 Budapest, Hungary. Preamble. This…. …That?. OR. Device.

thane-sykes
Download Presentation

IoT /FI Architecture – Some Thoughts

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IoT/FI Architecture – SomeThoughts Stephan Haller, SAP Research Breakout Session: Internet of Things and the Future Internet Panel on IoT/FI Architecture and Integration Future Internet Assembly May 17-19, 2011 Budapest, Hungary

  2. Preamble This… …That? OR Device PhysicalEntity

  3. Issues etc. … Connectivity Interoperability Service-Enablement Scalability Internet of Things /FI Architecture Mobility Managability Heterogeneity Deployability

  4. Connectivity • IoTispartofthe (Future) Internet • So let‘suseIPv6andwe‘redone… • 6LowPANhasshownfeasibilityofusing IP in constrainedenvironments (e.g., WSAN) But… • IP not well suitedwherehard real-time isrequired (e.g., manufacturing, safetyalarms) Gateways continuetobenecessary • Enabletheconnectionofnoveltechnologies • Howeverthinktwicebeforeresortingtogatewayapproaches!

  5. Real-World / IoT Services Different characteristics, in particular for on-device services • Granularity • Geo-location • Streaming data • Resource constraints & performance requirements • Reliability, Quality of Information, Quality of Service • … are services interacting with the physical world Why Services? • Abstraction of underlying hardware and protocol zoo • Sensors, actuators, machines, … • Easy integration and mash-up enablement Technically speaking… • Not necessarily SOAP-based Web Services, rather REST • E.g., „Web of Things“ • Deployment units for on-device services based on OSGi

  6. REST • REST hasprovenefficientforconnectingIoTresources • Web of Things • CoAP (IETF) • EXI (W3C) • Also enterprisesoftwarecompaniesaremovingtowards REST • SAP Data Protocol

  7. „Quandarrive-t-il?“ Interoperability • Technical interoperabilityachievedthroughstandards • Network layer (OSI 3): IPv6 • Presentation/applicationlayers (OSI 6&7): REST • But semanticinteroperability?? „赤色です！“

  8. 2 TypesofSemanticInteroperability • Combiningdatafrom different sources • Linked Data seemslike a promising approach • Increasedpopularity • Similaridentificationschemes (URIs) • But whoprovidestherdftriples? • Findingappropriatedevices, resources, services, … • Identifiers, addressingandresolution • Discovery  Basic infrastructureservices

  9. Summary • Protocols: IPv6 as a basis, but gatewaysneededasfallbacksolutions • Servicesasabstractionlayertoenableintegration & mash-up • IoTserviceshavetheirowncharacteristics • Extensionsofexistingservicedescriptionlanguagesneeded • RESTfulapproachesfavorable • Not just technical, but also semanticinteroperabilityisneeded • Useoflinkeddata? • Basic infrastructureservices

  10. Stephan Haller Development Architect – Internet of ThingsSAP Research CEC Zürich SAP (Schweiz) AG Kreuzplatz 20 CH - 8008 Zürich T +41 58 871 78 45 F +41 58 871 78 12 E stephan.haller@sap.com Danke　ありがとう　Merci आभारी हुँ Grazie Gracias 　謝謝 　Obrigado ΕυχαριστώTack 감사합니다 Dankieشكرا Xin cảm ơn благодаря Köszi Terima kasihспасибо Mahalo ขอบคุณ Ngiyabona நன்றி תודה TeşekkürlerMulţumescمرسي Ndiyabulela DziękiGrazcha Thank you!

More Related