ZigBee Layer PICS and Stack Profiles

1
5 ZigBee Document 08006r03

6 ZigBee-2007 Layer PICS and Stack Profiles
7
8 Revision 03
9
10 June 2008
11 Sponsored by:
12 ZigBee Alliance
13 Accepted for release by:

14 This document has not yet been accepted for release by the ZigBee Alliance Board of
15 Directors.
16 Abstract:
17
18 Keywords:
19 ZigBee, ZigBee-Pro, Stack profile, Architecture.
Copyright © 1996-2008 by the ZigBee Alliance.

2400 Camino Ramon, Suite 375, San Ramon, CA 94583, USA
http://www.zigbee.org
All rights reserved.
Permission is granted to members of the ZigBee Alliance to reproduce this document for their own use or the use of other ZigBee Alliance
members only, provided this notice is included. All other rights reserved. Duplication for sale, or for commercial or for-profit use is strictly
prohibited without the prior written consent of the ZigBee Alliance.
ZigBee-2007 Layer PICS and Stack Profiles ZigBee Document 08006r03, June 2008
1 Copyright © ZigBee Alliance, Inc. (2008). All rights Reserved. This information within this document is the property of the
2 ZigBee Alliance and its use and disclosure are restricted.
3 Elements of ZigBee Alliance specifications may be subject to third party intellectual property rights, including without limitation,
4 patent, copyright or trademark rights (such a third party may or may not be a member of ZigBee). ZigBee is not responsible and
5 shall not be held responsible in any manner for identifying or failing to identify any or all such third party intellectual property
6 rights.
7 This document and the information contained herein are provided on an “AS IS” basis and ZigBee DISCLAIMS ALL
8 WARRANTIES EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO (A) ANY WARRANTY THAT THE USE OF THE
9 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OF THIRD PARTIES (INCLUDING WITHOUT LIMITATION
10 ANY INTELLECTUAL PROPERTY RIGHTS INCLUDING PATENT, COPYRIGHT OR TRADEMARK RIGHTS) OR (B) ANY
11 IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE OR NON-
12 INFRINGEMENT. IN NO EVENT WILL ZIGBEE BE LIABLE FOR ANY LOSS OF PROFITS, LOSS OF BUSINESS, LOSS OF
13 USE OF DATA, INTERRUPTION OF BUSINESS, OR FOR ANY OTHER DIRECT, INDIRECT, SPECIAL OR EXEMPLARY,
14 INCIDENTIAL, PUNITIVE OR CONSEQUENTIAL DAMAGES OF ANY KIND, IN CONTRACT OR IN TORT, IN
15 CONNECTION WITH THIS DOCUMENT OR THE INFORMATION CONTAINED HEREIN, EVEN IF ADVISED OF THE
16 POSSIBILITY OF SUCH LOSS OR DAMAGE. All Company, brand and product names may be trademarks that are the sole
17 property of their respective owners.
18 The above notice and this paragraph must be included on all copies of this document that are made.
19
20 ZigBee Alliance, Inc.
21 2400 Camino Ramon, Suite 375
22 San Ramon, CA 94583, USA
23
Page ii Copyright © 2008, The ZigBee Alliance. All rights reserved.

This is an unaccepted ZigBee specification draft, subject to change.
ZigBee Document 08006r03, June 2008 ZigBee-2007 Layer PICS and Stack Profiles
1 Contact information
2 Much of the information in this document is preliminary and subject to change. Members of the ZigBee
3 Working Group are encouraged to review and provide inputs for this proposal. For document status
4 updates, please contact:
5 Don Sturek,
6 Texas Instruments,
7 1455 Frazee Road, Suite 800
8 San Diego, CA 92108
9 E-Mail: dsturek@ti.com
10 Phone: +1-619-497-3814
11 Fax: +1-619-497-3840
12
13
14 You can also submit comments using the ZigBee Alliance reflector. Its web site address is:
15 www.zigbee.org
16 The information on this page should be removed when this document is accepted.
Copyright © 2008, The ZigBee Alliance. All rights reserved. Page iii
1 Participants
2 The following is a list of those who were members of the ZigBee Alliance Core Stack Working Group
3 leadership when this document was released:
4 Phil Jamieson: Chair

5 Mads Westergreen: Vice Chair
6 Don Sturek: Chief Technical Editor
7 Tim Gilman: Secretary
8
9
10 The editing team was composed of the following members:
11 Robert Cragie
12 Phil Jamieson
13 Bob Old
14 Phil Rudland
15 Zachary Smith
16 Don Sturek
17
18
19
Page iv Copyright © 2008, The ZigBee Alliance. All rights reserved.

1 Table of Contents
2 1 Introduction..............................................................................................................................................1
3 1.1 Scope...............................................................................................................................................1
4 1.2 Purpose............................................................................................................................................1
5 2 References................................................................................................................................................2
6 2.1 ZigBee Alliance documents ............................................................................................................2
7 2.2 IEEE documents..............................................................................................................................2
8 3 Definitions................................................................................................................................................3
9 4 Acronyms and abbreviations....................................................................................................................4
10 5 General description ..................................................................................................................................5
11 6 Knob settings............................................................................................................................................6
12 6.1 Introduction .....................................................................................................................................6
13 6.2 Network settings..............................................................................................................................6
14 6.3 Application settings.........................................................................................................................6
15 6.4 Security settings ..............................................................................................................................7
16 7 Functional description..............................................................................................................................8
17 7.1 Device roles.....................................................................................................................................8
18 7.2 ZigBee: Compatibility with Other Feature sets.............................................................................8
19 7.3 ZigBee-PRO: Compatibility with Other Feature sets....................................................................9
20 7.4 Binding tables..................................................................................................................................9
21 7.5 Multicast mechanism and groups ....................................................................................................9
22 7.6 Trust Center Policies and Security Settings ....................................................................................9
23 7.7 Battery powered devices ...............................................................................................................10
24 7.8 Mains powered devices .................................................................................................................10
25 7.9 Persistent storage...........................................................................................................................10
26 7.10 Address Reuse...............................................................................................................................10
27 7.11 Duty cycle limitations and fragmentation .....................................................................................10
28 7.11.1 Vulnerability join..............................................................................................................11
29 7.11.2 Pre-installation..................................................................................................................11
30 7.12 Security .........................................................................................................................................11
31 7.12.1 Security Modes within PRO Networks.............................................................................12
32 8 Protocol implementation conformance statement (PICS) proforma.......................................................13

33 8.1 Abbreviations and special symbols ...............................................................................................13
34 8.2 ZigBee device types ......................................................................................................................13
35 8.3 IEEE 802.15.4 PICS......................................................................................................................14
36 8.3.1 FDT2 and FDT3 network join options..............................................................................14
37 8.3.2 IEEE 802.15.4 PHY..........................................................................................................15
38 8.3.3 IEEE 802.15.4 MAC.........................................................................................................16
39 8.4 Network layer PICS ......................................................................................................................31
40 8.4.1 ZigBee network frame format...........................................................................................31
41 8.4.2 Major capabilities of the ZigBee network layer................................................................31
42 8.5 Security PICS ................................................................................................................................53
43 8.5.1 ZigBee security roles ........................................................................................................53
44 8.5.2 ZigBee trust center capabilities.........................................................................................54
45 8.5.3 Modes of operation ...........................................................................................................55
46 8.5.4 Security levels...................................................................................................................55
47 8.5.5 NWK layer security ..........................................................................................................57
48 8.5.6 APS layer security ............................................................................................................59
49 8.5.7 Application layer security.................................................................................................64
Copyright © 2008, The ZigBee Alliance. All rights reserved. Page v
1 8.6 Application layer PICS..................................................................................................................69

2 8.6.1 ZigBee security device types ............................................................................................69
3 8.6.2 ZigBee APS frame format.................................................................................................70
4 8.6.3 Major capabilities of the ZigBee application layer ...........................................................71
Page vi Copyright © 2008, The ZigBee Alliance. All rights reserved.

1 List of Figures
Copyright © 2008, The ZigBee Alliance. All rights reserved. Page vii
1 List of Tables
2 Table 1 – Document revision change history ................................................................................................ ix

3 Table 2 – Network settings for this feature set ................................................................................................6
4 Table 3 – Application settings for this feature set ...........................................................................................6
5 Table 4 – Security settings for this feature set.................................................................................................7
6
Page viii Copyright © 2008, The ZigBee Alliance. All rights reserved.
1 Change history
2 Table 1 shows the change history for this specification.
3 Table 1 – Document revision change history
Revision Description
00 Original version as a merge of 064321r08, 074855r04, 04319r01,

04300r08, 043171r04, 064147r07.
01 Snapshot version provided to Core Stack and Qualification Working

Groups to validate format of the combined document
02 Major PICS update following many test events. Overhaul of the

formatting.
03 Final updates during the June 2008 ZigBee members meeting in

Atlanta.
Copyright © 2008, The ZigBee Alliance. All rights reserved. Page ix

1 1 Introduction
2 To evaluate conformance of a particular implementation, it is necessary to have a statement of which
3 capabilities and options have been implemented for a given standard. Such a statement is called a
4 protocol implementation conformance statement (PICS).
5 1.1 Scope
6 This document provides the protocol implementation conformance statement (PICS) proforma for
7 ZigBee specification (053474r17) in compliance with the relevant requirements, and in accordance
8 with the relevant guidance, given in ISO/IEC 9646-7.
9 1.2 Purpose
10 The supplier of a protocol implementation claiming to conform to the ZigBee standard shall complete
11 the following PICS proforma and accompany it with the information necessary to identify fully both
12 the supplier and the implementation.
13
14 The protocol implementation conformance statement (PICS) of a protocol implementation is a
15 statement of which capabilities and options of the protocol have been implemented. The statement is in
16 the form of answers to a set of questions in the PICS proforma. The questions in a proforma consist of
17 a systematic list of protocol capabilities and options as well as their implementation requirements. The
18 implementation requirement indicates whether implementation of a capability is mandatory, optional,
19 or conditional depending on options selected. When a protocol implementer answers questions in a
20 PICS proforma, they would indicate whether an item is implemented or not, and provide explanations
21 if an item is not implemented.
Copyright © 2008, The ZigBee Alliance. All rights reserved. Page 1

1 2 References
2 The following standards and specifications contain provisions, which through reference in this
3 document constitute provisions of this specification. All the standards and specifications listed are
4 normative references. At the time of publication, the editions indicated were valid. All standards and
5 specifications are subject to revision, and parties to agreements based on this specification are
6 encouraged to investigate the possibility of applying the most recent editions of the standards and
7 specifications indicated below.
8 2.1 ZigBee Alliance documents
9 [R1] ZigBee document 053474r17, ZigBee specification release 17, ZigBee Technical Steering
10 Committee
11 [R2] ZigBee 04140r05, ZigBee Protocol Stack Settable Values (knobs) release 05, ZigBee
12 Architecture Working Group
13 [R3] ZigBee document 04319r01, ZigBee IEEE 802.15.4 PHY & MAC Layer Test Specification
14 release r01, ZigBee Application Working Group
15 [R4] ZigBee document 084xxx, ZigBee Trust Centre Policies, ZigBee Security Task Group.
16 2.2 IEEE documents
17 [R5] IEEE Standards 802, Part 15.4: Wireless Medium Access Control (MAC) and Physical Layer
18 (PHY) specifications for Low Rate Wireless Personal Area Networks (LR-WPANs), IEEE,
19 April 2003.
Page 2 Copyright © 2008, The ZigBee Alliance. All rights reserved.

1 3 Definitions
Feature set A collection of parameter values and configuration settings,
collectively and loosely referred to as “knobs” in [R2], that determine
the specific performance of a ZigBee stack variant and govern
interoperability between stacks provided by different vendors.
ZigBee coordinator An IEEE 802.15.4-2003 PAN coordinator operating in a ZigBee

network.
ZigBee end device An IEEE 802.15.4-2003 RFD or FFD participating in a ZigBee

network, which is neither the ZigBee coordinator nor a ZigBee
router.
ZigBee router An IEEE 802.15.4-2003 FFD participating in a ZigBee network,

which is not the ZigBee coordinator but may act as an IEEE
802.15.4-2003 coordinator within its personal operating space, that is
capable of routing messages between devices and supporting
associations.

1 4 Acronyms and abbreviations

AODV Ad-Hoc On-Demand Distance Vector
FFD IEEE 802.15.4 Full Function Device
IEEE Institute of Electrical and Electronic Engineers
PICS Protocol Implementation Conformance Statement
RFD IEEE 802.15.4 Reduced Function Device

1 5 General description
2 The sections in this document are:
3 • Knob settings – details of values to be used for parameters specified in the ZigBee
4 specification for tuning the operation of the ZigBee stack, including network, application and
5 security settings.
6 • Functional description – further operational restrictions to be applied to all devices in this

7 feature set where various approaches are otherwise supported by the ZigBee specification.
8 • Protocol implementation conformance statement (PICS) – a formal definition of functionality

9 to be implemented in these devices.
10 These requirements aim to allow a designer to make necessary assumptions about what settings,
11 features and safeguards will be in place in the networks in which a device will be deployed.
12 For clarity, settings applied to the ZigBee feature set will be marked with the string ZigBee and
13 settings applied to the ZigBee-PRO feature set will be marked with the string ZigBee-PRO.

1 6 Knob settings
2 6.1 Introduction
3 This section specifies values for parameters specified in the ZigBee specification for tuning the
4 operation of the ZigBee and ZigBee-PRO stack. This section describes settings for both ZigBee and
5 ZigBee-PRO feature sets applied to the ZigBee-2007 Specification ([R1])
6 6.2 Network settings
7 The network settings for the ZigBee and ZigBee-PRO feature sets are, for the most part, described in
8 the restricted PICS captured in Section 8.4. Those setting not covered by the PICS are listed in Table 2.
9 Table 2 – Network settings for this feature set
Parameter Name Setting Comments
nwkTransactionPersistenceTime 0x01f4 Note that this value essentially “covers” the MAC
ZigBee
attribute of the same name.
Note also that, while [R1] implies that this quantity has
meaning only in beacon-enabled networks, it may
actually be used in beaconless networks as well and, in
ZigBee-
that case, is a multiplier for aBaseSuperframeDuration.

PRO
The value here yields a persistence time of 7.68

seconds using the 2.4Ghz symbol rate from [R5] in a
non-beaconed network.
nwkReportConstantCost FALSE The NWK layer in PRO shall always calculate routing
ZigBee
cost on the basis of neighbor link cost and never report

constant cost.
ZigBee-
PRO
10 6.3 Application settings
11 The application settings for the ZigBee and ZigBee-PRO feature sets are, for the most part, described
12 in the restricted PICS captured in Section 8.6. Those setting not covered by the PICS are listed in Table
13 3.
14 Table 3 – Application settings for this feature set
Number of active endpoints per - As the responsibility to arrange for caching of service
ZigBee
sleeping ZigBee end device discovery information lies with the end device itself,
(maximum) this parameter is not restricted.
ZigBee-
PRO

Config_NWK_Leave_removeChildr FALSE
ZigBee
en
ZigBee-
PRO
1 6.4 Security settings
2 The security settings for the ZigBee and ZigBee-PRO feature sets are listed in Table 4.
3 Table 4 – Security settings for this feature set
apsSecurityTimeoutPeriod 50ms * (2*NWK Maximum Where AES Encrypt/Decrypt times = 200ms, and
Depth) + (AES Encrypt/Decrypt
times) Where NWK Maximum Depth is assumed to be 5,
meaning every device in the network can be reached in
ZigBee
not more than 10 hops.
I.e. 700 milliseconds. Note that this timeout assumes

worst case AES engine speeds and is not indicative of
expected performance for most devices.
Where AES Encrypt/Decrypt times = 200ms, and
Where NWK Maximum Depth is assumed to be 15,

ZigBee-
meaning every device in the network can be reached in

PRO
not more than 30 hops.
I.e. 1.7 seconds. Note that this timeout assumes worst

case AES engine speeds and is not indicative of
expected performance for most devices.

