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

2.3 Trust Center (TC) Link Key Updates

R21 devices joining a Zigbee 3.0 centralized network must initiate a TC Link Key update procedure upon joining the network. This unique TC Link Key is used for all encrypted APS-layer communication instead of the well-known counterpart. The Node Descriptor packet that is sent during network association procedure indicates the joining device's Zigbee version. R21 coordinators (acting as a trust center) can be configured to accept or reject legacy devices that do not initiate the TC Link Key update procedure. Note the mandatory unique TC Link Keys for each capable device leads to an increased flash requirement on the coordinator.

Figure 1. R21 TC Link Key Update Procedure SWRA615_ZigBee_Link_key_update.gif