Architectural Design and Implementation of 2008 ZigBee Specification on TKNlS.4 Layer

Transcription

1 rchiecural Design and mplemenaion of 2008 ZigBee Specificaion on TKNlS.4 Layer nh-vu Dinh-Due Universiy of nfonnaion Technology Ho Chi Minh ciy, Vie Nam Ngoe-nLam HCMC Universiy of Technology Ho Chi Minh ciy, Vie Nam ngocan bsrac-tkn5.4 is a plaform-independen EEE MC implemenaion for he 2.1 release of he TinyOS operaing sysem. has araced srong ineres in indusry and academia and is now adoped by several oher wireless sandards, such as ZigBee, ETF 610wPN or WirelessHRT. n his paper, a 2008 specificaion ZigBee nework layer archiecure is presened. well-srucured archiecure of a complee nework layer based on TKN15.4 layer is designed. This archiecure is implemened for TinyOS. simple WSN applicaion is also developed as an illusraion of he proposed nework layer. Keywords-TinyOS, ZigBee proocol, nework layer archiecure, TKN15.4layer. NTRODUCTON For he pas few years, implemening WSN sysems has become an increasingly popular opic of research. WSNs have araced much aenion due o is grea poenial o be used in a wide range of applicaion, from miliary fields such as balefield surveillance o indusrial and consumer fields such as indusrial process monioring and conrol, machine healh monioring, and so on. ZigBee is a specificaion for a suie of high level communicaion proocols using small, low-power digial radios based on EEE 802.1S.4 sandard ha specifies he physical layer (PHY) and media access conrol (MC) for low-rae wireless personal area neworks (LR-WPNs). ZigBee appears as an opimal soluion o he need for a cos-effecive WSN sandard, which suppors low daa raes, long baery life and secure neworking. Thanks o developmen of ZigBee lliance wih over SO members worldwide, ZigBee has been specified as a full proocol sack. So far, here are many opions o deploy a WSN applicaion using ZigBee proocol ([2]). One of he mos common soluions is using Sysem-on-Chip echnology wih embedded ZigBee sack such as: CC2431 wih Z-sack from Texas nsrumens ([3]) or EM3S1EM3S7 wih Ember-Z-Ne PRO sack from Ember Corporaion ([4]). Besides, open-source ZigBee sack, such as Microchip sack from Microchip Technology nc., can also be used o experience ZigBee proocol ([S]). However, he bes way o build a flexible, general purpose WSN is using an OS and aking advanage of is developed nework layer. TinyOS sands as he mos flexible operaing sysem designed especially for WSN ([6], [7]). This is a widely-used open-source OS for low-power wireless devices, especially hose used in sensor neworks, ubiquious compuing, personal area neworks, smar buildings, and smar meers. pplicaions running on TinyOS are wrien in nesc, a dialec of he C language, opimized for he memory limis of sensor nodes ([8]). TinyOS is componen-based OS. This means ha TinyOS programs are buil ou of sofware componens, each of which implemens a specific ask or manages a specific piece of hardware. These componens are conneced o each oher using inerfaces. TinyOS iself provides inerfaces and componens for common absracions such as packe communicaion, rouing, sensing, acuaion and sorage. Therefore, developing applicaions in TinyOS is simply done by building modules and connecing hem ogeher or o exising modules. This feaure makes designing, implemening, repairing and improving TinyOS-based applicaions much easier and faser. Despie he grea poenial of combinaion beween TinyOS and ZigBee proocol, here is no well-srucured ZigBee nework layer for TinyOS 2.x so far. This paper inroduces a 2008 specificaion ZigBee nework layer archiecure for TinyOS. This well-srucured nework layer is based on TKNlS.4 layer ([]). n implemenaion of ZigBee layer is developed. The proposed archiecure can be used as a guideline for developing a flexible and reliable ZigBee nework layer.. RELTED WORKS ZigBee nework layer for TinyOS has been inroduced firs by a group called TinyOS ZigBee Working Group ([9]). The purpose of his group is o implemen and o mainain a sandard-complian implemenaion of he ZigBee 2007 specificaion. fer effors o implemen heir own EEE 802.1S.4 as well as ZigBee nework layer, hey finally inroduced Open-ZB - an open-source implemenaion of he EEE 802.1S.4/ZigBee proocol sack on TinyOS ([lo]). Their implemenaion provides some essenial nework services, such as associaion, synchronizaion or ree-rouing service. However, he design of heir implemenaion is no wellorganized. By using only one componen o implemen enire nework layer, he developers could no ake advanages of nesc benefis. lso, his design makes heir implemenaion inflexible. Logical and synax errors can also be found in he implemenaion. Moreover, his group has sopped updaing heir implemenaion since 2009, leaved i incomplee. Besides TinyOS ZigBee Working group, TinyOS has also organized TinyOS EEE 802.1S.4 Working Group o develop and mainain a plaform-independen, sandard-complian implemenaion of he EEE 802.1S which specifies MC and PHY layer. TinyOS call i TKNlS.4 layer ([11], S604-6/12/$3l EEE

2 [12]). Since 2011, TKNl5.4 layer has been compleely finished and fully suppored higher layer such as: ZigBee, S 100.lla, WirelessHRT. RCHTECTURL DESGN OF ZGBEE NETWORK LYER. Overview ojzigbee nework There are 3 device ypes in a ZigBee nework: J) ZigBee Coordinaor (ZC) iniiaes and configures he nework formaion. can ac as an EEE PN coordinaor or as a ZigBee rouer once he nework is formed. There is only one ZigBee coordinaor in a ZigBee nework. 2) ZigBee Rouer (ZR) acs as an EEE PN coordinaor. paricipaes in muli-hop rouing of packe afer associaing wih he ZC or wih an associaed ZR. 3) ZigBee End Device (ZED) does no paricipae in rouing. There is no device associaed wih a ZED. The ZigBee nework layer provides mechanisms for hese devices o join or leave a nework, and o roue frames o heir inended desinaions. n addiion, he discovery and mainenance of roues beween devices devolve o he nework layer. lso, he discovery of one-hop neighbors and he soring of perinen neighbor informaion are done a he nework layer. Securiy pplicaion layer.pplicaion objecs zoo ZigBee lliance use an exising daa link and physical layers ha were specified in he EEE sandard [14]. Low-rae, lowpower consumpion and low-cos wireless neworking are he key feaures of he EEE proocol, which ypically fi he requiremens of WSNs. ZigBee specificaion relies on he EEE daa link and physical layers, building up he nework and applicaion layer, hus defining a full proocol sack for LR-WPN. B. ZigBee nework layer To inerface wih he applicaion layer, he nework layer concepually includes wo service eniies: J) Nework Layer Daa Eniy (NLDE):provides he daa ransmission service for upper layer via is associaed Service ccess Poin - NLDE-SP. akes responsibiliy of generaing Nework level Proocol Daa Uni (NPDU), opology-specific rouing and securiy. More specifically, NLDE receives an pplicaion Proocol Daa Uni (PDU) from he applicaion layer and creae a new corresponding NPDU based on he implemened rouing and sercuriy algorihm. fer ha, i sends he NPDU o MC layer hrough MC Common Par Sub-Layer SP (MCPS-SP). 2) Nework Layer Managemen Eniy (NLME): provides he managemen service for upper layer via is Service ccess Poin - NLME-SP. Moreover, he NLME also uilizes he NLDE o achieve some of is managemen asks. also mainains a daabase of managed objecs known as he Nework nformaion Base - NB (Fig. 2)..ppllcaion Suppor Sub.Layer NLDE SP NLME-SP NLME NLDE NWK 16 MCPS-SP MLME-SP MC Sub-Layer Eniy Figure 2. The Zigebee nework layer Figure. The Zig8ee/EEE proocol sack n nex par, we will propose our archiecure for implemening his nework layer. C. Novel ZigBee nework layer archiecure ZigBee is bes described by referring o he 7-layer OS model for layered communicaion sysems. The lliance specifies he boom hree layers (physical, daa link, and nework) as well an pplicaion Suppor Sub-layer (PS) ha allows end developers o design cusom applicaions. These applicaions use services provided by he lower layers. Fig. 1 represens he layered archiecure of he ZigBee/EEE proocol sack. should be noed ha he ZigBee Because ZigBee nework layer has o provide many ypes of service, we decide o concepually spli i o several independen componens. Each of hem shall ake responsibiliy of a specific nework service. hus can be modified wihou any furher influence on oher componen

