ZigBee-2007层PICS与堆栈配置规范概述

需积分: 9 101 浏览量更新于2024-07-23 收藏 493KB PDF 举报

本文档是关于ZigBee Alliance在2008年发布的ZigBee-2007层PICS (Protocol Interconnect and Communication Specification) 及Stack Profiles的修订版03。ZigBee是一种低功耗、低成本的无线通信技术，主要应用于物联网(IoT)设备之间的通信，特别是智能家居、工业自动化和智能城市等领域。 ZigBee协议栈由多个层次构成，包括物理层(Physical Layer)、数据链路层(Data Link Layer)、网络层(Network Layer)和应用支持子层(Application Support Sub-layer)。这些层定义了设备如何通过无线网络进行通信，确保数据的可靠传输、安全性和网络管理。文档的版权信息表明，所有权利归ZigBee Alliance所有，只有联盟成员在保留此通知的前提下，才可复制该文档供内部使用。未经ZigBee Alliance书面许可，任何形式的商业或营利性复制都是严格禁止的。该文档作为未接受发布状态的ZigBee规范草案，可能会有所变更。 "Stack profiles"部分是文档的核心内容，它定义了一系列预定义的应用程序接口和功能集，这些堆栈配置适用于不同的设备类型和应用场景。例如，ZigBee-Pro可能提供了更高级别的功能和性能，而基础的ZigBee则更适合对成本和功耗有严格要求的简单设备。堆栈设计旨在简化开发过程，使制造商能够快速部署符合标准的设备。文档的"Abstract"部分可能概述了整个规范的主要目标和组成部分，强调了ZigBee在提供高效、低功耗的无线通信方面的优势，以及其在物联网生态系统中的作用。关键词如"ZigBee", "ZigBee-Pro", "Stack profile", 和 "Architecture"，反映了文档关注的重点，即技术架构、功能特性和标准化的应用环境。 ZigBee-2007 Layer PICS和Stack Profiles文档对于理解和实施ZigBee技术至关重要，它为开发者和制造商提供了一套完整的框架，以创建兼容的、互操作的ZigBee设备和系统。通过理解并遵循这些规格，用户可以确保设备间的无缝通信，并且能够在日益复杂的物联网环境中有效地工作。

ZigBee-2007 Layer PICS and Stack Profiles ZigBee Document 08006r03, June 2008

Page 6

This is an unaccepted ZigBee specification draft, subject to change.

6 Knob settings 1

6.1 Introduction 2

This section specifies values for parameters specified in the ZigBee specification for tuning the 3

operation of the ZigBee and ZigBee-PRO stack. This section describes settings for both ZigBee and 4

ZigBee-PRO feature sets applied to the ZigBee-2007 Specification (

[R1]) 5

6.2 Network settings 6

The network settings for the ZigBee and ZigBee-PRO feature sets are, for the most part, described in 7

the restricted PICS captured in Section

8.4. Those setting not covered by the PICS are listed in Table 2. 8

Table 2 – Network settings for this feature set 9

Parameter Name Setting Comments

ZigBee

nwkTransactionPersistenceTime 0x01f4

ZigBee-

PRO

Note that this value essentially “covers” the MAC

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

that case, is a multiplier for aBaseSuperframeDuration.

The value here yields a persistence time of 7.68

seconds using the 2.4Ghz symbol rate from

[R5] in a

non-beaconed network.

ZigBee

nwkReportConstantCost FALSE

ZigBee-

PRO

The NWK layer in PRO shall always calculate routing

cost on the basis of neighbor link cost and never report

constant cost.

6.3 Application settings 10

The application settings for the ZigBee and ZigBee-PRO feature sets are, for the most part, described 11

in the restricted PICS captured in Section

8.6. Those setting not covered by the PICS are listed in Table 12

3. 13

Table 3 – Application settings for this feature set 14

Parameter Name Setting Comments

ZigBee

Number of active endpoints per

sleeping ZigBee end device

(maximum)

ZigBee-

PRO

As the responsibility to arrange for caching of service

discovery information lies with the end device itself,

this parameter is not restricted.

ZigBee-2007 Layer PICS and Stack Profiles ZigBee Document 08006r03, June 2008

Page 8

This is an unaccepted ZigBee specification draft, subject to change.

7 Functional description 1

For the most part, the functioning of ZigBee and ZigBee-PRO with respect to the NWK layer, the APS 2

layer and the ZDO is described in

[R1]. However, the configuration details and operational 3

requirements for devices operating under the ZigBee and ZigBee-PRO feature sets lead to some special 4

