Smart Service Proxy provides direct access to - linked sensor data and linked sensor-related data, - aggregation of such data based on the real thing they are associated to

1. Semantic-Service Provisioning for the Internet of Things using Future Internet Research by Experimentation www.spitfire-project.eu
Smart Service Proxy
Oliver Kleine, Henning Hasemann, Alexander
Kroeller

2. Initial situation
 Diverse network types (Internet (www), WSN)
 Diverse protocol standards
Proprietary
communication

3. Target situation
HTTP/TCP endpoints
in WSNs not possible
due to resource constraints!

4. Semantic Entities

5. Semantic Entities

6. SE types: Service-Level SE

7. SLSE Construction

8. Se Types: In-Network SE

9. INSE Construction

10. The CoAP protocol
 IETF-draft (developed by CoRE working group)
 Lightweight alternative to HTTP
 GET/POST/PUT/DELETE for RESTful service provisioning
 Optional transport reliability
 Some main features (from draft-ietf-coap-07):
 UDP-binding with optional reliability
 Supporting unicast and multicast messages
 Asynchronous message exchanges
 Low Header-Overhead
 URI and content-type support
 Simple proxy and caching capabilities
 Stateless HTTP mapping

11. CoAP devices
 CoAP on Sensor Nodes
 RESTful webservices
– Current values of sensors
– Semantic self-descriptions (from WP 2)
 Accessable by any CoAP-Client from anywhere
 CoAP-Client for JAVA and Android
 Enable CoAP on a wide range of potential client devices
 Smart Service Proxy
 Caching of current values and self-descriptions
 Enables HTTP access to CoAP-services

12. The Smart Service Proxy
 Developed in cooperation between WP1 and WP3
 Border device WSN <-> Internet
 HTTP/TCP endpoint from internet perspective
 CoAP/UDP endpoint from WSN perspective
 Several Backends
 CoAP Backend (Translation HTTP <-> CoAP)
 SLSE Backend
 Any other backend

13. SSP: Network environment

14. SSP: More detailed insight