3 NLDE-SP NLME-SP NLDE RoueP NeworkJoiningC LpackeDispacherp J NibP NeworkLea NLME ving NeworkEsabliShing Neworksynchronizepil SarRouerP r MCPS-SP,,. MLME-SP " Figure 3. The novel Zigebee nework layer archiecure There are a lo of inernal as well as exernal inerfaces in nework layer defmed by ZigBee specificaion. n his paper, only funcionaliies, design and inerfaces of each componen ha are no specified in ZigBee specificaion 2008 [15], are presened. Oher inerfaces can be found m ZigBee specificaion Each device ype in a ZigBee nework (ZC, ZR and ZED) needs nework layer o provide differen services. Therefore, o limi he memory usage, we ry o separae implemenaion code beween ZC, ZR and ZED by using dummy componen and preprocessor direcives in configuraion o change componens' connecions. Design and funcionaliies of each componen are as follows: J) PackeDispacherP: This module is used o ranspor packes beween MC layer and Nework layer. When receving a packe from MC layer hrough MCPS-DT, i will read he packe's nework layer header, srip i, and send he remainder o he relevan nework componen. Moreover, his module is also responsible for packing NPDU when receving a packe from upper componen. ll packe processings are done by PackeUiliyP module. NeworkPacke NLME-SET NLME-RESET MLME-RESEl MLME-SET Figure 5. MC NibP module 3) NeworkEsablishingP: f ype of curren device is no end-device, his module will allow o esablish a new ZigBee nework hrough NLME-NETWORK-FORM non inerface. Moreover, coordinaor can also permi oher devices o join in curren nework hrough NLMP-PERMT-JONNG. Componen BeaconPayloadParserP is used o encapsulae or decompose beacon payload from a packe. Besides, if ype of curren device is end-device, i will use he dummy version of his module. +- NLME-NETWCRK-FCRMTO.L +- NLME-PERMrr.,JONNG.L NeworkEsabilshlngP MCPs.':"" M,,.sET NL -GET +- Go " MCP&ST RT MlME-GET NLME-5ET BeaoorPayloacParser Cop + GeEncDeviOeC8pa:;- j ac y PermiOuraijonTimer MC BeaconPayloadParserP NeworkJolnlngC Figure 6. NeworkEsablishingP Mlsecond clock PackeDispacherP MCPS-OT MLME-GEl NLME-GET MC ( NibP ) Figure 4. PackeDispacherP module PackeUil y PackeUiliyP 2) NibP: This module holds all nework layer aribues. These aribues may eiher be consan or variable. ll access from upper componen o hese informaion will be done hrough NLME-GET and NLME-SET. 4) NeworkJoiningC: his module allows ZigBee device o search for acive neworks in is POS area hrough NLME NETWORK-DSCOVERY and send a joining reques hrough NLME-JON inerface. NeighborTableUiliyP is used o keep he neighbor able informaion. Oher componen can access hese informaion hrough NeighborTableUiliy inerface. NLME-ED-SCN NLME-JON NLME-NETWORK-OSCOVERY --J.' ' NeworkJolnlngC R (r si(fimetmer MLM SelVlces :; NelghbaTableull1y BeaOCl'lPayoad"' ar ser ResfclalaTlmer MC NelghborTableUlliyP BeaconPayloadParserP Symbol clock Figure 7. NeworkJoiningC 5) NeworkLeavingP: This module is used o implemen he leaving nework process. When a device wans o leave nework or when i wan o force i's child devices o leave, i will send a reques hrough NLME-LE VE inerface

4 , MLME-RESET NLME-lEVE NeworkLeavingP + NLME-GET NeiglborTableUiliy.. SeWcinSaus Newo-packe NLME-SET GeUolnSakls [leve <fommndl MC NeighborTabloUiliyP NoworkJolnlngC rackeullspacher Figure 8. NeworkLeavingP MLME-8ET 1. MC NLME-STRT-ROUTER SarRouerP + NeighborTableUiliy NeighborTableUiliyP 6) NeworkSynchronizeP: When a device is already conneced, if i lose sync wih paren, his module will inform he upper layer hrough NLME-SYNC-LOSS inerface. Moreover, his module also allow device o resynchronizewih he nework hrough NLME-SYNC inerface. NLME-SYNC NLM E-SYNC-LOSS NeworkSynchronizeP.. MLME-SET MLME-GET Figure 9. MC J. MLME-SYNC MLME-5YNC-LOSS NeworkSynchronizeP 7) SarRouerP: Righ afer successful connecing o a nework, a rouer operaes like an end-device. f i wan o operae as a real rouer, i should send a reques hrough NLME-STRT-ROUTER. when receving ha reques, SarRouerP module will search in neighbor able, esablish saisics for exising beacons and use an approriae algorihm o compue is own beacon periods. n addiion, his module is only implemened in rouer device, oher device ypes only use is dummy version. Figure 10. SarRouerP 8) RoueP: When a device wans o send daa o oher nodes in he nework, i should send reques o RoueP hrough NLDE-DT. There are 3 rouing ypes in ZigBee nework Unicas, Mulicas and Broadcas. Based on he desinaion address conained in he reques, RoueP will use he approriae rouing ype. Moreover, f curren device is an enddivice, is RoueP module will be a dummy one which doesn' implemen any rouing algorihm. MLME-5ET 1. MC V. NLDE T / RoueP Figure 11. RoueP Newa":;iiY GelCurrerDeph GeUol'lSaliS NoworkJolnlngC NLM&ROUTE-OSCOVERY / Nelwa" Packe (DT RME (j>ackeullspacherp) V LlDTON OF PROPOSED RCHTECTURE To illusrae he proposed nework layer archiecure, a general purpose visualizaion ool for WSNs - NViz is developed. This ool can represen and visualize daa for any kind of WSN. allows user o se heir nework's properies and packe formas hrough XML files. Based on properies defined, user can choose he meaning of hem and le NViz represens he daa respecively. Fig. 12 shows a screensho of his visualizaion ool. Window boul Ci3111 -<ssodale> D = 1 -Sourceddress =3 -Desinaionddress = 12 -Linl(Srengh = 3 NoCleFuncion = 1 09:46: D13121 <ssodale> 10 = 1 SourceClClress =3 OeslinaionClClress = 13 LinkSlrengh = 3 NoCleFuncion = 2 09:47: ClO <ssodale> 10 = 1 SourceClClress = 12 DeslinaionClClress= 1B LinkSlrengh =2 NoCleFuncion = 2 09:47:14 -O/1/0/CiO/13/2/2/ <ssodale> D = 1 SourceClClress = 12 OeslinaionClClress= 19 LinkSlrengh =2 NoCleFuncion = 2 09:47: B12121 <ssodale> 10 = 1 SourceClClress =3 DeslinaionClClress= 11 LinkSlrengh =2 NoCleFuncion = 2 09:47:01 ClCl nocleo = 18 09:47:01 ClCllinkbe\ween nocle 12 ancl 18 09:47:14 ClCl nocled = 19 09:47:14 ClCllinkbe\ween nocle 12 ancl 19 09:47:54 ClCl nocled = 11 09:47:54 ClCllinkbe\ween nocle 3 ancl 11 Figure 12. Screensho of NViz

