OCARI: Optimization of Communication for Ad hoc Reliable Industrial networks

Tuan Dang* PhD Member IEEE, Catherine Devic* et al**

*EDF (Electricit De France) R&D - STEP Department Control Systems & Information Technologies Group **Consortium OCARI: EDF, DCNS, One RF Technology, LIMOS, LATTIS, LRI, INRIA 6, quai Watier 78401 Chatou Cedex FRANCE tuan.dang@edf.fr, catherine.devic@edf.fr, http://ocari.lri.fr
Abstract In this paper we present an industrial development of a wireless sensors network technology called OCARITM. It targets applications in harsh environments in power plants and in warships. OCARI is a radio communication technology that supports mesh topology and power-aware ad hoc routing protocol aiming at maximizing the network lifetime. It is based on IEEE 802.15.4 PHY layer with full deterministic MAC layer for time-constrained communication. During the non timeconstrained communication period, its ad hoc routing strategy uses an energy-aware OLSR proactive protocol. OCARI application layer is based on ZigBee APS and APL primitives and profiles to provide a maximum compatibility with ZigBee applications. To fully assess this technology, extensive tests will be done in industrial facility at EDF R&D as well as at DCNS. Our objective is then to promote this specification as an open standard of industrial wireless technology. Index Terms Wireless Sensors Network, Ad hoc Network, Electromagnetic Compatibility, Mobility, Battery Autonomy, Interference model, BER, SINR, Medium Access Control, Routing strategies, Application Architecture, Middleware, OPC, IEEE 802.15.4, ZigBee, WINA, ISA100, WirelessHART, Power Plants, Warships.

I. INTRODUCTION Wireless communication represents a major industrial stake in the next coming years. It offers numerous usages and helps industry save operating costs as well as improving the operational efficiency. In the recent years, WiFi (IEEE 802.11-WLANs) and Bluetooth technologies (IEEE 802.15WPANs) have known tremendous development and have penetrated the Small Office and Home Office (SOHO) as well as Large Enterprise Office. These general public wireless technologies may find their limited usage in industrial installations because of harsh environments, electromagnetic compatibility and interference issues, safety and IT security constraints and battery autonomy. Some of these issues have been addressed by addenda to existing standards. For example, IEEE 802.11i addresses the IT security, IEEE 802.11e deals with WiFi Multimedia Quality of Service (WMM QoS) and WMM Power Save. Although these specifications target consumer market and do not take into account industrial needs in constrained environment. Application of wireless sensors network technology in industrial environment such as in power plants or in warships typically requires the following characteristics:

