1.

2 ZIGBEE:
ZigBee is the name of a specification for a suite of high level communication protocols using small, low-
power digital radios based on the IEEE 802.15.4 standard for wireless personal area networks (WPANs), such as
wireless headphones connecting with cell phones via short-range radio. The technology is intended to be simpler
and cheaper than other WPANs, such as Bluetooth. ZigBee is targeted at radio-frequency (RF) applications which
require a low data rate, long battery life, and secure networking

1.3 OVERVIEW:
ZigBee builds upon the physical layer and medium access control defined in IEEE standard 802.15.4
(2003 version) for low-rate WPAN's. The specification goes on to complete the standard by adding four main
components: network layer, application layer, ZigBee device objects (ZDO's) and manufacturer-defined
application objects which allow for customization and favor total integration.

Besides adding two high-level network layers to the underlying structure, the most significant
improvement is the introduction of ZDO's. These are responsible for a number of tasks, which include keeping of
device roles, management of requests to join a network, device discovery and security.

(Fig 1:zigbee specifications)

At its core, ZigBee is a mesh network architecture. Its network layer natively supports three types of topologies:
both star and tree typical networks and generic mesh networks. Every network must have one coordinator device,
tasked with its creation, the control of its parameters and basic maintenance. Within star networks, the coordinator
must be the central node. Both trees and meshes allow the use of ZigBee routers to extend communication at the
network level (they are not ZigBee coordinators, but may act as 802.15.4 coordinators within their personal
operating space), but they differ in a few important details: communication within trees is hierarchical and
optionally utilizes frame beacons, whereas meshes allow generic communication structures but no router
beaconing.

The relationship between IEEE 802.15.4-2003 and ZigBee is similar to that between IEEE 802.11 and the
Wi-Fi Alliance. The ZigBee 1.0 specification was ratified on December 14, 2004 and is available to members of
the ZigBee Alliance. An entry level membership called Adopter, in the ZigBee Alliance costs US$3500 annually
and provides access to the specifications and permission to create products for market using the specifications.
For non-commercial purposes, the ZigBee specification is available to the general public at the ZigBee
Specification Download Request. Most recently, the ZigBee 2006 specification was posted in December 2006.
 ZigBee operates in the industrial, scientific and medical (ISM) radio bands; 868 MHz in Europe, 915 MHz
in countries such as USA and Australia, and 2.4 GHz in most jurisdictions worldwide. The technology is intended
to be simpler and cheaper than other WPANs such as Bluetooth. The most capable ZigBee node type is said to
require only about 10% of the software of a typical Bluetooth or Wireless Internet node, while the simplest nodes
are about 2% However, actual code sizes are much higher, closer to 50% of Bluetooth code size ZigBee chip
vendors have announced 128-kilobyte devices.

1.4 NETWORK LAYERS:

The main functions of the network layer are to enable the correct use of the MAC sublayer and provide a
suitable interface for use by the next upper layer, namely the application layer. Its capabilities and structure are
those typically associated to such network layers, including routing.

On the one hand, the data entity creates and manages network layer data units from the payload of the
application layer and performs routing according to the current topology. On the other hand, there is the layer
control, which is used to handle configuration of new devices and establish new networks: it can determine
whether a neighboring device belongs to the network and discovers new neighbors and routers. The control can
also detect the presence of a receiver, which allows direct communication and MAC synchronization.

1.5 APPLICATION LAYER:

The application layer is the highest-level layer defined by the specification, and is the effective interface of the
ZigBee system to its end users. It comprises the majority of components added by the ZigBee specification: both
ZDO and its management procedures, together with application objects defined by the manufacturer, are
considered part of this layer.
1.5.1 Main Components:
The ZDO is responsible for defining the role of a device as either coordinator or end device, as mentioned
above, but also for the discovery of new (one-hop) devices on the network and the identification of their offered
services. It may then go on to establish secure links with external devices and reply to binding requests
accordingly.

The application support sublayer (APS) is the other main standard component of the layer, and as such it
offers a well-defined interface and control services. It works as a bridge between the network layer and the other
components of the application layer: it keeps up-to-date binding tables in the form of a database, which can be
used to find appropriate devices depending on the services that are needed and those the different devices offer.
As the union between both specified layers, it also routes messages across the layers of the protocol stack.
In order for applications to communicate, their comprising devices must use a common application protocol (types
of messages, formats and so on); these sets of conventions are grouped in profiles. Furthermore, binding is
decided upon by matching input and output cluster identifiers, unique within the context of a given profile and
associated to an incoming our outgoing data flow in a device. Binding tables contain source and destination pairs.

Communication and device Discovery:

Depending on the available information, device discovery may follow different methods. When the
network address is known, the IEEE address can be requested using unicast communication. When it is not,
petitions are broadcast (the IEEE address being part of the response payload). End devices will simply respond
with the requested address, while a network coordinator or a router will also send the addresses of all the devices
associated with it.

This extended discovery protocol permits external devices to find out about devices in a network and the
services that they offer, which endpoints can report when queried by the discovering device (which has previously
obtained their addresses). Matching services can also be used.

The use of cluster identifiers enforces the binding of complementary entities by means of the binding
tables, which are maintained by ZigBee coordinators, as the table must be always available within a network and
coordinators are most likely to have a permanent power supply; backups may be needed by some applications,
whose higher-level layers must manage. Binding requires an established communication link; after it exists,
whether to add a new node to the network is decided, according to the application and security
policies.Communication can happen right after the association. Direct addressing uses both radio address and
endpoint identifier, whereas indirect addressing requires every relevant field (address, endpoint, cluster and
attribute) and sends it to the network coordinator, which maintains these associations and translates requests for
communication. Indirect addressing is particularly useful to keep some devices very simple and minimize their
need for storage. Besides these two methods, broadcast to all endpoints in a device is available, and group
addressing is used to communicate with groups of endpoints belonging to a set of devices.

Security architecture:

ZigBee uses 128-bit keys to implement its security mechanisms. A key can be associated either to a
network, being usable by both ZigBee layers and the MAC sublayer, or to a link, acquired through preinstallation,
agreement or transport. Establishment of link keys is based on a master key which controls link key
correspondence. Ultimately, at least the initial master key must be obtained through a secure medium (transport
or preinstallation), as the security of the whole network depends on it. Link and master keys are only visible to the
application layer. Different services use different one-way variations of the link key in order to avoid leaks and
security risks.
Key distribution is one of the most important security functions of the network. A secure network will
designate one special device which other devices trust for the distribution of security keys: the trust center.
Ideally, devices will have the trust center address and initial master key preloaded; if a momentary vulnerability is
allowed, it will be sent as described above. Typical applications without special security needs will use a network
key provided by the trust center (through the initially insecure channel) to communicate.
Thus, the trust center maintains both the network key and provides point-to-point security. Devices will only
accept communications originating from a key provided by the trust center, except for the initial master key. The
security architecture is distributed among the network layers as follows:

The MAC sublayer is capable of single-hop reliable communications. As a rule, the security level it is to use is
specified by the upper layers.
The network layer manages routing, processing received messages and being capable of broadcasting requests.
Outgoing frames will use the adequate link key according to the routing, if it is available; otherwise, the network
key will be used to protect the payload from external devices.
The application layer offers key establishment and transport services to both ZDO and applications. It is also
responsible for the propagation across the network of changes in devices within it, which may originate in the
devices themselves (for instance, a simple status change) or in the trust manager (which may inform the network
that a certain device is to be eliminated from it). It also routes requests from devices to the trust center and
network key renewals from the trust center to all devices. Besides this, the ZDO maintains the security policies of
the device.

1.6 PROTOCOLS:
The protocols build on recent algorithmic research (Ad-hoc On-demand Distance Vector, neuRFon) to
automatically construct a low-speed ad-hoc network of nodes. In most large network instances, the network will
be a cluster of clusters. It can also form a mesh or a single cluster. The current profiles derived from the ZigBee
protocols support beacon and non-beacon enabled networks.
In non-beacon-enabled networks (those whose beacon order is 15), an unslotted CSMA/CA channel
access mechanism is used. In this type of network, ZigBee Routers typically have their receivers continuously
active, requiring a more robust power supply. However, this allows for heterogeneous networks in which some
devices receive continuously, while others only transmit when an external stimulus is detected. The typical
example of a heterogeneous network is a wireless light switch: the ZigBee node at the lamp may receive
constantly, since it is connected to the mains supply, while a battery-powered light switch would remain asleep
until the switch is thrown. The switch then wakes up, sends a command to the lamp, receives an
acknowledgment, and returns to sleep. In such a network the lamp node will be at least a ZigBee Router, if not the
ZigBee Coordinator; the switch node is typically a ZigBee End Device.
In beacon-enabled networks, the special network nodes called ZigBee Routers transmit periodic beacons
to confirm their presence to other network nodes. Nodes may sleep between beacons, thus lowering their duty
cycle and extending their battery life. Beacon intervals may range from 15.36 milliseconds to 15.36 ms * 214 =
251.65824 seconds at 250 kbit/s, from 24 milliseconds to 24 ms * 214 = 393.216 seconds at 40 kbit/s and from 48
milliseconds to 48 ms * 214 = 786.432 seconds at 20 kbit/s. However, low duty cycle operation with long beacon
intervals requires precise timing which can conflict with the need for low product cost.
In general, the ZigBee protocols minimize the time the radio is on so as to reduce power use. In beaconing
networks, nodes only need to be active while a beacon is being transmitted. In non-beacon-enabled networks,
power consumption is decidedly asymmetrical: some devices are always active, while others spend most of their
time sleeping.
ZigBee devices are required to conform to the IEEE 802.15.4-2003 Low-Rate Wireless Personal Area
Network (WPAN) standard. The standard specifies the lower protocol layers—the physical layer (PHY), and the
medium access control (MAC) portion of the data link layer (DLL). This standard specifies operation in the
unlicensed 2.4 GHz, 915 MHz and 868 MHz ISM bands. In the 2.4 GHz band there are 16 ZigBee channels, with
each channel requiring 5 MHz of bandwidth. The center frequency for each channel can be calculated as, FC =
(2405 + 5*(k-11)) MHz, where k = 11, 12, ..., 26.
The radios use direct-sequence spread spectrum coding, which is managed by the digital stream into the
modulator. BPSK is used in the 868 and 915 MHz bands, and orthogonal QPSK that transmits two bits per
symbol is used in the 2.4 GHz band. The raw, over-the-air data rate is 250 kbit/s per channel in the 2.4 GHz band,
40 kbit/s per channel in the 915 MHz band, and 20 kbit/s in the 868 MHz band. Transmission range is between 10
and 75 meters (33 and 246 feet), although it is heavily dependent on the particular environment. The maximum
output power of the radios is generally 0 dBm (1 mW).
The basic channel access mode specified by IEEE 802.15.4-2003 is "carrier sense, multiple access/collision
avoidance" (CSMA/CA). That is, the nodes talk in the same way that people converse; they briefly check to see
that no one is talking before they start. There are three notable exceptions to the use of CSMA. Beacons are sent
on a fixed timing schedule, and do not use CSMA. Message acknowledgements also do not use CSMA. Finally,
devices in Beacon Oriented networks that have low latency real-time requirements may also use Guaranteed
Time Slots (GTS) which by definition does not use CSMA.

1.7 NODE TYPES:

This page describes the types of node that are used in a ZigBee network. Reference will be made to the
toplogies introduced on the previous page (Star, Tree, Mesh), but these topologies will be described in more detail
later in this module.

The ZigBee standard has the capacity to address up to 65535 nodes in a single network. However, there are only
three general types of node:

• Co-ordinator
• End Device
• Router

These roles described below exist at the network level – a ZigBee node may also be performing tasks at the
application level independent of the role it plays in the network. For instance, a network of ZigBee devices
measuring temperature may have a temperature sensor application in each node, irrespective of whether they are
End Devices, Routers or the Co-ordinator.

These node types are described below.

1.8.1 ZigBee coordinator(ZC): The most capable device, the coordinator forms the root of the network tree and
might bridge to other networks. There is exactly one ZigBee coordinator in each network since it is the device that
started the network originally. It is able to store information about the network, including acting as the Trust Centre
& repository for security keys.

All ZigBee networks must have one (and only one) Co-ordinator, irrespective of the network topology.

In the Star topology, the Co-ordinator is the central node in the network.

• In the Tree and Mesh topologies, the Co-ordinator is the top (root) node in the network.
• This is illustrated below, where the Co-ordinator is colour-coded in dark black.

At the network level, the Co-ordinator is mainly needed at system initialisation. The tasks of the Co-ordinator at
the network layer are:
 • Selects the frequency channel to be used by the network (usually the one with the least detected activity)
• Starts the network
• Allows other devices to connect to it (that is, to join the network)

The Co-ordinator can also provide message routing (for example, in a Star network), security management and
other services.

In some circumstances, the network will be able to operate normally if the Co-ordinator fails or is switched off.
This will not be the case if the Co-coordinator provides a routing path through the network (for instance, in a Star
topology, where it is needed to relay messages). Similarly the Co-ordinator provides services at the Application
layer and if these services are being used (for example, Co-ordinator binding), the Co-ordinator must be able to
provide them at all times.

1.8.2 ZigBee Router (ZR): As well as running an application function a router can act as an intermediate router,
passing data from other devices.

Networks with Tree or Mesh topologies need at least one Router. The main tasks of a Router are:

• Relays messages from one node to another

• Allows child nodes to connect to it

In a Star topology, these functions are handled by the Co-ordinator and, therefore, a Star network does not need
Routers.

In Tree and Mesh topologies, Routers are located as follows:

• In a Tree topology, Routers are normally located in network positions that allow messages to be passed
up and down the tree.
• In a Mesh topology, a Router can be located anywhere that a message passing node is required.

However, in all topologies (Star, Tree and Mesh), Router devices can be located at the extremities of the network,
if they run applications that are needed in these locations - in this case, the Router will not perform its message
relay function, unless in a Mesh network (see above).

The possible positions of Routers in the different network topologies are illustrated below, where the Routers are
color-coded in red:
1.8.3 ZigBee End Device (ZED): Contains just enough functionality to talk to the parent node (either the
coordinator or a router); it cannot relay data from other devices. This relationship allows the node to be asleep a
significant amount of the time thereby giving long battery life. A ZED requires the least amount of memory, and
therefore can be less expensive to manufacture than a ZR or ZC.

End Devices are always located at the extremities of a network:

• In the Star topology, they are perimeter nodes

• In the Tree and Mesh topologies, they are leaf nodes

This is illustrated below, where the End Devices are color-coded in light blue.

The main tasks of an End Device at the network level are sending and receiving messages. Note that End
Devices cannot relay messages and cannot allow other nodes to connect to the network through them.

An End Device can often be battery-powered and, when not transmitting or receiving, can sleep in order to
conserve power.

USES :
ZigBee protocols are intended for use in embedded applications requiring low data rates and low power
consumption. ZigBee's current focus is to define a general-purpose, inexpensive, self-organizing mesh network
that can be used for industrial control, embedded sensing, medical data collection, smoke and intruder warning,
building automation, home automation, etc. The resulting network will use very small amounts of power so
individual devices might run for a year or two using the originally installed battery.
Typical application areas include:
• Home Entertainment and Control - Smart Lighting, Advanced Temperature Control, Safety & Security and
Movies & Music
• Home Awareness - Water Sensors, Power Sensors, Smart Appliances and Access sensors
• Mobile Services – m-payment, m-monitoring and control, m-security and access control, m- healthcare and tele-
assist
• Commercial Building– Energy Monitoring, HVAC, Lighting, Access Control
• Industrial Plant– Process Control, Asset Management, Environmental management, Energy Management
CC3430

In addition to including the CC2430 transceiver RF, but also integrates enhanced 8051MCU, 32/64/128 KB
of flash memory, 8KB of RAM, as well as the ADC, DMA, and other watchdog. CC2430 can work in the 2.4
GHz band, the use of low-voltage (2.0 ~ 3.6V) power supply and low power consumption (when receiving data
27 mA, send data at 25 mA), its sensitivity as high as -91 dBm, maximum output for +0.6 dBm, the maximum
transmission rate of 250 kbps.

CC2430 small number of external components, it uses an antenna to connect to non-equilibrium non-equilibrium
transformers, in order to better antenna performance. Circuit in the transformer by the non-equilibrium
capacitance C309, C311 and inductor L301, L302, L303 of the entire structure to meet the RF input / output
matching resistor (50Ω) requirements. Internal T / R exchange circuit LNA and PA for the completion of the
exchange between. R200, R201 for the bias resistor R200 which is mainly used for the 32MHz crystal oscillator
to provide a suitable current through R201 for the Radio Frequency portion of the chip precision internal current
reference source. Selection of a 32MHz quartz resonator and two capacitors (C210, C211) can constitute a 32
MHz crystal oscillator circuit. Chip voltage regulator for all 1.8V voltage supply pin and the internal, C214, C209,
C200, such as decoupling capacitors, power supply filtering is mainly used to improve the stability of the chip
work. The main features of CC2430 chip is as follows:

◇ includes high performance and low power 8051 microcontroller core;

◇ integrated IEEE802.15.4 standards in line with the 2.4 GHz radio transceiver of the RF;

◇ Wireless has an excellent receiver sensitivity and strong anti-interference ability.

◇ only 0.9μA in sleep mode power consumption of the flow can be external interrupt or RTC wake-up system:
Standby mode current consumption is less than 0.6μA, can also use external interrupt wake-up system;

◇ hardware to support the CSMA / CA function;

◇ has a wide voltage range (2.0 ~ 3.6 V);

◇ with digital RSSI / LQI support and powerful DMA function;

◇ with battery monitoring and temperature sensing function;

◇ integrated 14-bit internal analog-to-digital conversion of the ADC;

◇ integrated AES security coprocessor;

◇ with two sets of agreements to support the USART, and a line with the norms of the MAC timer
IEEE802.15.4. At the same time with a conventional 16-bit timer and two 8-bit timer.

◇ with powerful and flexible development tools.

Why is ZigBee needed?

There are a multitude of standards that address mid to high data rates for voice, PC LANs, video, etc. However,
up till now there hasn’t been a wireless network standard that meets the unique needs of sensors and control
devices. Sensors and controls don’t need high bandwidth but they do need low latency and very low energy
consumption for long battery lives and for large device arrays.
There are a multitude of proprietary wireless systems manufactured today to solve a multitude of problems that
also don’t require high data rates but do require low cost and very low current drain.
These proprietary systems were designed because there were no standards that met their requirements. These
 legacy systems are creating significant interoperability problems with each other and with newer technologies.

The ZigBee Alliance is not pushing a technology; rather it is providing a standardized base set of solutions for
sensor and control systems.

• The physical layer was designed to accommodate the need for a low cost yet allowing for high levels of
integration. The use of direct sequence allows the analog circuitry to be very simple and very tolerant
towards inexpensive implementations.
• The media access control (MAC) layer was designed to allow multiple topologies without complexity. The
power management operation doesn’t require multiple modes of operation. The MAC allows a reduced
functionality device (RFD) that needn’t have flash nor large amounts of ROM or RAM. The MAC was
designed to handle large numbers of devices without requiring them to be “parked”.
• The network layer has been designed to allow the network to spatially grow without requiring high power
transmitters. The network layer also can handle large amounts of nodes with relatively low latencies.ZigBee
is poised to become the global control/sensor network standard. It has been designed to provide the
following features:
Low power consumption, simply implemented
Users expect batteries to last many months to years! Consider that a typical single family house has about 6
smoke/CO detectors. If the batteries for each one only lasted six months, the home owner would be
replacing batteries every month!
– Bluetooth has many different modes and states depending upon your latency and power requirements such
as sniff, park, hold, active, etc.; ZigBee/IEEE 802.15.4 has active (transmit/receive) or sleep. Application
software needs to focus on the application, not on which power mode is optimum for each aspect of
operation.
– Even mains powered equipment needs to be conscious of energy. Consider a future home with 100
wireless control/sensor devices,
– Case 1: 802.11 Rx power is 667 mW (always on)@ 100 devices/home & 50,000 homes/city = 3.33
megawatts
– Case 2: 802.15.4 Rx power is 30 mW (always on)@ 100 devices/home & 50,000 homes/city = 150
kilowatts
– Case 3: 802.15.4 power cycled at .1% (typical duty cycle) = 150 watts.
ZigBee devices will be more ecological than its predecessors saving megawatts at it full deployment.
Low cost (device, installation, maintenance)
Low cost to the users means low device cost, low installation cost and low maintenance. ZigBee devices
allow batteries to last up to years using primary cells (low cost) without any chargers (low cost and easy
installation). ZigBee’s simplicity allows for inherent configuration and redundancy of network devices
provides low maintenance.
High density of nodes per network
ZigBee’s use of the IEEE 802.15.4 PHY and MAC allows networks to handle any number of devices.
This attribute is critical for massive sensor arrays and control networks.
Simple protocol, global implementation
ZigBee’s protocol code stack is estimated to be about 1/4th of Bluetooth’s or 802.11’s. Simplicity is
essential to cost, interoperability, and maintenance. The IEEE 802.15.4 PHY adopted by ZigBee has
been designed for the 868 MHz band in Europe, the 915 MHz band in N America, Australia, etc; and the
2.4 GHz band is now recognized to be a global band accepted in almost all countries.
ZigBee/IEEE 802.15.4 - General Characteristics
Dual PHY (2.4GHz and 868/915 MHz)
Data rates of 250 kbps (@2.4 GHz), 40 kbps (@ 915 MHz), and 20 kbps (@868 MHz)
Optimized for low duty-cycle applications (<0.1%)
CSMA-CA channel access
Yields high throughput and low latency for low duty cycle devices like sensors and controls
Low power (battery life multi-month to years)
Multiple topologies: star, peer-to-peer, mesh
Addressing space of up to:
18,450,000,000,000,000,000 devices (64 bit IEEE address)
65,535 networks
Optional guaranteed time slot for applications requiring low latency
Fully hand-shaked protocol for transfer reliability
Range: 50m typical (5-500m based on environment)

ZigBee/IEEE802.15.4 - Typical Traffic Types Addressed

Periodic data
Application defined rate (e.g., sensors)
Intermittent data
 Application/external stimulus defined rate (e.g., light switch)
Repetitive low latency data
Allocation of time slots (e.g., mouse)

Each of these traffic types mandates different attributes from the MAC. The IEEE802.15.4 MAC is flexible
enough to handle each of these types.
• Periodic data can be handled using the beaconing system whereby the sensor will wake up for the
beacon, check for any messages and then go back to sleep.
• Intermittent data can be handled either in a beaconless system or in a disconnected fashion. In a
disconnected operation the device will only attach to the network when it needs to communicate saving
significant energy.
• Low latency applications may choose to the guaranteed time slot (GTS) option. GTS is a method of QoS
in that it allows each device a specific duration of time each Superframe to do whatever it wishes to do
without contention or latency.
The IEEE 802.15.4 PHY and MAC along with ZigBee’s Network and Application Support Layer provide:
Extremely low cost
Ease of implementation
Reliable data transfer
Short range operation
Very low power consumption
• Appropriate levels of security

There are two physical device types for the lowest system cost
To allow vendors to supply the lowest possible cost devices the IEEE standard defines two types of devices:
full function devices and reduced function devices
Full function device (FFD)
Can function in any topology
Capable of being the Network coordinator
• Capable of being a coordinator
Can talk to any other device

Reduced function device (RFD)

Limited to star topology
Cannot become a network coordinator
Talks only to a network coordinator
Very simple implementation

An IEEE 802.15.4/ZigBee network requires at least one full function device as a network coordinator, but endpoint
devices may be reduced functionality devices to reduce system cost.
All devices must have 64 bit IEEE addresses
Short (16 bit) addresses can be allocated to reduce packet size
Frame Structure
The frame structures have been designed to keep the complexity to a minimum while at the same time making
them sufficiently robust for transmission on a noisy channel. Each successive protocol layer adds to the structure
with layer-specific headers and footers.
The IEEE 802.15.4 MAC defines four frame structures:
• A beacon frame, used by a coordinator to transmit beacons.
• A data frame, used for all transfers of data.
• An acknowledgment frame, used for confirming successful frame reception.
• A MAC command frame, used for handling all MAC peer entity control transfers.
The data frame is illustrated below:
The Physical Protocol Data Unit is the total information sent over the air. As shown in the illustration above the
Physical layer adds the following overhead:
Preamble Sequence 4 Octets
Start of Frame Delimiter 1 Octet
Frame Length 1 Octet

The MAC adds the following overhead:

Frame Control 2 Octets
Data Sequence Number 1 Octet
Address Information 4 – 20 Octets
Frame Check Sequence 2 Octets

In summary the total overhead for a single packet is therefore 15 -31 octets (120 bits); depending upon the
addressing scheme used (short or 64 bit addresses). Please note that these numbers do not include any security
overhead.

The ZigBee Network Coordinator

Sets up a network
Transmits network beacons
Manages network nodes
Stores network node information
Routes messages between paired nodes
Typically operates in the receive state
The ZigBee Network Node
Designed for battery powered or high energy savings
Searches for available networks
Transfers data from its application as necessary
Determines whether data is pending
Requests data from the network coordinator
Can sleep for extended periods

The Inevitable Question is whether ZigBee and Bluetooth are competitors or complements?
Bluetooth seems best suited for:
Synchronization of cell phone to PDA
Hands-free audio
PDA to printer
While ZigBee is better suited for:
• Controls
• Sensors
• Lots of devices
• Low duty cycle
• Small data packets
• Long battery life is critical

Timing Considerations
ZigBee

New slave enumeration = 30ms typically

Sleeping slave changing to active = 15ms typically
Active slave channel access time = 15ms typically
Bluetooth
•
 • New slave enumeration = >3s, typically 20s
• Sleeping slave changing to active = 3s typically
• Active slave channel access time = 2ms typically

Conclusion:
ZigBee devices can quickly attach, exchange information, detach, and then go to deep sleep to achieve a very
long battery life. Bluetooth devices require about ~100X the energy for this operation.

Power Considerations
ZigBee
2+ years from ‘normal’ batteries
Designed to optimize slave power requirements

Bluetooth
Power model as a mobile phone (regular daily charging)
Designed to maximize ad-hoc functionality

Since IEEE 802.15.4 uses a CSMA-CA protocol the end nodes only talk when they have data to send with the
following benefits:
No waiting for polling (however they must wait for a clear channel which shouldn’t be a problem in low duty
cycle networks such as with sensor and control devices)
Current drain is substantially reduced over a polling protocol that must poll to maintain latencies even though
the majority of the time the device needed be polled
IEEE 802.15.4 protocol was designed to yield 6 months to 2 yrs on alkaline cell

Comparison Summary
ZigBee and Bluetooth are two solutions for two different application areas.
• The differences are from their approach to their desired application. Bluetooth has addressed a voice
application by embodying a fast frequency hopping system with a master slave protocol. ZigBee has
addressed sensors, controls, and other short message applications by embodying a direct sequence
system with a star or peer to peer protocols.
• Minor changes to Bluetooth or ZigBee won’t change their inherent behavior or characteristics. The
different behaviors come from architectural differences.
Will Bluetooth, ZigBee, and 802.11 all have a place in your home? Here's what ZigBee offers for
home wireless networking.

For the last few years, we've witnessed a great expansion of remote control devices in our day-to-day life.
Five years ago, infrared (IR) remotes for the television were the only such devices in our homes. Now I
quickly run out of fingers as I count the devices and appliances I can control remotely in my house. This
number will only increase as more devices are controlled or monitored from a distance.
To interact with all these remotely controlled devices, we'll need to put them under a single standardized
control interface that can interconnect into a network, specifically a HAN or home-area network. One of the
most promising HAN protocols is ZigBee, a software layer based on the IEEE 802.15.4 standard. This
article will introduce you to ZigBee—how it works and how it may be more appropriate than simply
accumulating more remotes.
Why so many remotes? Right now, the more remotely controlled devices we install in our homes, the more
remotes we accumulate. Devices such as TVs, garage door openers, and light and fan controls
predominantly support one-way, point-to-point control. They're not interchangeable and they don't support
more than one device. Because most remotely controlled devices are proprietary and not standardized
among manufacturers, even those remotes used for the same function (like turning on and off lights) are not
interchangeable with similar remotes from different manufacturers. In other words, you'll have as many
separate remote control units as you have devices to control.
Some modern IR remotes enable you to control multiple devices by "learning" transmitting codes. But
because the range for IR control is limited by line of sight, they're used predominantly for home
entertainment control.
A HAN can solve both problems because it doesn't need line-of-sight communication and because a single
remote (or other type of control unit) can command many devices.
Standard Bandwidt Power Protoco Stronghold Application
h Consumptio l Stack s
n Size
Wi-Fi Up to 400+mA TX, 100+KB High data rate Internet
54Mbps standby browsing,
20mA PC
networking,
file transfers
Bluetooth 1Mbps 40mA TX, ~100+K Interoperabilit Wireless
standby B y, cable USB,
0.2mA replacement handset,
headset
ZigBee 250kbps 30mA TX, 4"32KB Long battery Remote
standby life, low cost control,
3#&956;A battery-
operated
products,
sensors
ZigBee is the only standards-based technology that addresses the needs of most remote monitoring and
control and sensory network applications.

Figure 1: ZigBee stack architecture

It may be helpful to think of IEEE 802.15.4 as the physical radio and ZigBee as the logical network and
application software, as Figure 1 illustrates. Following the standard Open Systems Interconnection (OSI)
reference model, ZigBee's protocol stack is structured in layers. The first two layers, physical (PHY) and
media access (MAC), are defined by the IEEE 802.15.4 standard. The layers above them are defined by
the ZigBee Alliance. The IEEE working group passed the first draft of PHY and MAC in 2003. A final version
of the network (NWK) layer is expected sometime this year.
ZigBee-compliant products operate in unlicensed bands worldwide, including 2.4GHz (global), 902 to
928MHz (Americas), and 868MHz (Europe). Raw data throughput rates of 250Kbps can be achieved at
2.4GHz (16 channels), 40Kbps at 915MHz (10 channels), and 20Kbps at 868MHz (1 channel). The
transmission distance is expected to range from 10 to 75m, depending on power output and environmental
characteristics. Like Wi-Fi, Zigbee uses direct-sequence spread spectrum in the 2.4GHz band, with offset-
quadrature phase-shift keying modulation. Channel width is 2MHz with 5MHz channel spacing. The 868
and 900MHz bands also use direct-sequence spread spectrum but with binary-phase-shift keying
modulation.
Frame structure
Figure 2 illustrates the four basic frame types defined in 802.15.4: data, ACK, MAC command, and beacon.
Figure 2: The four basic frame types defined in 802.15.4: Data, ACK, MAC command, and beacon
The data frame provides a payload of up to 104 bytes. The frame is numbered to ensure that all packets are
tracked. A frame-check sequence ensures that packets are received without error. This frame structure
improves reliability in difficult conditions.
Another important structure for 802.15.4 is the acknowledgment (ACK) frame. It provides feedback from the
receiver to the sender confirming that the packet was received without error. The device takes advantage of
specified "quiet time" between frames to send a short packet immediately after the data-packet
transmission.
A MAC command frame provides the mechanism for remote control and configuration of client nodes. A
centralized network manager uses MAC to configure individual clients' command frames no matter how
large the network.
Finally, the beacon frame wakes up client devices, which listen for their address and go back to sleep if they
don't receive it. Beacons are important for mesh and cluster-tree networks to keep all the nodes
synchronized without requiring those nodes to consume precious battery energy by listening for long
periods of time.
Channel access, addressing
Two channel-access mechanisms are implemented in 802.15.4. For a non"beacon network, a standard
ALOHA CSMA-CA (carrier-sense medium-access with collision avoidance) communicates with positive
acknowledgement for successfully received packets. In a beacon-enabled network, a superframe structure
is used to control channel access. The superframe is set up by the network coordinator to transmit beacons
at predetermined intervals (multiples of 15.38ms, up to 252s) and provides 16 equal-width time slots
between beacons for contention-free channel access in each time slot. The structure guarantees dedicated
bandwidth and low latency. Channel access in each time slot is contention-based. However, the network
coordinator can dedicate up to seven guaranteed time slots per beacon interval for quality of service.
Device addresses employ 64-bit IEEE and optional 16-bit short addressing. The address field within the
MAC can contain both source and destination address information (needed for peer-to-peer operation). This
dual address information is used in mesh networks to prevent a single point of failure within the network

The ZigBee stack is small in comparison to other wireless standards. For network-edge devices with limited
capabilities, the stack requires about 4Kb of the memory. Full implementation of the protocol stack takes
less than 32Kb of memory. The network coordinator may require extra RAM for a node devices database
and for transaction and pairing tables. The 802.15.4 standard defines 26 primitives for the PHY and MAC
layers; probably another dozen will be added after finalizing the NWK layer specification. Those numbers
are still modest compared to 131 primitives defined for Bluetooth. Such a compact footprint enables you to
run Zigbee on a simple 8-bit microcontroller such as an HC08- or 8051-based processor core.

Figure 4: A typical ZigBee-enabled device will consist of RF IC and 8-bit microprocessor with
peripherals connected to an application sensor or actuators

ZigBee is not necessarily a replacement for the wireless standards you may already be familiar with but is
specifically designed for a unique set of applications, situations, and scenarios where existing wireless
standards fall short or won’t work at all.

ZigBee differs from existing networking standards to address several key areas:
• Supporting robust, fault tolerant mesh networks

• Low power requirements permitting a wide variety of truly

wireless devices which are battery powered with a long battery
life

• Simple network configuration and management allowing

devices to be added to existing networks with little if any
administrative work
The table below outlines some of the key characteristics of ZigBee and how it stacks up against other
common wireless standards.

ZigBee 802.11 Bluetooth UWB (Ultra Wireless IR Wireless

(Wi-Fi) Wide Band) USB
Data Rate 20, 40, and 11 & 54 1 Mbits/s 100-500 Mbits/s 62.5 Kbits/s 20-40 Kbits/s
250 Kbits/s Mbits/sec 115 Kbits/s
4 & 16 Mbits/s

Range 10-100 50-100 meters 10 meters <10 meters 10 meters <10 meters
meters (line of sight)

Networking Ad-hoc, peer Point to hub Ad-hoc, very Point to point Point to point Point to point
Topology to peer, star, small
or mesh networks

Operating 868 MHz 2.4 and 5 GHz 2.4 GHz 3.1-10.6 GHz 2.4 GHz 800-900 nm
Frequency (Europe)
900-928 MHz
(NA), 2.4 GHz
(worldwide)
Complexity Low High High Medium Low Low
(Device and
application
impact)
Power Very low (low High Medium Low Low Low
Consumption power is a
(Battery option design goal)
and life)
Security 128 AES plus 64 and 128 bit
application encyption
layer security

Other Devices can Device Device

Information join an connection connection
existing requires 3-5 requires up to
network in seconds 10 seconds
under 30ms

Typical Industrial Wireless LAN Wireless Streaming PC peripheral Remote

Applications control and connectivity, connectivity video, home connections controls, PC,
monitoring, broadband between entertainment PDA, phone,
sensor Internet devices such applications laptop links
networks, access as phones,
building PDA, laptops,
automation, headsets
home control
and
automation,
toys, games

Is ZigBee the only game in town?

No, while ZigBee can be used for a wide variety of networking topologies, in some cases, users may want
to build a network based more directly on the IEEE 802.15.4 standard to utilize features or capabilities
which are not supported or accessible using the current ZigBee standards.

For example, this might include beaconing or Guaranteed Time Slice support (GTS)..

With our broad range of experience, we can help you understand how ZigBee or other related networking
technologies fit into your plans and can help you make the right choice for your devices and applications.
 ZigBee FAQ
What is ZigBee?

What is IEEE802.15.4?

How is ZigBee different from other wireless standards (e.g. Bluetooth)?

What are the real-life applications of ZigBee?

How reliable is the data delivery?

How long is the battery life?

What are the cost considerations for ZigBee implementation?

How long is the Transmission Range?

How high is the Data Rate?

What is the Data Latency for ZigBee Networks?

How big is a Node?

How large/small a ZigBee Network can be?

How is the Data Security provided?

What is ZigBee Stack?

What Subunits can be on a Node?

What is called ZigBee Application?

What are the ZigBee Device Descriptors?

What is ZigBee Device Profile?

What is ZigBee Stack Profile?

What are the ZigBee Device Objects?

How does a Device/Service Discovery process work?

What are the Clusters, ZigBee Binding and Binding Table?

How is Addressing and Messaging done in a ZigBee network?

What types of ZigBee Devices exist in a network?

What Topologies are supported by ZigBee?

What is ZigBee network Gateway?

What is ZigBee?
ZigBee is an open global standard providing wireless networking based on the IEEE 802.15.4 standard and
taking full advantage of a powerful physical radio this standard specifies. ZigBee is the result of
collaborative efforts by a global consortium of companies known as the ZigBee Alliance. ZigBee includes
the following key features:

• Reliability and self-healing

• Support for a large number of nodes
• Fast, easy deployment
• Very long battery life
• Security
• Low cost
• Ability to be used globally
• Product interoperability
• Vendor independence

The term “ZigBee” originates from honeybees’ method of communicating newfound food sources. This
silent-but-powerful communication system is known as the “ZigBee Principle.” By dancing in a zig-zag
pattern, the bee is able to share critical information, such as the location, distance, and direction of a newly
discovered food source to its fellow hive members.

What is IEEE802.15.4?

IEEE 802.15.4 is a standard defined by the IEEE (Institute of Electrical and Electronics Engineers, Inc.) for
low-rate, wireless personal area networks (WPANs). This standard defines the ”physical layer” and the
“medium access layer.” The specification for the physical layer, or PHY, defines a low-power spread
spectrum radio operating at 2.4 GHz with a basic bit rate of 250 kilobits per second. There are also PHY
specifications for 915 MHz and 868 MHz that operate at lower data rates. For more information about IEEE
802.14.5 please refer to the official page.

How is ZigBee different from other wireless standards (e.g. Bluetooth)?

There is a multitude of standards that address mid to high data rates for voice, PC LANs, video, etc.
However, until ZigBee there hasn’t been a wireless network standard that meets the unique needs of
sensors and control devices. Sensors and control devices don’t need high bandwidth, but they do need low
latency and very low energy consumption for long battery lives and for large device arrays.

There are many proprietary wireless systems that function like ZigBee; inexpensive, very-low current
draining solutions that address a multitude of problems without requiring high data rates. These proprietary
systems were designed because there were no standards that met their requirements. These legacy
systems are now creating significant interoperability problems with each other and with newer technologies.

What are the real-life applications of ZigBee?

ZigBee is well suited for a wide range of building automation, industrial, medical and residential control and
monitoring applications. Examples include the following:

• Lighting controls
 • Automatic Meter Reading
• Wireless smoke and CO detectors
• HVAC control
• Heating control
• Home control, including units such as intrusion sensors, motion detectors, glass break detectors,
standing water sensors, loud sound detectors, etc.
• Environmental controls
• Blind, drapery and shade controls
• Medical sensing and monitoring
• Universal Remote Control to a Set-Top Box which includes Home Control
• Industrial and building automation
• Asset management

E.g., wireless sensors (temperature, humidity, shock, etc.) are installed into containers, where they form a
mesh network. Multiple containers in a ship form a mesh to report sensor data to the ship control center,
and further to a port control center

How reliable is the data delivery?

Reliable data delivery is critical to ZigBee applications. The underlying 802.15.4 standard provides strong
reliability through several mechanisms at multiple layers. For example, it uses 27 channels in three
separate frequency bands.

IEEE 802.15.4 provides three frequency bands for communications

The 2.4 GHz band is used worldwide and has 16 channels and a maximum over-the-air data rate of 250
Kbps. Lower frequency bands are also specified. The 902–928 MHz band serves the Americas and much of
the Pacific Rim, with 10 channels and a burst rate of 40 Kbps. European applications use one channel in
the 868–870 MHz band, which provides 20 Kbps burst rate. This rich assortment of frequencies lets
applications with the appropriate hardware configuration adjust in real time to local interference and/or
propagation conditions. Once on a specific channel, the 802.15.4 radio relies on a number of mechanisms
to ensure reliable data transmission, including binary phase shift keying (BPSK) in the 868/915 MHz bands
and offset quadrature phase shift keying (O-QPSK) at 2.4 GHz.

How long is the battery life?

The basic 802.15.4 node is fundamentally efficient in terms of battery performance. You can expect battery
lifetimes from a few months to many years as a result of a host of system’s power-saving modes and
battery-optimized network parameters, such as a selection of beacon intervals, guaranteed time slots, and
enablement/disablement options. Consider a typical security application, such as a magnetic reed switch
door sensor. The sensor itself consumes almost no electricity; it’s the radio that uses the bulk of the power.
The sensor is configured to have a “heartbeat” at one-minute intervals and to immediately send a message
when an event occurs. Assuming dozens of events per day, analysis shows that the sensor can still outlast
an alkaline AAA battery. The configuration allows the network to update the sensor parameters remotely,
change its reporting interval, or perform other remote functions and still have (theoretical) battery longevity
well beyond the shelf life.

What are the cost considerations for ZigBee implementation?

System, individual node, service, and battery costs are all important. ZigBee and 802.15.4 maximize utility
over this multidimensional space. There is sufficient flexibility in both standards to provide the sensor
system developer with an assortment of tradeoffs to optimize cost with respect to system performance. For
example, battery life can be optimized at the expense of service interval, and node cost and complexity can
be traded for network complexity. System simplicity and the underlying flexibility of 802.15.4 promise that
system developers will find ZigBee-based platforms more cost effective (at the same unit volumes) than
Bluetooth or proprietary bidirectional wireless solutions. While platform hardware cost is always a critical
part of the overall system cost, you must also consider the less tangible costs of system maintenance,
flexibility, and battery life.

How long is the Transmission Range?

ZigBee relies on the basic 802.15.4 standard to establish radio performance. As a short-range wireless
standard, 802.15.4 doesn’t try to compete with high-powered transmitters but instead excels in the ultra-
long battery life and low transmitter power. The standard specifies transmitter output power at a nominal –3
dBm (0.5 mW), with the upper limit controlled by the regulatory agencies of the region in which the sensor is
used. At –3 dBm output, single-hop ranges of 10 to more than 100 m are reasonable, depending on the
environment, antenna, and operating frequency band. Instead of pure power, ZigBee augments the basic
802.15.4 simple transmitter and protocol with an extensible, sophisticated network function that allows
multi-hop and flexible routing, providing communication ranges that can exceed the basic single-hop.
Indeed, depending on the data latency requirements, you can practically create networks that use dozens of
hops, with cumulative ranges in the hundreds to thousands of meters. Networks can have star, cluster tree,
or mesh structures; each comes with its own strengths.

How high is the Data Rate?

It may not be obvious why a simple temperature or intrusion sensor needs to transmit data at 250 Kbps (at
2.4 GHz) or even 20 Kbps (at 868 MHz), but the reason becomes clear when you consider the need to
prolong battery life. Even when the sensor is transmitting only a few bits or bytes, the system can be more
efficient if it transmits and receives the data quickly. For instance, a 0.5 mW transmitter consumes many
milliwatts whether it’s transmitting 100 or 100,000 bps. For any given quantity of data, transmitting at a
higher data rate allows the system to shut down the transmitter and receiver more quickly, saving significant
power. Higher data rates at a given power level mean there’s less energy per transmitted bit, which
generally implies reduced range. But both 802.15.4 and ZigBee value battery life more than raw range and
provide mechanisms to improve range while always concentrating on battery life.

What is the Data Latency for ZigBee Networks?

Sensor systems have a broad range of data-latency requirements. If sensor data are needed within tens of
milliseconds, as opposed to dozens of seconds, the requirement places different demands on the type and
extent of the intervening network. For many sensor applications, data latency is less critical than battery life
or data reliability. For simple star networks (many clients, one network coordinator), ZigBee can provide
latencies as low as ~16 ms in a beacon-centric network, using guaranteed time slots to prevent interference
from other sensors. You can further reduce latencies by several milliseconds if you forego the beacon
environment and are willing to risk potential interference from accidental data collision with other sensors on
the network. Data latency can also affect battery life. Generally, if you relax data-latency requirements, you
can assume that the battery life of the client nodes will increase. This is even truer of network hubs, which
are required to coordinate and supervise the network.

How big is a Node?

As silicon processes and radio technology progress, transceiver systems shrink in physical size. Forty years
ago, a simple radio transceiver was the size of a shoebox and weighed 10 kg. Today, a similar transceiver
might easily fit inside a thimble. In the case of ZigBee systems, the radio transceiver has become a single
piece of silicon, with a few passive components and a relatively non-critical board design. Microcontrollers
that have native ability to interface with sensors (e.g., built-in digital I/O and A/D converters) have eclipsed
even the radio’s rapid reduction in size. Today, the 8-bit MCU that hosts the application may already include
dozens of kilobytes of flash memory, RAM, and various hardware-based timer functions, along with the
ability to interface directly to the radio transceiver IC. The MCU requires only a few external passive
components to be fully functional. With the minimal overhead added by a ZigBee transceiver, the MCU can
often continue to host the application along with the ZigBee protocol. Therefore, the silicon system size of a
ZigBee solution (excluding sensors or batteries) is generally smaller than the batteries themselves. This
compact form factor lends itself well to innovative uses of radio technology in sensor applications. Certainly,
with the advances in silicon-based sensors that have been coming to market over the past five years, it’s
practical to design entire systems that take up less than 10–20% of the volume of current-generation
batteries. Integration is the key here, and even higher levels of integration are planned for future ZigBee
and 802.15.4 platforms.

How large/small a ZigBee Network can be?

The addressing space allows of extreme node density—up to 18,450,000,000,000,000,000 (264) devices
(64 bit IEEE address), which may form different topologies depending on customer needs: star, mesh,
cluster tree. At the same time, using local addressing, simple networks of more than 65,000 (2^16) nodes
can be configured, with reduced address overhead.

How is the Data Security provided?

It’s important to provide your sensor network with adequate security to prevent the data from being
compromised, stolen, or tampered with. IEEE 802.15.4 provides authentication, encryption, and integrity
services for wireless systems that allow systems developers to apply security levels as required. These
include no security, access control lists, and 32-bit to 128-bit AES encryption with authentication. This
security suite lets the developer pick and choose the security necessary for the application, providing a
manageable tradeoff against data volume, battery life, and system processing power requirements. The
IEEE 802.15.4 standard doesn’t provide a mechanism for moving security keys around a network; this is
where ZigBee comes in. The ZigBee security toolbox consists of key management features that let you
safely manage a network remotely. For those systems where data security is not critical (e.g., a set of
sensors monitoring microclimates in a forest), you may decide not to implement security features but
instead optimize battery life and reduce system cost. For the developer of an industrial or military perimeter
security sensor system, data security—and more importantly the ability to defend against sensor masking or
spoofing—may have the higher priority. In many ZigBee-approved applications, security will already be a
seamless part of the overall system.

What is ZigBee Stack?

ZigBee is based upon stack architecture that resembles standard OSI seven-layer model but defines only
those layers relevant to achieving functionality in the intended scope.

ZigBee Stack Architecture

The ZigBee stack architecture is made up of a set of blocks called layers. Each layer performs a specific set
of services for the layer above: a data entity provides a data transmission service and a management entity
provides all other services. Each service entity exposes an interface to the upper layer through a service
access point (SAP), and each SAP supports a number of service primitives to achieve the required
functionality. IEEE 802.15.4 standard defines the lower two layers: the physical (PHY) layer and the
medium access control (MAC) sub-layer. The ZigBee Alliance builds on this foundation by providing the
network (NWK) layer and the framework for the application layer, which includes the application support
(APS) sub-layer, the ZigBee device object (ZDO) and the manufacturer-defined application objects. IEEE
802.15.4 has two PHY layers that operate in two separate frequency ranges: 868/915 MHz and 2.4 GHz.
The lower frequency PHY layer covers both the 868 MHz European band and the 915 MHz band that is
used in countries such as the United States and Australia. The higher frequency PHY layer is used virtually
worldwide. The IEEE 802.15.4 MAC sub-layer controls access to the radio channel using a CSMA-CA
(Carrier Sense Multiple Access with Collision Avoidance) mechanism. Its responsibilities may also include
transmitting beacon frames, synchronization and providing a reliable transmission mechanism. 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 neighbors
and the storing of pertinent neighbor information are performed by the NWK layer. The NWK layer of a
ZigBee coordinator is responsible for starting a new network, when appropriate, and assigning addresses to
newly associated devices. For more information about the NWK layer please refer to
02130r10ZB_NWK_Network-Specification_V100 document of ZigBee specification v.1.0. The ZigBee
application layer consists of the APS sub-layer, 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 messages between bound devices. The responsibilities of the ZDO include defining
the role of the device within the network (e.g., ZigBee coordinator 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. The ZigBee stack is small in
comparison to other wireless standards. For network-edge devices with limited capabilities, the stack
requires about 4Kb of the memory. Full implementation of the protocol stack takes less than 32Kb of
memory. The network coordinator may require extra RAM for a node devices database and for transaction
and pairing tables.

What Subunits can be on a Node?

ZigBee network consists of a number of ZigBee Devices or Nodes. A node is a piece of hardware that
shares a single radio. Nodes can have several subunits, which are physical devices: sensors, switches,
lamps etc. Node subunits are modeled with Application Objects (AOs). In other words, Application Object is
a program that controls hardware device. ZigBee does not specify internal structure of this program. The
maximum number of subunits per node is 240. Each subunit is assigned an endpoint number, which is used
to identify it. Thus, each identifiable subunit in a node is assigned its own specific endpoint in the range 1-
240. In the figure below, there are two nodes, each containing a single radio. One node contains two
switches and the other contains 4 lamps.

Multiple subunits in a single node

What are the ZigBee Device Objects?

ZigBee Device Objects (ZDO) are an application solution residing within the Application Layer (APL) and
above the Application Support Sub-layer (APS) in the ZigBee stack architecture. ZDO are responsible for
defining the role of devices within the network (e.g., ZigBee coordinator 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. From Application point of
view, ZDO is an interface to the ZigBee stack (together with the Application Support Sub-layer).
How does a Device/Service Discovery process work?

Device discovery is the process whereby a ZigBee device can discover other ZigBee devices by initiating
queries that are broadcast or unicast addressed. Service discovery is the process whereby services
available on endpoints at the receiving device are discovered by external devices. Service means the
interfaces described by means of Device Descriptors set. Service discovery can be accomplished by
issuing a query for each endpoint on a given device, by using a match service feature (either broadcast or
unicast) or by having devices announce themselves when they join the network. Service discovery utilizes
the complex, user, node or power descriptors plus the simple descriptor further addressed by the endpoint
(for the connected application object). The service discovery process in ZigBee is critical for successfully
interfacing devices within the network. Through specific requests for descriptors on specified nodes,
broadcast requests for service matching and the ability to ask a device which endpoints support application
objects, a range of options are available for commissioning tools and applications.

What are the Clusters, ZigBee Binding and Binding Table?

A group of a number of Attributes (more or equal to one) is referred to as Cluster. Each Cluster has a
unique ID in the scope of a Profile. Cluster identifiers participate in Binding. Binding is a point-to-point
logical link between Input/Output ClusterIDs belonging to one Application Object and Input/Output
ClusterIDs of another Application Object. The information about which Cluster is bound between Nodes is
stored in a Binding Table. The example below clarifies the binding concept.

ZigBee binding and binding table

The use of a list of three entries in the binding table for switch 1 allows it to control three lamps, which could
also be in separate nodes (with their own ZigBee radios). It is also possible for one lamp to be controlled by
several switches: in this case there would be entries for each switch, all linked to the same lamp.

How is Addressing and Messaging done in a ZigBee network?

Each Node has a unique IEEE and NWK (ZigBee Network Layer) address that is assigned when a node
joins the network. Every subunit and thus Application Object in a node is addressed by endpoint number
unique within a node. An Application Object receives commands from outside world addressed to pair:
(node address, endpoint number). AO commands may be of two types: Key-Value Pair (KVP) and Generic
Messages.

What types of ZigBee Devices exist in a network?

According to IEEE MAC specification that introduces three device types, ZigBee specifies the following
ZigBee Devices:

• ZigBee Coordinator (MAC Network Coordinator). Maintains overall network knowledge; most
sophisticated of the three types; most memory and computing power
• ZigBee Router (MAC Full Function Device: Carries full 802.15.4 functionality and all features
specified by the standard).
• ZigBee End Device (MAC Reduced Function Device: Carriers limited functionality to control cost
and complexity. Also, may be MAC Full Function Device). That’s where the physical devices reside.
•
 •
•
•
•
•
•
•
•
•
•
•
•
• What Topologies are supported by ZigBee?
•
• The figure below illustrates the possible network configurations and the roles of the
devices.

ZigBee network topologies

As shown above, there are three different network topologies that are supported by Zigbee, namely the star,
mesh and cluster tree or hybrid networks. Each has its own advantages and can be used to advantage in
different situations. The star network is commonly used, having the advantage of simplicity. As the name
suggests it is formed in a star configuration with outlying nodes communicating with a central node. Mesh or
peer-to-peer networks enable high degrees of reliability. They consist of a variety of nodes placed as
needed, and nodes within range being able to communicate with each other to form a mesh. Messages
may be routed across the network using the different stations as relays. There is usually a choice of routes
that can be used and this makes the network very robust. If interference is present on one section of a
network, then another can be used instead. Finally there is what is known as a cluster tree network. This is
essentially a combination of star and mesh topologies.

What is ZigBee network Gateway?

There is another important type of ZigBee Node: Gateway. Its responsibilities are to interface a ZigBee
network into an external system, and to provide inter-network communications. Gateways clear the way for
ZigBee integration with existing and co-existing systems, for arrangement a global network that unites a
number of underlying ZigBee networks as well as other solutions and information systems. ZigBee Gateway
is intended to provide an interface between ZigBee and IP devices through an abstracted interface on the
IP side. The IP device is isolated from the ZigBee protocol by that interface. The ZigBee Gateway translates
both addresses and commands between ZigBee and IP.