1 7 Functional description
2 For the most part, the functioning of ZigBee and ZigBee-PRO with respect to the NWK layer, the APS
3 layer and the ZDO is described in [R1]. However, the configuration details and operational
4 requirements for devices operating under the ZigBee and ZigBee-PRO feature sets lead to some special
5 functional considerations, which are detailed here.
6 7.1 Device roles
7 The basic roles performed by ZigBee devices in ZigBee and ZigBee-PRO networks are determined by
8 their device type:
9 • The ZigBee coordinator initiates network formation, choosing the network channel, PAN ID
10 and extended PAN ID in the process, and thereafter should act as a ZigBee router. It may also
11 perform the roles of trust center and Network Channel Manager. With respect to binding, the
12 ZigBee coordinator is expected to handle end device bind request on behalf of all end devices
13 in the network but is not expected to be a global binding repository for the network.
14 • ZigBee routers are called upon to relay traffic on behalf of other devices in the network and,
15 in particular, are required to act as routing agents on behalf of their end device children, which
16 will typically not have the neighbor tables, routing tables, route discovery tables or broadcast
17 transaction tables required to perform routing. Since end devices may sleep, ZigBee routers
18 and ZigBee coordinators in their role of ZigBee routers may cache discovery information on
19 behalf of their sleeping end-device children. A ZigBee router may perform the role of trust
20 center and Network Channel Manager.
21 • ZigBee end devices are joined to and managed by ZigBee routers or the ZigBee coordinator.
22 Because ZigBee-PRO networks are beaconless, there is no built-in synchronization
23 mechanism between sleeping end devices and their router parents. End devices are free to set
24 their own duty cycles within the broad polling limits defined by this feature set. End devices
25 that wish to have their discovery information cached by their parent or some other device are
26 responsible for using the discovery cache commands to achieve this.
27 Under the ZigBee and ZigBee-PRO feature sets, all devices are expected to manage their own binding
28 tables if they use binding tables.
29 This section is valid for both the ZigBee and ZigBee-PRO feature sets.
30 7.2 ZigBee: Compatibility w ith Other Feature sets
31 Devices implementing the ZigBee feature set will advertise a feature set identifier of 1 in their beacon
32 payloads as stated below in the additional restrictions for PICS item NLF4. In general, such devices
33 will seek out and join networks in which the ZigBee coordinator and all ZigBee routers implement the
34 ZigBee feature set and advertise this fact by placing a feature set identifier of 1 in their beacon
35 payloads.
36 In order to provide compatibility with devices implemented according to the ZigBee-PRO feature set,
37 ZigBee devices shall additionally be able to join networks which advertise a feature set identifier of 2
38 in their beacon payloads but the device must join the ZigBee-PRO networks as end devices and only
39 those ZigBee-PRO networks employing standard network security.
40 This section is valid for the ZigBee feature set.
41

1 7.3 ZigBee-PRO: Compatibility w ith Other Feature sets
2 Devices implementing the ZigBee-PRO feature set will advertise a feature set identifier of 2 in their
3 beacon payloads as stated below in the additional restrictions for PICS item NLF4. In general, such
4 devices will seek out and join networks in which the ZigBee coordinator and all ZigBee routers
5 implement the ZigBee-PRO feature set and advertise this fact by placing a feature set identifier of 2 in
6 their beacon payloads.
7 In order to provide compatibility with devices implemented according to the ZigBee feature set,
8 ZigBee-PRO devices shall additionally be able to join networks which advertise a feature set identifier
9 of 1 in their beacon payloads but the device must join the ZigBee networks as end devices.
10 If a ZigBee PRO network is to allow ZigBee devices to join as end devices, it shall use the standard
11 network security. If high security is used, ZigBee devices will not be able to be authenticated on the
12 network.
13 This section is valid for the ZigBee-PRO feature set.
14 7.4 Binding tables
15 Binding tables, if used, shall be located on the source device. While binding is optional, devices that
16 choose to use binding tables should allocate enough binding table entries to handle their own
17 communications needs. This suggests that binding table size should be flexible enough that it can be
18 set, at least at compile time, with some awareness of the actual intended usage of the device.
19 This section is valid for both the ZigBee and ZigBee-PRO feature sets.
20 7.5 Multicast mechanism and groups
21 Support for APS level multicasts is mandatory to support compatibility with ZigBee devices. The
22 multicast groups are then established using the application level mechanisms. Support for routing of
23 network level multicasts is mandatory in the ZigBee-Pro feature set.
24 ZigBee devices do not support network level multicasts.
25 7.6 Trust Center Policies and Security Settings
26 A ZigBee PRO network shall have a trust center uniquely pointed to by each device in the network
27 through apsTrustCenterAddress within each network member device. It is beyond the scope of the
28 PRO Feature set to describe how this value is set or whether it is changed and the Trust Center
29 relocated to another device during operation. The only requirement of the PRO Feature set is that all
30 devices in the network point to the one unique Trust Center and that the device pointed to as the Trust
31 Center supplies the security services described by this document.
32 The trust center dictates the security parameters of the network, such as which network key type to use,
33 settings of the service permissions table, when, if at all, to allow devices to use unsecured association
34 to the network, and when, if at all, to allow an application master or link key to be set up between two
35 devices. For interoperability, there are two distinct security settings that can be used within the ZigBee
36 PRO feature set – a standard and a high security.
37 Networks can exist for periods without a trust center. There are some operations where it is necessary
38 for the trust center to be operational in the network. These include initial network setup, key changes,
39 and when joining and rejoining devices require updated keys.

1 A wide range of implementations are possible, depending on the requirements of the application. A
2 high security trust center may allow the user to install devices “out-of-band”, keep separate link keys
3 for different devices, optionally ignore Mgmt_Permit_Joining_req commands from other nodes, and
4 configure application trust policies between devices or groups of devices, etc. A standard security trust
5 center would not offer these advantages, but would not be required to carry the associated costs.
6 7.7 Battery pow ered devices
7 ZigBee-PRO networks may, of course, contain battery-powered devices. ZigBee routers are required to
8 have their receivers enabled whenever they are not transmitting.
9 As mentioned above, ZigBee-PRO networks are beaconless networks and, in the absence of an explicit
10 mechanism for synchronization and indirect transmission, sleeping devices must set their own duty
11 cycles and use polling, under ZDO control, if they expect to receive frames that are directed to them
12 when they are asleep. The feature set provides that parent devices, i.e. ZigBee routers and the ZigBee
13 coordinator, hold frames for 7.5 seconds on behalf of sleeping end devices and this is also, roughly
14 speaking, the maximum polling rate prescribed here. Devices may implement a polling interval longer
15 than 7.5 seconds, however the application will then have to handle the potential loss of messages
16 during longer sleep cycles.
17 7.8 Mains powered devices
18 It is assumed that for most ZigBee-PRO networks, the ZigBee coordinator and ZigBee routers will be
19 mains-powered and always on in order to properly perform their required roles with respect to the
20 operation of the network.
21 7.9 Persistent storage
22 The ZigBee-PRO feature set does not support devices without persistent storage. Devices have
23 information required to be saved between unintentional restarts and power failures. See [R1] sections
24 2.2.8 and 3.6.8 for details of persistent data in the application and NWK layers. Various security
25 material shall additionally be stored across power failures. All attributes in sections 4.3.3 and 4.4.10
26 shall be stored, except that it is not mandatory to store those values which can safely be recovered
27 using other stored information, or other methods.
28 7.10 Address Reuse
29 Re-use of previously assigned network short addresses in ZigBee-PRO devices is permitted subject to
30 execution of the address conflict procedure by the device on the re-used address.
31 7.11 Duty cycle limitations and fragmentation
32 No mandatory restrictions are defined for intermittent, low channel usage data, although developers are
33 encouraged to minimise bandwidth usage wherever possible.
34 Large acknowledged unicast transmissions should generally use the APS fragmentation mechanism,
35 where supported, as this handles retransmissions, duplicate rejection, flow control and congestion
36 control automatically. Use of the fragmentation mechanism is as specified in the application profile
37 documents.

1 7.11.1 Vulnerability join
2 Vulnerability join shall be optional for networked devices, but support for it shall be mandatory for
3 trust centers. The default for networks is permit joining is off. Permit joining is allowed for
4 established time periods based on application requirements and specific instructions based on the
5 system design.
6 Devices that join but do not successfully acquire and use the relevant security keys within the specified
7 security timeout period shall disassociate themselves from the network, and their short address may be
8 reused.
9 7 .11 .2 Pr e- in sta lla tion
10 Pre-installation is acceptable. Pre-installed devices are not exempt from the other requirements in this
11 document. For example, a device certified as a trust center for this feature set shall support
12 vulnerability installation of new devices, even if it is initially pre-installed.
13 7.12 Security
14 This feature set is designed to allow the efficient deployment of low cost devices, while also supporting
15 the security requirements of highly sensitive applications. Installation and network maintenance
16 procedures and administration are defined with the goal of satisfying the requirements of a range of
17 applications within a single network infrastructure.
18 To achieve this, two security modes are specified: Standard mode and High Security mode. By default
19 all applications will use the network key for communications. However, where confidentiality from
20 other network nodes is required an application shall be permitted to use application link keys. Where
21 link keys are required by specific application profiles, commands not secured with a link key shall be
22 processed according to the rules established by the application profile.
23 The trust center plays a key role in determining the security settings in use in the network, and can
24 optionally be implemented to apply further restrictions on the network. Please see section Error!
25 Reference source not found. for details.
26 It is recommended that the trust center change the network key if it is discovered that any device has
27 been stolen or otherwise compromised, and in order to avoid deadlock if all frame counter records
28 become filled up. It is an application responsibility within the Trust Center to effect the change to the
29 network key. There is no expectation that the network key be changed when adding a new device.
30 All devices may implement a service permissions table, which they may use to determine which
31 devices are authorized to issue which commands. Unauthorized commands should not be carried out.
32 The trust center should be implemented to make appropriate choices about when to initiate an
33 application master/link key shared between two devices. Where restrictions between devices are
34 required it is the responsibility of the system installer/administrator to deploy a suitably intelligent trust
35 center and configure it to make relevant checks before initiating sharing of application link keys
36 between two devices. For example, it might facilitate policies based on certain times, certain
37 manufacturers or device types, or when the trust center is configured in a certain way, etc. By default a
38 simple trust center should always allow requests for link keys.
39 Devices may perform the relevant in or out of band authentication or key exchange before acquiring or
40 using a link key with a new target.

1 7 .12 .1 Se cu rit y Mo de s w ithin PR O Netw orks
2 The feature set shall use two security modes: Standard mode and High Security mode.
3 With the Standard mode, network keys and application link keys are permitted for all devices. The
4 network key type shall be the “standard” network key. It shall not be required that devices perform
5 entity authentication with their parent on joining nor shall it be required to perform entity
6 authentication between neighbors. If end devices wish to have a trust center link key, this should be
7 requested using the request key command. Note that it is optional for the trust center to support link
8 keys.
9 With the High Security mode, all three key types are permitted and shall be supported by all devices.
10 The network key type shall be the “high security” network key. It shall be required that devices shall
11 perform entity authentication with their parent on joining and it shall be required to perform entity
12 authentication between neighbors. Frames from devices not in the neighbor table shall not be accepted.
13 When a “standard” type network key is in use, devices shall be permitted to update the network key
14 when requested to do so by a command appropriately secured with the current network key. When a
15 “high security” type of network key is in use this shall not be permitted. Additionally, in “high
16 security”, new trust center link keys may be deployed by SKKE only, ie: they shall not be sent using
17 key transport.
18 Bit 6 of the capabilities field (security bit) shall be used to indicate whether or not a joining (or
19 rejoining) device supports High Security mode. It shall be set to 0 if the joining or rejoining device
20 does not support High Security mode (i.e. supports Standard mode), and shall be set to 1 if it does
21 support High Security mode. The trust center may optionally make use of this information as part of its
22 policy settings, for example when determining whether or not to allow the device onto the network, or
23 when determining whether to initiate SKKE with a new joiner or send a link key and/or network key in
24 the clear to the new device.
25 The above specifications are as currently described in the ZigBee specification.. Standard mode and
26 High Security mode allow implementation of two different strengths of security depending on the
27 application requirements and the specification supports a device indicating its security capabilities as it
28 joins the network, thus giving the Trust Center the means to be able to accept or reject the device based
29 on its policy.
30
31

1 8 Protocol implementation conformance statement (PICS)

2 proforma
3 8.1 Abbreviations and special symbols

4 Notations for requirement status:
M Mandatory
O Optional
O.n Optional, but support of at least one of the group of options labeled O.n is required.
N/A Not applicable
X Prohibited
5
6 “item”: Conditional, status dependent upon the support marked for the “item”.
7 For example, if FDT1 and FDT2 are both marked “O.1” this indicates that the status is optional but at
8 least one of the features described in FDT1 and FDT2 is required to be implemented, if this
9 implementation is to follow the standard of which this PICS Proforma is a part.
10 8.2 ZigBee device types

Item ZigBee Feature set Additional Platform
Item description Reference
number Status Support Constraints Support
FDT1 Is this device capable [R1]/Preface O.1

ZigBee
of acting as a ZigBee (Definitions)

coordinator?
O.1
ZigBee-
PRO
FDT2 Is this device capable [R1]/ O.1

ZigBee
of acting as a ZigBee Preface

router? (Definitions)
O.1
ZigBee-
PRO
FDT3 Is this a ZigBee end [R1]/ O.1

ZigBee
device? Preface
(Definitions)
O.1
ZigBee-
PRO
11

1 8.3 IEEE 802.15.4 PICS
2 8 .3 .1 FD T2 an d FD T3 netw o rk jo in op t io ns
Item ZigBee Feature set Additional Platform
Item description Reference
number Status Support Constraints Support
JN1 The device joins a FDT1:X

[R5] 7.3.1.1
FDT2:O
ZigBee
network by scanning FDT1: X
and then associating FDT3:O FDT2: M
(client) FDT3: M
ZigBee-
FDT1: X
PRO
FDT2: M
FDT3: M
JN10 The device supports FDT1: O FDT1: M

[R5] 7.3.1.1
FDT2: O
ZigBee
joining a network by FDT2: M
associating (server) FDT3: FDT3: X
N/A
FDT1: M
ZigBee-
FDT2: M
PRO
FDT3: X
JN2 The device joins a [R5] 7.3.2.3 FDT1:

ZigBee
network by using an N/A FDT1: X

orphan scan (client) FDT2: O FDT2: O
FDT3: O FDT3: O
ZigBee-
FDT1: X
PRO
FDT2: O
FDT3: O
JN20 The device supports [R5] 7.3.2.3 FDT1: O FDT1: M

FDT2: M
ZigBee
joining a network by FDT2: O

using an orphan scan FDT3: FDT3: X
(server) N/A
FDT1: M
FDT2: M
ZigBee-
PRO
FDT3: X

1 8.3.2 IEEE 802.15.4 PH Y
2 8 . 3 .2 .1 R a d io f re qu en c y o f op er at io n
Item Item ZigBee Feature set Additional Platform

Reference
number description Status Support Constraints Support
RF1 The device [R5] 6.1.1, O3 O3
ZigBee
operates at a 6.1.2, 6.6
frequency of 868
MHz.
O3
ZigBee-
PRO
ZigBee
frequency of 915
MHz.
O3
ZigBee-
PRO

ZigBee

frequency of 2.4
GHz.
O3
ZigBee-
PRO
3 O3: at least one option must be selected.

4
5 8 . 3 .2 .2 C le ar cha nn e l as se ssme nt

Reference
CCA1 Mode 1: Energy [R5] 6.7.9 O4 O4

ZigBee
above threshold is
supported.
O4
ZigBee-
PRO


Reference
CCA2 Mode 2: Carrier [R5] 6.7.9 O4 O4
ZigBee
sense only is
supported.
O4
ZigBee-
PRO
CCA3 Mode 3: Carrier [R5] 6.7.9 O4 O4
ZigBee
sense with energy
above threshold is
supported.
ZigBee- O4
PRO
1 O4: at least one option must be selected.

2
3 8.3.3 IEEE 802.15.4 MAC
4 8 . 3 .3 .1 C h an ne l ac ces s

Reference
CA1 A super-frame [R5] 7.5.1.1 O

ZigBee
structure is
supported. X
ZigBee-
PRO
CA2 Un-slotted [R5] 7.5.1.1 M M All devices shall set their

CSMA-CA is
ZigBee
MIB values as follows:

supported. macBeaconOrder = 0x0f,
macSuperframeOrder =
0x0f.
M All devices shall set their

ZigBee-
MIB values as follows:

PRO
macBeaconOrder = 0x0f,
macSuperframeOrder =
0x0f.


Reference
CA3 Slotted CSMA- [R5] 7.5.1.1 CA1: M
ZigBee
CA is supported.
X
ZigBee-
PRO
X
CA4 Super-frame [R5] 7.5.1.1 CA1: M
ZigBee
timing is
supported. X
ZigBee-
PRO
X
2 8 . 3 .3 .2 G ua ran t eed t im e s l ots

Reference
GTS1 Guaranteed time [R5] 7.5.7 FDT1: O

ZigBee
slots are supported

(server). X
ZigBee-
PRO
GTS2 Guaranteed time [R5] 7.5.7 FDT2: O X

ZigBee
slots are supported FDT3: O

(client).
X
ZigBee-
PRO


Reference
GTS3 The client device [R5] 7.1.7.1, GTS2: M

has the ability to 7.1.7.2,
request a GTS. 7.3.3.1,
Operations 7.5.7.2,
include: 7.5.7.4
• Allocation
ZigBee
requests X
• De-allocation
requests
• [MLME-
GTS.request
primitive]
• [MLME-
GTS.confirm
primitive]
ZigBee-
PRO
• Transmission of X
the GTS request
command.
GTS4 The server has the [R5] 7.1.7.3, GTS1: M

ability to process 7.3.3.1,
GTS requests. 7.5.7.2,
Operations 7.5.7.4,
ZigBee
include: 7.5.7.5 X
• Allocation
requests
• De-allocation
requests
• Re-allocation
requests
• [MLME-
ZigBee-
GTS.indication
PRO
primitive] X
• Reception and
processing of
the GTS request
command.
GTS5 The server can [R5] 7.5.7 GTS1: M

ZigBee
manage the GTSs.

X
ZigBee-
PRO


