Zigbee

Zigbee for Control and Sensor Networks

Technologies such as Wi-Fi and Bluetooth Classic provide high-speed data transfer and audio streaming. As smart buildings and the Industrial Internet of Things (IIoT) developed, another communication profile became useful. Control and sensor networks require simple operation, very low power consumption, and predictable exchange of short messages among many devices. Zigbee was designed to connect dozens or hundreds of simple devices, such as light bulbs, sensors, and switches, into one local network.

The name Zigbee refers to the waggle dance of honeybees. It is a concise reference to information exchange among many simple participants. Zigbee enables low-power devices to communicate across a building or facility. The technology was developed and promoted by the Zigbee Alliance, now operating within the Connectivity Standards Alliance (CSA). Zigbee provides open specifications for control and sensor networks.

Unlike Wi-Fi, which targets higher throughput, and classic Bluetooth, which often serves direct personal-area links, Zigbee trades peak rate for simple control traffic and long battery life. Small devices can form mesh networks, where routers forward messages between neighboring nodes. This arrangement can reduce dependence on a single link and support home automation, lighting, energy management, and industrial control systems. Actual resilience depends on router placement, link quality, and network configuration.

IEEE 802.15.4 PHY and MAC Layers

Zigbee uses the standardized radio and access functions defined by IEEE 802.15.4. The standard describes basic transmitter, receiver, frame, and MAC behavior, including channel access and addressing. Zigbee adds network formation, routing, security mechanisms, device roles, and application functions above those layers. The two specifications therefore describe different parts of one communication stack.

The IEEE 802.15.4 specification defines the two lowest layers of the network stack:

1. The Physical Layer (PHY): This layer is concerned with the radio itself. It defines the raw, physical characteristics of the wireless transmission.
   • Frequency Bands: IEEE 802.15.4 specifies operation in several unlicensed ISM bands. The most common Zigbee variant uses the 2.4 GHz band, shared with Wi-Fi and Bluetooth. Sub-gigahertz variants also exist, including 868 MHz in Europe and 915 MHz in regions where radio regulations permit it, including the Americas and Australia. Lower frequencies often pass through obstacles more effectively and may provide longer range, but the choice depends on the PHY and local regulation.
   • Modulation: The base 2450 MHz PHY uses DSSS with O-QPSK modulation. The base 868 and 915 MHz PHYs use DSSS with BPSK. Spreading supports reception in the presence of interference. It is not an encryption mechanism.
   • Data Rates: The standard defines several raw radio data rates. The typical value for the 2.4 GHz band is $250 \text{ kbps}$. The base 868 MHz and 915 MHz PHYs specify 20 kbps and 40 kbps respectively. Later regional PHY variants can use other parameters. Compared with Wi-Fi, these rates are low by design. Short payloads spend less time on the radio, which supports battery operation. These rates are sufficient for short control and measurement messages, while the small amount of traffic supports low power consumption.
2. The Media Access Control (MAC) Layer: This layer defines how devices access the shared wireless medium and how frames are formatted.
   • Message Framing: It defines the basic structure of a data packet, including addressing information.
   • Channel Access: It uses CSMA-CA (Carrier Sense Multiple Access with Collision Avoidance). Before transmitting, a device assesses whether the channel is occupied. When the channel is clear, it starts transmission. When it is busy, the device selects a backoff and tries again. A beacon-enabled network uses slotted CSMA-CA aligned with superframe boundaries. A network without beacons uses unslotted CSMA-CA, so devices do not align the start of their backoff with a beacon.

On these layers, Zigbee defines higher-level network and application protocols. They cover addressing, routing, device roles, security, and the data model used by mesh networks. They also specify how devices join the network and expose application functions to other nodes.

Zigbee Network Roles and Topology

A mesh network allows routers to forward messages between neighboring devices. In a star topology, every end device maintains a direct link to a central point. In Zigbee, a message from a sensor can pass through several routers, such as powered light bulbs, before reaching its destination. The number of available paths depends on node placement and link state. Zigbee defines three device roles that describe participation in the network.

1. Zigbee Coordinator (ZC):

   Every Zigbee network has exactly one Coordinator. It is commonly the first device to start the network, forms that network, and provides coordination functions. Its primary responsibilities include:

   • Initiating the Network: The Coordinator scans available channels and establishes the network, selecting a PAN ID and the parameters needed for devices to join.
   • Managing Security: In a centralized security model, the Coordinator can act as the Trust Center. The Trust Center is the security role associated with centralized network management. It authenticates joining devices and participates in distributing the network key. Current specifications also define distributed security models.
   • Logical Root and Routing: The Coordinator is the point at which the network is formed and it may forward messages like a router. Its logical role requires availability during network formation and management. In practical installations, a mains-powered hub such as an Amazon Echo Plus or a Samsung SmartThings Hub often contains the Zigbee Coordinator.