Network topology flexibility: self-organizing, autoconfigurable network topology and transparency for application layer, Network scalability: ability to deal with large network topology and large density of network nodes, Low power consumption along with power management capability to maximize battery autonomy, Support of energy-aware routing protocol, Protocol stack with deterministic medium access methods, Robust radio transmission (low bit error rate, BER [22]) regarding electromagnetic interferences (as measured as signal-to-interference-plus-noise ratio, SINR [23] [24]), Radio transmission technique that is compatible with electromagnetic constraints (e.g.: TEMPEST military standard), Support of sink mobility (e.g.: a mobile user which collects data via a Personal Digital Assistant (PDA) from a sensors network), Support of authentication of network node and antiintrusion (to the network) mechanisms. In response to these industrial needs and challenges, there are some working groups such as the Wireless Industrial Networking Alliance (WINA), the ZigBee Alliance, WirelessHART [25] from HART Communication Foundation (HCF) and ISA100 who tried to define and establish industrial wireless technology standards for different application domains. Currently, only ZigBee has commercially available products as this Alliance was formed very soon in the end of 2004. WirelessHART compliant products are expected at the end of 2008. These specifications are all based on IEEE 802.15.4 which provides a good foundation for building ad hoc mesh network. However, IEEE 802.15.4 does not specify a standard way or algorithm to optimize power consumption in the MAC layer along with a corresponding routing schema. It is up to the application designer to elaborate his own strategy. Full deterministic MAC layer [11] is also absent from this standard. In this paper, we propose to describe the project in which we try to develop a wireless sensor communication module running an industrial ad hoc mesh networking protocol called OCARITM. It is based on IEEE 802.15.4 PHY layer and has autonomous behaviour: tolerance to topology changes (successful packet delivery in the face of node mobility and

1-4244-9701-0/06/$20.00 2008 IEEE.

failure). OCARI satisfies the following criteria in harsh environment: Deterministic MAC layer for time-constrained communication, Optimized energy consumption routing strategy for maximum network lifetime within the non timeconstrained communication period, Support of human walking speed mobility for some particular network nodes (sinks), The project is funded by the French National Research Agency (Agence Nationale de la Recherche) and industrial partners. It started at the end of 2006 and gathers partners (see [1] for more details) from industries (EDF/project leader, DCNS and One RF Technology) as well as university labs and research institutes (LIMOS, LATTIS, LRI and INRIA). EDF and DCNS provide requirements and use cases in power industry and warship applications. One RF Technology, a high tech company in wireless communication will industrialize the prototype. LIMOS and LATTIS university laboratories develop and implement OCARI medium access methods. INRIA and LRI research institutes work on optimized energy consumption routing strategy based on OLSR proactive protocol [2][3]. This paper is organized as follows. Section 2 presents a review of existing wireless communication standards which may be used in industrial environments. Section 3 shows the technical aspects of OCARI and details the technological choices. Finally, future works are drawn in Section 4. II. REVIEW OF EXISTING INDUSTRIAL WIRELESS COMMUNICATION STANDARDS Wireless mesh networking has emerged in the recent years as a promising design paradigm for next generation wireless communication networks with the very interesting characteristics such as self-organizing and auto-configurable topology, and ad hoc routing concept. These properties promise substantial benefices in terms of operating and maintenance costs of the communication infrastructure in industrial installations. They also ease the development of killer applications such as Condition Monitoring or Condition Based Maintenance (CBM) that requires flexible and cost effective sensors network. Wireless technologies help plant engineers achieve these objectives. However, most of existing general public wireless communication technologies does not take into account the industrial requirements. There exist proprietary radio communication technologies for industrial use such as, for example, WavenisTM, but we lose the benefits of interoperability (and thus cost) from multi-vendors solutions. Developing and promoting industrial wireless communication standards help industrial end users preserve the expected benefits of wireless technologies. We propose to review the state of the art of current industrial wireless networking standards. A. IEEE 802.15.4-2003 based ZigBee specifications
1-4244-9701-0/06/$20.00 2008 IEEE.

ZigBee is a Low-Rate Wireless Personal Area Network (LR-WPAN) standard for embedded communication system with very low power consumption. It proposes a lightweight1 protocol stack for applications which require low data rates (up to 250kbits/s) and low latency. ZigBee is designed to interconnect autonomous sensors and actuators to control units. Battery lifetimes last from a few months to many years as a result of a host of systems power-saving modes, batteryoptimized network parameters and application configurations. ZigBee is based on IEEE 802.15.4-2003 PHY (868MHz/915MHz or 2,4GHz) and MAC layers over which it specifies its network layer (NWK) and application layer (APL) (Fig. 1). The responsibilities of the ZigBee NWK layer include mechanisms used to join and leave a network, to apply security to frames and to route frames to their intended destinations. In addition, the discovery and maintenance of routes between devices devolve to the NWK layer. Also the discovery of one-hop neighbours and the storing of pertinent neighbour information are performed by the NWK layer. In a star topology, the network is controlled by one single device called the ZigBee coordinator. In mesh and tree topologies, the ZigBee coordinator is responsible for starting a new network, when appropriate, and assigning addresses to newly associated devices, but the network may be extended through the use of ZigBee routers. In tree networks, routers move data and control messages through the network using a hierarchical routing strategy. Tree networks may employ beacon-oriented2 communication as described in the IEEE 802.15.4-2003 specification. Concerning ZigBee routing strategy, it is a mixed mechanism composed of a simplified version of AODV [4] [7] and tree routing intended to extend the coverage of the network beyond the coverage of each network node. The ZigBee application layer consists of the APS sublayer, the ZDO (containing the ZDO management plane), and the manufacturer-defined Application Objects. The responsibilities of the APS sub-layer include maintaining tables for binding, which is the ability to match two devices together based on their services and their needs, and forwarding application messages between bound devices. The responsibilities of the ZDO include defining the role of the device within the network (ZigBee Coordinator, Router or End device), discovering devices on the network and determining which application services they provide, initiating and/or responding to binding requests and establishing a secure relationship between network devices. More details about NWK and APL may be found in [5]. IEEE 802.15.4 specifies two medium access methods: uncoordinated mode (unslotted CSMA-CA, without GTS) and coordinated mode (beacon mode) in which the coordinator (PAN coordinator) regularly sends beacons to synchronize the network nodes. In coordinated mode, the
Full implementation of the protocol stack takes less than 32Kbytes of memory version and up to 64Kbytes for the network coordinator which requires extra RAM for a node devices database and for transaction and pairing tables. 2 Since the new release of ZigBee specification in 2008, this feature is abandoned for saving space in the MAC layer.
1

