Smart Service Proxy

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

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

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

Semantic Entities

SE types: Service-Level SE

SLSE Construction

Se Types: In-Network SE

INSE Construction

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

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

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

SSP: Network environment

SSP: More detailed insight

Smart Service Proxy

by SPITFIRE_EU on Feb 22, 2012

Accessibility

Categories

Tags

Upload Details

Usage Rights

Statistics

Smart Service Proxy — Presentation Transcript