Documente Academic
Documente Profesional
Documente Cultură
top 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?
top 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.
There is a multitude of standards that address mid to high data rates for voice, PC LANs, video, etc. However, until ZigBee there hasnt been a wireless network standard that meets the unique needs of sensors and control devices. Sensors and control devices dont 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.
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.
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 902928 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 868870 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.
change its reporting interval, or perform other remote functions and still have (theoretical) battery longevity well beyond the shelf life.
top 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 its 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 theres 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.
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 radios 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, its practical to design entire systems that take up less than 1020% 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.
Its 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 doesnt 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 securityand more importantly the ability to defend against sensor masking or spoofingmay have the higher priority. In many ZigBeeapproved applications, security will already be a seamless part of the overall system.
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.
Node specifies type and capabilities of the node/LI> Node power gives a dynamic indication of the power status of the node. Simple contains information specific to each endpoint contained in this node. Complex (optional) contains extended information for each of the device descriptions contained in this node. User (optional) contains information that allows the user to identify the device using a user-friendly character string, such as "Bedroom TV" or "Stairs light."
ZigBee theres one-to-one correspondence of Application Profiles and Applications. Profiles are developed by ZigBee vendors to address solutions to specific technology needs. Profiles are simultaneously a means to unify interoperable technical solutions within the ZigBee standard, as well as to focus usability efforts within a given marketing area. For example, it is expected that vendors of lighting equipment will want to provide ZigBee profiles that interoperate with several varieties of lighting types or controller types. Application Profile is not an entity or some kind of software, but rather an agreement on messages, message formats and processing actions that enable applications residing on separate devices to send commands, request data and process commands/requests to create an interoperable, distributed application. The figure below shows a graphical representation of a part of Home Control Lightning (HCL) profile developed by ZigBee Alliance for home lightning management.
Part of HCL profile There are Switch, Remote Control, Occupancy Sensor, and Switching Load Controller depicted (other devices are missing here). Attributes at the left side of devices are input attributes; at the right, output attributes. As shown, the output on/off attribute for the Switch Remote Control is the input for the Switching Load Controller.
Stack Profiles are a convention on specific ZigBee Protocol Stack Settable Values established to provide interoperability in specified markets. Stack Settable Values are settings that need to be chosen so that differing ZigBee implementations and networks will be able to interoperate. The following stack profiles have been identified for ZigBee v1.0:
Home Controls intended for use with the Home Controls-Lighting application profile and all profiles written for complementary use with Home Controls-Lighting. Building Automation intended for use with future profiles targeted to building automation solutions. Plant Control intended for use with future profiles targeted to plant control solutions.
Additionally, a category of stack profile called "Network Specific" is proposed which indicates that no specific Stack Profile is in use; rather, the stack parameters are defined by the elemental values employed as stack parameters.
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.
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.
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.
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). Thats where the physical devices reside.
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.
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.