SWRA615A June   2019 CC1352P , CC1352R , CC2530 , CC2531 , CC2538 , CC2652P , CC2652R , CC2652R7 , CC2652RB , CC2652RSIP

 

  1.   What's New in Zigbee 3.0
    1. 1 Overview
    2. 2 Zigbee PRO Specification
      1. 2.1 Child Device Management
      2. 2.2 Parent Announce Command
      3. 2.3 Trust Center (TC) Link Key Updates
      4. 2.4 Install Codes
      5. 2.5 Outgoing NWK Frame Counter
      6. 2.6 Changes to Network Joining
      7. 2.7 New Mandatory Command Support
      8. 2.8 Optional Distributed Networks
    3. 3 Base Device Behavior (BDB)
      1. 3.1 BDB Commissioning Modes
      2. 3.2 BDB Security
      3. 3.3 Reset Methods Available with BDB
    4. 4 Green Power Basic Proxy
    5. 5 Zigbee Cluster Library
    6. 6 Zigbee Application Architecture
      1. 6.1 Zigbee Node
      2. 6.2 Zigbee Cluster
      3. 6.3 Zigbee Device
    7. 7 Zigbee Lighting & Occupancy (ZLO) Device Specification
    8. 8 Zigbee 3.0 Certification
    9. 9 References
      1.      Trademarks

6.2 Zigbee Cluster

Zigbee Clusters are defined by the ZCL specification. Each cluster specifies a set of cluster attributes, a set of commands generated and received, and other associated behavior. Attributes, commands, and behaviors for each cluster can be either mandatory or optional depending on the ZCL specification. Each Zigbee cluster has a server and client implementation. Generally, the device that supports the server side of the cluster is the one that implements the actual hardware functionality which the cluster intends to interact with. Using the example of a light and switch design, the light implements the On/Off server since it is what the On/Off command intends to control. For a Temperature Measurement cluster, the temperature sensor implements the Temperature Measurement server since it is the one that takes the actual temperature measurements using hardware. Each Zigbee cluster is defined as either a Utility or Application cluster, and either a Type 1 or Type 2 cluster.

  • Utility Cluster: Not part of the functional operation of the product, for example one used for device commissioning, configuration, discovery, or diagnostic.
  • Application Cluster: Generates persistent functional application transactions between client and server sides of a cluster, and the targets of these transactions are determined when binds are created between matching client/server clusters. Some examples are:
    • On/Off cluster: Switch (On/Off cluster client) sends commands to a light (On/Off cluster server)
    • Temperature Measurement cluster - Temperature sensor (Temperature Measurement cluster server) sends reports to a thermostat (Temperature Measurement cluster client)
  • Type 1 Cluster: Initiates transactions from the client side of the cluster to the server side. With BDB F&B, binds are created on the client side device. This makes the client device the BDB F&B initiator. The On/Off cluster is an appropriate example as the On/Off client sends commands to the On/Off server.
  • Type 2 Cluster: Initiates transactions from the server side of the cluster to the client side. With BDB F&B, binds are created on the server side device. This makes the server device the BDB F&B initiator. The Temperature Meas cluster is an example since the Temperature Measurement server sends attribute reports to the Temperature Measurement client.