Reference
GTS6 The server can [R5] 7.5.7.1 GTS1: M
ZigBee
perform CAP
maintenance. X
ZigBee-
PRO
X
GTS7 The device can [R5] 7.5.7.3 GTS1: M
ZigBee
transmit and/or GTS2: M
receive data X
within a GTS.
ZigBee-
PRO
X
2 8 . 3 .3 .3 S c ann i ng

Reference
S1 The device can [R5] 7.1.11.1, M All devices shall be able

perform some 7.1.11.2, to perform at least an
ZigBee
form of channel 7.5.2.1 active scan.

M
scan. Operations
include:
• Scanning
mechanism
All devices shall be able
• [MLME- to perform at least an
SCAN.request active scan.
ZigBee-
PRO
primitive] M
• [MLME-
SCAN.confirm
primitive]
S2 The device can [R5] 7.5.2.1.1 FDT1: M FDT1: M Network devices shall
perform an energy FDT2: M perform an energy
ZigBee
detection scan. FDT3: X detection scan on request

from the next higher
layer.
FDT1: M The coordinator shall

FDT2: M perform an energy
ZigBee-
detection scan on each

PRO
FDT3: X
available channel in the
active channel mask
before starting a network.


Reference
S3 The device can [R5] 7.3.2.4, FDT1: M All devices shall perform
ZigBee
perform an active 7.5.2.1.2 JN1: M an active scan on each
scan. Operations M available channel in the
include: active channel mask.
• Transmission of
the beacon
request All devices shall perform
ZigBee-
an active scan on each
PRO
command.
M available channel in the
active channel mask.
S4 The device can [R5] 7.5.2.1.3 O
ZigBee
perform a passive
scan. X
ZigBee-
PRO X
S5 The client can [R5] 7.3.2.3, JN2: M

ZigBee
perform an orphan 7.3.2.5,

scan. Operations 7.5.2.1.4 JN2:M
include:
• Orphan device
realignment.
• Transmission of
the orphan
notify
ZigBee-
command.
PRO
JN2:M
• Reception and
processing of
the coordinator
realignment
command.
S6 The server can [R5] 7.1.8.1, FDT1: O Network rejoin is the

perform orphan 7.1.8.2, FDT2: O preferred mechanism for
scan processing. 7.3.2.3, devices to use, however,
ZigBee
FDT1: M
Operations 7.3.2.5, FDT2: M orphan scan may be used
include: 7.5.2.1.4 FDT3: X and the parent devices
shall support orphan
• [MLME- scan.
ORPHAN.indic
ate primitive]
Network rejoin is the
• [MLME- preferred mechanism for
ORPHAN.respo devices to use, however,
nse primitive] orphan scan may be used
and the parent devices
• Reception and shall support orphan
ZigBee-
processing of FDT1: M scan.

PRO
the orphan FDT2: M

notify FDT3: X
command.
• Transmission of
the coordinator
realignment
command.


Reference
S7 The server can [R5] 7.3.2.4 S3 &
ZigBee
receive and FDT1: M FDT1: M
process a beacon FDT2: M
request command. FDT3: X
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X
2 8 . 3 .3 .4 P A N id ent if ie r c onf l ic t re so l ut io n

Reference
PICR1 PAN identifier [R5] 7.3.2.2, FDT1: O

conflict resolution 7.3.2.5,
is supported 7.5.2.2
ZigBee
FDT1: X
(server).
FDT2: X
Operations
FDT3: X
include:
• Reception and
processing of
the PAN
identifier
conflict
notification
ZigBee-
command. FDT1: X
PRO
FDT2: X
• Transmission of FDT3: X
the coordinator
realignment
command.
PICR2 PAN identifier [R5] 7.3.2.2, FDT2: O FDT1: X

conflict resolution 7.3.2.5, FDT3: O FDT2: X
is supported 7.5.2.2 FDT3: X
ZigBee
(client).
Operations
include:
• Transmission of
the PAN
identifier FDT1: X
conflict FDT2: X
notification FDT3: X
command.
ZigBee-
PRO
• Reception and
processing of
the coordinator
realignment
command.

1 8 . 3 .3 .5 P A N st art

Reference
PS1 Starting a PAN is [R5] 7.1.14.1, FDT1: M
ZigBee
supported. 7.1.14.2, FDT2: M FDT1: M
Operations 7.5.2.3 FDT3: O FDT2: M
include: FDT3: X
• [MLME-
START.request
primitive]
ZigBee-
FDT1: M
PRO
• [MLME- FDT2: M
START.confirm FDT3: X
primitive]
3 8 . 3 .3 .6 A s so c iat ion

Reference
A1 Association is [R5] 7.5.3.1 FDT1: O

supported FDT2: O
ZigBee
FDT1: M
(server).
FDT2: M
FDT3: X
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X
A2 Association is [R5] 7.5.3.1 FDT2: O FDT1: X

ZigBee
supported (client). FDT3: O FDT2: M

FDT3: M
FDT1: X
ZigBee-
FDT2: M
PRO
FDT3: M


Reference
A3 The server can [R5] 7.1.3.2, A1: M

process 7.1.3.3,
association 7.3.1.1,
requests. 7.3.1.2
Operations
ZigBee
FDT1: M
include: FDT2: M
FDT3: X
• [MLME-
ASSOCIATE.in
dicate
primitive]
• [MLME-
ASSOCIATE.re
sponse
primitive]
• Reception and
processing of
ZigBee-
FDT1: M
PRO
the association
request FDT2: M
command. FDT3: X
• Transmission of
the association
response
command.
A4 The client can [R5] 7.1.3.1, A2: M

perform 7.1.3.4,
association. 7.3.1.1,
Operations 7.3.1.2
ZigBee
FDT1: X
include: FDT2: M
FDT3: M
• [MLME-
ASSOCIATE.re
quest primitive]
• [MLME-
ASSOCIATE.c
onfirm
primitive]
• Transmission of
the association
ZigBee-
request FDT1: X
PRO
command. FDT2: M
FDT3: M
• Reception and
processing of
the association
response
command.

1 8 . 3 .3 .7 D is ass oc ia t i on

Reference
D1 The device can [R5] 7.1.4.1, O

request a 7.1.4.3,
disassociation. 7.3.1.3
ZigBee
FDT1: X
Operations
FDT2: X
include:
FDT3: X
• [MLME-
DISASSOCIAT
E.request
primitive]
• [MLME-
DISASSOCIAT
E.confirm
ZigBee-
primitive] FDT1: X
PRO
FDT2: X
• Transmission of FDT3: X
the
disassociation
notify
command.
D2 The client can [R5] 7.1.4.2, O

react to a 7.3.1.3
disassociation
ZigBee
FDT1: X
from the server. FDT2: X
Operations FDT3: X
include:
• [MLME-
DISASSOCIAT
E.indicate
primitive]
• Reception and
ZigBee-
FDT1: X
PRO
processing of FDT2: X
the FDT3: X
disassociation
notify
command.
D3 The server can [R5] 7.1.4.2, O

react to a 7.3.1.3
disassociation
ZigBee
FDT1: X
from a client FDT2: X
device. FDT3: X
Operations
include:
• [MLME-
DISASSOCIAT
E.indicate
primitive]
ZigBee-
• Reception and FDT1: X

PRO
processing of FDT2: X
the FDT3: X
disassociation
notify
command.

1 8 . 3 .3 .8 B e ac on s yn ch ro n iz at i o n

Reference
BS1 Beacon [R5] 7.1.5.1 O
ZigBee
FDT1: M
notification is
FDT2: M
supported.
FDT3: M
Operations
include:
• [MLME-
ZigBee-
BEACON- FDT1: M
PRO
NOTIFY.indica FDT2: M
tion primitive] FDT3: M
BS2 The client can [R5] 7.1.15.1, O

synchronize to a 7.1.15.2, 7.5.4
beacon.
ZigBee
FDT1: X
Operations FDT2: X
include: FDT3: X
• (Tracking only
for beacon
networks)
• [MLME-
SYNC.request
ZigBee-
primitive] FDT1: X
PRO
FDT2: X
• [MLME- FDT3: X
SYNC-
LOSS.indicatio
n primitive]
3 8 . 3 .3 .9 T ra ns m is sio n

Reference
T1 Frame [R5] 7.1.1.1, M

transmission is 7.1.1.2, 7.2.1,
supported. 7.2.2.2,
ZigBee
Operations 7.5.6.1 M
include:
• Frame
construction
• [MCPS-
DATA.request
primitive]
ZigBee-
• [MCPS-
PRO
M
DATA.confirm
primitive]
• Transmission of
data frames.


Reference
T2 Implicit [R5] 7.1.12.1 M
ZigBee
(command frame)
transmission M
confirmation is
supported.
Operations
include:
ZigBee-
• [MLME-
PRO
COMM- M
STATUS.indica
tion primitive]
2 8 . 3 .3 .1 0 R e ce pt io n

Reference
R1 Frame reception is [R5] 7.1.1.3, M

supported. 7.2.1, 7.2.2.2
ZigBee
Operations
M
include:
• Data frame de-
construction
• [MCPS-
DATA.indicatio
ZigBee-
PRO
n primitive] M
• Reception of
data frames.
R2 Receiver control is [R5] 7.1.10.1, O

ZigBee
supported. 7.1.10.2
Operations O
include:
• [MLME-RX-
ENABLE.reque
st primitive]
ZigBee-
PRO
• [MLME-RX- O
ENABLE.confir
m primitive]
R3 Filtering and [R5] 7.5.6.2 M

ZigBee
rejection is
supported. M
ZigBee-
PRO


Reference
R4 Promiscuous [R5] 7.5.6.6 O
ZigBee
mode is supported. O
ZigBee-
PRO
O
2 8 . 3 .3 .1 1 T ra ns act ion ha nd l i ng

Reference
TH1 Transaction [R5] 7.5.5 FDT1: O The server shall be able
ZigBee
handling is FDT2: O FDT1: M to handle at least one
supported FDT2: M transaction.
(server). FDT3: X
The server shall be able

ZigBee-
FDT1: M to handle at least one

PRO
FDT2: M transaction.
FDT3: X
TH2 Transaction [R5] 7.5.5 FDT2: O

ZigBee
handling is FDT3: O FDT1: X

supported (client). FDT2: X
FDT3: M
ZigBee-
FDT1: X
PRO
FDT2: X
FDT3: M
TH3 The server can [R5] 7.5.5, TH1: M

manage 7.1.1.4,
transactions to its 7.1.1.5,
devices. 7.3.2.1
ZigBee
FDT1: M
Operations FDT2: M
include: FDT3: X
• Transaction
queuing
• Reception and
processing of
ZigBee-
the data request FDT1: M

PRO
command. FDT2: M
FDT3: X


Reference
TH30 The server can [R5] 7.1.1.4, TH1: M
ZigBee
manage 7.1.1.5, O
transaction 7.3.2.1
purging
operations:
• [MCPS-
PURGE.request
ZigBee-
PRO
primitive]
O
• [MCPS-
PURGE.confir
m primitive]
TH4 The client can [R5] 7.5.6.3 TH2: O5
ZigBee
extract data from FDT1: X
the coordinator FDT2: X
following an FDT3: X
indication of data
in a beacon.
ZigBee-
FDT1: X
PRO
FDT2: X
FDT3: X
TH5 The client can poll [R5] 7.1.16.1, TH2: O5

for data. 7.1.16.2,
ZigBee
Operations 7.3.2.1 FDT1: X

include: FDT2: X
FDT3: M
• [MLME-
POLL.request
primitive]
• [MLME-
POLL.confirm
ZigBee-
primitive] FDT1: X
PRO
FDT2: X
• Transmission of FDT3: M
the data request
command.
1 O5: At least one of these options must be supported.
2 8 . 3 .3 .1 2 A c kn ow led ge me nt se r vi c e

Reference
AS1 The [R5] 7.5.6.4 O

ZigBee
acknowledgement
service is M
supported.
ZigBee-
PRO


Reference
AS2 The device can [R5] 7.2.2.3 AS1: M
ZigBee
transmit, receive
and process M
acknowledgement
frames.
ZigBee-
PRO
M
AS3 Deprecated [R5] 7.5.6.4.2, AS1: M
ZigBee
7.5.6.5 X
ZigBee-
PRO
X
AS4 Retransmissions [R5] 7.5.6.5 AS1: M

are supported. ZigBee
M
ZigBee-
PRO
2 8 . 3 .3 .1 3 M IB m anag e men t

Reference
MM1 MIB management [R5] 7.4.2 O

ZigBee
is supported.
Operations M
include:
• MIB attribute
storage
ZigBee-
PRO


Reference
MM2 The device [R5] 7.1.6.1, MM1: O

supports the 7.1.6.2, 7.4.2
ZigBee
reading of MIB M
attributes.
Operations
include:
• [MLME-
GET.request
ZigBee-
primitive]
PRO
M
• [MLME-
GET.confirm
primitive]
MM3 The device [R5] 7.1.13.1, MM1: O

supports the 7.1.13.2, 7.4.2
ZigBee
writing of MIB
attributes. M
Operations
include:
• MIB attribute
verification
• [MLME-
SET.request
ZigBee-
PRO
primitive] M
• [MLME-
SET.confirm
primitive]
2 8 . 3 .3 .1 4 M A C se cu rit y

Reference
MS1 The device [R5] 7.4.2, O

ZigBee
supports ACL 7.5.8.1,

mode. Operations 7.5.8.3 X
include:
• ACL storage
• ACL
ZigBee-
mode
PRO
usage X
MS2 The device [R5] 7.5.8.4 O

supports secured
ZigBee
mode. X
ZigBee-
PRO
3
4

1 8 . 3 .3 .1 5 D e vic e re se t

Reference
DR1 The device is able [R5] 7.1.9.1, O
ZigBee
to reset. 7.1.9.2
Operations O
include:
• [MLME-
RESET.request
primitive]
ZigBee-
PRO
O
• [MLME-
RESET.confirm
primitive]
3 8.4 Network layer PICS
4 8 . 4 .1 Z i gBe e ne t w ork f r a me f or m at

Reference
GFF1 Does the device [R1]/3.3.1

ZigBee
support the
general ZigBee M
network frame
format?
ZigBee-
PRO
6 8 . 4 .2 M a jo r ca pa b i l it ie s of t he Z igBe e n etw ork l a ye r

7 Tables in the following sub-clauses detail the capabilities of NWK layer for ZigBee devices.
8 8 . 4 .2 .1 N e tw ork laye r f un ct io ns

Reference
NLF1 Does the network [R1]/3.2.1.1, M

ZigBee
layer support 3.2.1.2,

transmission of 3.6.2.1 M
data by the next
higher layer?
ZigBee-
PRO


Reference
ZigBee
layer support 3.6.2.2
reception of data M
by the next higher
layer?
ZigBee-
PRO
M
ZigBee
layer support 3.2.2.2
discovery of M
existing ZigBee
networks?
ZigBee-
PRO M
NLF4 Does the network [R1]/3.2.2.3, FDT1:M, Devices using the ZigBee
layer support 3.2.2.4, FDT2:X, feature set shall set:
formation of 3.6.1.1 FDT3:X
ZigBee networks? Feature set = 1
nwkcProtocolVersion = 2
FDT1: M
FDT2: X
ZigBee
and shall advertise these

FDT3: X values in their beacon
payload in response to
MAC beacon requests.
Devices using the ZigBee

feature set shall also set:
nwkSecurityLevel = 5
Devices using the

ZigBee-PRO feature set
shall set:
Feature set = 2
nwkcProtocolVersion = 2
ZigBee-
FDT1: M and shall advertise these

PRO
FDT2: X values in their beacon

FDT3: X payload in response to
MAC beacon requests.
Devices using the

ZigBee-PRO feature set
shall also set:
nwkSecurityLevel = 5


Reference
NLF5 Can the network [R1]/3.2.2.5, FDT1:M,

layer permit other 3.2.2.6, FDT2:M,
devices to join the 3.6.1.2 FDT3:X
ZigBee
FDT1: M
network of which
FDT2: M
it is a part (and
FDT3: X
also deny such
permission)?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X
NLF6 Can the device [R1]/3.2.2.7, FDT1:X,
ZigBee
start as a router? 3.2.2.8 FDT2:M, FDT1: X
FDT3:X FDT2: M
FDT3: X
ZigBee-
FDT1: X
PRO
FDT2: M
FDT3: X
NLF60 Can the network [R1]/3.2.2.9, M NLME-ED-SCAN is

layer perform 3.2.2.10 mandatory for the
ZigBee
FDT1: M
energy detection FDT2: M coordinator and optional
scans at the FDT3: X for all routers on a
request of the next ZigBee network.
higher layer?
NLME-ED-SCAN is
ZigBee-
FDT1: M mandatory for the

PRO
FDT2: M coordinator and all

FDT3: X routers on a PRO
network.
NLF7 Can the device [R1]/3.2.2.11, FDT1:

ZigBee
request 3.2.2.13, N/A FDT1: X

membership in a 3.6.1.4 FDT2: M FDT2: M
ZigBee network? FDT3: M FDT3: M
ZigBee-
FDT1: X
PRO
FDT2: M
FDT3: M

