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

BDB Commissioning Modes

There are four types of commissioning modes available through BDB:

  • Touchlink
  • Network Steering
  • Network Formation
  • Finding and Binding (F&B)

Touchlink is the Zigbee Light Link profile equivalent for proximity-based commissioning. Network Steering enables permit joining (to open the network for joining), but only if the device is already on a network. If an end device or router type is not currently in a network, the device will try to join an existing network and only continue with permit joining if this procedure is successful. For coordinators (and routers if distributed networks are allowed), Network Formation will be invoked if Network Steering determines that there is not a suitable network to join. This will create a new centralized security network for coordinators or a distributed security network for router types.

F&B is invoked once the device is in a network and looks for other nodes that are also in F&B mode and interested in exchanging data from matching clusters. If matching clusters are found in other nodes, the appropriate binds are made. Once bindings are formed by the F&B procedure, any clusters with bindings that support ZCL attribute reporting will start doing so immediately to the destination set in the binding table entry. The BDB specification also mandates automatic ZCL attribute reporting for all reportable attributes. Users can configure a default reporting interval and reportable change amount.