PAN coordinator does not need to listen all the time to the communication channel. But ZigBee has chosen the uncoordinated mode that requires the ZigBee coordinator to listen permanently to the channel, and thus wastes the coordinator battery. ZigBee does allow however a very low power consumption for the end devices in doze mode (lower than 10A), and let them switch to normal operating mode in less than 300s.
Application (APL) Layer Application Framework
ZDO Public Interfaces (End manufacturer defined) Application Object 240 ZigBee
Endpoint 240 APSDE-SAP

B. IEEE 802.15.4-2006 based ISA100.11a specification ISA100.11a is part of ISA100, a family of standards of wireless systems for industrial automation, which results from converging efforts of defining industrial wireless standards from different organizations and alliances such as WINA, NCCR-MICS, NSF-Program on Sensors and Sensor Networks and HCF, etc. ISA100.11a Working Group3 aims at defining all specifications including security and management; for wireless devices serving application classes 1 through 5 (Fig. 2) for fixed, portable and moving devices. The projects application focus will address performance needs for periodic monitoring and process control where latencies on the order of 100 ms can be tolerated with optional behaviour for shorter latency. The first release of the standard is expected at the fourth quarter of 2008. This review is based on published presentations at different webinars and on current works from the ISA100.11a WG. Category Safety
Class / Application Class 0: Emergency action Description Always critical

...

(End manufacturer defined ) Application Object 1

Endpoint 1 APSDE-SAP

ZigBee Device Object (ZDO)

Endpoint 0 APSDE-SAP

APSMESAP NLMESAP

Security Service Provider

APS Security Management NLDE-SAP

APS Message Broker

Reflector Management NLME-SAP

Network (NWK) Layer

Security Management MLDE-SAP Message Broker Routing Management Network Management MLME -SAP

IEEE 802.15.4

Medium Access Control (MAC) Layer

PD-SAP 2.4 GHz Radio PLME-SAP

Physical (PHY) Layer

868/915 MHz Radio

Fig. 1. ZigBee stack architecture [5]. Although these characteristics of ZigBee, this standard does not satisfy the very constrained battery autonomy of the wireless sensors networks in application such as environmental monitoring in large industrial facility in power plants. Indeed, as ZigBee does not retain coordinated mode, only ZigBee End Device (IEEE 802.15.4 Reduce Function Device) can be put to doze mode, ZigBee Routers and Coordinators need to be always awakened (active mode) in order to listen to the communication channel. Moreover, another limitation of ZigBee is that it does not directly support device mobility: AODV only discovers the route on demand and the only used QoS is the instantaneous radio link, thus route repair is done on error. The complete route discovery process can take a significant time (up to 10 seconds). This is not useable in unstable topology in which network nodes regularly move. In ZigBee 2006 specification, when the link to the parent node failed, a re-association is required and a new network address is attributed to the concerned child node depending on its position in the network tree. But this does not work for the sleeping End Devices which did not receive the broadcast message signalling the new network address renumbering. This limitation was removed by the ZigBee Pro specification since its release in January 2008 [6]: the network nodes keep their existing address; new routes have to be rediscovered. In spite of these properties, ZigBee does not offer support for sink mobility [8] in which data collector points travel through the nodes of a wireless sensor network.
1-4244-9701-0/06/$20.00 2008 IEEE.