ZigBee
request to join or 3.2.2.15, N/A FDT1: X

rejoin a network 3.6.1.4.3.1 FDT2: O FDT2: O
using the FDT3: O FDT3: O
orphaning
procedure?
ZigBee-
FDT1: X
PRO
FDT2: O
FDT3: O


Reference
ZigBee
request to join / 3.2.2.13, N/A FDT1: X
rejoin a network 3.6.1.4.2.1 FDT2: O FDT2: M
using the rejoin FDT3: O FDT3: M
command frame
and associated
procedure?
ZigBee-
FDT1: X
PRO
FDT2: M
FDT3: M
NLF72 Can the network [R1]/3.2.2.11, O The network layer can be
ZigBee
layer be directed 3.2.2.13 directed by the next
by the next higher M higher layer to change the
layer to change the operating channel of the
operating channel network of which it is
of the network of currently part.
which it is
currently a part? ZigBee-
PRO M
NLF8 Can the device [R1]/3.6.1.4.1 FDT1: M

ZigBee
respond to .2, 3.6.1.4.2.2 FDT2: M FDT1: M

requests to join the FDT3: X FDT2: M
network of which FDT3: X
it is a part?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X
NLF81 Does the network [R1]/3.2.2.12 FDT1: M

ZigBee
layer of a device FDT2: M FDT1: M

inform the next FDT3: X FDT2: M
higher layer when FDT3: X
a second device
has joined or
rejoined its
network as a
ZigBee-
FDT1: M
PRO
child? FDT2: M
FDT3: X
NLF9 Does the network [R1]/3.6.1.6 FDT1: O The ZigBee feature set
layer employ the FDT2: O always employs the
Distributed FDT3: distributed addressing
Address N/A scheme with:
ZigBee
FDT1: M
Mechanism to FDT2: M
generate a unique FDT3: X nwkMaxDepth = 5
network address to nwkMaxChildren = 20
assign to a joining nwkMaxRouters = 6
device?
ZigBee-
FDT1: X
PRO
FDT2: X
FDT3: X


Reference
NLF90 Does the network [R1]/3.6.1.7 FDT1: O
ZigBee
layer employ the FDT2: O FDT1: X
Stochastic FDT3: FDT2: X
Addressing N/A FDT3: X
Scheme to
generate a unique
network address to The ZigBee-PRO feature
assign to a joining set employs stochastic
or rejoining address allocation.
device?
The follow parameter
values are defined:
nwkAddrAlloc = 2
nwkUseTreeRouting =
FALSE
nwkMaxDepth = 15
ZigBee-
FDT1: M
PRO
FDT2: M Note that nwkMaxDepth
FDT3: X above is only used to
compute timeouts and
shall not limit the actual
network radius, as this
feature set does not use
tree-based addressing.
The parameter
nwkMaxChildren is not
restricted in this feature
set.
NLF100 Does the network Deprecated X

ZigBee
layer employ the

Higher Layer X
Address
Assignment
Mechanism to
generate a unique
network address to
ZigBee-
PRO
assign to a joining X
device?
NLF10 Can the next [R1]/3.2.2.14, FDT1: O This service is useful for
higher layer 3.2.2.15, FDT2: O testing and may be
request that a 3.6.1.4.3 FDT3: X allowed as a part of test
ZigBee
particular device X procedures at the option

be “pre-joined” to of the stack developer.
it using the
DIRECT-JOIN
procedure?
This service is useful for
ZigBee-
testing and may be

PRO
X allowed as a part of test

procedures at the option
of the stack developer.


Reference
NLF11 Can the device [R1]/3.2.2.16, O

make a request to 3.2.2.18,
leave the network? 3.6.1.10.1
ZigBee
FDT1: X
FDT2: M
FDT3: M
ZigBee-
FDT1: X
PRO
FDT2: M
FDT3: M
NLF12 Can the device [R1]/3.2.2.16, FDT1: O

make a request 3.2.2.18, FDT2: O ZigBee FDT1: M
that one of its 3.6.1.10.2 FDT3: FDT2: M
child devices N/A FDT3: X
leave the network?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X
NLF13 Can the network [R1]/3.6.1.10. FDT1: M

ZigBee
layer process 3 FDT2: M FDT1: M

network leave FDT3: FDT2: M
commands from N/A FDT3: X
child devices?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X
NLF130 Can the network [R1]/3.6.1.10. FDT1:

ZigBee
layer process 3 N/A FDT1: X

network leave FDT2: M FDT2: M
commands from FDT3: M FDT3: M
parent devices?
ZigBee-
FDT1: X
PRO
FDT2: M
FDT3: M
NLF131 Does the network [R1]/3.2.2.17 M

ZigBee
layer inform the

next higher layer M
if the device itself
has left the
network?
ZigBee-
PRO


Reference
NLF14 Does the device [R1]/3.2.2.3, FDT1: O The ZigBee coordinator
ZigBee
support changing 3.2.2.4, FDT2: X FDT1: M shall change the logical
of the ZigBee 3.6.1.11 FDT3: X FDT2: X channel and PAN ID
coordinator FDT3: X when directed to by the
configuration in Network Channel
an operating Manager.
network?
ZigBee-
FDT1: M
PRO
FDT2: X
FDT3: X
NLF15 Does the device [R1]/3.2.2.7, FDT1: X
ZigBee
support changing 3.2.2.8 FDT2: O FDT1: X
of the ZigBee FDT3: X FDT2: M The ZigBee router shall
router FDT3: X change the logical
configuration in channel and PAN ID
an operating when directed to by the
network? Network Channel
ZigBee-
FDT1: X Manager.
PRO
FDT2: M
FDT3: X

ZigBee
layer support 3.2.2.20,

reset? 3.6.1.12 M
ZigBee-
PRO


Reference
NLF17 Does the network [R1]/3.2.2.22, FDT1: X Recommended polling

layer allow the 3.2.2.23 FDT2: O rates for end devices
next higher layer FDT3: M using this feature set:
to synchronize
with or extract Maximum: once per 7.5s
data from the Minimum: once per hour
device’s ZigBee
coordinator or
router? Note that these values
represent the (rather
loose) recommended
boundaries on polling
rate for normal operation
only.
Additionally, the polling

rate established to meet
ZigBee
FDT1: X
FDT2: X this requirement shall
FDT3: M have a maximum value
less than
nwkTransactionPersisten
ceTime to ensure that
child devices can poll
frequently enough to
retrieve messages prior to
expiration in the indirect
message queue of their
parent.
The polling rate

established here also does
not consider APS
acknowledgement
timeout (which is much
shorter than
nwkTransaction-
PersistenceTime). If
APS acknowledged
messages are directed to
sleeping end devices,
ZigBee-
FDT1: X then the polling rate of

PRO
FDT2: X those destination devices

FDT3: M may be adjusted to occur
more frequently than the
APS acknowledgement
timeout.
NLF18 Does the network [R1]/3.2.2.23 FDT1: X

ZigBee
layer report a loss FDT2: O

of synchronization FDT3: M X
with the device’s
ZigBee router or
ZigBee
coordinator to the
next higher layer?
ZigBee-
PRO


Reference

layer offer the 3.2.2.27
next higher layer
the ability to
retrieve network
ZigBee
information base M
(NIB) attributes?
ZigBee-
PRO
M
ZigBee
layer offer the 3.2.2.29
next higher layer M
the ability to set
network
information base
(NIB) attributes?
ZigBee-
PRO
NLF110 Does the network [R1]/3.2.2.30 M

ZigBee
layer support FDT1: M

network status FDT2: M
reporting to the FDT3: X
next higher layer?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X
NLF111 Does the network [R1]/3.2.2.31, FDT1: O

ZigBee
layer support 3.2.2.32, FDT2: O FDT1: M

Route Discovery? 3.6.3.5 FDT3: X FDT2: M
FDT3: X
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X


Reference

layer support 3.2.2.32, FDT2: O
Route Discovery 3.6.3.5 FDT3: X
requests with
DstAddrMode of
0x00 in support of
ZigBee
Many-to-One
X
discovery?
Initiation of a Many-to-
One route discovery is
optional, and should be
used in cases where there
ZigBee- are relatively few
PRO FDT1: O
concentrators in the
FDT2: O
network. Application
FDT3: X
developers should weigh
the trade-offs between
Many-to-One discovery
and unicast discovery
before deploying.

layer support 3.2.2.32, FDT2: O
Route Discovery 3.6.3.5, 3.6.6 FDT3: X
ZigBee
requests with
X
DstAddrMode of
0x01 in support of
Multicast Group
Discovery?
Initiation of route
ZigBee-
FDT1: O discovery commands

PRO
FDT2: O where DstAddrMode is

FDT3: X 0x01 (Multicast Group
Discovery) is optional.
NLF114 Does the network [R1]/3.2.2.31, FDT1: O Initiation of route

ZigBee
layer support 3.2.2.32, FDT2: O FDT1: O discovery commands

Route Discovery 3.6.3.5 FDT3: X FDT2: O where DstAddrMode is
requests with FDT3: X 0x02 (Unicast) is
DstAddrMode of optional.
0x02 in support of
the discovery of ZigBee coordinators and
Unicast routes? ZigBee routers shall
ZigBee-
FDT1: O
PRO
support reception and

FDT2: O
correct handling of
FDT3: X
unicast discovery
commands.


Reference
NLF115 Does the network 3.6.3.3 O Devices using the ZigBee

layer employ tree stack profile must set:
routing?
nwkUseTreeRouting =
ZigBee
TRUE
M
Devices using the

ZigBee-PRO stack
ZigBee-
profile shall set:
PRO
X
nwkUseTreeRouting =
FALSE
NLF21 Does the network 3.6.3.1 O
ZigBee
layer calculate FDT1: M
routing cost based FDT2: M
on probability of FDT3: X
reception?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X
NLF22 Does the network [R1]/3.6.3.2 FDT1: O ZigBee coordinators and

layer maintain a FDT2: O ZigBee routers shall
routing table and FDT3: X maintain a routing table
route discovery and a route discovery
table? FDT1: M table as follows:
ZigBee
FDT2: M
FDT3: X
Routing table
(minimum): 8 entries
Route discovery table

ZigBee coordinators and

ZigBee routers shall
maintain a routing table
and a route discovery
table as follows:
Routing table
An aging algorithm is
ZigBee-
FDT1: M
PRO
recommended but is
FDT2: M
beyond the scope of this
FDT3: X
specification.
Route discovery table

entries (minimum): 4
entries
The Route discovery

table entries shall be
managed as described in
[R1] sub-clause 3.6.3.6.


Reference
NLF220 Does the network [R1]/3.5.2, FDT1: O
ZigBee
layer maintain a 3.6.3.2 FDT2: O
route record table? FDT3: X X
ZigBee-
FDT1: O
PRO
FDT2: O
FDT3: X
NLF221 Does the network [R1]/3.6.6.1 FDT1:O, ZigBee coordinators and

layer maintain a FDT2:O,
ZigBee
ZigBee routers that use
multicast group ID FDT3:X X this stack profile shall set
table? nwkUseMulticast to
FALSE.
ZigBee-
FDT1: O
PRO
FDT2: O
FDT3: X
NLF23 Does the network None X

ZigBee
layer reserve
routing capacity X
for route repair
operations?
(Note: This
capability has
ZigBee-
PRO
been removed
X
from the ZigBee
specification as of
r08).
NLF24 Does the device [R1]/3.6.4 O

ZigBee
implement beacon
collision- X
avoidance
measures?
ZigBee-
PRO
NLF25 Does the network None X

ZigBee
layer support
router re- X
enumeration as a
route repair
method?
(Note: This
ZigBee-
capability has
PRO
been removed X
from the ZigBee
specification as of
r10).


Reference
NLF26 Does the network [R1]/3.5.2, O Devices using the ZigBee
ZigBee
layer assume that 3.6.3.5.2 stack profile must set:
links are X
symmetrical and nwkSymLink = FALSE
establish forward
and reverse routes
at the same time? Devices using the
ZigBee-
ZigBee-PRO stack
PRO
M profile shall set:
nwkSymLink = TRUE
NLF27 Does the network [R1]/3.6.1.5 M ZigBee coordinators and

layer maintain a ZigBee routers shall
neighbor table or maintain a neighbor table
tables in order to or tables as follows:
store information
about nearby ZigBee coordinator
ZigBee
devices? (minimum): 24 entries 1
M
ZigBee router
ZigBee end device

(minimum): 1 entry
ZigBee coordinators and

ZigBee routers shall
maintain a neighbor table
or tables as follows:
ZigBee coordinator
(minimum): (Number of
child end devices
accepted) plus 16
ZigBee router
(minimum): (Number of
child end devices
accepted) plus 16
ZigBee-
PRO
M
ZigBee end device: 1
(Note: End Device shall
only support only a single
neighbor table entry and
that entry shall be for
their parent)
Where (Number of child

end devices accepted) is
the maximum number of
end device children that a
particular router or
coordinator in the
network is configured to
accept.
1
LB #047


Reference
NLF28 Does the network [R1]/3.6.3.5.1 O
ZigBee
layer buffer
frames pending O
route discovery or
route repair
operations?
ZigBee-
PRO
O
NLF29 Does the network [R1]/3.6.5 FDT1:M ZigBee router and
ZigBee
layer buffer data FDT2:M FDT1: M coordinator devices shall
frames on behalf FDT3:X FDT2: M set:
of end device that FDT3: X
are its children? Number of frames
buffered on behalf of
sleeping end devices
(minimum): 1
Note that this means 1

frame TOTAL not 1
ZigBee-
FDT1: M frame for each end

PRO
FDT2: M device. In other words, it

FDT3: X is up to the implementer
to put in some buffering
but routers should not be
overburdened with,
possibly unnecessary,
buffering.
NLF30 Is the device [R1]/Preface O On invocation of the

ZigBee
capable of Definitions NLME-NETWORK-

participating in a and Network X FORMATION.request or
beacon-oriented Topology NLME-START-
network? sections ROUTER.request
primitives, devices shall
employ:
ZigBee-
PRO
X BeaconOrder = 0x0f
SuperframeOrder = 0x0f
NLF31 Does the network [R1]/3.6.1.9 O

ZigBee
layer support the

detection of X
address conflicts?
Address conflict
detection is mandatory
for this stack profile
ZigBee-
FDT1: M (nwkUniqueAddr =
PRO
FDT2: M FALSE). The

FDT3: X coordinator and all
routers shall implement
the Address Conflict
procedure.


Reference
NLF32 Does the network [R1]/3.6.1.9.3 FDT1: O

layer support FDT2: O
resolving address FDT3: X
ZigBee
conflicts?
X
Address conflict
resolution is mandatory
for this stack profile
ZigBee-
FDT1: M (nwkUniqueAddr =
PRO
FDT2: M FALSE). The
FDT3: X coordinator and all
routers shall implement
the Address Conflict
procedure.
NLF33 Does the network [R1]/3.6.1.13 O PAN ID conflict
ZigBee
layer support the FDT1:M resolution is mandatory
detection of PAN FDT2:M for the coordinator and
ID conflicts? FDT3:X routers. Notification of a
PAN ID conflict via the
NWK Status command
frame directed to the
nwkManagerAddr is
mandatory for all routers
and the coordinator. The
ZigBee-
FDT1:M
PRO
nwkManagerAddr is
FDT2:M required to process all
FDT3:X NWK Status command
frames directed to it by
the coordinator and
routers.
NLF34 Does the device [R1]/3.6.1.13 O PAN ID conflict

ZigBee
support resolving FDT1: M resolution is mandatory

PAN ID conflicts? FDT2: M for the coordinator and
FDT3: X routers. Notification of a
PAN ID conflict via the
NWK Status command
frame directed to the
nwkManagerAddr is
mandatory for all routers
and the coordinator. The
ZigBee-
FDT1: M
PRO
nwkManagerAddr is
FDT2: M required to process all
FDT3: X NWK Status command
frames directed to it by
the coordinator and
routers.

1 8 . 4 .2 .2 N e tw ork laye r f ra me s

Reference
NDF1 Does the device [R1]/3.3.2.1, M

support the 3.6.2.1
ZigBee
origination of M
network data
frames?
ZigBee-
PRO
M
NDF2 Does the device [R1]/3.3.2.1, M
ZigBee
support the receipt 3.6.2.2
of network data M
frames?
ZigBee-
PRO
NDF3 Does the device [R1]/3.3.2.1, FDT1: M

ZigBee
support the 3.6.3.3 FDT2: M FDT1: M

relaying of unicast FDT3: X FDT2: M
network data FDT3: X
frames?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X

1
Reference
NDF4 Does the device [R1]/3.3.2.1, FDT1: M Devices using the ZigBee
support relaying 3.6.5 FDT2: M stack profile must set:
of broadcast FDT3: X
network data Broadcast Transaction
frames? Table size: 9 (minimum)
ZigBee
FDT1: M
FDT2: M
FDT3: X nwkBroadcastDeliveryTi
me = 9
nwkPassiveAckTimeout
= 0.5 (maximum)
nwkMaxBroadcastRetries
=2
Devices using the

