Documente Academic
Documente Profesional
Documente Cultură
jing sun1,2, Zhongxiao Wang 2, hong wang1, Xiaofen Zhang 1 1 Shenyang Normal University, Shenyang China, 2 JiLin Normal University, Siping China Sunjing431@tom.com
In mesh topology, there is also one PAN coordinator. In contrast to star topology, any device can communicate with any other device as long as they are in range of one another. A mesh network can be ad hoc, self-organizing and self-healing. Applications such as industrial control and monitoring, wireless sensor networks, asset and inventory tracking would benefit from such a topology. It also allows multiple hops to route messages from any device to any other device in the network. It can provide reliability by multipath routing. The mesh network uses the integrated routing method combined with AODV and Hierarchical/Tree routing. Cluster-tree network is a special case of mesh network in which most devices are FFDs (Full Function Device) and an RFD (Reduced Function Device) may connect to a cluster-tree network as a leave node at the end of a branch. Any of the FFD can act as a coordinator and provide synchronization services to other devices and coordinators. Only one of these coordinators however is the PAN coordinator. The tree network uses a Hierarchical/Tree Routing mechanism.
Abstract
ZigBee is the new standard that has been developed for low cost, low data rate and low power consumption wireless network. This paper provides a brief description of ZigBee network topologies including star, mesh, and cluster tree and introduces ZigBee routing protocols such as AODV, AODVjr, Clustertree and integrated routing algorithm. The mesh network uses the integrated routing method combined with AODV and Hierarchical/Tree routing. The tree network uses a Hierarchical/Tree Routing mechanism. Protocol analysis focuses on several issues: routing mechanism, cost and maintenance, and so on. Routing mechanism includes the configuration of tree addresses and tree addressing routing. And route cost gives how to compute cost metric during route discovery and maintenance.
1. Introduction
The IEEE 802.15.4 [1] is released for low power and low cost wireless networking for residential and industrial environments in December 2003. The ZigBee Alliance released its first specification [2, 3] in December 2004, based upon the physical (PHY) and medium access control (MAC) layer of IEEE 802.15.4 protocol. ZigBee defines three types of devices: ZigBee coordinator, ZigBee router and ZigBee end device. And three network topologies are defined: star, tree and mesh (peer-to-peer) topology, illustrated in Figure 1. In the star topology, the communication is established between devices and a single central controller, called the PAN coordinator. The PAN coordinator may be mains powered while the devices will most likely be battery powered. The star topology may not be adequate for traditional wireless sensor networks. The star topology of ZigBee is mainly designed for the simple communication from one node to several nodes.
domain algorithm Ad hoc On Demand Distance Vector (AODV)[ 4,5] and Motorolas Cluster-Tree algorithm.
that indicates the cluster head. The nodes that receive this message send a CONNECTION REQUEST message to the CH. When the CH receives it, it responds to the node with a CONNECTION RESPONSE message that contains a node ID for the node (node ID corresponds to the short address at the MAC layer). The node that is assigned a node ID replies with an ACK message to the cluster head. If all nodes are located in the range of the cluster head, the topology of connection becomes a star and every member nodes are connected to the cluster head with one hop. A cluster can expand into a multi-hop structure when each node supports multiple connections. 2.2.2. Multi-cluster network. To form a network, a Designated Device (DD) is needed. If a member has received the HELLO message from the DD, it adds CID 0 in its neighbor list and reports to its CH. The reported CH selects the member node as a border node to its parent cluster and sends a NETWORK CONNECTION REQUEST message to the member node to set up a connection with the DD. The border node requests a connection and joins the cluster 0 as its member node. Then it sends a CID REQUEST message to the DD. After the CID RESPONSE message arrival, the border node sends NETWORK CONNECTION RESPONSE message that contains a new CID to the CH. When the CH gets a new CID, it informs to its member nodes by the HELLO message. The process is shown in Figure 2.
an AODV route, depending on various factors such as session duration and tolerable route discovery delay. Cluster-tree routing favors memory-constrained devices and is very suitable for short communication sessions. Most cluster tree routes [12] are not optimal in terms of hop count. AODV and AODVjr are capable of finding optimal or near-optimal routes, and thus help reduce the message delivery latency. And in general, AODV and AODVjr are suitable for devices with sufficient memories, and favor long communication sessions. The integrated routing combines these two routings and makes tradeoff between them according to the network conditions and requirements.
Destination D is a descendant of router with address A and depth d, if A<D<A+Cskip(d-1) is true, then the destination node with address D is its child node, the address of the next hop node is
Table 2.Route discovery table Otherwise, the next hop node is the father node of this router.
Where each of the values C{[Di,Di+1]} is referred to as a link cost. The link cost C{l} for a link l is a function with values in the interval[07] defined as:
initiate route repair. Implementers may choose a simple failure-counting scheme to generate this failure counter value or they may use a more accurate timewindowed scheme. Note that it is important not to initiate repair too frequently since repair operations may flood the network and cause other traffic disruptions. 3.4.1. Mesh network repair. When a link or a device fails in mesh network topology, the upstream device shall initiate route repair. If the upstream device is unable to initiate route repair due to a lack of routing capacity or some other limitation, the device shall issue a route error command frame back to the source device with the error code indicating the reason for the failure. If an end device that is also an RFD is unable to transmit messages to its parent, the end device shall initiate the orphaning procedure which permits the device to re-associate with the same ZigBee coordinator or ZigBee router if network communication is lost. If the orphaning procedure is successful and the end device re-establishes communications with its parent, the end device shall resume operation on the network as before. If the orphaning procedure fails, the end device shall attempt to re-join the network through a new parent. 3.4.2. Tree network repair. When a downstream device loses synchronization with its parent beacon, or is unable to transmit a message to its parent, the device may either initiate the orphaning procedure to search for its parent or the association procedure to find a new parent. If a disassociated child has its own children, it shall disassociate them from the network before attempting re-association.
4. Conclusion
ZigBee is a recent standard and is more appropriate in sensor network. This paper reviews three network topologies and introduces routing protocols of the Zigbee standard: AODV, AODVjr, Cluster-tree, and integrated routing, and then describes the formulas to analyze the routing mechanisms and the corresponding costs. Finally we introduce the approaches to repair the network while some devices fail. With the consequent develop of a series of products based on ZigBee protocol, more attention and development will be dedicated to the fields of application design and realization, interoperability test and market promotion.
Low-Rate Wireless Personal Area Networks (LR-WPANs), IEEE standard for Information Technology, 2003. [2] P. Kinney, ZigBee Technology: Wireless Control that Simply Works, Communication Design Conference, October, 2003 [3] ZigBee Alliance, ZigBee Specification Version 1.0, www.zigbee.org, December 14th, 2004. [4] Charles E.Perkins,Elizabeth M.Belding-Royer, and Samir Das. Ad hoc On-Demadn Distance Vector(AODV) Routing, Protol.IETF Internet Draft,draft-ietf-manet-aodv10.txt, January 2002. [5] C. E. Perkins, E. M. Royer, and S. R. Das, Ad hoc on demand distance vector (AODV) routing, IETF Internet draft, draft-ietf-manetaodv- 13.txt, Feb. 2003. [6] K. Kim, S. D. Park, G. Montenegro, S. Yoo, 6LoWPAN Ad Hoc On-Demand Distance Vector Routing (LOAD), draft-daniel-6lowpan-load-adhocrouting-01, IETF Internet Draft (Work in progress), July, 2005. [7] G. Montenegro, AODV for IEEE 802.15.4 Networks, draft-montenegro-lowpan-aodv-00, IETF Internet Draft (Work in progress), July, 2005. [8] C. Perkins, E. Belding-Royer, S. Das, Ad hoc On Demand Distance Vector Routing (AODV), RFC 3561, July 2003. [9] R. Bruno and M. Conti. Mesh Networks: Commodity Multi hop Ad Hoc Networks, IEEE Communication Magazine, March, 2005, pp.123-131. [10] Ian D. Chakeres, Lukr Klein-Berndt, AODVjr, AODV Simplified, Mobile Computing and Communications Review, Vol. 6, No. 3, July 2002 pp. 100-101. [11] Sinem Coleri Ergen, ZigBee/IEEE 802.15.4 Summary, September 10, 2004. [12] A. Kouba, M. Alves, and E. Tovar, Modeling and Worst-Case Dimensioning of Cluster-Tree Wireless Sensor Networks: proofs and computation details, Technical Report IPP-HURRAY!, TR-060601, available online www.dei.isep.ipp.pt/~akoubaa,2006. [13] Mesh Networking Forum, Building the business case for implementation of wireless mesh networks, Mesh Networking Forum 2004, San Francisco, CA, October 2004. [14] Kwang Koog Lee, Seong Hoon Kim, Yong Soon Choi and Hong Seong Park, A Mesh Routing Protocol using Cluster Label in the ZigBee Network,802-806,IEEE2006. [15] Ran Peng, Sun Mao-heng, Zou You-min, ZigBee Routing Selection Strategy Based on Data Services and Energy-balanced ZigBee Routing , Proceedings of the 2006 IEEE Asia-Pacific Conference on Services Computing 6. Type-style and fonts.
Reference
[1] IEEE-TG15.4, Part 15.4 Wireless Medium Access Control(MAC) and Physical Layer(PHY) Specification for