| |
|
2004 |
2006 |
2007 |
PRO |
| Interference avoidance |
|
|
|
|
| |
Network coordinator selects best available RF channel/Network ID at startup time. |
 |
|
|
|
| |
Support for ongoing interference detection under operational conditions and wholesale adoption of a new operating RF channel and/or Network ID. |
|
|
|
|
| Automated/distributed address management |
|
|
|
|
|
| |
Device addresses automatically assigned using a hierarchical, distributed scheme. |
|
|
|
|
|
| |
Device addresses automatically assigned using a stochastic scheme. |
|
|
|
|
|
| Group addressing |
|
|
|
|
|
| |
Devices can be assigned to groups, and whole groups can be addressed with a single frame; thereby reducing network traffic for packets destined for groups. |
|
|
|
|
|
| Centralized data collection |
|
|
|
|
|
| |
Low-overhead data collection by ZigBee Coordinator explicitly supported. |
|
|
|
|
|
| |
Low-overhead data collection by other devices supported under special circumstances (e.g. with Tree Routing). |
|
|
|
|
|
| |
Many-to-one routing allows the whole network to discover the aggregator in one pass. |
|
|
|
|
|
| |
Source routing allows the aggregator to respond to all senders in an economical manner. |
|
|
|
|
|
| Security |
|
|
|
|
|
| |
128-bit AES encryption with 32-bit Message Integrity Code (MIC) and frame counters to assure message freshness. |
|
|
|
|
|
| |
Security applied at the NWK layer by default, with key rotation to prevent hacking of the NWK key. |
|
|
|
|
|
| |
Higher-layer security supported. |
|
|
|
|
|
| |
Trust Center application, operating on the ZigBee Coordinator, manages trust on behalf of network devices and acts as the central authority on what devices can join the network. |
|
|
|
|
|
| |
Trust Center can run on any device in the network. |
|
|
|
|
|
| |
"High Security" mode available, which is selectable by Trust Center policy, and requires Application Layer Link keys; peer-entity authentication; and peer-to-peer key establishment using Master Keys. |
|
|
|
|
|
| Network scalability |
|
|
|
|
|
| |
Network scales up to the limits of the addressing algorithm. Typically, networks with tens to hundreds of devices are supported. |
|
|
|
|
|
| |
An addressing algorithm that relaxes the limits on network size. Networks with hundreds to thousands of devices are supported. |
|
|
|
|
|
| Message size |
|
|
|
|
| |
< 100 bytes. Exact size depends on services employed, such as security. |
|
|
|
|
| |
Large messages, up to the buffer capacity of the sending and receiving devices, are supported using Fragmentation and Reassembly. |
|
|
|
|
| Standardized commissioning |
|
|
|
|
| |
Standardized startup procedure and attributes support the use of commissioning tools in a multi-vendor environment. |
|
|
|
|
| Robust mesh networking |
|
|
|
|
| |
Fault tolerant routing algorithms respond to changes in the network and in the RF environment. |
|
|
|
|
| |
Every device keeps track of its "neighborhood"; thereby further improving reliability and robustness. |
|
|
|
|
| Cluster Library support |
|
|
|
|
| |
The ZigBee Cluster Library, as an adjunct to the stack, standardizes application behavior across profiles and provides an invaluable resource for profile developers. |
|
|
|
|
The ZigBee Alliance creates technology standards designed to create a thriving market for a variety of uses.