ZDO Management Plane

Application Support Sublayer (APS)

Usually non-critical

Control

Human in the loop NOTE: Batch levels* 3 & 4 could be class 2, class 1 or even class 0, depending on function *Batch levels as defined by ISA S88; where L3 = unit and L4 = process cell Short-term operational consequence (e.g., event-based maintenance) No immediate operational consequence (e.g., history collection, sequence-of-events, preventive maintenance)

Class 4: Alerting

Monitoring

Class 5: Logging and downloading / uploading

Fig. 2. ISA100 usage classes [9]. ISA100.11a key features aims at responding to the following requirements:

Composed of industrial end users and technology providers.

Importance of message timeliness increases

Class 1: Closed loop regulatory control Class 2: Closed loop supervisory control Class 3: Open loop control

Often critical

The ability to serve process industry applications without excluding factory automation, In-plant and near-plant use, Technology to address class 1 (non-critical) to class 5 applications such as monitoring, A single application layer providing both native and tunnelling protocol capability for broad usability, Addressing only 2.4 GHz IEEE 802.15.4-2006 physical layer devices, A comprehensive coexistence strategy with channel hopping to support coexistence (with IEEE 802.11) and increase reliability, Simple, flexible, and scalable security addressing major industrial threats leveraging IEEE 802.15.4-2006 security, Field device meshing and star capability. ISA100.11a stack architecture (Fig. 3) has more layers than the ZigBee one. It lets the Device Management Application Process (DMAP) directly access (using Service Access Point, SAP) to the Data Link Layer, the Network Layer, the Transport Layer and the Application Sub-Layer in order to manage the device and its communication services. The DMAP is a special type of user application process (UAP) that provides a basis for building system management configuration application and communications monitoring application. Either a distributed or centralized system manager is supported in ISA100.11a.

ISA100.11a

Two main classes of devices are defined in ISA100.11a: Field Devices and Backbone Devices. Field Device class can have devices with (i.e.: IEEE 802.15.4 Full Function Device) and without routing capability (i.e.: IEEE 802.15.4 Reduce Function Device). Handheld Device is considered as a nonrouting field device. The typical mode of operation of a SP100.11a handheld device is to attach to a full function device and to communicate data or monitor network traffic. Roaming of handheld device is not supported by ISA100.11a. Backbone devices are full function devices which have mains power source (continuously powered); whereas field devices have limited battery power (without routing capability) or moderate power (with routing capability). Network time and time synchronization information for devices on the network are provided by the system manager, a particular backbone device, which act as clock source. Routing in ISA100.11a is based on graph using a directed list of links that connect devices. The links associated with each graph are configured by the system management function on a centralized or decentralized basis. A single network instance may have multiple graphs, some of which may overlap. Each device may have multiple graphs going through it, even to the same neighbours. Each device data link layer service has one route associated with it. It is difficult to make some critical analysis of this evolving specification. But one may wonder the technical difficulties to implement the full stack architecture on low cost hardware. In term of software architecture, ISA100.11a WG has produced a relatively complete functional specification for system management that is almost absent from ZigBee standard. Coexistence with WiFi is also taken into account in ISA100.11a and that is really appreciated in industrial environment. Currently, there is no optimized routing strategy for maximizing the lifetime of field network. Before describing our OCARI project, lets summarize the important points of ISA100.11a and ZigBee specifications: Features supported PHY layer ZigBee IEEE 802.15.42003 with 868MHz/915MHz or 2,4GHz radio IEEE 802.15.42003 with a slow frequency hopping schema (Frequency agility in ZigBee-2007 initiated by the NWK Channel Manager) No deterministic access methods ISA100.11a IEEE 802.15.42006 with 2,4GHz radio only IEEE 802.15.42006 with an extension shim for frequency hopping and slotted hopping No deterministic access methods

SP100.11a MAC Extension Shim

MAC layer
IEEE 802.15.4-2006