ZigBee-PRO stack
profile shall set:
Broadcast Transaction
Table size: 9 (minimum)
nwkBroadcastDeliveryTi
me = 9 2
ZigBee-
FDT1: M nwkPassiveAckTimeout =
PRO
FDT2: M 0.5 (maximum)

FDT3: X nwkMaxBroadcastRetries
=2
Application designers
should take care to use
multicast and broadcast
sparingly due to the
limitations of the
broadcast bandwidth of a
network.
NDF100 Does the device [R2]/3.3.2.1, FDT1: O

ZigBee
support relaying 3.6.6 FDT2: O

of multicast FDT3: X X
network data
frames?
The coordinator and all

ZigBee-
FDT1: M routers in a PRO network

PRO
FDT2: M shall be able to relay

FDT3: X member mode 3 multicast
network data frames.
NDF101 Does the device [R2]/3.3.2.1, FDT1:O,

ZigBee
support the 3.6.3.3.2 FDT2:O,

relaying of source FDT3:X X
routed network
data frames?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X
2
CCB 884
3
CCB 872

1 8 . 4 .2 .3 N e tw ork co m m and f ra m es

Reference
NCF1 Does the device [R1]/3.4.1, FDT1: O
ZigBee
support the 3.6.3.5.1 FDT2: O FDT1: M
origination of FDT3: X FDT2: M
route request FDT3: X
command frames?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X
NCF2 Does the device [R1]/3.4.1, FDT1: M
ZigBee
support the receipt 3.6.3.5.2 FDT2: M FDT1: M
of route request FDT3: X FDT2: M
command frames? FDT3: X
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X

ZigBee
support the 3.6.3.5.2 FDT2: M FDT1: M

relaying of route FDT3: X FDT2: M
request command FDT3: X
frames?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X
NCF4 Does the device [R1]/3.4.2, FDT1:M,

ZigBee
support the 3.6.3.5.2 FDT2:M, FDT1: M

origination of FDT3:X FDT2: M
route reply FDT3: X
command frames?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X

ZigBee
support the receipt 3.6.3.5.3 FDT2: O FDT1: M

of route reply FDT3: X FDT2: M
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X


Reference

support the 3.6.3.5.3 FDT2:M,
relaying of route FDT3:X
ZigBee
FDT1: M
reply command
FDT2: M
frames?
FDT3: X
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X
ZigBee
support the 3.6.1.9.3, FDT2: M FDT1: M
transmission of 3.6.3.3, FDT3: X FDT2: M
network status 3.6.3.7.1 FDT3: X
command frames?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X
NCF8 Does the device [R1]/3.4.3, M

ZigBee
support the receipt 3.6.1.9.3, FDT1: M

of network status 3.6.3.7.1 FDT2: M
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X

support the 3.4.9, 3.4.10 FDT2:M,
relaying of FDT3:X
network command
ZigBee
FDT1: M
frames? In FDT2: M
particular, does it FDT3: X
support the
relaying of those
command frames,
specifically
network status,
network report
and network
update, which
ZigBee-
require relaying FDT1: M

PRO
but for which FDT2: M

there are no FDT3: X
special per-hop
processing
requirements?


Reference
NCF100 Does the device [R1]/3.4.4, FDT1:O,

support the 3.6.1.10 FDT2:O,
origination of FDT3:O
ZigBee
FDT1: M
leave command
FDT2: M
frames?
FDT3: M
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: M
NCF101 Does the device [R1]/3.4.4, M
ZigBee
of leave command M
frames?
ZigBee-
PRO

ZigBee
support the 3.6.3.5.4 FDT2: O

origination of FDT3: X X
route record
command frames?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X

ZigBee
support the receipt 3.6.3.5.4 FDT2: O

of route record FDT3: X X
command frames?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X

ZigBee

relaying of route FDT3: X X
record command
frames?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X


Reference
NCF106 Does the device [R1]/3.4.6, FDT1:X

support the 3.7.1.3.2.1 FDT2:M
transmission of FDT3:M
rejoin request
command frames?
ZigBee
FDT1: X
FDT2: M
FDT3: M
ZigBee-
FDT1: X
PRO
FDT2: M
FDT3: M
ZigBee
support the 3.7.1.3.2.2 FDT2: M FDT1: M
reception of rejoin FDT3: X FDT2: M
request command FDT3: X
frames?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X

ZigBee
support the 3.7.1.3.2.2 FDT2: M FDT1: M

transmission of FDT3: X FDT2: M
rejoin response FDT3: X
command frames?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X
NCF109 Does the device [R1]/3.4.7, FDT1: X

ZigBee
support the 3.7.1.3.2.1 FDT2: M FDT1: X

reception of rejoin FDT3: M FDT2: M
response FDT3: M
command frames?
ZigBee-
FDT1: X
PRO
FDT2: M
FDT3: M


Reference
NCF110 Does the device [R1]/3.4.9, O

support the 3.6.1.13.1
generation of a
network report
ZigBee
FDT1: X
command frame.
FDT2: M
FDT3: M
ZigBee-
FDT1: X
PRO
FDT2: M
FDT3: M
NCF111 Does the device [R1]/3.4.9, O While this feature is
ZigBee
support the 3.6.1.13.2 FDT1: O optional, one device in
reception of a FDT2: O the network must be
network report FDT3: X designated as the network
command frame manager and for that
device this feature is
mandatory.
ZigBee-
FDT1: O
PRO
FDT2: O
FDT3: X
NCF112 Does the device [R1]/3.4.10, O While this feature is

ZigBee
support the 3.6.1.13.2 FDT1: O optional, one device in

generation of a FDT2: O the network must be
network update FDT3: X designated as the network
command frame. manager and for that
device this feature is
mandatory.
ZigBee-
FDT1: O
PRO
FDT2: O
FDT3: X
NCF113 Does the device [R1]/3.4.10, O

ZigBee
support the 3.6.1.13.3 FDT1: M

reception of a FDT2: M
network update FDT3: M
command frame
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: M

ZigBee

generation of a FDT3: X X
link status
command frame.
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X


Reference
ZigBee
support the 3.6.1.5, FDT2: O
reception of a link 3.6.3.4.2 FDT3: X X
status command
frame.
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X
1 8.5 Security PICS
2 8 . 5 .1 Z i gBe e sec ur it y r o l es
Reference
SR1 Is this device [R1]/1.4, FDT1: M Upon initial network

capable of acting 4.6.2 FDT2: O formation, the
in the role of a FDT3: X coordinator must at least
trust center? temporarily serve as the
trust center. After
formation, at least one of
the routers or the
coordinator must be
capable of acting in the
role of the trust center. It
is an application
responsibility to
transition the trust center
from the coordinator to
another router device
ZigBee
FDT1: M pointed to by apsTrust-

FDT2: O CenterAddress within all
FDT3: X devices in the network if
desired. For the device
whose address is
apsTrustCenterAddress,
it is mandatory to act in
the role of the trust
center. All devices in the
network shall maintain a
single consistent
definition of apsTrust-
CenterAddress. It is
possible, under
application control, to
change apsTrustCenter-
Address during later
network operation,
however, it is the
application’s
ZigBee-
FDT1: M responsibility to ensure

PRO
FDT2: O that all devices in the

FDT3: X network are notified of
the change.

1 8 . 5 .2 Z i gBe e t r us t ce nte r ca pa b i l it ies

Reference
TCC1 Is this device [R1]/1.4.1.2, SR1:O.2

capable of acting 4.6.2.1
ZigBee
as a ZigBee trust X
center in high
security mode?
Every PRO network shall

have a Trust Center either
running in Standard or
High Security mode
The device designated as

the Trust Center shall be
ZigBee-
declared a concentrator in
PRO
SR1: O.2 a PRO network and a
Many to One route shall
be created to the Trust
Center.
At least one of TCC1 or

TCC2 must be supported
if the device supports
SR1.
TCC2 Is this device [R1]/1.4.1.2, SR1:O.2

ZigBee
capable of acting 4.6.2.2

as a ZigBee trust M
center in standard
mode?
Every PRO network shall

have a Trust Center either
High Security mode
The device designated as

the Trust Center shall be
ZigBee-
declared a concentrator in
PRO
SR1: O.2 a PRO network and a

Many to One route shall
be created to the Trust
Center.
At least one of TCC1 or

TCC2 must be supported
if the device supports
SR1.

1 8 . 5 .3 M od es of o pe rat i on
Reference
MOO1 Is this device [R1]/1.4.1.2, O.3

capable of 4.6.2.1
ZigBee
operating in a X
network secured
with a trust center
running in high
security mode?
A PRO device shall join
a PRO network either
ZigBee-
High Security mode.
PRO
O.3
At least one of MOO1 or
MOO2 must be
supported.
MOO2 Is this device [R1]/1.4.1.2, O.3
ZigBee
capable of
operating in a M
network secured
with a trust center
running in
standard mode? A PRO device shall join
a PRO network either
ZigBee-
High Security mode.

PRO
O.3
At least one of MOO1 or
MOO2 must be
supported.
3 8 . 5 .4 S e cu rit y l e ve l s
Reference
SL1 Is this device [R1]/4.5.1.1.1 O.4 The device shall not

capable of apply security to
ZigBee
supporting X outgoing frames or

security level accept secured incoming
0x01? frames using any level
other than level 0x05.
ZigBee-
PRO

ZigBee

ZigBee-
PRO


Reference
ZigBee
ZigBee-
PRO
X
ZigBee
ZigBee-
PRO X
SL5 Is this device [R1]/4.5.1.1.1 O.4 The device shall apply

ZigBee
capable of security to outgoing

supporting M frames or accept secured
security level incoming frames using
0x05? only level 0x05 (i.e.,
ENC-MIC-32)
ZigBee-
PRO

ZigBee

ZigBee-
PRO

ZigBee

ZigBee-
PRO
1
2

1 8 . 5 .5 N W K la ye r s ec ur it y

Reference
NLS1 Does the device [R1]/4.3.1.1 M

support the
ZigBee
security M
processing of
NWK layer
outgoing frames?
ZigBee-
PRO
M
NLS2 Does the device [R1]/4.3.1.2 M
ZigBee
support the
security M
processing of
NWK layer
incoming frames?
ZigBee-
PRO
M
NLS3 Does the device [R1]/4.3.1 M

ZigBee
support the
ZigBee secured M
NWK layer frame
format?
ZigBee-
PRO
NLS4 Does the device [R1]/4.2.1.3, M

ZigBee
support the ability 4.3.3

to manage at least M
one network key
and corresponding
outgoing frame
counter?
ZigBee-
PRO


Reference
NLS5 Does the device [R1]/4.2.1.3, O All devices shall

support the ability 4.3.1, 4.3.3 maintain at least 2 NWK
to manage two keys with the frame
network keys and counters consistent with
corresponding the security mode of the
outgoing frame network (Standard or
counter? High).
ZigBee
M A NWK key of all zero’s
shall be treated as
reserved. Due to the fact
that a NWK key of all
zero’s was used as a
“dummy key” and
employed in the trust
center exchange where
pre-configured keys are
used, a NWK key of all
zero’s is
ZigBee- indistinguishable from
PRO transport of a dummy
M key.
NLS7 Does the device [R1]/4.2.1.3, O Devices using this stack

ZigBee
support at least 4.3.1, 4.3.3 profile in Standard

one frame counter M Security and High
for incoming Security mode shall store
NWK layer a single frame counter
frames for each per neighbor table entry
potential source of associated with the
incoming frames current NWK Key.
(e.g., a coordinator
or router should
support the same
number of
ZigBee-
counters per
PRO
network key as the M

maximum number
of neighbor table
entries and an end
device should
support one
counter per
network key)?
NLS8 Does the device [R1]/4.4.1.2, MOO1: See also the trust centre
ZigBee
support a setting 4.6.2.1, M MOO1: M policies document [R4].

to indicate that all 4.6.2.2 MOO2: MOO2: O
incoming NWK O
frames must be
checked for
freshness (i.e.,
nwkAllFresh).
ZigBee-
PRO
MOO1: M
MOO2: O


Reference
NLS9 Does the device [R1]/4.2.3, O Devices using the ZigBee

support the ability 4.6 and ZigBee-PRO feature
to secure all sets shall set:
incoming and
outgoing NWK
ZigBee
nwkSecureAllFrames =
frames (i.e., the M TRUE
nwkSecureAllFra
mes attribute of
the NIB)?
ZigBee-
PRO
M
NLS10 Does the device [R1]/4.2.3, O Coordinator and Router
ZigBee
support the ability 4.6 MOO1: M devices employing
to reject frames MOO2: O ZigBee and ZigBee PRO
from neighbors Standard Mode security
which have not shall not reject frames
been properly from neighbors which
authenticated? have not been properly
authenticated.
Coordinator and Router
ZigBee-
devices employing
PRO
MOO1: M ZigBee PRO High

MOO2: O Security shall reject
frames from neighbors
which have not been
properly authenticated.
2 8 . 5 .6 A P S la ye r s ec ur it y

Reference
ASLS1 Does the device [R1]/4.4.1.1 M

support the
ZigBee
security M
processing of APS
layer outgoing
frames?
ZigBee-
PRO


Reference

support the
security
processing of APS
layer incoming
ZigBee
frames? M
ZigBee-
PRO
M

support the ZigBee
ZigBee secured M
APS layer frame
format?
ZigBee-
PRO
ASLS4 Does the device [R1]/4.4.3, O In ZigBee and ZigBee

ZigBee
support the ability 4.4.10, 4.6.3 MOO1: M PRO Standard Mode

to manage trust MOO2: O security, trust center
center master master keys are optional
keys? for all devices. In
ZigBee PRO High
Security, trust center
ZigBee-
master keys mandatory

PRO
MOO1: M for all devices.

MOO2: O
ASLS5 Does the device [R1]/4.2.3.5, O In ZigBee and ZigBee

ZigBee
support the ability 4.4.3, 4.4.6, PRO Standard and

to manage 4.4.10, 4.6.3.5 O ZigBee PRO High
application master security modes,
keys? application master keys
are optional for all
devices.
ZigBee-
PRO
ASLS6 Does the device [R1]/4.2.1.3, O

ZigBee
support the ability 4.4.1, 4.4.10

to manage O
application data
keys and
corresponding
security material
(e.g., the incoming
ZigBee-
PRO
and outgoing O
frame counters)?


Reference
ASLS7 Does the device [R1]/4.4.1.2, O ZigBee and ZigBee PRO
ZigBee
support network 4.3.3 Standard Mode or
key incoming X ZigBee-PRO High Mode
frame counters for security use nwkSecure-
incoming APS AllFrames=TRUE, the
layer frames APS security header is
secured with the not employed when the
network key?
ZigBee-
network key is used for
PRO
X incoming APS layer
frames.

support establish- 4.4.2, 4.4.9.1
ZigBee
MOO1: M PRO Standard Mode
key service using security, SKKE is
MOO2: O
the Symmetric- optional for all devices.
Key Key In ZigBee PRO High
Establishment Security, SKKE is
(SKKE) protocol? mandatory for all
ZigBee-
devices.
PRO
MOO1: M
MOO2: O
ASLS9 Does the device [R1]/4.2.3.2, SR1: M

support the 4.4.3, 4.4.9.2
ZigBee
origination of SR1: M
transport-key
commands?
ZigBee-
PRO
SR1: M
ASLS10 Does the device [R1]/4.2.3.2, O A newly joined device in

support the receipt 4.4.3, 4.4.9.2
ZigBee
ZigBee or ZigBee PRO

of transport-key M Standard and ZigBee
commands? PRO High Security shall
be capable of receiving
the NWK key from the
trust center via transport-
ZigBee-
key commands.
PRO
ASLS11 Does the device [R1]/4.2.3.3, FDT1: O

support the 4.4.4, 4.4.9.3 FDT2: O
ZigBee
FDT1: M
origination of FDT3: X FDT2: M
update-device FDT3: X
commands?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X


Reference
ASLS12 Does the device [R1]/4.2.3.3, SR1:M

of update-device
ZigBee
commands? SR1: M
ZigBee-
PRO
SR1: M

support the 4.4.5, 4.4.9.4
ZigBee
remove-device
commands?
ZigBee-
PRO
SR1: M
ASLS14 Does the device [R1]/4.2.3.4, FDT1: O The trust center shall be
support the receipt 4.4.5, 4.4.9.4 FDT2: O
ZigBee
FDT1: M able to ask a ZigBee

of remove-device FDT3: X FDT2: M router or the ZigBee
commands? FDT3: X coordinator to request
that a child device leave
the network.
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X

support the 4.4.6, 4.4.9.5
ZigBee
origination of O
request-key
commands?
ZigBee-
PRO

ZigBee
of request-key SR1: M
commands?
ZigBee-
PRO
SR1: M


Reference

support 4.4.7, 4.4.9.6
ZigBee
switch-key
commands?
ZigBee-
PRO
SR1: M

support receipt of 4.4.7, 4.4.9.6
ZigBee
switch-key M
commands?
ZigBee-
PRO
M
ASLS19 Does the device [R1]/4.4.3.1, SR1:M In ZigBee and ZigBee

support 4.4.9.8 PRO Standard security,
ZigBee
MOO1: M
origination of the ability to originate
MOO2: O
tunnel commands? tunnel commands from
the Trust Center is
optional unless using link
keys. In ZigBee PRO
High Security, it is
ZigBee-
PRO
MOO1: M mandatory.
MOO2: O