functional considerations, which are detailed here. 5

7.1 Device roles 6

The basic roles performed by ZigBee devices in ZigBee and ZigBee-PRO networks are determined by 7

their device type: 8

• The ZigBee coordinator initiates network formation, choosing the network channel, PAN ID 9

and extended PAN ID in the process, and thereafter should act as a ZigBee router. It may also 10

perform the roles of trust center and Network Channel Manager. With respect to binding, the 11

ZigBee coordinator is expected to handle end device bind request on behalf of all end devices 12

in the network but is not expected to be a global binding repository for the network. 13

• ZigBee routers are called upon to relay traffic on behalf of other devices in the network and, 14

in particular, are required to act as routing agents on behalf of their end device children, which 15

will typically not have the neighbor tables, routing tables, route discovery tables or broadcast 16

transaction tables required to perform routing. Since end devices may sleep, ZigBee routers 17

and ZigBee coordinators in their role of ZigBee routers may cache discovery information on 18

behalf of their sleeping end-device children. A ZigBee router may perform the role of trust 19

center and Network Channel Manager. 20

• ZigBee end devices are joined to and managed by ZigBee routers or the ZigBee coordinator. 21

Because ZigBee-PRO networks are beaconless, there is no built-in synchronization 22

mechanism between sleeping end devices and their router parents. End devices are free to set 23

their own duty cycles within the broad polling limits defined by this feature set. End devices 24

that wish to have their discovery information cached by their parent or some other device are 25

responsible for using the discovery cache commands to achieve this. 26

Under the ZigBee and ZigBee-PRO feature sets, all devices are expected to manage their own binding 27

tables if they use binding tables. 28

This section is valid for both the ZigBee and ZigBee-PRO feature sets. 29

7.2 ZigBee: Compatibility with Other Feature sets 30

Devices implementing the ZigBee feature set will advertise a feature set identifier of 1 in their beacon 31

payloads as stated below in the additional restrictions for PICS item NLF4. In general, such devices 32

will seek out and join networks in which the ZigBee coordinator and all ZigBee routers implement the 33

ZigBee feature set and advertise this fact by placing a feature set identifier of 1 in their beacon 34

payloads. 35

In order to provide compatibility with devices implemented according to the ZigBee-PRO feature set, 36

ZigBee devices shall additionally be able to join networks which advertise a feature set identifier of 2 37

in their beacon payloads but the device must join the ZigBee-PRO networks as end devices and only 38

those ZigBee-PRO networks employing standard network security. 39

This section is valid for the ZigBee feature set. 40

ZigBee Document 08006r03, June 2008 ZigBee-2007 Layer PICS and Stack Profiles

This is an unaccepted ZigBee specification draft, subject to change.

Page 9

7.3 ZigBee-PRO: Compatibility with Other Feature sets 1

Devices implementing the ZigBee-PRO feature set will advertise a feature set identifier of 2 in their 2

beacon payloads as stated below in the additional restrictions for PICS item NLF4. In general, such 3

devices will seek out and join networks in which the ZigBee coordinator and all ZigBee routers 4

implement the ZigBee-PRO feature set and advertise this fact by placing a feature set identifier of 2 in 5

their beacon payloads. 6

In order to provide compatibility with devices implemented according to the ZigBee feature set, 7

ZigBee-PRO devices shall additionally be able to join networks which advertise a feature set identifier 8

of 1 in their beacon payloads but the device must join the ZigBee networks as end devices. 9

If a ZigBee PRO network is to allow ZigBee devices to join as end devices, it shall use the standard 10

network security. If high security is used, ZigBee devices will not be able to be authenticated on the 11

network. 12

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

7.4 Binding tables 14

Binding tables, if used, shall be located on the source device. While binding is optional, devices that 15

choose to use binding tables should allocate enough binding table entries to handle their own 16

communications needs. This suggests that binding table size should be flexible enough that it can be 17

set, at least at compile time, with some awareness of the actual intended usage of the device. 18

This section is valid for both the ZigBee and ZigBee-PRO feature sets. 19

7.5 Multicast mechanism and groups 20

Support for APS level multicasts is mandatory to support compatibility with ZigBee devices. The 21

multicast groups are then established using the application level mechanisms. Support for routing of 22

network level multicasts is mandatory in the ZigBee-Pro feature set. 23

ZigBee devices do not support network level multicasts. 24

7.6 Trust Center Policies and Security Settings 25

A ZigBee PRO network shall have a trust center uniquely pointed to by each device in the network 26