Fig. 3. ISA100.11a stack architecture [9]. ISA100.11a address failed communications using frequency hopping and slotted hopping architecture by adding a MAC Extension Shim [10] to IEEE 802.15.4 MAC; whereas a slow frequency hopping schema (frequency agility) is adopted in ZigBee-2007 MAC, which is designed primarily for operation in a fixed channel network.
1-4244-9701-0/06/$20.00 2008 IEEE.

Network topology Network scalability

Tree, Star, Mesh Up to 65536 nodes per network group and up to 65536 network groups (16-bit node address and 16-bit group address) or 64-bit extended network address

Star, Mesh 128-bit network layer address assigned by the system manager. These 128-bit addresses are hierarchical, with the upper 64 bits identifying a network and the lower 64 bits identifying a device Graph routing (link state routing) No energyaware routing strategy

Use cases analysis of the described industrial applications shows that in most cases, the network topology can be modeled as depicted in Fig. 4. OCARI End Device is a radio fixed network node (i.e. its position varies very little comparing to its initial location so that its radio link is always managed by the same cell coordinator). It is a Reduce Function Device as defined in IEEE 802.15.4 specification. OCARI Cell and Workshop Coordinators are Full Function Devices as specified in IEEE 802.15.4. They are fixed device in the infrastructure and are equivalent to ZigBee Coordinator. The functions of Cell Coordinator consist of: Coordinating the intra-cell network nodes using a star topology, and Routing data packets in push mode from end device network nodes (i.e. sensors in our industrial applications) to the Workshop Coordinator per Workshop domain. Tree routing [12] [13] is used in time-constrained period and an energy-aware OLSR [14] is used otherwise between Cell Coordinators. Workshop domain is a permissive volume (delimited by a threshold of the BER, the SINR or the RSSI [15]) to electromagnetic wave that is covered by a unique Workshop Coordinator network node.
End device (RFD)

Network routing strategy

Mixed mechanism composed of AODV and tree routing No energyaware routing strategy

Table 1. ZigBee and ISA100.11a network characteristics. III. OCARI SPECIFICATION Regarding the above features of ZigBee and ISA100.11a, we have focused our work on improving ZigBee standard by developing a complementary industrial specification called OCARI rather than creating a new one from scratch. It aims at responding to the following requirements which are particularly important in power generation industry and in warship construction and maintenance: Support of deterministic MAC layer as much as possible (at least inside a cell) for time-constrained communication, Support of optimized energy consumption routing strategy in order to maximize the network lifetime within the non time-constrained communication period, Autonomous behaviour for unattended operation, Support of Electronic Device Description Language (EDDL-IEC61804) and HART communication protocol. The development of OCARI targets the following industrial applications: Real time centralized supervision of personal radiation dose in nuclear power plant, Condition Based Maintenance of mechanical and electrical components in power plant as well as in warship, Environmental monitoring in and around power plant, Structure monitoring of hydro-electric facilities. In the following paragraphs, we will describe the main specification points of OCARI. A. OCARI Network Topology
1-4244-9701-0/06/$20.00 2008 IEEE.

Time server

Industrial facility backbone

Cell Coordinator

Sink node Workshop Coordinator Sink node

Cell Coordinator

Workshop

Sink path

Sink node Cell Coordinator

Fig. 4. OCARI Network Topology Workshop Coordinator is a gateway (even in polling mode used by most of SCADA applications) between the wireless sensors network resided in a Workshop domain and the industrial facility backbone. As depicted in Fig. 4, Sink node is a mobile network node which usually represents a patrolman/maintenance operator, equipped with PDA, collecting data from sensors inside a

cell. Sink leaves the cell when it finishes to acquire data (in polling mode). Time server is a particular network node which is used for clocks synchronization in the whole Workshop domain. For a precision clock synchronization, IEEE-1588/IEC 61588-2004 protocol [16] [17] (Precision Time Protocol, PTP) is used. B. OCARI PHY and MAC layers Previous studies [18] [19] and our field tests show that IEEE 802.15.4 PHY is very robust as depicted by the following figure (Fig. 5):

using SERENA algorithm [20] for relay nodes (among Cell Coordinators) is thus limited inside this perimeter. C. OCARI Platform Prototype In order to evaluate, verify and validate the OCARI specification, we define the following platform (Fig. 7) in which we will implement different communication layers. The PHY and MAC layers will be implemented inside the same communication controller module (One-RF B2400MCTiny), designed by our partner, One RF Technology.