5 V. CONCLUSON n his paper, a 2008 specificaion ZigBee nework layer archiecure is presened. well-srucured archiecure of a complee nework layer based on TKN5.4 layer is designed. akes advanages of NesC language and TinyOS operaing sysem o make nework layer more flexible and expandable. This archiecure is implemened for TinyOS. can also be used as a reference source when implemening ZigBee nework layer in oher sysem. simple WSN applicaion is also developed as an illusraion of he proposed nework layer. REFERENCES [] Zig8ee lliance "Zig8ee Specificaion 2008" [2] P. Baroni, P. Pilai, V. W. C. Chook, S. Chessa,. Goa, and Y. F. Hu, "Wireless sensor neworks : survey on he sae of he ar and he and Zig8ee sandards," Compuer Communicaions, vol. 30, pp , [3] Texas nsrumens,"cc2431 Low-power RF SoC" [Online]. vailable: hp:// [4] Ember Corporaion, "EM High-Performance, negraed Zig8ee/EEE Sysem-On-Chip",[Online]vailable: hp:// dvanced.pdf [5] Microchip Technology nc, "Microchip Sack for he Zig8eeTM Proocol", [Online] vailable:hp:// ppnoesl00965c.pdf [6] TinyOS Exension Proposal (TEPs), [Online] vailable: hp://docs. inyos.ne/inywikilindex.phpteps [7] P. Levis and L. Gay, "TinyOS Programming" 2009 [8] D. Gay, P. Levis, D. Culler, and E. 8rewer, "nesc 1.2 Language Reference Manual," [9] TinyOSZig8ee Working Group hpj/ working group inyos Zig8ee.hml [10]. Cunha,. Koubiia, R. Severino, and M. lves, "Open-Z8 : an opensource implemenaion of he EEE /Zig8ee proocol sack on TinyOS" [] J.Hauer 'TKN5.4: n EEE MC mplemenaion for TinyOS 2", Technical repor, March [12] EEE, "EEE Sandard for Par 15.4: Wireless Medium ccess Conrol (MC) and Physical Layer (PHY) specificaions for Low Rae Wireless Personal rea Neworks (LR-WPNs)",