MOO2:
support receipt of 4.4.9.8
ZigBee
FDT1: O PRO Standard and High

tunnel commands? security, the ability for
FDT2: O
FDT3: X the coordinator and all
routers to receive tunnel
commands is mandatory.
MOO1:
FDT1: M
FDT2: M
FDT3: X
ZigBee-
PRO
MOO2:
FDT1: O
FDT2: O
FDT3: X


Reference

support the 4.4.8, 4.4.9.7 PRO Standard security,
authentication the ability to support the
service using the authentication service
entity using the entity
authentication authentication protocol is
protocol? optional. In ZigBee PRO
MOO2: High Security, it is
ZigBee
FDT1: O mandatory.
FDT2: O
FDT3: X
MOO1:
FDT1: M
FDT2: M
FDT3: X
ZigBee-
PRO
MOO2:
FDT1: O
FDT2: O
FDT3: X
1 8 . 5 .7 A p p l ic at ion l a ye r s ec ur it y

Reference
ALS1 Is this device [R1]/4.4.10, O Trust Center must

capable of 4.6.1 initially reside on the
learning and ZigBee coordinator but
maintaining may, under application
knowledge of its control, move to any
ZigBee
trust center using router on the PAN as

O
the apsTrust- long as all devices in the
CenterAddress PAN have their
attribute in the apsTrustCenterAddress
AIB? attribute updated
appropriately by the
application.
ZigBee-
PRO
ALS2 Is this device [R1]/4.6.3.1 FDT1: O

capable of FDT2: O
ZigBee
FDT1: M
following the FDT3: X FDT2: M
“joining a secure FDT3: X
network
procedure” in the
role of a router?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X


Reference
ALS3 Is this device [R1]/4.6.3.1 O

capable of
ZigBee
following the FDT1: X
“joining a secure FDT2: M
network FDT3: M
procedure” in the
role of a joining
device?
ZigBee-
FDT1: X
PRO
FDT2: M
FDT3: M
ALS4 Is this device [R1]/4.6.3.2, TCC1: O
ZigBee
capable of 4.6.3.2.2.1 TCC2: O
following the SR1: M
“authentication
procedure” in the
role of a trust
center?
ZigBee-
PRO
SR1: M
ALS5 Is this device [R1]/4.6.3.2, FDT1: O

ZigBee
capable of 4.6.3.2.1 FDT2: O FDT1: M

following the FDT3: X FDT2: M
“authentication FDT3: X
procedure” in the
role of a router?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X
ALS6 Is this device [R1]/4.6.3.2, O For devices

ZigBee
capable of 4.6.3.2.3.1 implementing ZigBee

following the O and ZigBee PRO
“authentication Standard Security,
procedure” in the following the
role of a joining “authentication
device with a procedure” in the role of
preconfigured joining device with a pre-
ZigBee-
network key? configured network key

PRO
O is optional. For devices

implementing ZigBee
PRO High Security, it is
prohibited.


Reference

following the and ZigBee PRO
device with a procedure” in the role of
ZigBee
preconfigured O joining device with a pre-
trust center link configured trust center
key? link key is optional. For
devices implementing
ZigBee PRO High
Security, it is mandatory
unless the ZigBee PRO
High Security Trust
Center policy permits in
the clear delivery of the
master key.
ZigBee-
PRO
O

ZigBee

following the O and ZigBee PRO
device without procedure” in the role of
preconfigured joining device without a
network or trust pre-configured trust
center link keys? center link key is optional
and supported by default
due to the requirement to
permit ZigBee
Residential Security
Mode devices onto PRO
ZigBee-
Standard Security
PRO
O networks as end devices.

For devices
implementing ZigBee
PRO High Security, it is
optional and supported
only if the ZigBee PRO
High Security Trust
Center policy permits in
the clear delivery of the
master key.

ZigBee
capable of 4.6.3.4.1 TCC2: O

following the SR1: M
“network key
update procedure”
in the role of a
trust center?
ZigBee-
PRO
SR1: M


Reference
ALS10 Is this device [R1]/4.6.3.4, O

capable of 4.6.3.4.2
ZigBee
following the FDT1: X
“network key FDT2: M
update procedure” FDT3: M
in the role of a
network device?
ZigBee-
FDT1: X
PRO
FDT2: M
FDT3: M
ALS11 Is this device TCC1:O. This item was
ZigBee
capable of 1 deprecated.
X
following the TCC2:O.
“network key 1
recovery
ZigBee-
procedure” in the
PRO
role of a trust X
center?
ALS12 Is this device O This item was

ZigBee deprecated.
capable of X
following the
“network key
recovery
ZigBee-
procedure” in the
PRO
role of a network X
device?
ALS13 Is this device [R1]/4.6.3.5, TCC1: O For ZigBee and ZigBee

ZigBee
capable of 4.6.3.5.2 TCC2: O PRO Standard Security, it

SR1: O is optional for the trust
following the
“end-to-end center to perform the
application key “end-to-end application
establishment key establishment”
ZigBee-
procedure. For ZigBee

PRO
procedure” in the
SR1: O PRO High Security, it is
role of a trust
center? mandatory.
ALS14 Is this device [R1]/4.6.3.5, O For ZigBee and ZigBee

PRO Standard Security
ZigBee
capable of 4.6.3.5.1,
following the 4.6.3.5.1.2 O and ZigBee PRO High
"end-to-end Security, it is optional for
application key the network devices to
establishment perform the “end-to-end
procedure" in the application key
role of a device establishment”
ZigBee-
receiving a master procedure.

PRO
key for use with O

the SKKE
protocol?
ALS15 Is this device [R1]/4.6.3.5, O For ZigBee and ZigBee

ZigBee
capable of 4.6.3.5.1, PRO Standard Security

O
following the 4.6.3.5.1.1 and ZigBee PRO High
“end-to-end Security, it is optional for
application key the network devices to
establishment perform the “end-to-end
application key
ZigBee-
procedure” in the
PRO
role of a device O establishment”

directly receiving procedure.
a link key?


Reference
ZigBee
capable of 4.6.3.6.1 TCC2: O SR1: M
following the
“network leave
procedure” in the
ZigBee-
role of a trust
PRO
center? SR1: M
ALS17 Is this device [R1]/4.6.3.6, FDT1:O,
ZigBee
capable of 4.6.3.6.2 FDT2:O, FDT1: X
following the FDT3:X FDT2: M
“network leave FDT3: X
procedure” in the
role of a router?
ZigBee-
FDT1: X
PRO
FDT2: M
FDT3: X
ALS18 Is this device [R1]/4.6.3.6, O ZigBee FDT1: X

capable of 4.6.3.6.3 FDT2: M
following the FDT3: M
“network leave
procedure” in the
ZigBee-
role of a leaving FDT1: X

PRO
device? FDT2: M
FDT3: M
ALS19 Is this device [R1]/4.6.3.3, FDT1: O

ZigBee
FDT1: M
capable of 4.6.3.3.1 FDT2: O FDT2: M
following the FDT3: X FDT3: X
“intra-PAN
portability
ZigBee-
procedure” in the FDT1: M

PRO
role of a parent? FDT2: M

FDT3: X
ALS20 Is this device [R1]/4.6.3.3, O

ZigBee
FDT1: X
capable of 4.6.3.3.2 FDT2: X
following the FDT3: M
“intra-PAN
portability
ZigBee-
procedure” in the FDT1: X

PRO
role of an end FDT2: X

device? FDT3: M
ALS21 Is this device [R1]/4.6.3.8, TCC1: O For ZigBee PRO High

ZigBee
capable of 4.6.3.8.1 TCC2: O SR1: O Security, the command

following the tunneling procedure in
“command the role of a trust center
tunneling device is mandatory. For
ZigBee-
procedure” in the ZigBee and ZigBee PRO

PRO
role of a trust SR1: O Standard Security, it is

center device? optional.


Reference
ALS22 Is this device [R1]/4.6.3.8, FDT1: O For ZigBee PRO High

capable of 4.6.3.8.2 FDT2: O Security, the command
following the FDT3: X tunneling procedure in
“command the role of a router device
tunneling is mandatory. For
ZigBee
FDT1: O
procedure” in the FDT2: O ZigBee and ZigBee PRO
role of a router? FDT3: X Standard Security, it is
optional.
ZigBee-
FDT1: O
PRO
FDT2: O
FDT3: X
ALS23 Does the device [R1]/4.2.3.8, O The Permissions

support the 4.6.3.8 Configuration Table is
permissions optional for all devices.
ZigBee
configuration O
table?
ZigBee-
PRO
2 8.6 Application layer PICS
3 8 . 6 .1 Z i gBe e sec ur it y d e vi c e t yp e s

Reference
SDT1 Is this device [R1]/4.2.4, O.2 This item was deprecated

capable of acting 4.6.2 in favor of SR1.
ZigBee
FDT1: M
as a ZigBee Trust FDT2: O
Center? FDT3: X
ZigBee-
FDT1: M
PRO
FDT2: O
FDT3: X


Reference
SDT2 Is this device [R1]/4.6.3 O.2

capable of joining
a secure ZigBee
network only as a
device?
ZigBee
FDT1: X
FDT2: M
FDT3: M
ZigBee-
FDT1: X
PRO
FDT2: M
FDT3: M
2 8 . 6 .2 Z i gBe e A PS f r a me f or m at

Reference
AFF1 Does the device [R1]/2.2.5.1 M

support the
general ZigBee
ZigBee
APS frame
M
format?
ZigBee-
PRO
AFF2 Does the device [R1]/2.2.5.2.1 M

support the
ZigBee
ZigBee APS data M

frame format?
ZigBee-
PRO
AFF3 Does the device [R1]/2.2.5.2.2 O

ZigBee
support the , 2.2.6

ZigBee APS M
command frame
format?
ZigBee-
PRO


Reference
AFF4 Does the device [R1]/2.2.5.2.3 M
ZigBee
support the
ZigBee APS M
acknowledgement
frame format?
ZigBee-
PRO
M
2 8 . 6 .3 M a jo r ca pa b i l it ie s of t he Z igBe e a pp l ic at i on la ye r
3 Tables in the following subclauses detail the capabilities of the APL layer for ZigBee devices.
4 8 . 6 .3 .1 A p p l ic at ion l a ye r f un ct io ns
5 8 . 6 .3 .1 . 1 A p p l ic at ion S up po rt S u b- la ye r f unc t io ns

Reference
ALF1 Does the [R1]/2.2.4.1.1 M

ZigBee
application , 2.2.4.1.2
support sub-layer M
support
transmission of
data by the next
higher layer?
ZigBee-
PRO
ALF200 Does the device [R1]/2.2.4.1.1 O This must be handled by

support the application.
ZigBee
transmission of X
outgoing APS
frames within
APSDE with the
DstAddrMode set
to 0x00 (indirect)
ZigBee-
PRO
ALF201 Does the device [R1]/2.2.4.1.1 M

ZigBee
support
transmission of M
outgoing APS
frames within
APSDE with the
DstAddrMode set
to 0x01 (group
ZigBee-
PRO
addressed) M


Reference
ZigBee
support
transmission of M
outgoing APS
frames within
APSDE with the
DstAddrMode set
to 0x02 (unicast
ZigBee-
PRO
using NWK
address and M
Destination
Endpoint)
ALF203 Does the device [R1]/2.2.4.1.1 O
ZigBee
support
transmission of O
outgoing APS
frames within
APSDE with the
DstAddrMode set
to 0x03 (unicast
ZigBee-
PRO
using IEEE
address and O
Destination
Endpoint)
ALF2 Does the [R1]/2.2.4.1.3 M

ZigBee
application
support sub-layer M
support reception
of data by the next
higher layer at the
endpoint supplied
by the incoming
ZigBee-
PRO
packet? M
ALF300 Does the device [R1]/2.2.4.1.3 O

ZigBee
support reception
of incoming APS X
frames within
APSDE with the
DstAddrMode set
to 0x00 (indirect)
ZigBee-
PRO

ZigBee
support reception
of incoming APS M
frames within
APSDE with the
DstAddrMode set
to 0x01 (group
addressed)
ZigBee-
PRO


Reference
ZigBee
support reception
of incoming APS M
frames within
APSDE with the
DstAddrMode set
to 0x02 (unicast
using NWK
ZigBee-
PRO
address and M
Destination
Endpoint)
ALF3 Does the [R1]/2.2.4.3.1 O Binding support is

application , 2.2.4.3.2, optional for all devices,
support sub-layer 2.2.4.3.3, except that:
support BIND and 2.2.4.3.4
UNBIND requests • Source binding only
and confirms? is supported
(coordinator based
ZigBee
O binding is
disallowed)
• All devices shall

minimally respond
with
NOT_IMPLEMEN
TED
The ZigBee Coordinator

shall implement the
ZigBee-
PRO
mechanism for matching

O
end device bind requests
(AZD24; FDT1: M).
ALF4 Does the device’s [R1]/2.2.4.4.1 M

ZigBee
support sub- layer M
offer the next
higher layer the
ability to get
application
information base
ZigBee-
PRO
(AIB) attributes. M
ALF5 Does the device’s [R1]/2.2.4.4.3 M

ZigBee
support sub- layer M
offer the next
higher layer the
ability to set
application
information base
ZigBee-
PRO
(AIB) attributes. M


Reference
ALF100 Does the [R1]/2.2.4.5.1 M If supported, the group

application , 2.2.4.5.2 table in the APS shall
support sub-layer contain a minimum of 16
ZigBee
support ADD group addresses.
O
GROUP requests
and confirms?
ZigBee-
PRO
O
ALF101 Does the [R1]/ M
ZigBee
application 2.2.4.5.3,
support sub-layer 2.2.4.5.4 O
support REMOVE
GROUP requests
and confirms?
ZigBee-
PRO
ALF102 Does the [R1]/ M

ZigBee
application 2.2.4.5.5,
support sub-layer 2.2.4.5.6 O
support REMOVE
ALL GROUPS
requests and
confirms?
ZigBee-
PRO
2 8 . 6 .3 .1 . 2 A p p l ic at ion l a ye r f rame s

Reference
ADF1 Does the device [R1]/2.2.5.1, M

ZigBee
support the 2.2.5.2.1,

origination of 2.2.8.4.1 M
application data
frames.
ZigBee-
PRO


Reference
ADF2 Does the device [R1]/2.2.5.1 M

support the receipt 2.2.5.2.1,
of application data 2.2.8.3.2,
ZigBee
frames. 2.2.8.3.3
M
ZigBee-
PRO
M
ADF3 Does the device [R1]/ 2.2.5.1, O Use of the auxiliary APS
ZigBee
support the 2.2.5.2.1, security header is
origination of 2.2.8.4.1, O optional for all devices.
application data 4.4.1.1 The application profiles
frames with the shall determine
auxiliary APS requirements for use of
security header? the auxiliary APS
ZigBee-
security header.
PRO
O
ADF4 Does the device [R1]/ 2.2.5.1 O Use of the auxiliary APS
ZigBee
support the receipt 2.2.5.2.1, security header is

of application data 2.2.8.3.2, O optional for all devices.
frames with the 2.2.8.3.3, The application profiles
auxiliary APS 4.4.1.2 shall determine
security header? requirements for use of
the auxiliary APS
ZigBee-
security header.
PRO
ADF5 Does the device [R1]/ 2.2.5.1, O Use of the extended APS
support the 2.2.5.2.1, fragmentation/re-
origination of 2.2.8.4.1, assembly header is
ZigBee
application data 2.2.5.1.8, optional, but in all cases

frames with the 2.2.8.4.5.1 O the parameters shall be
extended APS set by agreement within
fragmentation/re- specific application
assembly header? profiles.

and ZigBee-PRO feature
sets shall set:
ZigBee-
Config_Max_ZDO-
PRO
O _Payload = 0 (i.e. for

compatibility with the
earlier ZigBee feature set,
ZDO messages shall not
be fragmented)


Reference
ADF6 Does the device [R1]/ 2.2.5.1 O Use of the extended APS
support the receipt 2.2.5.2.1, fragmentation/re-
of application data 2.2.8.3.2, assembly header is
frames with the 2.2.8.3.3, optional, but in all cases
extended APS 2.2.5.1.8, the parameters shall be
fragmentation/re- 2.2.8.4.5.2 set by agreement within
ZigBee
assembly header? specific application
O profiles.

and ZigBee-PRO feature
sets shall set:
Config_Max_ZDO-
_Payload = 0 (i.e. for
compatibility with the
earlier ZigBee feature set,
ZigBee-
ZDO messages shall not
PRO
O be fragmented)
1 8 . 6 .3 .1 . 3 A p p l ic at ion l a ye r c om m a nd f rame s

Reference
ACF500 Does the device [R1]/ 2.2.5.1, O

ZigBee
support the 2.2.5.2.2,

origination of 2.2.6, 4.4.1.1 O
command frames
with the auxiliary
APS security
header?
ZigBee-
PRO
ACF501 Does the device [R1]/ 2.2.5.1 O

ZigBee
support the receipt 2.2.5.2.1,

of command 2.2.6, O
frames with the 2.2.8.3.3,
auxiliary APS 4.4.1.2
security header?
ZigBee-
PRO