IEE

Fig. 5. Comparison of different IEEE PHY layers [18] Based on the robustness of IEEE 802.15.4 PHY 2.4 GHz, we decided to adopt it for the OCARI specification. However, as stated earlier, IEEE 802.15.4 MAC layer does not completely satisfy our requirements. Our consortium is developing a derived MAC layer [12] [13] that offers different access methods to the medium within a global cycle as depicted by the following figure (Fig. 6).
Reserved for routing use Reserved for routing use
PHY + MAC

S Y N C

Collision-Free Activity Scheduling constrained by a hierarchical tree

Deterministic MAC period

IEE E8 02 .15 .4

IEE E8 02 .11 b

E8

02

.15 .1

UART

Serial interface (RS232, USB) Analog and Digital IO

NWK + Routi ng + APS Control PIN

HART Protocol (4-20mA)

Sensors (HART compliant)

Fig. 7. OCARI platform prototype. OCARI routing strategy and the ZigBee NWK and APS will be implemented on another module, which is a PC computer platform for ease testing and debugging. The final architecture will be put on the same micro-controller by our partner, One RF Technology. D. OCARI Application Architecture

Free Activity (beacon mode: slotted CSMA-CA)

Optimized network lifetime energy-aware OLSR

T0 T1 T1

T2 T2 Global Cycle

T3

Fig. 6. OCARI global cycle. The ratio of (T2-T1)/(T3-T2) depends on the tradeoff between time-constrained communication period and the concern of energy saving. In OCARI specification, the interference model is based on two times the estimated radio range. Neighborhood search
1-4244-9701-0/06/$20.00 2008 IEEE.

To achieve a seamless integration of wireless sensors network (WSN) into real world applications in industrial information systems, we need to develop and provide an application architecture that can interoperate with existing industrial standards. The architecture depicted in Fig. 8 aims at responding to such requirement while supporting the state of the art in industrial information technology. The role of a WSN oriented middleware is to provide standard and homogenous services to user applications. It also contributes to the energy saving of the WSN by

implementing a centralized and optimized management of network resources [21]. Moreover, it serves as a gateway between different user applications and different Workshop Coordinators, which orchestrate the attached cells. The choice of a software bus standard such as OPC-DA and the upcoming version OPC-UA allows us to provide the compatibility with EDDL for asset management and for SCADA application.

Workshop Coordinator

Workshop Coordinator

WSN oriented middleware

OCARI protocol Other protocol

Dynamic Communication Drivers Manager RTDB

Software Bus (Publish/Subscribe) OPC-DA OPC-UA OPC-UA OPC-UA

SCADA

CBM

Asset Management Network Monitoring

Fig. 8. OCARI application architecture. IV. FUTURE WORKS In the next steps of our project, we are working on the implementation and the development of different components of our specification. We believe that OCARI will fill some gaps, as stated earlier, in ZigBee while trying to be compatible with ZigBee APS and APL layers. In this way, we can preserve existing efforts and investments on application development already realized using ZigBee technology. V. ACKNOWLEDGMENT This work is done in the Information & Communication Technology (ICT) Program of EDF R&D and is partly funded by the French National Research Agency. Many thanks to Yves Mayadoux and the OCARI consortium members, in particular Marc-Henri Bertin and Prof. Thierry Val for their valuable suggestions. VI. REFERENCES [1]. OCARITM Consortium Web site: http://ocari.lri.fr [2]. RFC3626, http://www.ietf.org/rfc/rfc3626.txt.
1-4244-9701-0/06/$20.00 2008 IEEE.

