each other regarding time, space, and synchronization
(Eugster et al., 2003). With these communication de-
coupling nodes of a WSN operate as autonomously as
possible. It suggests that a system following the pub-
lish/subscribe paradigm fits the nature of WSN com-
munications. A publish/subscribed based event mes-
sage management system for WSNs has to show that
it is possible to have a publish/subscribe paradigm
based message system in WSN on the one hand but
also to combine real-time functionality to a WSN
message system on the other hand. So far, as we
know, only few research results are published con-
cerning real-time publish/subscribe in WSNs, while
publish/subscribe itself next to real-time, and data dis-
tribution for WSN is discussed widely
In a WSN, sensor nodes placed randomly in the
environment detect events like for e.g. a sharp rise of
temperature. Actor nodes in the network react on an
alert message by for e.g. closing a valve or activating
an alarm. Gateway nodes distribute messages send by
sensor nodes to monitor equipment placed outside the
WSN. Communication overhead in such a scenario
will reduce the total run-time of the WSN as power
consumption is the mean problem. In the outlined
publish/subscribe driven concept actors (maybe also
the gatewayas required) tell the sensor nodes that they
are interested in a certain event and that the message
should be delivered in a certain time. So the actor
nodes transmit a subscription to sensor nodes, whom
notify the subscribers (actor nodes) within the given
time period if an event is detected and the event ful-
fills the subscription.
actor
sensor
Gateway
Type A sensor / actor
Type B sensor / actor
wireless connection
4
5
6
7
8
9
5ms
9ms
2ms
3ms
4ms
subscribe
(RT 8ms)
subscribe
(RT 4ms)
subscribe
(RT 4ms)
publication
(avg 7ms)
Event A
Figure 3: Example of efficient message communication.
Figure 3 shows a typical scenario of a WSN with
4 sensor nodes and 2 actor nodes. In the start phase
ACTOR NODE 9 (right side) sends a subscribe request
message to all reachable nodes. In this scenario only
SENSOR NODE 5 is reachable that receives the re-
quest. As SENSOR NODE 5 only monitors events of
type A and ACTOR NODE 9 requests to get informed
about type B events the sensor node only proves that
the deliverable time is lower than the requested max-
imum deliverable time. In this case the deliverable
time is in average 4 ms and the subscriber needs a no-
tification within 8 ms. Therefore, SENSOR NODE 5
will forward the subscription request to all its neigh-
bors, here nodes 8, 6, 4, AND 7. NODE 4 is an actor
node and will neglect the request, next to SENSOR
NODE 6 which can calculate that the real-time con-
straint can never be fulfilled as the deliverable time
on the route back to the requester will take too long.
Only SENSOR NODE 8 and 7 can notify the request-
ing node in-time. Both sensor nodes monitor events
of Type A which fulfills the received subscription re-
quest and will store the subscription locally. Since
the remaining deliverable time is very low and cal-
culation and notification packet calculation have to
be considered, the sensor nodes will not try to for-
ward the request to other neighbors. The presented
concept for efficient message transportation by a real-
time enabled publish/subscribe system can be used to
distribute trust values. Therefore, the calculated trust
value represents a parameter for a subscription rule.
If this rule is fulfilled all subscribed nodes with one-
hop distance will get informed. The publish/subscribe
system is flexible in such that if a connection to a node
is disturbed a subscription could be deleted or if a new
connection is established a new subscription could be
registered. For further details have a look at (Stelte,
2011).
Next we will show that it is possible to use the
Byzantine decision algorithm to find a common ma-
jority decision based on reported trust values.
4 BYZANTINE DECISION
The name Byzantine Attack is based on the Byzan-
tine Generals’ Problem which is a generalized version
of the famous Two Armies Problem.The Byzantine
Generals’ Problem was first introduced by Lamport
et al. in (Lamport et al., 1982). It describes a decision
problem where one Commander in Chief and n − 1
generals communicate with each other. The commu-
nication between two persons is handled over a syn-
chronous and non error-prone communication chan-
nel. The commander informs his generals the deci-
sion to attack or to retreat. The action is success-
ful only if all generals carry out the instruction of
the commander. In this scenario it is possible that at
least one person (general or commander) tries to tam-
per. Goal of a Byzantine protocol is to let the honest
generals come to a collective decision (under the as-
SECRYPT 2011 - International Conference on Security and Cryptography
398