Limits...
Using LOTOS for Formalizing Wireless Sensor Network Applications

View Article: PubMed Central

ABSTRACT

The number of wireless sensor network (WSN) applications is rapidly increasing and becoming an integral part of sensor nodes. These applications have been widely developed on TinyOS operating system using the nesC programming language. However, due to the tight integration to physical world, limited node power and resources (CPU and memory) and complexity of combining components into an application, to build such applications is not a trivial task. In this context, we present an approach for treating with this complexity adopting a formal description technique, namely LOTOS, for formalising the WSN applications ‘behaviour. The formalisation has three main benefits: better understanding on how the application actually works, checking of desired properties of the application's behaviour, and simulation facilities. In order to illustrate the proposed approach, we apply it to two nesC traditional applications, namely BLink and Sense.

No MeSH data available.


nesC interface in LOTOS
© Copyright Policy
Related In: Results  -  Collection

License
getmorefigures.php?uid=PMC3814862&req=5

f1-sensors-07-01447: nesC interface in LOTOS

Mentions: As mentioned in Section 2.2, each nesC interface has a set of functions (commands and events). As we are only interested in the module interactions or temporal ordering of events (not in their functionality), these functions are defined as LOTOS operations of an abstract data type (ADT) defined for each interface. In this way, the nesC interface <interface-name> leads to the definition of the LOTOS ADT “I”<interface-name>. The command <command-name> and event <event-name> are defined as type operations “c_”<command-name> and “e_”<event-name>, respectively. In order to illustrate this approach, the interface SendMsg is presented in Figure 1.


Using LOTOS for Formalizing Wireless Sensor Network Applications
nesC interface in LOTOS
© Copyright Policy
Related In: Results  -  Collection

License
Show All Figures
getmorefigures.php?uid=PMC3814862&req=5

f1-sensors-07-01447: nesC interface in LOTOS
Mentions: As mentioned in Section 2.2, each nesC interface has a set of functions (commands and events). As we are only interested in the module interactions or temporal ordering of events (not in their functionality), these functions are defined as LOTOS operations of an abstract data type (ADT) defined for each interface. In this way, the nesC interface <interface-name> leads to the definition of the LOTOS ADT “I”<interface-name>. The command <command-name> and event <event-name> are defined as type operations “c_”<command-name> and “e_”<event-name>, respectively. In order to illustrate this approach, the interface SendMsg is presented in Figure 1.

View Article: PubMed Central

ABSTRACT

The number of wireless sensor network (WSN) applications is rapidly increasing and becoming an integral part of sensor nodes. These applications have been widely developed on TinyOS operating system using the nesC programming language. However, due to the tight integration to physical world, limited node power and resources (CPU and memory) and complexity of combining components into an application, to build such applications is not a trivial task. In this context, we present an approach for treating with this complexity adopting a formal description technique, namely LOTOS, for formalising the WSN applications &lsquo;behaviour. The formalisation has three main benefits: better understanding on how the application actually works, checking of desired properties of the application's behaviour, and simulation facilities. In order to illustrate the proposed approach, we apply it to two nesC traditional applications, namely BLink and Sense.

No MeSH data available.