Reference
ACF1 Does the device [R1]/4.4.9, SDT1: M

support the 4.6.2, 4.6.3.2,
origination of 4.6.3.3,
application 4.6.3.4,
command frames 4.6.3.5,
from the Trust 4.6.3.6,
ZigBee
Center. 4.6.3.7
SR1: M
ZigBee-
PRO
SR1: M
ACF100 Does the device [R1]/4.4.9.1 SDT1:M In ZigBee and ZigBee

support the ZigBee PRO Standard Security
origination of Key SR1: O Mode, it is optional to
Establishment originate Key
application Establishment command
command frames frames from the Trust
from the Trust Center. In ZigBee PRO
Center?
ZigBee-
PRO
SR1: O mandatory.

ZigBee
support the PRO Standard Security

origination of SR1: M Mode, it is mandatory to
Transport Key originate Transport Key
application command frames from
command frames the Trust Center for Key
from the Trust Type 1 (Network Key
Center? Standard Mode). In
ZigBee PRO High
Security Mode, it is
mandatory to originate
Transport Key command
frames from the Trust
Center for Key Type 0
(Trust Center Master
Key) and Key Type 5
ZigBee-
(Network Key High

PRO
SR1: M Security Mode). It is

optional in either ZigBee
and ZigBee PRO
Standard Security or
High Security to
originate Transport Key
command frames for Key
Types 4 (Trust Center
Link Key), Key Type 2
(Application Master Key)
and Key Type 3
(Application Link Key).


Reference
ACF102 Does the device [R1]/4.4.9.4 SDT1:M
ZigBee
support the
Remove Device
application
command frames
from the Trust
Center?
ZigBee-
PRO
SR1: M
ZigBee
support the
Switch Key
application
command frames
from the Trust
Center? ZigBee-
PRO SR1: M

ZigBee
support the
origination of SR1: O
entity
authentication
application
command frames?
MOO2:
ZigBee-
PRO
O
MOO1:
M
ACF2 Does the device [R1]/4.4.9, SDT1:M Mandatory for the trust
ZigBee
support the receipt 4.6.2, 4.6.3.2, centre and optional for

of application 4.6.3.3, SR1: M other devices.
command frames 4.6.3.4,
at the Trust Center 4.6.3.5,
4.6.3.6,
4.6.3.7
ZigBee-
PRO
SR1: M

ZigBee
support the receipt PRO Standard Security

of Key SR1: O Mode, it is optional to
Establishment receive Key
application Establishment command
command frames frames from the Trust
at the Trust Center. In ZigBee PRO
Center?
ZigBee-
PRO
SR1: O mandatory.


Reference

support the receipt PRO Standard Security
of Transport Key Mode, it is mandatory to
application receive Transport Key
command frames command frames from
at the Trust the Trust Center for Key
Center? Type 1 (Network Key
Standard Mode). In
ZigBee PRO High
ZigBee
Security Mode, it is
SR1: M mandatory to receive
frames from the Trust
Center for Key Type 0
(Trust Center Master
Key) and Key Type 5
(Network Key High
Security Mode). It is
optional in ZigBee and
ZigBee PRO Standard
Security to receive
frames for Key Types 4
(Trust Center Link Key),
Key Type 2 (Application
Master Key) and Key
Type 3 (Application Link
Key). It is prohibited in
ZigBee PRO High
ZigBee-
Security to receive
PRO
SR1: M Transport Key command

frames for Key Types 4
(Trust Center Link Key)
and optional to receive
frames for Key Type 2
(Application Master Key)
and Key Type 3
(Application Link Key). 4

ZigBee
support the receipt

of Update Device SR1: M
application
command frames
at the Trust
Center?
ZigBee-
PRO
SR1: M

ZigBee
support the receipt

of Request Key SR1: M
application
command frames
at the Trust
Center?
ZigBee-
PRO
SR1: M
4
CCB 873


Reference
ZigBee
support the receipt
of entity X
authentication
application
command frames?
ZigBee-
PRO
MOO1: M
MOO2: O
ACF3 Does the device [R1]/4.4.9, SDT2:M In ZigBee and ZigBee
ZigBee
support the 4.6.3 FDT1: X PRO Standard Security,
origination of FDT2: M non Trust Center devices
application FDT3: O may optionally originate
command frames application command
from a non-Trust frames. In ZigBee PRO
Center device. MOO1: High Security, all non
FDT1: X Trust Center routers and
FDT2: M the coordinator shall
FDT3: M originate application
ZigBee-
PRO
command frames and end

devices may originate
MOO2:
application command
FDT1: X
frames.
FDT2: M
FDT3: O
ACF300 Does the device [R1]/4.4.9.1, SDT2:M In ZigBee and ZigBee

support the 4.6.3.5 PRO Standard Security, it
origination of Key is optional for all devices
ZigBee
Establishment O to support origination of

application Key Establishment
command frames command frames from a
from a non-Trust non Trust Center device.
Center device? In ZigBee PRO High
Security, it is mandatory
for all devices to support
ZigBee-
origination of Key
PRO
O Establishment command
frames from a non Trust
Center device.

ZigBee
support the
origination of O
Transport Key
application
command frames
from a non-Trust
Center device?
ZigBee-
PRO
ACF302 Does the device [R1]/4.4.9.3, SDT2:M Assumes it is legal to

ZigBee
support the 4.6.3.4 FDT1: M have the Trust Center on

origination of FDT2: M a non-ZigBee
Update Device FDT3: O Coordinator device for
application the ZigBee feature set via
command frames ZigBee-2007
from a non-Trust
Center device?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: O


Reference
ZigBee
support the
origination of O
Request Key
application
command frames
from a non-Trust
Center device?
ZigBee-
PRO
O
ACF304 Does the device [R1]/4.4.9.7, SDT2:M

support the 4.6.3.2
ZigBee
origination of O
Authenticate
application
command frames
from a non-Trust
Center device?
ZigBee-
PRO
O
ACF4 Does the device [R1]/4.4.9, SDT1:M, SR1: In all ZigBee and ZigBee
ZigBee
support the receipt 4.6.3 SDT2:M FDT1: M PRO security modes, the
of application FDT2: M Trust Center shall receive
command frames FDT3: O application command
from a non-Trust frames from non Trust
Center device. Center devices. In
ZigBee and ZigBee PRO
Standard Security, all non
Trust Center routers and
the coordinator shall
SR1:
ZigBee-
receive application
PRO
FDT1: M command frames. In

FDT2: M ZigBee PRO High
FDT3: O Security, all non Trust
Center devices shall
receive application
command frames.
ACF400 Does the device [R1]/4.4.9.1, SDT1:M, For all devices in ZigBee
ZigBee
support the receipt 4.6.3.5 SDT2:M PRO Standard Security,

of Key O receipt of Key
Establishment Establishment application
application command frames from a
command frames non Trust Center device
from a non-Trust is optional. In ZigBee
Center device? PRO High Security,
receipt of Key
ZigBee-
PRO
Establishment application
O command frames from
non Trust Center devices
is mandatory in all
devices.


Reference
ACF401 Does the device [R1]/4.4.9.2 SDT1:M,

support the receipt SDT2:M
of Transport Key
application
ZigBee
command frames SR1: M
from a non-Trust SDT2: M
Center device?
ZigBee-
PRO
SR1: M
SDT2: M
ACF402 Does the device [R1]/4.4.9.3, SDT1:M
ZigBee
of Update Device SR1: M
application
command frames
from a non-Trust
Center device?
ZigBee-
PRO
SR1: M

ZigBee
support the receipt

of Request Key SR1: M
application
command frames
from a non-Trust
Center device?
ZigBee-
PRO
SR1: M
ACF404 Does the device [R1]/4.4.9.7, SDT1:M Need a comment that this
ZigBee
support the receipt 4.6.3.2 SDT2:M feature is optional in

of entity O ZigBee and ZigBee PRO
authenticate Standard Security and
application mandatory for all devices
command frames in ZigBee PRO High
from a non-Trust Security.
Center device?
ZigBee-
PRO

1 8 . 6 .3 .1 . 4 A p p l ic at ion ac know le dg ement f ra me s

Reference
AFR1 Does the device [R1]/2.2.8.3.1 M

support the , 2.2.8.3.3
origination of
ZigBee
application M
acknowledgement
frames.
ZigBee-
PRO
M
AFR2 Does the device [R1]/2.2.8.3.2 M

support the receipt , 2.2.8.3.3
ZigBee
of application M
acknowledgement
frames?
ZigBee-
PRO
M
2 8 . 6 .3 .1 . 5 Z i gBe e D evic e O b ject s f u nct i on s

Reference
AZD700 Does the device [R1]/4.6.3.8 O

ZigBee
support the
permissions O
configuration
table?
ZigBee-
PRO
AZD701 Does the device [R1]/4.6.3.8 AZD700:

ZigBee
support the O AZD700:

ModifyPermission O
sCapabilityTable
element of the
permissions
configuration
ZigBee-
table?
PRO
AZD700:
O


Reference

support the O
NetworkSettings
ZigBee
element of the AZD700:
permissions O
configuration
table?
ZigBee-
PRO
AZD700:
O

support the O
ZigBee
Application- AZD700:
Settings element O
of the permissions
configuration
table?
ZigBee-
PRO
AZD700:
O

ZigBee

SecuritySettings O
element of the
permissions
configuration
table?
ZigBee-
PRO
AZD700:
O

ZigBee

Application- O
Commands
element of the
permissions
configuration
table?
ZigBee-
PRO
AZD700:
O

ZigBee

SKKEWith- O
MasterKey
element of the
permissions
configuration
table?
ZigBee-
PRO
AZD700:
O


Reference
AZD707 Does the device [R1]/ M Support of the rejoin

support the NWK 3.6.1.4.2 mechanism for
rejoin procedure? recovering from a missed
ZigBee
M network update (of any
kind) is mandatory ([R1]
Section 2.5.5.5.4).
The length of time
between hearing from its
parent, or from the
ZigBee coordinator,
beyond which a ZigBee
ZigBee-
router shall initiate steps
PRO
M to rejoin the “fragment”
of the network which has
the ZigBee coordinator in
it, is left up to the
application designer.
AZD600 Does the device [R1]/2.5.5.5.3 FDT1: O
ZigBee
act as a Binding FDT2: O FDT1: O
Table Cache? FDT3: X FDT2: O
FDT3: X
ZigBee-
FDT1: O
PRO
FDT2: O
FDT3: X
AZD601 Does the device [R1]/2.5.5.5.4 FDT1: M

ZigBee
perform the Intra- FDT2: M FDT1: M

PAN portability FDT3: X FDT2: M
parent procedure? FDT3: X
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X
AZD602 Does the device [R1]/2.5.5.5.4 FDT1: X

perform the Intra- FDT2: X
PAN portability FDT3: M
ZigBee
FDT1: X
child procedure?
FDT2: X
FDT3: M
ZigBee-
FDT1: X
PRO
FDT2: X
FDT3: M


Reference
AZD603 Does the device [R1]/2.5.5.5.6 O For the ChannelMask

support the .1, 2.5.5.5.6.2, parameter, in the 2.4 Ghz
Configuration 2.5.5.5.6.3 band, channel 26 shall
Parameters, either not be used or else
ZigBee
Startup Procedures a special provision for
and Additional O limited transmission
Configuration power shall be imposed
Parameters? to permit U.S. FCC
operations.
ZigBee-
PRO
M
AZD1 Does the device [R1]/2.5.5.6.1 M

ZigBee
support the
mandatory Device M
and Service
Discovery Object?
ZigBee-
PRO

ZigBee
support the
mandatory M
attributes of the
Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3 Does the device [R1]/2.5.5.6.1 O

ZigBee
support the
optional attributes O
of the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD4 Does the device [R1]/2.5.5.6.1 AZD3: O

ZigBee
support the
optional NWK AZD3: O
address client
service of the
Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O


Reference
ZigBee
support the
optional IEEE AZD3: O
address client
service of the
Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O
ZigBee
support the
optional Node AZD3: O
Descriptor client
service of the
Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O

ZigBee
support the
optional Power AZD3: O
Descriptor client
service of the
Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O

ZigBee
support the
optional Simple AZD3: O
Descriptor client
service of the
Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O

ZigBee
support the
optional Active AZD3: O
Endpoint client
service of the
Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O


Reference

support the
ZigBee
optional Match
Descriptor client AZD3: O
service of the
Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O
ZigBee
support the
optional Complex AZD3: O
Descriptor client
service of the
Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O

ZigBee
support the
optional Complex AZD3: O
Descriptor server
service of the
Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O

ZigBee
support the
optional User AZD3: O
Descriptor client
service of the
Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O

ZigBee
support the
optional User AZD3: O
Descriptor server
service of the
Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O


Reference
AZD17 Does the device [R1]/2.5.5.6.1 AZD1: M
ZigBee
support the
mandatory Device M
Announce client
service of the
Device and
Service Discovery
Object?
ZigBee-
PRO
M
AZD18 Does the device [R1]/2.5.5.6.1 AZD1: M
ZigBee
support the Device
Announce server M
service of the
Device and
Service Discovery
Object?
ZigBee-
PRO
M

ZigBee
support the
optional System AZD3: O
Server Discovery
client service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O

ZigBee
support the
optional System AZD3: O
Server Discovery
server service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
SR1: M

support the
ZigBee
optional AZD3: O
Discovery Cache
client service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O


Reference

support the AZD3:
ZigBee
optional FDT1: O
Discovery Cache FDT2: O
server service of FDT3: X
the Device and
Service Discovery
Object?
AZD3:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: X
ZigBee
support the
optional AZD3: O
Discovery Store
client service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O
AZD105 Does the device [R1]/2.5.5.6.1 AZD103:

ZigBee
support the M AZD103:

optional M
Discovery Store
server service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD103:
M

ZigBee
support the
optional Node AZD3: O
Descriptor Store
client service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O

ZigBee

optional Node M
Descriptor Store
server service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD103:
M


Reference

support the
ZigBee
optional Power
AZD3: O
Descriptor Store
client service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O
ZigBee
optional Power M
Descriptor Store
server service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD103:
M

ZigBee
support the
optional Active AZD3: O
Endpoint Store
client service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O

ZigBee

optional Active M
Endpoint Store
server service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD103:
M

support the
ZigBee
optional Simple AZD3: O

Descriptor Store
client service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O


Reference

support the M
ZigBee
optional Simple AZD103:
Descriptor Store M
server service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD103:
M
ZigBee
support the
optional Remove AZD3: O
Node Cache client
service of the
Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O

ZigBee

optional Remove M
Node Cache
server service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD103:
M

ZigBee
support the
optional Find AZD3: O
Node Cache client
service of the
Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O

ZigBee

optional Find M
Node Cache
server service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD103:
M


Reference

support the
ZigBee
optional Extended
Simple Descriptor AZD3: O
client service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O
ZigBee
optional Extended M
Simple Descriptor
server service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD103:
M

ZigBee
support the
optional Extended AZD3: O
Active Endpoint
client service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD3: O

ZigBee

optional Extended M
Active Endpoint
server service of
the Device and
Service Discovery
Object?
ZigBee-
PRO
AZD103:
M
AZD19 Does the device [R1]/2.5.5.7.1 O

support the
ZigBee
optional Security M
Manager Object?
ZigBee-
PRO


Reference
ZigBee
support the SDT1: M
mandatory SR1: M
attributes of the
Security Manager
Object with the
device in a Trust
Center role?
ZigBee-
PRO
SR1: M
ZigBee
support the SDT2: M
mandatory SDT2: M
attributes of the
Security Manager
Object with the
device in a non-
Trust Center role? ZigBee-
PRO SDT2: M
AZD22 Does the device [R1]/2.5.5.8.1 O End_Device_Bind_req

ZigBee
support the FDT1: M server processing in the

optional Binding FDT2: O coordinator is required.
Manager Object? FDT3: O
The ZigBee coordinator
must process end device
bind requests and supply
ZigBee-
FDT1: M Bind_req commands to

PRO
FDT2: O the source of matched

FDT3: O clusters in the paired end
device bind requests.
AZD23 Does the device [R1]/2.5.5.8.1 AZD22: AZD22:

ZigBee
support the FDT1: O FDT1: O

optional End [R1]/2.4.3.2.1 FDT2: O FDT2: O
Device Bind client FDT3: O FDT3: O
service of the
Binding Manager
Object?
AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O

ZigBee
support the FDT1: M FDT1: M

optional End [R1]/2.4.4.2.1 FDT2: X FDT2: X
Device Bind FDT3: X FDT3: X
server service of
the Binding
Manager Object?
AZD22:
ZigBee-
PRO
FDT1: M
FDT2: X
FDT3: X


Reference

support the FDT1: O AZD22:
ZigBee
optional Bind [R1]/2.4.3.2.2 FDT2: O FDT1: O
client service of FDT3: O FDT2: O
the Binding FDT3: O
Manager Object?
AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O
ZigBee
server service of FDT3: O FDT3: O
the Binding
Manager Object?
AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O

ZigBee

optional Unbind [R1]/2.4.3.2.3 FDT2: O FDT2: O
client service of FDT3: O FDT3: O
the Binding
Manager Object?
AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O