2. Zigbee Router (ZR):

   Routers provide the forwarding infrastructure of the mesh. A network can have multiple routers that forward messages and maintain relationships with child devices. Their key functions are:

   • Extending Network Range: A Router's main job is to relay messages from other devices, allowing the network to cover an area far larger than the range of any single device.
   • Hosting Applications: Like a Coordinator, a Router can also run its own applications (e.g., be a smart light bulb that also participates in routing).
   • Allowing Other Devices to Join: Routers can allow other Routers and End Devices to join the network through them.

   A Router must remain available to receive and relay messages. For that reason, practical deployments usually use mains power for routers. Most Zigbee smart plugs and permanently installed smart light bulbs can function as Routers, increasing the number of available links when a new device is added.

3. Zigbee End Device (ZED):

   End Devices are edge devices in the network. They perform a defined task, such as sensing or control, and can be optimized for very low power consumption. Their characteristics include:

   • Battery Operation: Most ZEDs are designed to run for years on a small battery. Examples include wireless door/window sensors, motion sensors, and battery-powered remote controls.
   • No Routing Function: An End Device does not relay messages for other devices. It communicates with its designated parent, either the Coordinator or a nearby Router.
   • Sleepy Behavior: A ZED can remain asleep for most of the time. It wakes to send a measurement, such as "the window has opened", or to check with its parent for pending messages. Polling frequency and the parent timeout affect power use and the retention of the device entry in the network.

Application Layer, Profiles, and Clusters

Establishing a network provides frame transport. Devices from different manufacturers also need a common application language. That language defines the meaning of commands such as "turn on," "dim to 50%," and "report temperature." Zigbee builds its application layer around Profiles, Clusters, and Endpoints.

1. Clusters: The Building Blocks of Functionality

   A Cluster is a standardized set of commands and attributes, or data values, that describe one function. It is a reusable block of functionality. For example:

   • The On/Off Cluster contains commands like On, Off, and Toggle, and an attribute that stores the current on/off state. Typical smart plugs and light bulbs implement this cluster.
   • The Level Control Cluster is used for dimming. It contains commands like Move to Level, Step Up, and Step Down, and an attribute for the current brightness level.
   • The Temperature Measurement Cluster has a read-only attribute that reports the current measured temperature.
2. Endpoints: Virtual Devices on a Physical Device

   A single physical device can have multiple functions. For example, a multi-socket smart power strip can control three separate outlets and monitor the power consumption of each. In Zigbee, each of these distinct functions is represented by an Endpoint. The power strip would have at least three endpoints, each implementing the On/Off Cluster, allowing each socket to be controlled independently. This provides a clean way to model complex devices.

3. Profiles: The Rulebook for Interoperability

   A Profile describes a set of device types and required clusters for a particular market or application. It can specify a dimmable light, a motion sensor, and the functions required for each device type. Historically, there were several competing profiles:

   • Zigbee Home Automation (ZHA): A broad profile for smart home devices such as sensors, lights, and thermostats.
   • Zigbee Light Link (ZLL): A simplified profile focused specifically on lighting products, enabling features like easy, touch-link commissioning.

   Different profiles made device selection more difficult. A ZLL-certified bulb might not support the set of functions expected by a ZHA-compatible hub. The Zigbee Alliance introduced Zigbee 3.0 to unify core device behavior and the application model.

Zigbee 3.0 and Interoperability

Zigbee 3.0 unifies core device behavior and the application layer in response to issues caused by multiple earlier profiles. It is not a new radio technology. It is a set of application-layer rules that uses shared elements from profiles such as ZHA and ZLL and bases interoperability on device types, clusters, and certification.

Zigbee 3.0 certification confirms compliance with a defined set of requirements. Shared clusters and device types make cooperation easier, while a specific function still depends on supported clusters, manufacturer extensions, versions, and commissioning. Zigbee 3.0 also uses two security levels. AES-128-CCM provides authentication and confidentiality at the network and APS levels, while key distribution depends on the security model and the Trust Center role. The network key protects network-layer communication, while APS link keys can protect application support relationships. This scope makes it possible to assess interoperability for a particular set of devices without promising automatic cooperation between every product.