This document is a companion document of “D2.2.2 ? The Final e-SENSE System Architecture Part A” and aims at providing recommended protocol stack instantiations of the e-SENSE system architecture.
It describes three protocol stack instantiations of the e-SENSE system, which cover all main envisioned e-SENSE application scenarios. The protocol stack instantiations are based on selected protocol elements that have been developed in WP3 and WP4 and realise main service functions of the e-SENSE system architecture.
The first protocol stack instantiation is recommended for wireless sensor network systems in body sensor network applications. Such networks usually form simple topologies and do not require real routing support beyond 2 communication hops. The protocol stack needs to support potentially high QoS requirements and ensure proper operation of many of such systems in spatial proximity in dense environments.
The second protocol stack instantiation is recommended for wireless sensor network systems deployed in environmental or object sensor network applications. It is particularly suitable for applications that require localisation and positioning, and thus have some form of geographic notion. The protocol stack supports multi-hop communication (of typically up to 10+ hops) and limited mobility of sensor nodes within the WSN system and is further optimised for in-network communication.
The third protocol stack instantiation is recommended for wireless sensor network systems deployed in environmental or object sensor network applications. It is particular suitable for converge-cast applications, which do not require explicit localisation support. The protocol stack supports multi-hop communication of typically up to 10 hops or more and enables interest dissemination and converge-cast within the multi-hop network. Mobility of both sensor nodes as well as the sinks is supported as well as energy-efficient operation by enabling load-sharing among sensor nodes to prolong the lifetime of the network
A detailed specification of each utilised protocol element is provided in the ANNEX of this document. This includes a brief description of the protocol element operation and specific features, service invocations and required protocol stack interactions, detailed protocol state machines and message formats. The reader is also guided to further details on the protocol elements and their performance by appropriate references to WP3 and WP4 deliverables.