ZigBee

optional Unbind [R1]/2.4.4.2.3 FDT2: O FDT2: O
server service of FDT3: O FDT3: O
the Binding
Manager Object?
AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O

AZD22:
support the FDT1: O
ZigBee
FDT1: O
optional Bind [R1]/2.4.3.2.4 FDT2: O
FDT2: O
Register client FDT3: O
FDT3: O
service of the
Binding Manager
Object?
AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O


Reference
ZigBee
Register server FDT3: O FDT3: O
service of the
Binding Manager
Object?
AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O
ZigBee
optional Replace [R1]/2.4.3.2.5 FDT2: O FDT2: O
Device client FDT3: O FDT3: O
service of the
Binding Manager
Object?
ZigBee- AZD22:
PRO FDT1: O
FDT2: O
FDT3: O

ZigBee

optional Replace [R1]/2.4.4.2.5 FDT2: O FDT2: O
Device server FDT3: O FDT3: O
service of the
Binding Manager
Object?
AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O

ZigBee

optional Store [R1]/2.4.3.2.6 FDT2: O FDT2: O
Backup Bind FDT3: O FDT3: O
Entry client
service of the
Binding Manager
Object? AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O

ZigBee

optional Store [R1]/2.4.4.2.6 FDT2: O FDT2: O
Entry server
service of the
Binding Manager
Object? AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O


Reference

ZigBee
optional Remove [R1]/2.4.3.2.7 FDT2: O FDT1: O
Entry client FDT3: O
service of the
Binding Manager
Object?
AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O
ZigBee
optional Remove [R1]/2.4.4.2.7 FDT2: O FDT2: O
Entry server
service of the
Binding Manager
Object? AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O

ZigBee

optional Backup [R1]/2.4.3.2.8 FDT2: O FDT2: O
Bind Table client FDT3: O FDT3: O
service of the
Binding Manager
Object?
AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O

ZigBee

Bind Table server FDT3: O FDT3: O
service of the
Binding Manager
Object?
AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O

AZD22:
support the FDT1: O
ZigBee
FDT1: O
optional Recover [R1]/2.4.3.2.9 FDT2: O
FDT2: O
Bind Table client FDT3: O
FDT3: O
service of the
Binding Manager
Object?
AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O


Reference
ZigBee
optional Recover [R1]/2.4.4.2.9 FDT2: O FDT2: O
Bind Table server FDT3: O FDT3: O
service of the
Binding Manager
Object?
AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O
ZigBee
Source Bind client 0 FDT3: O FDT3: O
service of the
Binding Manager
Object?
ZigBee- AZD22:
PRO FDT1: O
FDT2: O
FDT3: O

ZigBee

Source Bind 0 FDT3: O FDT3: O
server service of
the Binding
Manager Object?
AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O

ZigBee

Source Bind client 1 FDT3: O FDT3: O
service of the
Binding Manager
Object?
AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O

ZigBee

Source Bind 1 FDT3: O FDT3: O
server service of
the Binding
Manager Object?
AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O


Reference

ZigBee
optional APSME FDT2: O FDT1: O
BIND and FDT3: O FDT2: O
UNBIND service FDT3: O
of the Binding
Manager Object?
AZD22:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O
ZigBee
support the
mandatory NLME M
GET, SET and
NETWORK
DISCOVERY
services of the
Network Manager
ZigBee-
PRO
Object? M

ZigBee
support the FDT2: X FDT1: M

optional NLME FDT3: X FDT2: X
NETWORK FDT3: X
FORMATION
service of the
Network Manager
Object?
ZigBee-
FDT1: M
PRO
FDT2: X
FDT3: X

ZigBee
support the FDT2: M FDT1: X

optional NLME FDT3: M FDT2: M
JOIN service of FDT3: M
the Network
Manager Object?
ZigBee-
FDT1: X
PRO
FDT2: M
FDT3: M

ZigBee
support the FDT2: M FDT1: X

optional NLME FDT3: X FDT2: M
START ROUTER FDT3: X
service of the
Network Manager
Object?
ZigBee-
FDT1: X
PRO
FDT2: M
FDT3: X


Reference

support the FDT2: M
ZigBee
FDT1: X
mandatory NLME FDT3: M FDT2: M
LEAVE service of FDT3: M
the Network
Manager Object?
ZigBee-
FDT1: X
PRO
FDT2: M
FDT3: M
ZigBee
optional NLME FDT3: X FDT2: M
PERMIT FDT3: X
JOINING service
of the Network
Manager Object? ZigBee-
PRO FDT1: M
FDT2: M
FDT3: X

ZigBee

optional NLME FDT3: O FDT2: O
RESET service of FDT3: O
the Network
Manager Object?
ZigBee-
FDT1: O
PRO
FDT2: O
FDT3: O
AZD35 Does the device [R1]/2.5.5.9.1 FDT1: O See clause 8.4.2.1 in this
ZigBee
support the FDT2: O FDT1: X document, Network layer

optional NLME FDT3: O FDT2: X functions, Item number
SYNC service of FDT3: M NLF17.
the Network
Manager Object?
ZigBee-
FDT1: X
PRO
FDT2: X
FDT3: M

ZigBee
support the
mandatory NLME M
NWK_STATUS
service of the
Network Manager
Object?
ZigBee-
PRO

Reference

support the FDT2: O
ZigBee
optional NLME FDT3: O FDT1: O
ROUTE FDT2: O
DISCOVERY FDT3: O
service of the
Network Manager
Object?
ZigBee-
FDT1: O
PRO
FDT2: O
FDT3: O
AZD36 Does the device [R1]/2.5.5.10. FDT1: O
ZigBee
support the 1 FDT2: O FDT1: O
optional Node FDT3: O FDT2: O
Manager Object? FDT3: O
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: O
AZD37 Does the device [R1]/2.5.5.10. AZD36: AZD36:

ZigBee

Manager NWK FDT3: O FDT3: O
Discovery client
service?
AZD36:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O

ZigBee
support the 1 FDT1: O FDT1: M

optional Node FDT2: O FDT2: M
Manager NWK FDT3: O FDT3: O
Discovery server
service?
AZD36:
ZigBee-
PRO
FDT1: M
FDT2: M
FDT3: O
AZD39 Does the device [R1]/2.5.5.10. AZD36:

AZD36:
support the 1 FDT1: O
ZigBee

Manager LQI FDT3: O FDT2: O
FDT3: O
client service?
AZD36:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O

Reference
ZigBee
Manager LQI FDT3: O FDT3: O
server service?
AZD36:
ZigBee-
PRO
FDT1: M
FDT2: M
FDT3: O
ZigBee
Manager RTG FDT3: O FDT3: O
client service?
ZigBee- AZD36:
PRO FDT1: O
FDT2: O
FDT3: O

ZigBee

Manager RTG FDT3: O FDT3: O
server service?
AZD36:
ZigBee-
PRO
FDT1: M
FDT2: M
FDT3: O

ZigBee

Manager Bind FDT3: O FDT3: O
client service?
AZD36:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O

ZigBee

Manager Bind FDT3: O FDT3: O
server service?
AZD36:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O

Reference

support the 1 FDT1: O AZD36:
ZigBee
Manager Leave FDT3: O FDT2: O
client service? FDT3: O
AZD36:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O
ZigBee
Manager Leave FDT3: O FDT3: O
server service?
AZD36:
ZigBee-
PRO
FDT1: M
FDT2: M
FDT3: O

ZigBee

Manager Direct FDT3: O FDT3: O
Join client
service?
AZD36:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O

ZigBee

optional Node FDT2: O X
Manager Direct FDT3: O
Join server
service?
ZigBee-
PRO

AZD36:
ZigBee

Manager Permit FDT3: O FDT2: M
FDT3: X
Joining client
service?
AZD36:
ZigBee-
PRO
FDT1: M
FDT2: M
FDT3: X

Reference
ZigBee
Manager FDT3: O FDT3: O
Discovery Cache
client service?
AZD36:
ZigBee-
PRO
FDT1: O
FDT2: O
FDT3: O
ZigBee
Manager FDT3: O FDT3: O
Discovery Cache
server service?
ZigBee- AZD36:
PRO FDT1: O
FDT2: O
FDT3: O
AZD800 Does the device [R1]/2.4.3.3.9 AZD36: AZD36: The ability to send the
ZigBee
support the FDT1: O FDT1: O Mgmt_NWK_Update-

optional Node FDT2: O FDT2: O _req command in order to
Manager NWK FDT3: X FDT3: O request the target to
update client perform an energy scan is
service? mandatory for the
Network Channel
AZD36:
ZigBee-
Manager, and optional

PRO
FDT1: O for all non Network

FDT2: O Channel Manager routers
FDT3: O and the coordinator.
AZD801 Does the device [R1]/2.4.4.3.9 AZD36: AZD36: The ability for a non
ZigBee
support the FDT1: O FDT1: O Network Channel

optional Node FDT2: O FDT2: O Manager to receive and
Manager NWK FDT3: O FDT3: O process the
update server Mgmt_NWK_Update_-
service? req command is
mandatory for the
AZD36:
ZigBee-
network manager and all

PRO
FDT1: O routers and optional for

FDT2: O end devices.
FDT3: O
AZD49 Does the device [R1]/2.5.6 M

ZigBee
support the
mandatory M
Configuration
Attributes?
ZigBee-
PRO

Reference
AZD50 Does the device [R1]/2.5.6 O

support the
ZigBee
optional Complex
Descriptor O
configuration
attribute?
ZigBee-
PRO
O
ZigBee
support the
optional User O
Descriptor
configuration
attribute?
ZigBee-
PRO
O

ZigBee
support the
optional Max Bind O
configuration
attribute?
ZigBee-
PRO

ZigBee
support the
optional Master O
Key configuration
attribute?
ZigBee-
PRO
AZD54 Does the device [R1]/2.5.6 FDT1: M

support the FDT2: X
ZigBee
FDT1: M
optional End FDT3: X FDT2: X
Device Bind FDT3: X
Timeout
configuration
attribute?
ZigBee-
FDT1: M
PRO
FDT2: X
FDT3: X

Reference
AZD55 Does the device [R1]/2.5.6 FDT1: M
ZigBee
optional Permit FDT3: X FDT2: M
Join Duration FDT3: X
configuration
attribute?
ZigBee-
FDT1: M
PRO
FDT2: M
FDT3: X
AZD56 Does the device [R1]/2.5.6 AZD19:
ZigBee
support the O
Security Level
configuration
attribute?
ZigBee-
PRO AZD19: O
AZD57 Does the device [R1]/2.5.6 AZD19:

ZigBee
support the O
Secure All Frames
configuration
attribute?
ZigBee-
PRO
AZD19: O
AZD500 Does the device [R1]/2.5.6 AZD19: AZD19:

ZigBee

optional NWK FDT2: M FDT2: M
Leave Remove FDT3: X FDT3: X
Children
configuration
attribute?
AZD19:
ZigBee-
PRO
FDT1: M
FDT2: M
FDT3: X
AZD501 Does the device [R1]/2.5.6 FDT1: O

ZigBee

optional NWK FDT3: X FDT2: O
Broadcast FDT3: X
Delivery
configuration
attribute?
ZigBee-
FDT1: O
PRO
FDT2: O
FDT3: X

Reference

support the FDT2: O
ZigBee
Transaction FDT2: O
Persistence Time FDT3: X
configuration
attribute?
ZigBee-
FDT1: O
PRO
FDT2: O
FDT3: X
AZD503 Does the device [R1]/2.5.6 FDT1: X
ZigBee
support the FDT2: X FDT1: X
optional NWK FDT3: M FDT2: X
Indirect Poll Rate FDT3: M
configuration
attribute?
ZigBee-
FDT1: X
PRO
FDT2: X
FDT3: M

ZigBee

optional Max FDT3: X FDT2: O
Associations FDT3: X
configuration
attribute?
ZigBee-
FDT1: O
PRO
FDT2: O
FDT3: X

ZigBee

Direct Join FDT3: X
Addresses
configuration
attribute?
ZigBee-
FDT1: O
PRO
FDT2: O
FDT3: X

support the FDT2: O
ZigBee
FDT1: X
optional Parent FDT3: O FDT2: O
Link Retry FDT3: O
Threshold
configuration
attribute?
ZigBee-
FDT1: X
PRO
FDT2: O
FDT3: O

Reference
ZigBee
support the FDT2: O FDT1: X
optional Orphan FDT3: O FDT2: O
Rejoin Interval FDT3: O
configuration
attribute?
ZigBee-
FDT1: X
PRO
FDT2: O
FDT3: O
ZigBee
support the FDT2: O FDT1: X
optional Max FDT3: O FDT2: O
Orphan Rejoin FDT3: O
Interval
configuration
attribute?
ZigBee- FDT1: X
PRO FDT2: O
FDT3: O
1 8 . 6 .3 .1 . 6 Z i gBe e A pp l i cat i on Fr a mew ork f unc t io ns

Reference
AAF2 Does the device [R1]/2.3.2 M

ZigBee
support the
mandatory ZigBee M
Descriptor
structures?
ZigBee-
PRO
AAF3 Does the device [R1]/2.3.2 O

support the
ZigBee
optional ZigBee O
Complex
Descriptor
structure?
ZigBee-
PRO
AAF4 Does the device [R1]/2.3.2 O

ZigBee
support the
optional ZigBee O
User Descriptor
structure?
ZigBee-
PRO

Reference
AAF5 Does the device [R1]/2.3.2.1 M
ZigBee
support the
transmission of M
descriptors?
ZigBee-
PRO
M

ZigBee Layer PICS and Stack Profiles

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ZigBee Layer PICS and Stack Profiles

Încărcat de

Drepturi de autor:

Formate disponibile

1

5 ZigBee Document 08006r03

13 Accepted for release by:

Copyright © 1996-2008 by the ZigBee Alliance.

Page ii Copyright © 2008, The ZigBee Alliance. All rights reserved.

4 Phil Jamieson: Chair

Page iv Copyright © 2008, The ZigBee Alliance. All rights reserved.

9 4 Acronyms and abbreviations....................................................................................................................4

10 5 General description ..................................................................................................................................5

32 8 Protocol implementation conformance statement (PICS) proforma.......................................................13

1 8.6 Application layer PICS..................................................................................................................69

Page vi Copyright © 2008, The ZigBee Alliance. All rights reserved.

2 Table 1 – Document revision change history ................................................................................................ ix

2 Table 1 shows the change history for this specification.

3 Table 1 – Document revision change history

00 Original version as a merge of 064321r08, 074855r04, 04319r01,

01 Snapshot version provided to Core Stack and Qualification Working

02 Major PICS update following many test events. Overhaul of the

03 Final updates during the June 2008 ZigBee members meeting in

Copyright © 2008, The ZigBee Alliance. All rights reserved. Page ix

Copyright © 2008, The ZigBee Alliance. All rights reserved. Page 1

8 2.1 ZigBee Alliance documents

16 2.2 IEEE documents

Page 2 Copyright © 2008, The ZigBee Alliance. All rights reserved.

ZigBee coordinator An IEEE 802.15.4-2003 PAN coordinator operating in a ZigBee

ZigBee end device An IEEE 802.15.4-2003 RFD or FFD participating in a ZigBee

ZigBee router An IEEE 802.15.4-2003 FFD participating in a ZigBee network,

Copyright © 2008, The ZigBee Alliance. All rights reserved. Page 3

1 4 Acronyms and abbreviations

FFD IEEE 802.15.4 Full Function Device

IEEE Institute of Electrical and Electronic Engineers

PICS Protocol Implementation Conformance Statement

RFD IEEE 802.15.4 Reduced Function Device

Page 4 Copyright © 2008, The ZigBee Alliance. All rights reserved.

6 • Functional description – further operational restrictions to be applied to all devices in this

8 • Protocol implementation conformance statement (PICS) – a formal definition of functionality

Copyright © 2008, The ZigBee Alliance. All rights reserved. Page 5

6 6.2 Network settings

9 Table 2 – Network settings for this feature set

Parameter Name Setting Comments

that case, is a multiplier for aBaseSuperframeDuration.

The value here yields a persistence time of 7.68

cost on the basis of neighbor link cost and never report

10 6.3 Application settings

14 Table 3 – Application settings for this feature set

Parameter Name Setting Comments

Page 6 Copyright © 2008, The ZigBee Alliance. All rights reserved.

Parameter Name Setting Comments

3 Table 4 – Security settings for this feature set

Parameter Name Setting Comments

not more than 10 hops.

I.e. 700 milliseconds. Note that this timeout assumes

Where AES Encrypt/Decrypt times = 200ms, and

Where NWK Maximum Depth is assumed to be 15,

meaning every device in the network can be reached in

not more than 30 hops.

I.e. 1.7 seconds. Note that this timeout assumes worst

Copyright © 2008, The ZigBee Alliance. All rights reserved. Page 7

6 7.1 Device roles

30 7.2 ZigBee: Compatibility w ith Other Feature sets

40 This section is valid for the ZigBee feature set.

Page 8 Copyright © 2008, The ZigBee Alliance. All rights reserved.

1 7.3 ZigBee-PRO: Compatibility w ith Other Feature sets

13 This section is valid for the ZigBee-PRO feature set.