through apsTrustCenterAddress within each network member device. It is beyond the scope of the 27

PRO Feature set to describe how this value is set or whether it is changed and the Trust Center 28

relocated to another device during operation. The only requirement of the PRO Feature set is that all 29

devices in the network point to the one unique Trust Center and that the device pointed to as the Trust 30

Center supplies the security services described by this document. 31

The trust center dictates the security parameters of the network, such as which network key type to use, 32

settings of the service permissions table, when, if at all, to allow devices to use unsecured association 33

to the network, and when, if at all, to allow an application master or link key to be set up between two 34

devices. For interoperability, there are two distinct security settings that can be used within the ZigBee 35

PRO feature set – a standard and a high security. 36

Networks can exist for periods without a trust center. There are some operations where it is necessary 37

for the trust center to be operational in the network. These include initial network setup, key changes, 38

and when joining and rejoining devices require updated keys. 39

ZigBee-2007 Layer PICS and Stack Profiles ZigBee Document 08006r03, June 2008

Page 10

This is an unaccepted ZigBee specification draft, subject to change.

A wide range of implementations are possible, depending on the requirements of the application. A 1

high security trust center may allow the user to install devices “out-of-band”, keep separate link keys 2

for different devices, optionally ignore Mgmt_Permit_Joining_req commands from other nodes, and 3

configure application trust policies between devices or groups of devices, etc. A standard security trust 4

center would not offer these advantages, but would not be required to carry the associated costs. 5

7.7 Battery powered devices 6

ZigBee-PRO networks may, of course, contain battery-powered devices. ZigBee routers are required to 7

have their receivers enabled whenever they are not transmitting. 8

As mentioned above, ZigBee-PRO networks are beaconless networks and, in the absence of an explicit 9

mechanism for synchronization and indirect transmission, sleeping devices must set their own duty 10

cycles and use polling, under ZDO control, if they expect to receive frames that are directed to them 11

when they are asleep. The feature set provides that parent devices, i.e. ZigBee routers and the ZigBee 12

coordinator, hold frames for 7.5 seconds on behalf of sleeping end devices and this is also, roughly 13

speaking, the maximum polling rate prescribed here. Devices may implement a polling interval longer 14

than 7.5 seconds, however the application will then have to handle the potential loss of messages 15

during longer sleep cycles. 16

7.8 Mains powered devices 17

It is assumed that for most ZigBee-PRO networks, the ZigBee coordinator and ZigBee routers will be 18

mains-powered and always on in order to properly perform their required roles with respect to the 19

operation of the network. 20

7.9 Persistent storage 21

The ZigBee-PRO feature set does not support devices without persistent storage. Devices have 22

information required to be saved between unintentional restarts and power failures. See

[R1] sections 23

2.2.8 and 3.6.8 for details of persistent data in the application and NWK layers. Various security 24

material shall additionally be stored across power failures. All attributes in sections 4.3.3 and 4.4.10 25

shall be stored, except that it is not mandatory to store those values which can safely be recovered 26

using other stored information, or other methods. 27

7.10 Address Reuse 28

Re-use of previously assigned network short addresses in ZigBee-PRO devices is permitted subject to 29

execution of the address conflict procedure by the device on the re-used address. 30

7.11 Duty cycle limitations and fragmentation 31

No mandatory restrictions are defined for intermittent, low channel usage data, although developers are 32

encouraged to minimise bandwidth usage wherever possible. 33

Large acknowledged unicast transmissions should generally use the APS fragmentation mechanism, 34

where supported, as this handles retransmissions, duplicate rejection, flow control and congestion 35

control automatically. Use of the fragmentation mechanism is as specified in the application profile 36

documents. 37

剩余118页未读，继续阅读

hardlord

粉丝: 0
资源: 2

ZigBee-2007层PICS与堆栈配置规范概述

zigbee 规范

ZIGBEE CLUSTER LIBRARY SPECIFICATION

zigbee

zigbee.rar_ZigBee_matlab zigbee_zigbee matlab_zigbee源码

zigbee.rar_ZigBee cc2430_Zigbee测试_cc2430 zigbee_zigbee源码

ZigBee_sys.zip_ZigBee_ZigBee代码_ZigBee的仿真_matlab simulink_zigbee仿

ZigBee无线传感器网络设计与实现_无线传感Zigbee_ZigBee_zigbee传感器_zigbee设计_

WSN_ZigBee_ZigBee_Zigbee开发_源码

zigbee整套练习代码.rar_zigbee led_zigbee源码_zigbee，led

Zigbee大师

最新资源