ZigBee Green Power Basics
©Rafael Han (mq_han <at> hotmail.com)
Hello ZigBee
Traditional ZigBee network works like this:
They talk in ZigBee messages
ZigBee messages are based on ZigBee (Pro) stack, like this:
… and in ZCL syntax
Normally ZCL is used, however you are free to use your own for closed systems
- Basic
- Identify
- Groups
- Scenes
- On/Off
- Level Control
- ……
But ultra-low devices cannot afford that much
Like the energy-harvesting switch, you need to be OUTMAN to generate enough power for ZigBee!
ZGP comes to rescue
ZGP operates on a lean stack compared to ZigBee Pro stack, like:
And don’t be wordy
ZGP talks just enough. No more.
- ZigBee says ON by using ZCL on/off cluster + network security
60 bytes
- ZGP says ON by using GPDF ON
24 bytes
ZigBee needs to understand ZGP
Compact frames requires explanation. So GP feature should be added to ZigBee Pro stack:
Inside GP feature
GP feature bottom to up like:
ZigBee forwards GPDF
GPDF gets transported in ZigBee networks via GP cluster messages, an extension to ZCL.
Act as GP Infrastructure Devices
So we call them GPP & GPS, respectively. They are GP infrastructure devices.
Proxy functionality
Proxy forwarding can be:
- unicast
- groupcast
- use multiple proxies within the range of GPD
Proxy Info Storage
Put GP proxy information in proxy table within GPP/GPS -> RO attribute
Sink Info Storage
Put sink information within GPS -> RO attribute
How to Process GP Command ?
So we need translation table -> defines mapping from GP command to ZCL command
