ZigBee Concepts 1: Architecture Basics

ZigBee Concepts 1: Architecture Basics

Understanding Zigbee Mesh Networking

Introduction to Mesh Networking

  • The presentation begins by introducing Zigbee as a mesh networking technology, contrasting it with star networks commonly found in Wi-Fi or Bluetooth setups.
  • Star networks funnel all traffic through a central access point, creating a bottleneck and single point of failure for reliability in messaging.
  • In contrast, mesh networks allow each device to act as a relay point, providing multiple paths for communication and eliminating central points of failure.

Advantages of Zigbee Mesh Networks

  • Unlike repeaters in Wi-Fi networks, intermediate nodes in Zigbee can serve as sources or destinations for application layer communication.
  • This topology maximizes effective communication range while reducing costs by eliminating the need for specialized repeaters or central access points.
  • The flexibility of routing options within the mesh network enhances reliability and robustness compared to star or tree topologies.

Comparison of Network Topologies

  • A direct comparison illustrates that in star and tree topologies, routing opportunities are limited based on initial network construction.
  • In both cases, the PAN coordinator is essential for initiating the network; however, its role is less critical in mesh topology where redundancy exists.
  • The decentralized nature of mesh networks allows for scalability and adaptability over time.

Zigbee System Architecture Overview

  • The architecture consists of several layers: MAC (Medium Access Control), physical layer (related to radio access), and higher-level features defined by the Zigbee Alliance.
  • Governed by IEEE standard 802.15.4 since 2003, ensuring compliance across unlicensed ISM bands while coexisting with other standards.

Feature Sets and Application Profiles

  • There are two feature sets detailed in the specification: Zigbee and Zigbee Pro; with Zigbee Pro being more dominant.
  • Application profiles at the highest level are defined by working groups within the Zigbee Alliance focusing on specific use cases like building automation or smart energy.

Hardware Implementation Models

  • Two primary models exist: RFIC model (dedicated RF transceiver component paired with an external microcontroller).

Accessing Stack Functionality

Overview of Library API Calls

  • Access to stack functionality is primarily provided through Library API calls, which may involve shared access to microcontroller peripherals between the stack and application.
  • This sharing can impose constraints on application developers but ultimately results in lower material costs and a more compact design compared to other models.

Network Co-Processor Model

  • The next implementation discussed is the network co-processor (NCP), which integrates stack and low-level functionalities onto one chip for enhanced efficiency.
  • Interaction with the stack occurs via a serial interface (e.g., SPI or UART), using a proprietary protocol that allows for abstraction into libraries or operating system modules tailored to application needs.

Flexibility in Application Design

  • The NCP model provides flexibility by allowing designers to overlook many implementation details of the stack, depending on its specific implementation.
  • NCP firmware may offer additional features or abstractions that facilitate higher-level tasks suited for various applications.

Zigbee Compliance and Standards

Zigbee Networking Layer Implementation

  • The Zigbee networking layer, along with MAC and PHY layers, adheres to standard protocols ensuring interoperability with other designs.
  • Compliance testing at approved facilities is mandatory for products claiming Zigbee compliance; these facilities have experience with various networking designs.

Zigbee Alliance Structure

  • There are two types of Zigbee networking stacks: Zigbee and Zigbee Pro, each certified based on different feature sets. Non-Pro versions are considered legacy protocols.
  • The Zigbee Alliance oversees software stack specifications related to network security and application support layers while promoting interoperability standards.

Membership Benefits within the Alliance

  • Over 250 companies are part of the Zigbee Alliance, including manufacturers and tool providers. A 16-member Board manages it.
  • Different membership levels exist: promoters can influence specifications; participants can vote; adopters only view changes without voting rights.

Compliance Testing and Certification

Importance of Compliance Testing

  • All members can undergo compliance testing for certification of their products as per the Zigbee standard. Non-members can only access completed specifications.
Video description

This video provides a starting point for understanding how the ZigBee protocol stack is organized and how ZigBee applications are implemented on top of the stack. Also discussed is how this architecture model applies to system-on-chip (SOC) versus network coprocessor (NCP) platforms. http://www.silabs.com/products/wireless/zigbee/Pages/zigbee-getting-started.aspx Trademarks Notifications Silicon Laboratories Inc.®, Silicon Laboratories®, Silicon Labs®, SiLabs® and the Silicon Labs logo, CMEMS®, ClockBuilder®, DSPLL®, EFM™, EFM32™, EFR™, Energy Micro™, Energy Micro logo and combinations thereof, “the world’s most energy friendly microcontrollers,” Ember®, EZLink®, EZMac®, EZRadio®, EZRadioPRO®, Gecko™, ISOmodem®, Precision32®, ProSLIC®, Simplicity Studio™, SiPHY®, USBXpress® and others are trademarks or registered trademarks of Silicon Laboratories Inc. ARM, Cortex-M0/M0+/M3/M4, ARM mbed, mbed and Keil are trademarks or registered trademarks of ARM Limited. ZigBee is a registered trademark of ZigBee Alliance, Inc.All other products or brand names mentioned herein are trademarks of their respective holders.