[3]. V. Gauthier, R. de Rasse, M. Marot, M. Becker, On a Comparison of four Ad-hoc Routing Protocols when taking into account the Radio Interferences., www.comp.brad.ac.uk/het-net/HETNETs05/ReadCamera05/P42.pdf [4]. Charles E. Perkins, Elizabeth M. Belding-Royer, and Samir Das. Ad hoc On demand Distance Vector (AODV) Routing, IETF RFC 3561. [5]. ZigBee Specification-Document 053474r17, http://www.zigbee.org. [6]. ZigBee-PRO Stack Profile, ZigBee Document 074855r05, January 2008. [7]. Andrew Wheeler, Commercial Applications of Wireless Sensor Networks Using ZigBee, IEEE Communications Magazine, April 2007. [8]. Javier Garca Castao, Algorithms and Protocols Enhancing Mobility Support for Wireless Sensor Networks Based on Bluetooth and ZigBee, Mlardalen University Press Dissertations, No. 32, September 2006. [9]. ISA100.11a Release 1 Status, October 2007, www.isa.org/source/ISA100.11a_Release1_Status.ppt [10]. Melanie Swiderek/ISA100 Committee, ISA100.11a Functional Description, version 2007-0718. [11]. Adrien Van Den Bossche, Proposition dune nouvelle mthode daccs dterministe pour un rseau personnel sans fil fortes contraintes temporelles, Thse de lUniversit Toulouse le Mirail - Toulouse II (2007-0706), Thierry VAL (Dir.). [12]. G. Chalhoub, A. Guitton, M. Misson, MAC specifications for a WPAN allowing both energy saving and guaranted delay - Part A: MACARI: a synchronized tree-based MAC protocol, IFIP 2008 Conference on Wireless Sensor and Actor Networks. [13]. E. Livolant, A Van den Bossche, T.Val, MAC specifications for a WPAN allowing both energy saving and guaranted delay - Part B: Optimisation of the intra cellular exchanges for MACARI, IFIP 2008 Conference on Wireless Sensor and Actor Networks. [14]. S. Mahfoudh, P. Minet, An energy efficient routing based on OLSR in wireless ad hoc and sensor networks, PAEWN 2008, IEEE International Workshop on Performance Analysis and Enhancement of Wireless Networks, Ginowan, Japan, March 2008. [15]. Abdalkarim Awad, Thorsten Frunzke, Falko Dressler, Adaptive Distance Estimation and Localization in WSN using RSSI Measures, 10th Euromicro Conference on Digital System Design Architectures, Methods and Tools (DSD 2007), pp. 471-478. [16]. John C. Eidson et al, IEEE-1588 Standard for a precision clock synchronization protocol for networked measurement and control systems, 34th Annual Precise Time and Time Interval (PTTI) Meeting [17]. Precision clock synchronization protocol for networked measurement and control systems, standard IEC 615882004. [18]. Bob Heile, ZigBee Alliance Tutorial, SeptemberNovember 2005, http://www.zigbee.org.

[19]. Ed Callaway, Member of the Technical Staff, Motorola Labs, PHY Proposal for the Low Rate 802.15.4 Standard, July 2001, http://grouper.ieee.org/groups/802/15/pub/2001/Jul01/0 1229r1P802-15_TG4-Motorola-PHY-Proposal.ppt. [20]. S. Mahfoudh, P. Minet, Performance evaluation of the SERENA algorithm to SchEdule RoutEr Nodes Activity in wireless ad hoc and sensor networks, AINA 2008, IEEE 22nd International Conference on Advanced Information Networking and Applications, Ginowan, Japan, March 2008. [21]. S. Hadim, N. Mohamed, Middleware Challenges and Approaches for Wireless Sensor Networks, IEEE Distributed Systems Online, vol. 7, no.3, 2006, art. no. 0603-o3001. [22]. Gary Breed, Bit Error Rate: Fundamental Concepts and Measurement Issues, High Frequency Electronics, January 2003. [23]. Daniel R. Jeske, Ashwin Sampath, Signal-tointerference-plus-noise ratio estimation for wireless communication systems: Methods and analysis, Wiley Periodicals, Inc. Naval Research Logistics, Volume 51, Issue 5, Pages 720 740, 2004. [24]. Ernesto Zimmermann, Assessment of Radio-link technologies, IST-2003-507581 WINNER, D2.3 ver. 1.0. [25]. http://www.hartcomm2.org/hart_protocol/wireless_hart/ wireless_hart_main.html, February 2008.

1-4244-9701-0/06/$20.00 2008 IEEE.