The Datasheet Archive - 100 Million Datasheets from 7500 Manufacturers.    


Datasheet Search Engine   
 
Part # or Description: • 5V RS232 Driver • 2SC5066* • "Real Time Clock" • "USB connector" • "blue led" 5mm • 10 watt zener diode • 2N3055* motorola
 
Search Tip: Try entering the part number only. Include a wildcard (eg. lm317* or 1n4148*)

 

 

ZigBee Document 053474r06, Version December 14th, 2004 Sponsored ZigBe


Datasheet Thumbnail

   

Download PDF

Top Searches for this datasheet



ZigBee Specification
ZigBee Document 053474r06, Version December 14th, 2004 Sponsored ZigBee Alliance Accepted Abstract Keywords ZigBee Alliance Board Directors. ZigBee Specification describes infrastructure services available applications operating ZigBee platform. ZigBee, Stack, Network, Application, Profile, Framework, Device description, Binding, Security
June 2005
ZigBee Specification
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
Legal Notice
ZigBee Specification available individuals, companies institutions free charge non-commercial purposes (including university research, technical evaluation, development non-commercial software, tools, documentation). ease use, clearly marked errata have been incorporated into this document. These errata have been subjected Intellectual Property review, such, contain undeclared Necessary Claims. part this specification used development product sale without becoming member ZigBee Alliance. Copyright ZigBee Alliance, Inc. (2005). rights Reserved. This information within this document property ZigBee Alliance disclosure restricted. Elements ZigBee Alliance specifications subject third party intellectual property rights, including without limitation, patent, copyright trademark rights (such third party member ZigBee). ZigBee responsible shall held responsible manner identifying failing identify such third party intellectual property rights. This document information contained herein provided basis ZigBee DISCLAIMS WARRANTIES EXPRESS IMPLIED, INCLUDING LIMITED WARRANTY THAT INFORMATION HEREIN WILL INFRINGE RIGHTS THIRD PARTIES (INCLUDING WITHOUT LIMITATION INTELLECTUAL PROPERTY RIGHTS INCLUDING PATENT, COPYRIGHT TRADEMARK RIGHTS) IMPLIED WARRANTIES MERCHANTABILITY, FITNESS PARTICULAR PURPOSE, TITLE NONINFRINGEMENT. EVENT WILL ZIGBEE LIABLE LOSS PROFITS, LOSS BUSINESS, LOSS DATA, INTERRUPTION BUSINESS, OTHER DIRECT, INDIRECT, SPECIAL EXEMPLARY, INCIDENTIAL, PUNITIVE CONSEQUENTIAL DAMAGES KIND, CONTRACT TORT, CONNECTION WITH THIS DOCUMENT INFORMATION CONTAINED HEREIN, EVEN ADVISED POSSIBILITY SUCH LOSS DAMAGE. Company, brand product names trademarks that sole property their respective owners. above notice this paragraph must included copies this document that made. ZigBee Alliance, Inc. 2400 Camino Ramon, Suite Ramon, 94583
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
Copyright 2005 ZigBee Standards Organization. rights reserved.
Contents
Chapter Application Layer Specification
General description 1.1.1 Application support sub-layer. 1.1.2 Application framework. 1.1.3 Addressing 1.1.4 Application communication fundamentals. 1.1.5 Discovery 1.1.6 Binding 1.1.7 Messaging. 1.1.8 ZigBee device objects. ZigBee application support (APS) sub-layer 1.2.1 Scope. 1.2.2 Purpose. 1.2.3 Application support (APS) sub-layer overview. 1.2.4 Service specification 1.2.5 Frame formats. 1.2.6 Command frames 1.2.7 Constants attributes 1.2.8 Functional description ZigBee application framework 1.3.1 Creating ZigBee profile 1.3.2 Standard data type formats. 1.3.3 ZigBee descriptors 1.3.4 frame formats 1.3.5 command frames 1.3.6 Functional description ZigBee device profile. 1.4.1 Scope. 1.4.2 Device Profile overview. 1.4.3 Client services. 1.4.4 Server services 1.4.5 enumeration description 1.4.6 Conformance ZigBee device objects (ZDO) 1.5.1 Scope. 1.5.2 Device Object Descriptions. 1.5.3 Layer Interface Description 1.5.4 System Usage. 1.5.5 Object Definition Behavior 1.5.6 Configuration Attributes
Chapter Network Specification
layer status values General description 2.2.1 Network (NWK) layer overview
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
Service specification. 2.3.1 data service 2.3.2 Network discovery. 2.3.3 Network formation. 2.3.4 Allowing devices join. 2.3.5 Begin router. 2.3.6 Joining network 2.3.7 Joining device directly network 2.3.8 Leaving network. 2.3.9 Resetting device 2.3.10 Receiver synchronization. 2.3.11 Information base maintenance. Frame formats 2.4.1 General NPDU frame format. 2.4.2 Format individual frame types. Command frames 2.5.1 Route request command. 2.5.2 Route reply command. 2.5.3 Route error command 2.5.4 Leave command Constants attributes. 2.6.1 constants 2.6.2 information base Functional description. 2.7.1 Network device maintenance. 2.7.2 Transmission reception. 2.7.3 Routing. 2.7.4 Scheduling beacon transmissions 2.7.5 Broadcast communication. 2.7.6 information beacons 2.7.7 Persistent data
Chapter Security Services Specification
Document Organization. General Description. 3.2.1 Security Architecture Design. 3.2.2 Layer Security 3.2.3 Layer Security. 3.2.4 Layer Security 3.2.5 Trust Center Role. Layer Security. 3.3.1 Frame Security. 3.3.2 Security-Related Attributes Layer Security 3.4.1 Frame Security. 3.4.2 Secured NPDU Frame 3.4.3 Security-Related Attributes Layer Security 3.5.1 Frame Security.
Copyright 2005 ZigBee Standards Organization. rights reserved.
Contents
3.5.2 3.5.3 3.5.4 3.5.5 3.5.6 3.5.7 3.5.8 3.5.9 3.5.10
Key-Establishment Services Transport-Key Services Update-Device Services Remove Device Services. Request Services. Switch Services Secured APDU Frame Command Frames Security-Related Attributes
Common Security Elements 3.6.1 Auxiliary Frame Header Format. 3.6.2 Security Parameters 3.6.3 Cryptographic Hierarchy 3.6.4 Implementation Guidelines (Informative) Functional Description 3.7.1 ZigBee Coordinator. 3.7.2 Trust Center Application 3.7.3 Security Procedures.
Annex CCM* Mode Operation
Notation representation CCM* mode encryption authentication transformation. A.2.1 Input transformation A.2.2 Authentication transformation A.2.3 Encryption transformation CCM* mode decryption authentication checking transformation. A.3.1 Decryption transformation. A.3.2 Authentication checking transformation Restrictions.
Annex Security Building Blocks
Symmetric-key cryptographic building blocks B.1.1 Block-cipher B.1.2 Mode operation B.1.3 Cryptographic hash function B.1.4 Keyed hash function message authentication B.1.5 Specialized keyed hash function message authentication B.1.6 Challenge domain parameters. Agreement Schemes. B.2.1 Symmetric-key agreement scheme. Challenge Domain Parameter Generation Validation B.3.1 Challenge Domain Parameter Generation. B.3.2 Challenge Domain Parameter Verification. Challenge Validation Primitive. Secret Generation (SKG) Primitive
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
Block-Cipher-Based Cryptographic Hash Function. Symmetric-Key Authenticated Agreement Scheme B.7.1 Initiator Transformation B.7.2 Responder Transformation
Annex Test Vectors Cryptographic Building Blocks
Data Conversions. Block Cipher. CCM* Mode Encryption Authentication Transformation. C.3.1 Input Transformation. C.3.2 Authentication Transformation C.3.3 Encryption Transformation. CCM* Mode Decryption Authentication Checking Transformation. C.4.1 Decryption Transformation. C.4.2 Authentication Checking Transformation Cryptographic Hash Function. C.5.1 Test Vector C.5.2 Test Vector Keyed Hash Function Message Authentication C.6.1 Test Vector C.6.2 Test Vector Specialized Keyed Hash Function Message Authentication Symmetric-Key Agreement Scheme C.8.1 Initiator Transformation C.8.2 Responder Transformation
Annex ZigBee Protocol Stack, Settable Values (Knobs)
Network Settings D.1.1 nwkMaxDepth nwkMaxChildren. D.1.2 NwkMaxRouters. D.1.3 Size routing table D.1.4 Size neighbor table D.1.5 Size route discovery table. D.1.6 Number reserved routing table entries. D.1.7 Buffering pending route discovery D.1.8 Buffering behalf devices. D.1.9 Routing cost calculation D.1.10 nwkSymLink. Application Settings. Security Settings
Annex
ZigBee Stack Profiles.
Copyright 2005 ZigBee Standards Organization. rights reserved.
Contents
Stack Profiles Stack Profile Definitions Home Controls Stack Profile E.3.1 Network Settings. E.3.2 Application Settings E.3.3 Security Settings Building Automation Stack Profile E.4.1 Network Settings. E.4.2 Application Settings E.4.3 Security Settings Plant Control Stack Profile E.5.1 Network Settings. E.5.2 Application Settings E.5.3 Security Settings
Annex
schemas
schema command schema response command. schema command. schema response command. schema event command. schema event response command. Example commands. Example command
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
Copyright 2005 ZigBee Standards Organization. rights reserved.
Figures
Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure
Outline ZigBee stack architecture Multiple subunits single node ZigBee binding binding table. sub-layer reference model General frame format. Format frame control field Data frame format command frame format. Acknowledgement frame format Direct binding ZigBee coordinator SrcAddr device Successful data transmission without acknowledgement Successful data transmission with acknowledgement Format character string type Format octet string type Format complex descriptor. Format individual complex descriptor field Format capability flags field. Format language character field. Format general application framework command frame. Format transaction field. Format general command frame. Format transaction frame. Format with acknowledgement command frame Format response command frame Format set/set with acknowledgement command frame. Format response command frame Format event/event with acknowledgement command frame. Format event response command frame Cluster Format Device Profile ZigBee Device Object details layer reference model. Capability Information parameter format. Message sequence chart resetting network layer. Message sequence chart synchronizing non-beaconing network. Message sequence chart synchronizing beacon-enabled network. General frame format. Frame control field Data frame format command frame format. Route request command frame format Route request command options field. Route reply command format. Route reply command options field. Route error command frame format. Leave command frame format Leave command options field
Copyright 2005 ZigBee Standards Organization. rights reserved.
Figures
Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure
Establishing network. Permitting devices join network. Procedure joining network through association Procedure handling join request Joining device network directly Child procedure joining re-joining network through orphaning Parent procedure joining re-joining device network through orphaning219 Address assignment example network. Sequence diagrams NLME-LEAVE.request, various scenarios Leave command, various scenarios. Basic routing algorithm. Receipt route request. Receipt route reply Typical frame structure beaconing device Parent-child superframe positioning relationship Broadcast transaction message sequence chart Format sub-layer beacon payload. ZigBee frame with security level ZigBee frame with security level ZigBee frame with security level Secured layer frame format Sequence chart successful APSME-ESTABLISH-KEY primitives. Secured layer frame format Generic SKKE frame command format. Transport-key command frame Trust center master descriptor field transport-key command Network descriptor field transport-key command Application master descriptor transport-key command. Update-device command frame format. Remove-device command frame format Request-key command frame format. Switch-key command frame format. Auxiliary frame header format Security control field format. CCM* nonce. Example joining secured network Example residential-mode authentication procedure Example commercial-mode authentication procedure Example Network key-update procedure Example Network key-recovery procedure Example end-to-end application establishment procedure. Example remove-device procedure Example device-leave procedure. Symmetric-Key Authenticated Agreement Scheme. Example with acknowledgement command frame Example response command frame. Example command frame Example command frame speed Example command frame coordinates sensor
Copyright 2005 ZigBee Standards Organization. rights reserved.
Tables
Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table
APSDE-SAP primitives. APSDE-DATA.request parameters APSDE-DATA.confirm parameters APSDE-DATA.indication parameters Summary primitives accessed through APSME-SAP APSME-BIND.request parameters. APSME-BIND.confirm parameters APSME-UNBIND.request parameters. APSME-UNBIND.confirm parameters. APSME-GET.request parameters APSME-GET.confirm parameters APSME-SET.request parameters APSME-SET.confirm parameters. Values frame type sub-field. Values delivery mode sub-field sub-layer constants attributes Address ZigBee standard data types ZigBee descriptors Fields node descriptor Values logical type field. Values frequency band field Fields node power descriptor Values current power mode field. Values available power sources field Values current power sources field Values current power source level field. Fields simple descriptor. Values application device version field. Values application flags field Fields complex descriptor. Values character identifier sub-field Fields user descriptor Values frame type field. Values command type identifier field. Values error code field Device Service Discovery Client Services primitives NWK_addr_req parameters IEEE_addr_req parameters. Node_Desc_req parameters Power_Desc_req parameters. Simple_Desc_req parameters. Active_EP_req parameters Match_Desc_req parameters Complex_Desc_req parameters.
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table
User_Desc_req parameters Discovery_Register_req parameters. End_Device_annce parameters User_Desc_set parameters. Device Bind, Bind Unbind Client Services primitives End_Device_Bind_req parameters Bind_req parameters. Unbind_req parameters. Network Management Client Services primitives Mgmt_NWK_Disc_req parameters. Mgmt_Lqi_req parameters Mgmt_Rtg_req parameters Mgmt_Bind_req parameters. Mgmt_Leave_req parameters Mgmt_Direct_Join_req parameters Device Service Discovery Server Services primitives NWK_addr_rsp parameters. IEEE_addr_rsp parameters. Node_Desc_rsp parameters Power_Desc_rsp parameters. Simple_Desc_rsp parameters Active_EP_rsp parameters. Match_Desc_rsp parameters Complex_Desc_rsp parameters. User_Desc_rsp parameters Discovery_Register_rsp parameters User_Desc_conf parameters. Device Bind, Bind Unbind Server Services primitives. End_Device_Bind_rsp parameters. Bind_rsp parameters Unbind_rsp parameters. Network Management Server Services primitives. Mgmt_NWK_Disc_rsp parameters. Mgmt_Lqi_rsp parameters NeighborTableList record format Mgmt_Rtg_rsp parameters. RoutingTableList record format Mgmt_Bind_rsp parameters BindingTableList record format. Mgmt_Leave_rsp parameters Mgmt_Direct_Join_rsp parameters enumerations description ZigBee Device Objects. Device Service Discovery Attributes Security Manager Attributes Binding Manager Attributes Network Manager Attributes. Node manager attributes. Configuration Attributes. layer status values NLDE-SAP Primitives. NLDE-DATA.request parameters. NLDE-DATA.confirm parameters NLDE-DATA.indication parameters.
Copyright 2005 ZigBee Standards Organization. rights reserved.
Tables
Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table
Summary primitives accessed through NLME-SAP NLME-NETWORK-DISCOVERY.request parameters NLME-NETWORK-DISCOVERY.confirm parameters Network descriptor information fields NLME-NETWORK-FORMATION.request parameters. NLME-NETWORK-FORMATION.confirm parameters NLME-PERMIT-JOINING.request parameters. NLME-PERMIT-JOINING.confirm parameters. NLME-START-ROUTER.request parameters. NLME-START-ROUTER.confirm parameters NLME-JOIN.request parameters. CapabilityInformation bit-fields NLME-JOIN.indication parameters. NLME-JOIN.confirm parameters NLME-DIRECT-JOIN.request parameters NLME-DIRECT-JOIN.confirm parameters NLME-LEAVE.request parameters NLME-LEAVE.indication parameters NLME-LEAVE.confirm parameters. NLME-RESET.confirm parameters NLME-SYNC.request parameters NLME-SYNC.confirm parameters NLME-GET.request parameters. NLME-GET.confirm parameters. NLME-SET.request parameters NLME-SET.confirm parameters Values frame type sub-field. Values discover route sub-field command frames Error codes route error command frame. layer constants. attributes. Neighbor table entry format. Example addressing offset values each given depth within network Routing table Route status values. Route discovery table. Start time beacon transmissions layer information fields security attributes Elements network security material descriptor. Elements incoming frame counter descriptor layer security primitives. APSME-ESTABLISH-KEY.request parameters APSME-ESTABLISH-KEY.confirm parameters APSME-ESTABLISH-KEY.indication parameters APSME-ESTABLISH-KEY.response parameters Mapping frame names symmetric-key agreement scheme messages. Mapping symmetric-key agreement error conditions status codes. APSME-TRANSPORT-KEY.request parameters. KeyType parameter transport-key primitive TransportKeyData parameter trust-center master key. TransportKeyData parameter Network key. TransportKeyData parameter application master link
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table
APSME-TRANSPORT-KEY.indication parameters. TransportKeyData parameter trust-center master key. TransportKeyData parameter Network key. APSME-UPDATE-DEVICE.request parameters APSME-UPDATE-DEVICE.indication parameters APSME- REMOVE-DEVICE.request parameters APSME-REMOVE-DEVICE.indication parameters APSME-REQUEST-KEY.request parameters. APSME-REQUEST-KEY.indication parameters APSME-SWITCH-KEY.request parameters. APSME-SWITCH-KEY.indication parameters. Command identifier values. security attributes Elements key-pair descriptor. Security levels available MAC, NWK, layers. Encoding identifier sub-field
Copyright 2005 ZigBee Standards Organization. rights reserved.
Preface
ZigBee Alliance developing very low-cost, very power consumption, two-way, wireless communications standard. Solutions adopting ZigBee standard will embedded consumer electronics, home building automation, industrial controls, peripherals, medical sensor applications, toys games.
Scope
This document contains specifications, interface descriptions, object descriptions, protocols algorithms pertaining ZigBee protocol standard, including application support sub-layer (APS), ZigBee device objects (ZDO), ZigBee device profile (ZDP), application framework, network layer (NWK) ZigBee security services.
Purpose
purpose this document provide definitive description ZigBee protocol standard basis future implementations, such that number implementers incorporating ZigBee standard into platforms devices basis this document will produce interoperable, low-cost highly usable products burgeoning wireless marketplace.
Stack architecture
ZigBee stack architecture made blocks called layers. Each layer performs specific services layer above: data entity provides data transmission service management entity provides other services. Each service entity exposes interface upper layer through service access point (SAP), each supports number service primitives achieve required functionality. ZigBee stack architecture, which depicted Figure based standard Open Systems Interconnection (OSI) seven-layer model (see [B14]) defines only those layers relevant achieving functionality intended market space. IEEE 802.15.4-2003 standard defines lower layers: physical (PHY) layer medium access control (MAC) sub-layer. ZigBee Alliance builds this foundation providing network (NWK) layer framework application layer, which includes application support sub-layer (APS), ZigBee device objects (ZDO) manufacturerdefined application objects. IEEE 802.15.4-2003 layers that operate separate frequency ranges: 868/915 GHz. lower frequency layer covers both European band band that used countries such United States Australia. higher frequency layer used virtually worldwide. complete description IEEE 802.15.4-2003 layer found [B1]. IEEE 802.15.4-2003 sub-layer controls access radio channel using CSMA-CA mechanism. responsibilities also include transmitting beacon frames, synchronization providing reliable transmission mechanism. complete description IEEE 802.15.4-2003 sub-layer found [B1]. responsibilities ZigBee layer shall include mechanisms used join leave network, apply security frames route frames their intended destinations. addition, discovery maintenance routes between devices devolve layer. Also discovery one-hop neighbors
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
storing pertinent neighbor information done layer. layer ZigBee coordinator (see "Network topology") responsible starting network, when appropriate, assigning addresses newly associated devices ZigBee application layer consists APS, Application Framework (AF), manufacturer-defined application objects. responsibilities sub-layer include maintaining tables binding, which ability match devices together based their services their needs, forwarding messages between bound devices. responsibilities include defining role device within network (e.g., ZigBee coordinator device), initiating and/or responding binding requests establishing secure relationship between network devices. also responsible discovering devices network determining which application services they provide.
Application (APL) Layer Application Framework
Application Object
Application Object
ZigBee Device Object (ZDO)
Public Interfaces
Endpoint APSDE-SAP
Endpoint APSDE-SAP
Endpoint APSDE-SAP APSME-SAP
Management Plane
Application Support Sublayer (APS) Security Service Provider
Security Management
NLDE-SAP
Message Broker
Reflector Management
IEEE 802.15.4 defined ZigBeeAlliance defined manufacturer defined Layer function Layer interface
Network (NWK) Layer
Security Management
MLDE-SAP
NLME-SAP
Message Broker
Routing Management
Network Management
MLME-SAP
Medium Access Control (MAC) Layer
PLME-SAP
PD-SAP
Physical (PHY) Layer
Radio 868/915
Figure Outline ZigBee stack architecture
Network topology
ZigBee network layer (NWK) supports star, tree mesh topologies. star topology, network controlled single device called ZigBee coordinator. ZigBee coordinator responsible initiating maintaining devices network, other devices, known devices, directly communicate with ZigBee coordinator. mesh tree topologies, ZigBee coordinator responsible starting network choosing certain network parameters network extended through ZigBee routers. tree networks, routers move data control messages through network using hierarchical routing strategy. Tree networks employ beacon-oriented communication described IEEE 802.15.4-2003 specification. Mesh networks shall allow full peerto-peer communication. ZigBee routers mesh networks shall emit regular IEEE 802.15.4-2003 beacons.
Copyright 2005 ZigBee Standards Organization. rights reserved.
Preface
This specification describes only intra-PAN networks, i.e., networks which communications begin terminate within same network.
Definitions, Abbreviations, References
Conformance Levels
conformance level definitions shall follow those Clause section IEEE Style Manual [B12]. Expected: word used describe behavior hardware software design models assumed this Specification. Other hardware software design models also implemented. May: word indicating course action permissible within limits standard (may equals permitted). Shall: word indicating mandatory requirements strictly followed order conform standard from which deviation permitted (shall equals required to). Should: word indicating that among several possibilities recommended particularly suitable, without mentioning excluding others; that certain course action preferred necessarily required; that negative form) certain course action deprecated prohibited (should equals recommended that). Reserved Codes: codes that defined this specification, otherwise used. Future specifications implement these codes. product implementing this specification shall generate these codes. Reserved Fields: fields that defined this specification, otherwise used. Products that implement this specification shall zero these fields shall make further assumptions about these fields perform processing based their content. Products that implement future revisions this specification these fields defined specification. ZigBee v1.0: version ZigBee protocols governed this specification. ZigBee v1.0 first officially recognized version these protocols. protocol version sub-field frame control field header ZigBee v1.0 frames shall have value 0x01. Frames defined later versions specification protocol version sub-field frame control field different value. ZigBee device that conforms this specification shall discard frames that carry protocol version subfield value other than 0x01.1
Strings string operations
string sequence symbols over specific (e.g., binary alphabet {0,1} octets). length string number symbols contains (over same alphabet). right-concatenation strings length respectively (notation: string length that coincides with leftmost symbols with rightmost symbols. octet symbol string length context, octets strings over binary alphabet.
Comment
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
Transmission order
convention, frame structures presented such that leftmost field written this document shall transmitted received first. multiple octet fields shall transmitted received least significant octet first. Each individual octet shall transmitted received least significant first.
Integers, octets, their representation
Throughout this specification, representation integers octet strings octet strings binary strings shall fixed. integers shall represented octet strings most-significant-octet first order. This representation conforms convention Section ANSI X9.63-2001 [B7]. octets shall represented binary strings most-significant-bit first order.
Entities
Throughout this specification, each entity shall shall uniquely identified 64-bit IEEE device address [B1]. parameter entlen shall have integer value
Definitions
purposes this standard, following terms definitions apply. Terms defined this clause found IEEE P802.15.4 [B1] ANSI X9.63-2001 [B7]. Access control list: table used device determine which devices authorized perform specific function. This table also store security material (e.g., cryptographic keys, frame counts, counts, security level information) used securely communicating with other devices. Active network key: used ZigBee device secure outgoing frames that available process incoming frames. Alternate network key: available lieu active Network process incoming frames. Application domain: this describes broad area applications, such building automation. Application object: component portion application layer defined manufacturer that actually implements application. Application segment: some application domains split into application segments, instance lighting application segment within home control application domain. Application support sub-layer protocol data unit: unit data that exchanged between application support sub-layers peer entities. command frame: frame that contains neither source endpoints. Association: service provided IEEE 802.15.4-2003 sub-layer that used establish membership network. Attribute: data entity which represents physical quantity state. This data communicated other devices using commands. Beacon-enabled personal area network: personal area network containing least device that transmits beacon frames regular interval.
Copyright 2005 ZigBee Standards Organization. rights reserved.
Preface
Binding: creation unidirectional logical link between source endpoint/cluster identifier pair destination endpoint, which exist more devices.2 Broadcast: transmission message every device within network. Broadcast jitter: random delay time introduced device before relaying broadcast transaction. Broadcast transaction record: local receipt broadcast message that either initiated relayed device. Broadcast transaction table: collection broadcast transaction records. Cluster: container more attributes under service type synonymous with "message" under service type. Cluster identifier: reference unique enumeration clusters within specific profile. cluster identifier 8-bit number unique within scope application domain segment identifies specific cluster. Cluster identifiers identified inputs outputs simple descriptor creating binding table. Component: component consists physical object (e.g., switch, controller, etc.) corresponding application profile(s). Coordinator: IEEE 802.15.4-2003 device responsible associating disassociating devices into PAN. coordinator must full function device (FFD). Data integrity: assurance that data been modified from original form. Data key: shared between devices peer-to-peer data communications. Device: entity that contains implementation ZigBee protocol stack. Device application: special application that responsible Device operation. Device Application resides Endpoint convention contains logic manage Devices networking general maintenance features. Device description: description specific device within application segment and/or domain. instance, light sensor monochromatic device description member lighting application segment. device description also unique identifier that exchanged part discovery process. Direct addressing: mode addressing which destination frame completely specified frame itself. Direct binding: procedure through which uppers layers device which maintains binding table create remove binding link that binding table. Direct transmission: frame transmission using direct addressing. Disassociation: service provided IEEE 802.15.4-2003 sub-layer that used discontinue membership device network. application: applications that reside Endpoints through Device. Applications implement features that non-networking ZigBee protocol related. device binding: procedure creating removing binding link initiated each devices that will form link. procedure involve user intervention.
Comment #127
Copyright 2005 ZigBee Standards Organization. rights reserved.
Preface
Endpoint: particular component within unit. Each ZigBee device support such components. Endpoint address: address assigned endpoint. This address assigned addition unique, 64-bit IEEE address 16-bit network address. First indirect frame: period transit frame that been indirectly addressed when only source address appears frame. Indirect addressing: ability resource limited devices communicate without having know address desired destination. Indirect transmissions shall include only source endpoint-addressing field along with Indirect Addressing APDU directed ZigBee Coordinator source. ZigBee Coordinator expected lookup source address/endpoint/cluster within binding table re-issues message each corresponding destination address/endpoint. Information base: collection variables that define certain behavior layer. These variables specified obtained from layer through management service. establishment: mechanism that involves execution protocol devices derive mutually shared secret key. transport: mechanism communicating from device another device other devices. Key-transport key: used protect transport messages. update: mechanism implementing replacement shared amongst more devices means another available that same group. Local coordinator: ZigBee Coordinator ZigBee Router, which IEEE 802.15.4 coordinator, which processed association request specific Device. Link key: that shared between devices within PAN. Master key: shared used during execution symmetric-key establishment protocol. master basis long-term security between devices, used generate link keys. Mesh network: network which routing messages performed decentralized, cooperative process involving many peer devices routing each others' behalf. Multihop network: network, particular wireless network, which there guarantee that transmitter receiver given message connected linked each other. This implies that intermediate devices must used routers. Non-beacon-enabled personal area network: personal area network that does contain devices that transmit beacon frames regular interval. Neighbor table: table used ZigBee device keep track other devices within POS. Network address: address assigned device network layer used network layer routing messages between devices. Network broadcast delivery time: time duration required broadcast transaction reach every device given network. Network protocol data unit: unit data that exchanged between network layers peer entities. Network service data unit: Information that delivered unit through network service access point. Node: collection independent device descriptions applications residing single unit sharing common 802.15.4 radio.
Copyright 2005 ZigBee Standards Organization. rights reserved.
Preface
Normal operating state: processing which occurs after startup initialization processing occurred prior initiation shutdown processing. NULL: parameter variable value that mean unspecified, undefined unknown. Octet: eight bits data, used synonym byte. One-way function: function that computationally much easier perform than inverse. Orphaned device: device that lost communication contact with information about ZigBee device through which membership. coordinator: principal controller IEEE 802.15.4-2003-based network that responsible network formation maintenance. coordinator must full function device (FFD). information base: collection variables IEEE 802.15.4-2003 standard that passed between layers, order exchange information. This database include access control list, which stores security material. Personal operating space: area within reception range single device. Private method: attributes which accessible ZigBee device objects only unavailable applications. Profile: collection device descriptions, which together form cooperative application. instance, thermostat node communicates with furnace another node. Together, they cooperatively form heating application profile. Protocol data unit: unit data that exchanged between peer entities. Proxy binding: procedure through which device create remove binding link ZigBee coordinator between devices (none which device itself). Public method: attributes which accessible Applications. Radio: IEEE 802.15.4-2003 radio that part every ZigBee device. Route discovery: operation which ZigBee coordinator ZigBee router attempts discover route remote device issuing route request command frame.3 Route discovery table: table used ZigBee coordinator ZigBee router store temporary information used during route discovery. Route reply: ZigBee network layer command frame used reply route requests. Route request: ZigBee network layer command frame used discover paths through network over which subsequent messages delivered. Routing table: table which ZigBee coordinator ZigBee router stores information required participate routing frames. Service discovery: ability device locate services interest. Symmetric-key establishment: mechanism which parties establish shared secret, based pre-shared secret so-called master key). Trust center: device trusted devices within ZigBee network distribute keys purpose network end-to-end application configuration management. Unicast: transmission message single device network.
Comment #126
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
Unit: component collection components that share single ZigBee radio. Each unit unique 64bit IEEE address 16-bit network address. ZigBee coordinator: IEEE 802.15.4-2003 coordinator. ZigBee device object: portion application layer responsible defining role device within network (e.g., ZigBee coordinator device), initiating and/or responding binding discovery requests establishing secure relationship between network devices. ZigBee device: IEEE 802.15.4-2003 participating ZigBee network, which neither ZigBee coordinator ZigBee router. ZigBee router: IEEE 802.15.4-2003 participating ZigBee network, which ZigBee coordinator IEEE 802.15.4-2003 coordinator within personal operating space, that capable routing messages between devices supporting associations.
Acronyms Abbreviations
purposes this standard, following acronyms abbreviations apply.
APDU APSDE APSDE-SAP APSME APSME-SAP CCM* CSMA-CA LR-WPAN MCPS-SAP Application support layer information base Application framework Application support sub-layer protocol data unit Application layer Application support sub-layer Application support sub-layer data entity Application support sub-layer data entity service access point Application support sub-layer management entity service access point Application support sub-layer management entity service access point Broadcast retry timer Broadcast transaction record Broadcast transaction table Enhanced counter with CBC-MAC mode operation Carrier sense multiple access collision avoidance Full function device Guaranteed time slot Information base Key-value pair Link quality indicator rate wireless personal area network Medium access control Medium access control common part sub-layer service access point
Copyright 2005 ZigBee Standards Organization. rights reserved.
Preface
MLME-SAP MSDU NBDT NHLE NLDE NLDE-SAP NLME NLME-SAP NPDU NSDU PD-SAP PLME-SAP RREP RREQ SKKE
Message integrity code Medium access control sub-layer management entity service access point Message sequence chart Medium access control sub-layer service data unit Message service type Network broadcast delivery time Next Higher Layer Entity Network layer information base Network layer data entity Network layer data entity service access point Network layer management entity Network layer management entity service access point Network layer protocol data unit Network service data unit Network Open systems interconnection Personal area network Physical layer data service access point Protocol data unit Physical layer Personal area network information base Physical layer management entity service access point Personal operating space Quality service Radius counter Reduced function device Route reply Route request Routing node Service access point Secret generation Symmetric-key establishment Security services provider Security services specification
Copyright 2005 ZigBee Standards Organization. rights reserved.
Preface
WPAN
Wireless personal area network Extensible markup language ZigBee ZigBee device object
Symbols Notation
Notation follows from ANSI X9.63-2001, [B7]
References
following standards contain provisions, which, through reference this document, constitute provisions this standard. Normative references given "ZigBee/IEEE References" "Normative References" informative references given "Informative References". time publication, editions indicated were valid. standards subject revision, parties agreements based this standard encouraged investigate possibility applying most recent editions standards indicated below. ZigBee/IEEE References [B1] Institute Electrical Electronics Engineers, Inc., IEEE Std. 802.15.4-2003, IEEE Standard Information Technology Telecommunications Information Exchange between Systems Local Metropolitan Area Networks Specific Requirements Part 15.4: Wireless Medium Access Control (MAC) Physical Layer (PHY) Specifications Rate Wireless Personal Area Networks (WPANs). York: IEEE Press. 2003. [B2] IEEE 754-1985, IEEE Standard Binary Floating-Point Arithmetic, IEEE, 1985. [B3] Document 03285r0: Suggestions Improvement IEEE 802.15.4 Standard, July 2003. [B4] Document 02055r4: Network Requirements Definition, August 2003. Normative References [B5] ISO/IEC 639-1:2002 Codes representation names languages Part Alpha-2 code. [B6] ISO/IEC 646:199 Information technology 7-bit coded character information interchange. [B7] ANSI X9.63-2001, Public Cryptography Financial Services Industry Agreement Transport Using Elliptic Curve Cryptography, American Bankers Association, November 2001. Available from http://www.ansi.org. [B8] FIPS 197, Advanced Encryption Standard (AES), Federal Information Processing Standards Publication 197, Department Commerce/N.I.S.T, Springfield, Virginia, November 2001. Available from http://csrc.nist.gov/. [B9] FIPS 198, Keyed-Hash Message Authentication Code (HMAC), Federal Information Processing Standards Publication 198, Department Commerce/N.I.S.T., Springfield, Virginia, March 2002. Available from http://csrc.nist.gov/. [B10] ISO/IEC 9798-2, Information Technology Security Techniques Entity Authentication Mechanisms Part Mechanisms Using Symmetric Encipherment Algorithms, International Standardization Organization, Geneva, Switzerland, 1994 (first edition). Available from http://www.iso.org/.
Copyright 2005 ZigBee Standards Organization. rights reserved.
Preface
[B11] NIST 800-38A 2001 Recommendation Block Cipher Modes Operation Methods Techniques, NIST Special Publication 800-38A, 2001 Edition, Department Commerce/N.I.S.T., December 2001. Available from http://csrc.nist.gov/. Informative References [B12] FIPS 140-2, Security requirements Cryptographic Modules, Department Commerce/ N.I.S.T., Springfield, Virginia, June 2001 (supersedes FIPS 140-1). Available from http://csrc.nist.gov/. [B13] IEEE Standards Style Manual, published distributed 2000 revised September 2001. Available from [B14] ISO/IEC 7498-1:1994 Information technology Open systems interconnection Basic reference model: basic model. [B15] ISO/IEC 10731:1994, Information technology Open Systems Interconnection Conventions definition services. [B16] ISO/IEC 9646-1:1991, Information technology Open Systems Interconnection Conformance testing methodology framework Part General concepts. [B17] ISO/IEC 9646-7:1995, Information technology Open Systems Interconnection Conformance testing methodology framework Part Implementation conformance statements. [B18] A.J. Menezes, P.C. Oorschot, S.A. Vanstone, Handbook Applied Cryptography, Boca Raton: Press, 1997. [B19] FIPS 113, Computer Data Authentication, Federal Information Processing Standards Publication 113, Department Commerce/N.I.S.T., 1985. Available from http://csrc.nist.gov/. [B20] Housley, Whiting, Ferguson, Counter with CBC-MAC (CCM), submitted N.I.S.T., June 2002. Available from [B21] Jonsson, Security CBC-MAC, Proceedings Selected Areas Cryptography 2002, Nyberg, Heys, Eds., Lecture Notes Computer Science, Vol. 2595, 76-93, Berlin: Springer, 2002. [B22] Jonsson, Security CBC-MAC, NIST Mode Operation Additional Documentation. Available from [B23] Rogaway, Wagner, Critique CCM, IACR ePrint Archive 2003-070, April 2003.
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
Copyright 2005 ZigBee Standards Organization. rights reserved.
Chapter
Application Layer Specification
General description
ZigBee stack architecture includes number layered components including IEEE 802.15.4 2003 Medium Access Control (MAC) layer Physical (PHY) layer well ZigBee Network (NWK) layer. Each these provide applications with services capabilities. portion stack covered this document roughly that labeled Application (APL) Layer Figure shown, ZigBee application layer consists sub-layer, (containing management plane), manufacturer-defined application objects. responsibilities sublayer include maintaining tables binding, which ability match devices together based their services their needs, forwarding messages between bound devices. responsibilities include defining role device within network (e.g., ZigBee coordinator device), discovering devices network determining which application services they provide, initiating and/ responding binding requests establishing secure relationship between network devices.
1.1.1
Application support sub-layer
application support sub-layer (APS) provides interface between network layer (NWK) application layer (APL) through general services that used both manufacturer-defined application objects. services provided entities: data entity (APSDE) through APSDE service access point (APSDE-SAP) management entity (APSME) through APSME service access point (APSME-SAP). APSDE provides data transmission service transport application PDUs between more devices located same network. APSME provides services discovery binding devices maintains database managed objects, known information base (AIB).
1.1.2
Application framework
application framework ZigBee environment which application objects hosted ZigBee devices. Inside application framework, application objects send receive data through APSDE-SAP. Control management application objects performed through public interfaces (see clause 1.5). data service, provided APSDE-SAP, includes request, confirm, response indication primitives data transfer. request primitive supports data transfers between peer application object entities. confirm primitive reports results request primitive call. indication primitive used indicate transfer data from destination application object entity. distinct application objects defined, each interfacing endpoint indexed from 240. additional endpoints defined APSDE-SAP usage: endpoint reserved data interface endpoint reserved data interface function broadcast data application objects. Endpoints 241-254 reserved future use.4 Using these services offered APSDE-SAP, application framework provides application object data services: value pair service generic message service. Each service will discussed following sub-clauses.
Comment #227
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
1.1.2.1
value pair service
value pair (KVP) service allows attributes, defined application objects, manipulated employing state variable approach with get, response, event transactions. latter transactions sent with request response, resulting corresponding response event response transactions, respectively. Additionally, uses tagged data structures using compressed XML. Together, this solution provides elegant command/control mechanism small footprint devices with extensibility enable gateways expand full XML. service frame structure described sub-clause 1.3.5. 1.1.2.2 Message service
Many application areas targeted ZigBee addressed proprietary protocols that well KVP. Additionally, some overhead assumed since state variable approach assumes support get, event actions requiring devices maintain storage state variables. address these cases, generic message (MSG) service supported. service type transported same mechanisms used KVP. difference that does assume content data frame leaving that field free form profile developer define. service frame structure described sub-clause 1.3.4.5.2.
1.1.3
1.1.3.1
Addressing
Node addressing
Figure there nodes, each containing single radio. node contains switches other contains lamps.
Copyright 2005 ZigBee Standards Organization. rights reserved.
Application Layer Specification
Radio
Lamps
Radio
Switch
Switch
Figure Multiple subunits single node node contains more device descriptions single IEEE 802.15.4 radio. Figure individual parts nodes (the switches lamps) subunits containing device description each subunit. Each node given address when joins ZigBee network. 1.1.3.2 Endpoint addressing
Figure required that switch should control lamps while switch should control only lamp However, only addressable component radio, possible identify address individual subunits, would possible switch turn lamp only. ZigBee provides another level sub-addressing, which used conjunction with mechanisms IEEE802.15.4. endpoint number used identify individual switches lamps. instance, example above, switch could endpoint while switch could endpoint Similarly, lamps will each have their endpoints. Endpoint reserved device management used address descriptors node. Each identifiable subunit node (such switches lamps) assigned specific endpoint range 1-240. Physical devices described terms data attributes that they contain. instance, thermostat might contain output attribute "temperature" which represents current temperature room. furnace controller take this attribute input control furnace according temperature value received from thermostat. These physical devices, including their attributes, would described relevant device descriptions those devices. simple room thermostat described temperature-sensing circuitry, which queried external furnace controller. advertises service endpoint service described simple description implemented that endpoint. more complex version thermostat also have optional "heartbeat" report timer, which causes device report current room temperature after period. this example, ReportTime attribute
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
specifies when reports sent writing suitable time value this attribute sets frequency these temperature reports. This implementation would advertise services list cluster identifiers) different endpoint. order allow product differentiation marketplace, manufacturers clusters containing extra attributes their context more private profiles. These manufacturer-specific clusters form part this other ZigBee specification interoperability guaranteed these clusters. Such services would advertised different endpoints from those described above.
1.1.4
1.1.4.1
Application communication fundamentals
Profiles
Profiles agreement messages, message formats processing actions that enable applications residing separate devices send commands, request data process commands/requests create interoperable, distributed application. instance, thermostat node communicates with furnace another node. Together, they cooperatively form heating application profile. Profiles developed ZigBee vendors address solutions specific technology needs. Profiles simultaneously means unify interoperable technical solutions within ZigBee standard, well focus usability efforts within given marketing area. example, expected that vendors lighting equipment will want provide ZigBee profiles that interoperate with several varieties lighting types controller types. Additional information profiles provided clause this document. 1.1.4.2 Clusters
Clusters identified cluster identifier, which associated with data flowing into, device. Cluster identifiers unique within scope particular profile. Binding decisions taken matching output cluster identifier input cluster identifier, assuming both within same profile. thermostat example above, binding takes place temperature, between device with temperature cluster identifier output device with temperature cluster identifier input. binding table contains 8-bit identifier temperature along with address source destination devices.
1.1.5
1.1.5.1
Discovery
Device discovery
Device discovery process whereby ZigBee device discover other ZigBee devices initiating queries that broadcast unicast addressed. There forms device discovery requests: IEEE address requests address requests. IEEE address request unicast assumes address known. address request broadcast carries known IEEE address data payload. Responses broadcast unicast device discovery messages vary logical device type follows: ZigBee devices: respond device discovery query sending their IEEE address (depending request). ZigBee coordinator device: respond query sending their IEEE addresses IEEE addresses devices that associated with ZigBee coordinator (depending request). ZigBee router devices: respond query sending their IEEE addresses IEEE addresses devices that associated with ZigBee router (depending request).
Copyright 2005 ZigBee Standards Organization. rights reserved.
Application Layer Specification
description procedure details, primitive calls, applicable parameters given clause 1.4. 1.1.5.2 Service discovery
Service discovery process whereby services available endpoints receiving device discovered external devices. Service discovery accomplished issuing query each endpoint given device using match service feature (either broadcast unicast). Service discovery utilizes complex, user, node power descriptors plus simple descriptor further addressed endpoint (for connected application object). service discovery process ZigBee interfacing devices within network. Through specific requests descriptors specified nodes, broadcast requests service matching ability device which endpoints support application objects, range options available commissioning tools applications. clause details service discovery.
1.1.6
Binding
ZigBee, there application level concept using cluster identifiers (and attributes contained them) individual endpoints different nodes. This referred binding creation logical links between complementary application devices endpoints. example sub-clause 1.1.3.2, binding could made between thermostat furnace controller. Figure switch bound with lamps 1-3, while switch bound with lamp only. information about which cluster bound between nodes stored binding table. This described fully sub-clause 1.1.6 illustrated Figure
Radio
Lamps
EP17
Radio
Binding Table
Switch Switch EP21
Figure ZigBee binding binding table list three entries binding table switch allows control three lamps, which could also separate nodes (with their ZigBee radios). also possible lamp controlled several switches: this case there would entries each switch, linked same lamp.
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
Binding always performed after communications link been established. Once link been established, implementation decides whether node should part network. This will depend security operation application implemented. Binding only allowed implemented security devices allows this (see Chapter binding table implemented ZigBee coordinator. This because needs available time network operative most probable that ZigBee coordinator mains supply. Some applications need duplicate binding table available event that device storing table fails. Backup binding table other ZigBee coordinator data outside scope ZigBee version responsibility application software. details creation binding links covered ZigBee device profile (see clause 1.4).
1.1.7
1.1.7.1
Messaging
Direct addressing
Once devices have been associated, commands sent from device another. command sent application object destination address (radio address plus endpoint). Details commands found sub-clause 1.3.5. Note that binding pre-requisite using direct addressing. Direct addressing assumes device discovery service discovery have identified particular device endpoint, which supply complementary service requestor. Specifically, direct addressing defines means directing messages device including full address endpoint information.
1.1.7.2
Indirect addressing
direct addressing requires controlling device have knowledge address, endpoint, cluster identifier attribute identifier target device that wishes communicate with have this information committed binding table ZigBee coordinator prior creation indirectly addressed message between device pair. full IEEE 802.15.4 address amounts octets (PAN identifier plus 64-bit IEEE address) further octet required endpoint. Extremely simple devices, such battery-powered switches, want overhead storing this information, software acquiring this information. these devices, indirect addressing will more appropriate. When source device wishes send command destination using indirect addressing, instead including address destination device (which does know stored), omits address specifies indirect addressing APSDE-SAP. included source address, source endpoint cluster identifier indirect addressed message translated binding table those destination device(s) messages relayed each indicated destination.5 Where cluster contains several attributes, cluster identifier used addressing attribute identifier used command itself identify particular attribute within cluster. further information, sub-clause 1.3.4.5.1. Attributes used indirect addressing mechanism treated part data payload. applications, however, parse utilize attributes defined within their profile.
1.1.7.3
Broadcast addressing
application broadcast messages endpoints given destination device. This form broadcast addressing called application broadcast. destination address shall 16-bit network broadcast address broadcast flag shall frame control field. source shall include cluster identifier, profile identifier source endpoint fields frame (see sub-clause 1.2.5).
Comment #171,
Copyright 2005 ZigBee Standards Organization. rights reserved.
Application Layer Specification
1.1.8
ZigBee device objects
ZigBee device objects (ZDO), represents base class functionality that provides interface between application objects, device profile APS. located between application framework application support sub-layer. satisfies common requirements applications operating ZigBee protocol stack. responsible following: Initializing application support sub-layer (APS), network layer (NWK), security services specification (SSS). Assembling configuration information from applications determine implement discovery, security management, network management, binding management.
presents public interfaces application objects application framework layer control device network functions application objects. interfaces lower portions ZigBee protocol stack, endpoint through APSDE-SAP data through APSME-SAP control messages. public interface provides address management device, discovery, binding, security functions within application framework layer ZigBee protocol stack. These services described following sub-clauses. fully described clause 1.5.
1.1.8.1
Discovery management
Discovery management provided application objects whereby, when queried, IEEE address requested device shall returned device ZigBee device), along with device addresses associated devices device ZigBee coordinator router). This referred device discovery, used discovery ZigBee devices. addition device discovery, service discovery also provided determine what services offered each endpoint, defined device, respective application objects. device discover active endpoints individual devices devices device discover specific services that match given criteria (profile identifiers cluster identifiers).
1.1.8.2
Binding management
Binding management provided application objects order bind application objects ZigBee devices each other clear concise connections through layers protocol stack though various connections provided ZigBee network nodes. Binding tables constructed populated according binding calls results. device bind, bind unbind commands between devices supported ZigBee device profile.
1.1.8.3
Security management
Security management provided application objects enabling disabling security portion system. enabled, management performed master keys, network keys, means establish link key. Primitives defined Chapter permit establishment, transport authentication.
1.2.1
ZigBee application support (APS) sub-layer
Scope
This clause specifies portion application layer providing service specification interface both manufacturer-defined application objects ZigBee device objects. specification includes
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
data service methods discovery binding, well description application support sublayer frame format frame type specifications.
1.2.2
Purpose
purpose this clause define requirements ZigBee application support (APS) sublayer protocol. These requirements based both driver functionality necessary enable correct operation ZigBee network layer functionality required manufacturer-defined application objects. This specification shall provide solution requirements defined ZigBee Network Working Group Requirements Definition document [B4] including fully specified primitive interface.
1.2.3
Application support (APS) sub-layer overview
application support sub-layer provides interface between network layer application layer through general services both ZigBee device object (ZDO) manufacturerdefined application objects. These services offered entities: data service management service. data entity (APSDE) provides data transmission service associated SAP, APSDE-SAP. management entity (APSME) provides management service associated SAP, APSME-SAP, maintains database managed objects known information base (AIB).
1.2.3.1
Application support sub-layer data entity (APSDE)
APSDE shall provide data service network layer both application objects enable transport application PDUs between more devices. devices themselves must located same network. APSDE will provide following services: Generation Application level (APDU). APSDE shall take application generate adding appropriate protocol overhead. Binding. This ability match devices together based their services their needs. Once devices bound, APSDE shall able transfer message received from bound device over second device.
1.2.3.2
Application support sub-layer management entity (APSME)
APSME shall provide management service allow application interact with stack. APSME shall provide ability match devices together based their services their needs. This service called binding service APSME shall able construct maintain table store this information. addition, APSME will provide following services: Management. ability attributes device's AIB. Security. ability authentic relationships with other devices through secure keys.
Copyright 2005 ZigBee Standards Organization. rights reserved.
Application Layer Specification
1.2.4
Service specification
sub-layer provides interface between next higher layer entity (NHLE) layer. sub-layer conceptually includes management entity called sub-layer management entity (APSME). This entity provides service interfaces through which sub-layer management functions invoked. APSME also responsible maintaining database managed objects pertaining sub-layer. This database referred sub-layer information base (AIB). Figure depicts components interfaces sub-layer. sub-layer provides services, accessed through service access points (SAPs). These data service, accessed through sub-layer data entity (APSDE-SAP), management service, accessed though sub-layer management entity (APSME-SAP). These services provide interface between NHLE layer, NLDE-SAP NLMESAP interfaces (see clause 2.3). addition these external interfaces, there also implicit interface between APSME APSDE that allows APSME data service.
Next Higher Layer Entity APSDE-SAP APSME-SAP APSME APSDE NLME-SAP Layer Entity
NLDE-SAP
Figure sub-layer reference model 1.2.4.1 data service
sub-layer data entity (APSDE-SAP) supports transport application protocol data units between peer application entities. Table lists primitives supported APSDE-SAP. Each these primitives will discussed following sub-clauses.
Table APSDE-SAP primitives
APSDE-SAP primitive Request Confirm Indication
APSDE-DATA
1.2.4.1.1
1.2.4.1.2
1.2.4.1.3
1.2.4.1.1
APSDE-DATA.request
This primitive requests transfer NHLE (ASDU) from local NHLE single peer NHLE entity.
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
1.2.4.1.1.1
Semantics service primitive
This semantics this primitive follows:
APSDE-DATA.request DstAddrMode, DstAddress, DstEndpoint, ProfileId, ClusterId, SrcEndpoint, asduLength, asdu, TxOptions, DiscoverRoute, RadiusCounter
Table specifies parameters APSDE-DATA.request primitive.
Table APSDE-DATA.request parameters
Name Type Valid range Description
addressing mode destination address used this primitive APDU transferred. This parameter take non-reserved values from following list: 0x00 DstAddress DstEndpoint present. 0x01 short address DstAddress DstEndpoint present. 0x02 extended address DstAddress DstEndpoint present. 0x03 0xff reserved. DstAddress Device address Integer Integer specified DstAddrMode parameter. 0x00 0xff 0x0000 0xffffa individual device address entity which ASDU being transferred. individual endpoint entity which ASDU being transferred. identifier profile which this frame intended.b identifier object binding operation frame sent using indirect addressing. indirect addressing being used, this parameter ignored. individual endpoint entity from which ASDU being transferred. number octets comprising ASDU transferred.
DstAddrMode
Integer
0x00 0xff
DstEndpoint ProfileId
ClusterId
Integer
0x00 0xff
SrcEndpoint asduLength
Integer Integer
0x00 0xfe
Copyright 2005 ZigBee Standards Organization. rights reserved.
Application Layer Specification
Table APSDE-DATA.request parameters
Asdu octets octets comprising ASDU transferred. transmission options ASDU transferred. These bitwise more following: 0000 0xxx TxOptions Bitmap (Where 0x02 key. 0x04 Acknowledged transmission. DiscoverRoute parameter supplies control information from application layer network layer regarding actions taken route discovery. possible values are: 0x00 suppress route discovery (use existing routing information this request). DiscoverRoute Integer 0x00-0x02 0x01 enable route discovery (perform route discovery there already existing route this request). 0x02 force route discovery (explicitly request route discovery occur before routing this request). DiscoverRoute parameter value corresponding NLDEDATA.request (see Chapter 2)d. RadiusCounter
aCCB Comment #168 bCCB Comment #208 cCCB Comment #336 dCCB Comment #256
0x01 Security enabled transmission.
Unsigned Integer
0x00-0xff
distance, hops, that broadcast frame will allowed travel through network.
1.2.4.1.1.2
When generated
This primitive generated local NHLE whenever data (ASDU) transferred peer NHLE.
1.2.4.1.1.3
Effect receipt
receipt this primitive sub-layer entity begins transmission supplied ASDU. DstAddrMode parameter 0x00, DstAddress DstEndpoint parameters ignored value DstEndpoint parameter placed resulting APDU; this option allows indirect addressing used. DstAddrMode parameter 0x01, DstAddress parameter contains 16-bit short address DstEndpoint parameters placed resulting APDU. DstAddrMode parameter 0x02, DstAddress parameter contains extended, 64-bit IEEE address DstEndpoint parameters placed resulting APDU.
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
DiscoverRoute parameter application based requested handling route discovery Network Layer. application employ Acknowledgement application-level message responses determine whether messages received reliably destination. Based metrics managed within application, DiscoverRoute parameter used request route discovery operations Network Layer improve reliable delivery. broadcast messaging employed (the DstAddress 0xffff), application specify RadiusCounter (0x00 targets devices that part network, value 0x01-0xff sets radius broadcast message measured from source)6 APDU transmitted using direct addressing destination address present), APSDE transmits constructed frame issuing NLDE-DATA.request primitive layer. receipt NLDE-DATA.confirm primitive, APSDE issues APSDE-DATA.confirm primitive (see subclause 1.2.4.1.2) with status equal that received from layer. APDU transmitted using indirect addressing (indirect addressing value specified delivery mode sub-field destination address present) this primitive received APSDE ZigBee coordinator router, search made binding table devices bound this device with endpoint information specified SrcEndpoint parameter. bound devices found, APSDE issues APSDE-DATA.confirm primitive with status NO_BOUND_DEVICE. more bound devices were found, APSDE constructs ASDU with destination address endpoint information bound device transmits frame issuing NLDE-DATA.request primitive layer. receipt corresponding NLDE-DATA.confirm, APSDE constructs transmits APDU next bound device, described above; until more bound devices remain. receipt initial request, APSDE issues APSDE-DATA.confirm primitive with status SUCCESS originator indicating that message will reflected each bound device indicated binding table.7 APDU transmitted using indirect addressing non-ZigBee coordinator ZigBee router device received this primitive, APSDE constructs ASDU, without destination endpoint field, issues NLDE-DATA.request primitive layer. receipt NLDE-DATA.confirm primitive, APSDE issues APSDE-DATA.confirm primitive with status equal that received from layer.
1.2.4.1.2
APSDE-DATA.confirm
TxOptions parameter specifies that secured transmission required, sub-layer shall security service provider (see sub-clause 3.2.4 secure ASDU. security processing fails, APSDE shall issue APSDE-DATA.confirm primitive with status SECURITY_FAIL.APSDEDATA.confirm This primitive reports results request transfer data (ASDU) from local NHLE single peer NHLE.
6CCB
Comment #256 Comment #173, 214,
Copyright 2005 ZigBee Standards Organization. rights reserved.
Application Layer Specification
1.2.4.1.2.1
Semantics service primitive
This semantics this primitive follows:
APSDE-DATA.confirm DstAddrMode, DstAddress, DstEndpoint, SrcEndpoint, Status
Table specifies parameters APSDE-DATA.confirm primitive.
Table APSDE-DATA.confirm parameters
Name Type Valid range Description
addressing mode destination address used this primitive APDU transferred. This parameter take nonreserved values from following list: 0x00 DstAddress DstEndpoint present. 0x01 short address DstAddress DstEndpoint present. 0x02 extended address DstAddress DstEndpoint present. 0x03 0xff reserved. DstAddress Device address Integer specified DstAddrMode parameter. 0x00 0xff individual device address entity which ASDU being transferred. individual endpoint entity which ASDU being transferred. individual endpoint entity from which ASDU being transferred. status corresponding request.
DstAddrMode
Integer
0x00 0xff
DstEndpoint
SrcEndpoint
Integer
0x00 0xfe SUCCESS, NO_BOUND_DEVICE, SECURITY_FAIL status values returned from NLDE-DATA.confirm primitive.
Status
Enumeration
1.2.4.1.2.2
When generated
This primitive generated local sub-layer entity response APSDE-DATA.request primitive. This primitive returns status either SUCCESS, indicating that request transmit successful, error code NO_BOUND_DEVICE SECURITY_FAIL status values returned from NLDE-DATA.confirm primitive. reasons these status values fully described next section.
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
1.2.4.1.2.3
Effect receipt
receipt this primitive next higher layer initiating device notified result request transmit. transmission attempt successful, status parameter will SUCCESS. Otherwise, status parameter will indicate error.
1.2.4.1.3
APSDE-DATA.indication
This primitive indicates transfer data (ASDU) from sub-layer local application entity.
1.2.4.1.3.1
Semantics service primitive
This semantics this primitive follows:
APSDE-DATA.indication DstEndpoint, SrcAddrMode, SrcAddress, SrcEndpoint, ProfileId,a ClusterId, asduLength, asdu, WasBroadcast, SecurityStatus
aCCB
Comment #208
Table specifies parameters APSDE-DATA.indication primitive.
Table APSDE-DATA.indication parameters
Name Type Valid range Description
DstEndpoint
Integer
0x00 0xff
target endpoint local entity which ASDU being transferred. addressing mode source address used this primitive APDU transferred. This parameter take non-reserved values from following list: 0x00 SrcAddress SrcEndpoint present. 0x01 short address SrcAddress SrcEndpoint present. 0x02 extended address SrcAddress SrcEndpoint present. 0x03 0xff reserved.
SrcAddrMode
Integer
0x00 0xff
SrcAddress
Device address Integer
specified SrcAddrMode parameter. 0x00 0xfe
individual device address entity from which ASDU being transferred. source endpoint from which ASDU being transferred.
SrcEndpoint
Copyright 2005 ZigBee Standards Organization. rights reserved.
Application Layer Specification
Table APSDE-DATA.indication parameters
ProfileId ClusterId asduLength asdu WasBroadcast Integer Integer Integer octets Boolean 0x0000 0xffff 0x00-0xff
identifier profile from which this frame originated.a identifier received object. number octets comprising ASDU being indicated APSDE. octets comprising ASDU being indicated APSDE. TRUE transmission broadcast, FALSE otherwise. UNSECURED ASDU received without security.
TRUE FALSE
SecurityStatus
Enumeration
UNSECURED, SECURED_NWK_KEY, SECURED_LINK_KEY
SECURED_NWK_KEY received. ASDU secured with key. SECURED_LINK_KEY ASDU secured with link key.
aCCB Comment #208 bCCB Comment #336
1.2.4.1.3.2
When generated
This primitive generated sub-layer issued next higher layer receipt appropriately addressed data frame from local layer entity. frame control field ASDU header indicates that frame secured, then security processing shall done specified subclause 3.2.4.
1.2.4.1.3.3
Effect receipt
receipt this primitive next higher layer notified arrival data device.
1.2.4.2
management service
management entity (APSME-SAP) supports transport management commands between next higher layer APSME. Table summarizes primitives supported APSME through APSME-SAP interface. following sub-clauses more details individual primitives.
Table Summary primitives accessed through APSME-SAP
Name Request Indication Response Confirm
APSME-BIND APSME-GET APSME-SET APSME-UNBIND
1.2.4.3.1 1.2.4.4.1 1.2.4.4.3 1.2.4.3.3
1.2.4.3.2 1.2.4.4.2 1.2.4.4.4 1.2.4.3.4
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
1.2.4.3
Binding Primitives
This primitives defines next higher layer device (commit) binding record local binding table remove binding record from local binding table.8
1.2.4.3.1
APSME-BIND.request
This primitive allows next higher layer request bind devices together issued ZigBee coordinator device indicated SrcAddr request.9
1.2.4.3.1.1
Semantics service primitive
semantics this primitive follows:
APSME-BIND.request SrcAddr, SrcEndpoint, ClusterId, DstAddr, DstEndpoint
Table specifies parameters APSME-BIND.request primitive.
Table APSME-BIND.request parameters
Name Type Valid range Description
SrcAddr SrcEndpoint ClusterId
IEEE address Integer
valid 64-bit IEEE address 0x01 0xff
source IEEE address binding entry. source endpoint binding entry. identifier cluster source device that bound destination device. destination IEEE address binding entry. destination endpoint binding entry.
Integer DstAddr DstEndpoint
0x00 0xff valid 64-bit IEEE address 0x01 0xff
IEEE address Integer
1.2.4.3.1.2
When generated
This primitive generated next higher layer issued sub-layer order instigate binding operation ZigBee coordinator device indicated SrcAddr request.10
1.2.4.3.1.3
Effect receipt
ZigBee coordinator device indicated SrcAddr request receives this primitive from NHLE, APSME attempts create specified entry directly binding table. entry could created, APSME issues APSME-BIND.confirm primitive with Status
Comment #172 Comment #173 Comment #173
9CCB
Copyright 2005 ZigBee Standards Organization. rights reserved.
Application Layer Specification
parameter SUCCESS. entry could created lack capacity binding table, APSME issues APSME-BIND.confirm primitive with Status parameter TABLE_FULL.11
1.2.4.3.2
APSME-BIND.confirm
This primitive allows next higher layer notified results request bind devices directly proxy.
1.2.4.3.2.1
Semantics service primitive
semantics this primitive follows:
APSME-BIND.confirm Status, SrcAddr, SrcEndpoint, ClusterId, DstAddr, DstEndpoint
Table specifies parameters APSME-BIND.confirm primitive.
Table APSME-BIND.confirm parameters
Name Type Valid range Description
Status
Enumeration
SUCCESS, ILLEGAL_DEVICE, ILLEGAL_REQUEST, TABLE_FULL, NOT_SUPPORTED valid 64-bit IEEE address 0x01 0xff
results binding request.
SrcAddr SrcEndpoint
IEEE address Integer
source IEEE address binding entry. source endpoint binding entry. identifier cluster source device that bound destination device. destination IEEE address binding entry. destination endpoint binding entry.
ClusterId
Integer
0x00 0xff
DstAddr DstEndpoint
IEEE address Integer
valid 64-bit IEEE address 0x01 0xff
1.2.4.3.2.2
When generated
This primitive generated APSME issued NHLE response APSME-BIND.request primitive. request successful, Status parameter will indicate successful bind request. Otherwise, status parameter indicates error code ILLEGAL_DEVICE, ILLEGAL_REQUEST TABLE_FULL.
Comment #173,
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
1.2.4.3.2.3
Effect receipt
receipt this primitive, next higher layer notified results bind request. bind request successful, Status parameter SUCCESS. Otherwise, Status parameter indicates error.
1.2.4.3.3
APSME-UNBIND.request
This primitive allows next higher layer ZigBee coordinator device indicated SrcAddr request request unbinding devices.12
1.2.4.3.3.1
Semantics service primitive
semantics this primitive follows:
APSME-UNBIND.request SrcAddr, SrcEndpoint, ClusterId, DstAddr, DstEndpoint
Table specifies parameters APSME-UNBIND.request primitive.
Table APSME-UNBIND.request parameters
Name Type Valid range Description
SrcAddr SrcEndpoint
IEEE address Integer
valid 64-bit IEEE address 0x01 0xff
source IEEE address binding entry. source endpoint binding entry. identifier cluster source device that bound destination device. destination IEEE address binding entry. destination endpoint binding entry.
ClusterId
Integer
0x00 0xff valid 64-bit IEEE address 0x01 0xff
DstAddr DstEndpoint
IEEE address Integer
1.2.4.3.3.2
When generated
This primitive generated next higher layer issued sub-layer order instigate unbind operation ZigBee coordinator device indicated SrcAddr request.13
1.2.4.3.3.3
Effect receipt
receipt this primitive device that currently joined network, APSME issues APSME-UNBIND.confirm primitive with Status parameter ILLEGAL_REQUEST.
12CCB
Comment #173 Comment #173
Copyright 2005 ZigBee Standards Organization. rights reserved.
Application Layer Specification
ZigBee coordinator device indicated SrcAddr request receives this primitive from NHLE, APSME searches specified entry binding table. entry exists, APSME removes entry issues APSME-UNBIND.confirm (see sub-clause 1.2.4.3.4) primitive with Status parameter SUCCESS. entry could found, APSME issues APSME-UNBIND.confirm primitive with Status parameter INVALID_BINDING. devices exist network, APSME issues APSME-BIND.confirm primitive with Status parameter ILLEGAL_DEVICE.14
1.2.4.3.4
APSME-UNBIND.confirm
This primitive allows next higher layer notified results request unbind devices directly proxy.
1.2.4.3.4.1
Semantics service primitive
semantics this primitive follows:
APSME-UNBIND.confirm Status, SrcAddr, SrcEndpoint, ClusterId, DstAddr, DstEndpoint
Table specifies parameters APSME-UNBIND.confirm primitive.
Table APSME-UNBIND.confirm parameters
Name Type Valid range Description
Status
Enumeration
SUCCESS, ILLEGAL_DEVICE, ILLEGAL_REQUEST, INVALID_BINDING valid 64-bit IEEE address 0x01 0xff
results unbind request.
SrcAddr SrcEndpoint
IEEE address Integer
source IEEE address binding entry. source endpoint binding entry. identifier cluster source device that bound destination device. destination IEEE address binding entry. destination endpoint binding entry.
ClusterId
Integer
0x00 0xff
DstAddr DstEndpoint
IEEE address Integer
valid 64-bit IEEE address 0x01 0xff
1.2.4.3.4.2
When generated
This primitive generated APSME issued NHLE response APSMEUNBIND.request primitive. request successful, Status parameter will indicate successful
Comment #173
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
unbind request. Otherwise, status parameter indicates error code ILLEGAL_DEVICE, ILLEGAL_REQUEST, INVALID_BINDING.
1.2.4.3.4.3
Effect receipt
receipt this primitive, next higher layer notified results unbind request. unbind request successful, Status parameter SUCCESS. Otherwise, Status parameter indicates error.
1.2.4.4
Information base maintenance
This primitives defines next higher layer device read write attributes AIB.
1.2.4.4.1
APSME-GET.request
This primitive allows next higher layer read value attribute from AIB.
1.2.4.4.1.1
Semantics service primitive
semantics this primitive follows:
APSME-GET.request AIBAttribute
Table specifies parameters this primitive.
Table APSME-GET.request parameters
Name Type Valid Range Description
AIBAttribute
Integer
Table
identifier attribute read.
1.2.4.4.1.2
When generated
This primitive generated next higher layer issued APSME order read attribute from AIB.
1.2.4.4.1.3
Effect receipt
receipt this primitive, APSME attempts retrieve requested attribute from database. identifier attribute found database, APSME issues APSME-GET.confirm primitive with status UNSUPPORTED_ATTRIBUTE. requested attribute successfully retrieved, APSME issues APSME-GET.confirm primitive with status SUCCESS such that contains attribute identifier value.
1.2.4.4.2
APSME-GET.confirm
This primitive reports results attempt read value attribute from AIB.
Copyright 2005 ZigBee Standards Organization. rights reserved.
Application Layer Specification
1.2.4.4.2.1
Semantics service primitive
semantics this primitive follows:
APSME-GET.confirm Status, AIBAttribute, AIBAttributeValue
Table specifies parameters this primitive.
Table APSME-GET.confirm parameters
Name Type Valid Range Description
Status
Enumeration
SUCCESS UNSUPPORTED_A TTRIBUTE Table Attribute Specific (see Table 17).
results request read attribute value. identifier attribute that read. value attribute that read.
AIBAttribute AIBAttributeValue
Integer Various
1.2.4.4.2.2
When generated
This primitive generated APSME issued next higher layer response APSMEGET.request primitive. This primitive returns status SUCCESS, indicating that request read attribute successful, error code UNSUPPORTED_ATTRIBUTE. reasons these status values fully described sub-clause 1.2.4.4.1.3.
1.2.4.4.2.3
Effect receipt
receipt this primitive, next higher layer notified results request read attribute. request read attribute successful, Status parameter will SUCCESS. Otherwise, status parameter indicates error.
1.2.4.4.3
APSME-SET.request
This primitive allows next higher layer write value attribute into AIB.
1.2.4.4.3.1
Semantics service primitive
semantics this primitive follows:
APSME-SET.request AIBAttribute, AIBAttributeValue
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
Table specifies parameters this primitive.
Table APSME-SET.request parameters
Name Type Valid Range Description
AIBAttribute AIBAttributeValue
Integer Various
Table Attribute Specific (see Table 17).
identifier attribute written. value attribute that should written.
1.2.4.4.3.2
When generated
This primitive generated next higher layer issued APSME order write value attribute AIB.
1.2.4.4.3.3
Effect receipt
receipt this primitive APSME attempts write given value indicated attribute database. AIBAttribute parameter specifies attribute that found database, APSME issues APSME-SET.confirm primitive with status UNSUPPORTED_ATTRIBUTE. AIBAttributeValue parameter specifies value that valid range given attribute, APSME issues APSME-SET.confirm primitive with status INVALID_PARAMETER. requested attribute successfully written, APSME issues APSME-SET.confirm primitive with status SUCCESS.
1.2.4.4.4
APSME-SET.confirm
This primitive reports results attempt write value attribute.
1.2.4.4.4.1
Semantics service primitive
semantics this primitive follows:
APSME-SET.confirm Status, AIBAttribute
Table specifies parameters this primitive.
Table APSME-SET.confirm parameters
Name Type Valid Range Description
Status
Enumeration
SUCCESS, INVALID_PARAMETER UNSUPPORTED_ATTRIBUTE Table
result request write Attribute. identifier attribute that written.
AIBAttribute
Integer
1.2.4.4.4.2
When generated
This primitive generated APSME issued next higher layer response APSMESET.request primitive. This primitive returns status either SUCCESS, indicating that requested
Copyright 2005 ZigBee Standards Organization. rights reserved.
Application Layer Specification
value written indicated attribute, error code INVALID_PARAMETER UNSUPPORTED_ATTRIBUTE. reasons these status values fully described subclause 1.2.4.4.3.3.
1.2.4.4.4.3
Effect receipt
receipt this primitive, next higher layer notified results request write value attribute. requested value written indicated attribute, Status parameter will SUCCESS. Otherwise, Status parameter indicates error.
1.2.5
Frame formats
This sub-clause specifies format frame (APDU). Each frame consists following basic components: header, which comprises frame control addressing information. payload, variable length, which contains information specific frame type.
frames sub-layer described sequence fields specific order. frame formats this sub-clause depicted order which they transmitted layer, from left right, where leftmost transmitted first time. Bits within each field numbered from (leftmost least significant) (rightmost most significant), where length field bits. Fields that longer than single octet sent layer order from octet containing lowest numbered bits octet containing highest numbered bits.
1.2.5.1
General APDU frame format
frame format composed header payload. fields header appear fixed order, however, addressing fields included frames. general frame shall formatted illustrated Figure
Octets: Variable
Frame control
Destination endpoint
Cluster Identifier
Profile Identifier
Source endpoint Frame payload
Addressing fields header payload
Figure General frame format 1.2.5.1.1 Frame control Field
frame control field 8-bits length contains information defining frame type, addressing fields other control flags. frame control field shall formatted illustrated Figure
Bits:
Frame type
aCCB
Delivery mode
Indirect address modea
Security
Ack. request
Reserved
Comment #210
Figure Format frame control field
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
1.2.5.1.1.1
Frame type sub-field
frame type sub-field bits length shall non-reserved values listed Table
Table Values frame type sub-field
Frame type value Frame type name
Data Command Acknowledgement Reserved
1.2.5.1.1.2
Delivery mode sub-field
delivery mode sub-field bits length shall non-reserved values from Table
Table Values delivery mode sub-field
Delivery mode value Delivery mode name
Normal unicast delivery Indirect addressing Broadcast Reserved
value 0b01 then indirect addressing either destination source endpoint shall omitted, depending value indirect address mode sub-field. value 0b10 then message broadcast. this case message will devices endpoints.15
1.2.5.1.1.3 Indirect address mode sub-field
indirect address mode sub-field length specifies whether source destination endpoint fields present frame when delivery mode sub-field indicate indirect addressing. this sub-field destination endpoint field shall omitted from frame, indicating indirect transmission ZigBee coordinator. this sub-field source endpoint field shall omitted from frame, indicating indirect transmission from ZigBee coordinator. delivery mode sub-field frame control field does indicate indirect addressing, indirect address mode sub-field shall ignored.16
1.2.5.1.1.4
Security sub-field
Security Services Provider (see Chapter manages security sub-field.
15CCB
Comment #165. Comment #210
Copyright 2005 ZigBee Standards Organization. rights reserved.
Application Layer Specification
1.2.5.1.1.5
Acknowledgement request sub-field
acknowledgement request sub-field length specifies whether current transmission requires acknowledgement frame sent recipient receipt frame. this sub-field recipient shall construct send acknowledgement frame back originator after determining that frame valid. this sub-field recipient shall send acknowledgement frame back originator after determining that frame valid.
1.2.5.1.2
Destination endpoint field
destination endpoint field 8-bits length specifies endpoint final recipient frame. destination endpoint value 0x00 addresses frame ZigBee device object (ZDO), resident each device. destination endpoint value 0x01-0xf0 addresses frame application operating that endpoint. destination endpoint value 0xff addresses frame active endpoints. other endpoints (0xf1-0xfe) reserved.
1.2.5.1.3
Cluster identifier field
cluster identifier field 8-bits length specifies identifier cluster that used binding operation ZigBee coordinator device indicated SrcAddr request. frame type sub-field frame control field specifies whether cluster identifier field present not. will data frames, command frames.17
1.2.5.1.4
Profile identifier field
profile identifier octets length specifies ZigBee profile identifier which frame intended shall used during filtering messages each device that takes delivery frame. This field shall present only data acknowledgement frames.18
1.2.5.1.5
Source endpoint field
source endpoint field 8-bits length specifies endpoint initial originator frame. source endpoint value 0x00 indicates that frame originated from ZigBee device object (ZDO) resident each device. source endpoint value 0x01-0xf0 indicates that frame originated from application operating that endpoint. other endpoints (0xf1-0xfe) reserved. delivery mode sub-field frame control field indicates delivery mode indirect addressing indirect address mode sub-field this field shall included frame19
1.2.5.1.6
Frame payload field
frame payload field variable length contains information specific individual frame types.
1.2.5.2
Format individual frame types
There three defined frame types: data, command acknowledgement. Each these frame types discussed following sub-clauses.20
Comment #173 Comment #186 19CCB Comment #165, Comment #230
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
1.2.5.2.1
Data frame format
data frame shall formatted illustrated Figure
Octets: 0/b1 Variable
Frame control
Destination endpoint
Cluster identifier header
Profile identifier
Source endpoint
Data payload payload
Comment #186, Comment #188
Figure Data frame format
order fields data frame shall conform order general frame illustrated Figure 3.21
1.2.5.2.1.1
Data frame header field
header field data frame shall contain frame control, cluster identifier, profile identifier source endpoint fields. destination endpoint field shall included data frame according value delivery mode sub-field frame control field.22 frame control field, frame type sub-field shall contain value that indicates data frame, shown Table source endpoint present sub-field shall other sub-fields shall appropriately according intended data frame.
1.2.5.2.1.2
Data payload field
outgoing data frame, data payload field shall contain sequence octets that next higher layer requested data service transmit. incoming data frame, data payload field shall contain sequence octets that been received data service that reflected destination devices delivered next higher layer coordinator destinations.
1.2.5.2.2
command frame format
command frame shall formatted illustrated Figure
Octets: Variable
Frame control header
command identifier
command payload
payload
Figure command frame format
order fields command frame shall conform order general frame illustrated Figure
21CCB
Comment #186,
ibid
Copyright 2005 ZigBee Standards Organization. rights reserved.
Application Layer Specification
1.2.5.2.2.1
command frame header field
header field command frame shall contain frame control Payload. Payload portion Command Frame shall contain Command Identifier followed Command Payload. frame control field, frame type sub-field shall contain value that indicates command frame, shown Table Command Payload shall appropriately according intended command frame.
1.2.5.2.2.2
command identifier field
command identifier field identifies command being used.
1.2.5.2.2.3
command payload field
command payload field command frame shall contain command itself.
1.2.5.2.3
Acknowledgement frame format
acknowledgement frame shall formatted illustrated Figure
Octets: 0/a1
Frame control
Destination endpoint
Cluster header
Profile identifierb
Source endpoint
aCCb Comment #165 bCCB Comment #186,
Figure Acknowledgement frame format
order fields acknowledgement frame shall conform order general frame illustrated Figure 5.23
1.2.5.2.3.1
Acknowledgement frame header field
header field acknowledgement frame shall contain frame control, cluster identifier profile identifier fields. delivery mode indicates direct addressing both source destination endpoint fields shall included acknowledgement frame. delivery mode indicates indirect addressing source destination endpoint fields shall included acknowledgement frame according value indirect address mode sub-field frame control field. frame control field, frame type sub-field shall contain value that indicates acknowledgement frame, shown Table other sub-fielsds shall appropriately according intended acknowledgement frame. Where present, source endpoint field shall reflect value destination endpoint field frame that being acknowledged. Similarly, where present, destination endpoint field shall reflect value source endpoint field frame that being acknowledged.24
23CCB
Comment #186, Comment #165, 186,
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
1.2.6
Command frames
This specification defines command frames. Refer sub-clause 3.5.9 thorough description command frames primitives related security.
1.2.7
1.2.7.1
Constants attributes
Constants
constants that define characteristics sub-layer presented Table
Table sub-layer constants
Constant Description Value
apscMaxAddrMapEntries
maximum number Address entries.
(minimum value) Implementation-specific (maximum value)
apscMaxDescriptorSize
maximum number octets contained non-complex descriptor. maximum number octets that returned through discovery process. maximum number octets added sub-layer payload.
apscMaxDiscoverySize
(without security) (with security)
apscMaxFrameOverhead
apscMaxFrameRetries
maximum number retries allowed after transmission failure. maximum number seconds wait acknowledgement transmitted frame.
0.05 (2*nwkcMaxDepth) (security encrypt/decrypt delay), where (security encrypt/ decrypt delay) (assume 0.05 encrypt decrypt cycle)a
apscAckWaitDuration
aCCB
Comment #166, #366
Copyright 2005 ZigBee Standards Organization. rights reserved.
Application Layer Specification
1.2.7.2
Information Base
information base comprises attributes required manage layer device. attribtues listed Table also comprises some additional attributes that required manage security service provider. These attributes listed sub-clause 3.5.10.
Table attributes
Attribute Identifier
Type
Range
Description
Default
apsAddressMap
0xc0
Variable
current IEEE address maps (see Table 18). current binding table entries device (see subclause 1.2.8.1.1).
Null
apsBindingTable
0xc1
Variable
Null
Comment #150 bCCB Comment #248
Table Address
Entry Number IEEE address address
0x00 apscMaxAddrMapEntries
0x00000000 0xffffffff
0x0000 0xffff
1.2.8
1.2.8.1
Functional description
Binding
maintain binding table, which allows ZigBee devices establish designated destination frames from given source endpoint with given cluster This table employed indirect addressing mechanism.
1.2.8.1.1
Binding table implementation
ZigBee coordinator device designated containing binding table shall able support binding table implementation specific length. binding table shall implement following mapping: Where:
ad1, ad2, adn, )}25
address device source binding link, endpoint identifier device source binding link,
Comment #173
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
cluster identifier used binding link, address device destination binding link, endpoint identifier device destination binding link
1.2.8.1.2
Binding
APSME-BIND.request APSME-UNBIND.request primitive executed ZigBee coordinator device designated SrcAddr initiates procedure creating removing binding link. Only those devices that ZigBee coordinator capable currently operating ZigBee coordinator device indicated SrcAddr request shall initiate this procedure. this procedure initiated other device, APSME shall terminate procedure notify NHLE illegal request. This achieved issuing APSME-BIND.confirm APSME-UNBIND.confirm primitive with Status parameter ILLEGAL_REQUEST. When this procedure initiated, APSME ZigBee coordinator device designated SrcAddr shall first extract address endpoint both source destination binding link. With this information, APSME shall either create entry remove corresponding entry from binding table, depending whether bind unbind procedure, respectively, initiated. bind operation requested, APSME shall create entry binding table. ZigBee coordinator device designated SrcAddr shall only create entry binding table capacity capacity available, shall terminate procedure notify NHLE unavailable capacity. This achieved issuing APSME-BIND.confirm primitive with Status parameter TABLE_FULL.26 unbind operation requested, APSME shall search binding table existing entry that matches information contained initiation request. entry found, APSME shall terminate procedure notify NHLE invalid binding. This achieved issuing APSME-UNBIND.confirm primitive with Status parameter INVALID_BINDING. entry found, APSME shall remove entry binding table. binding link successfully created removed, APSME shall notify NHLE results direct binding attempt success procedure. This achieved issuing APSMEBIND.confirm primitive with binding results status parameter SUCCESS. procedure successful direct binding illustrated shown Figure
Comment #173
Copyright 2005 ZigBee Standards Organization. rights reserved.
Application Layer Specification
ZigBee coord. SrcAddr
ZigBee coord SrcAddr.
APSME(UN)BIND.request Create entry remove existing entry binding table
ZigBee coord SrcAddr.
APSME(UN)BIND.confirm
Figure Direct binding ZigBee coordinator SrcAddr device27 1.2.8.2 Transmission, reception acknowledgement
This sub-clause describes fundamental procedures transmission, reception acknowledgement
1.2.8.2.1
Transmission
Only those devices that currently part network shall send frames from sub-layer. other device receives request transmit frame shall discard frame notify instigating layer error. APSDE-DATA.confirm primitive with status CHANNEL_ACCESS_FAILURE indicates that attempt transmission frame unsuccessful channel being busy. frames handled generated within sub-layer shall constructed according general frame format specified transmitted using layer data service28 Transmissions either direct indirect. Direct transmissions shall include both destination source endpoint fields. this case, delivery mode sub-field frame control field shall either 0x00 (Normal Unicast) 0x02 (Broadcast). layer device originating indirect transmission where binding table entry stored ZigBee coordinator shall direct transmission ZigBee coordinator, which shall handle task message reflection. Indirect transmissions (i.e. those which delivery mode sub-field 0b01) shall include only either source endpoint field destination endpoint field, depending direction transmission with respect ZigBee coordinator. indirect transmission directed ZigBee coordinator, indirect address mode sub-field shall destination endpoint field shall omitted from frame. Conversely, indirect transmission directed from ZigBee coordinator after message reflection, indirect address mode sub-field shall source endpoint field shall omitted from frame. devices where binding table stored source device, layer source device originating transmission shall employ direct transmission destination addresses indicated corresponding binding table entries. this case, delivery mode sub-field frame control field shall 0x00.29
27ibid
Comment #208
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
destination endpoint field, present, shall contain endpoint intended recipient APDU. source endpoint field, present, shall contain endpoint originator APDU. security required, then frame shall processed described clause 3.5. When frame constructed ready transmission, shall passed data service with suitable destination source address. APDU transmission initiated issuing NLDEDATA.request primitive layer results transmission returned NLDEDATA.confirm primitive.
1.2.8.2.2
Reception rejection
sub-layer shall able filter frames arriving layer data service only present frames that interest NHLE. APSDE receives secured frame, shall process frame described clause remove security. APSDE receives frame containing both destination source endpoints, shall assumed direct transmission. this case, APSDE shall pass directly NHLE. APSDE ZigBee coordinator receives frame containing only source endpoint with delivery mode sub-field frame control field indirect addressing value (0x01) shall assumed indirect transmission. device ZigBee coordinator, frame shall discarded destination endpoint present delivery mode sub-field frame control field indirect addressing value (0x01). APSDE ZigBee coordinator receives indirect transmission, shall search binding table entry that matches source address communicated from layer, cluster identifier included received frame source endpoint included frame. match found, frame shall discarded. match found, APSDE shall build APDU each destination endpoint contained matching entry binding table. APSDE shall then transmit each frame using data service.30 APSDE device receives transmission, shall pass directly NHLE, unless needs reflected.
1.2.8.2.3
acknowledgements
data command frame shall sent with acknowledgement request sub-field appropriately frame. acknowledgement frame shall always sent with acknowledgement request sub-field Similarly, frame that broadcast shall sent with acknowledgement request sub-field
1.2.8.2.3.1
acknowledgement
frame that received intended recipient with acknowledgement request (AR) sub-field shall acknowledged. originating device shall assume that transmission frame successful. Figure shows scenario transmitting single frame data from originator recipient without requiring acknowledgement. this case, originator transmits data frame with sub-field equal
29CCB
Comment #173, Comment #210
Copyright 2005 ZigBee Standards Organization. rights reserved.
Application Layer Specification
Originator next higher layer
Originator
Recipient
Data (AR=0)
Recipient next higher layer
APSDE-DATA.request (AR=0) APSDE-DATA.confirm APSDE-DATA.indication
Figure Successful data transmission without acknowledgement 1.2.8.2.3.2 Acknowledgement
frame that received intended recipient with acknowledgement request (AR) sub-field shall acknowledged. intended recipient correctly receives frame, shall generate send acknowledgement frame originator frame that being acknowledged. original transmission used indirect addressing, then ZigBee coordinator shall send acknowledgement originator, then each reflected message shall indicate recipient that requires acknowledgement transmitting data frame with acknowledgement request sub-field frame control field 1.31 transmission acknowledgement frame shall commence when sub-layer determines that frame valid. Figure shows scenario transmitting single frame data from originator recipient with acknowledgement. this case, originator indicates recipient that requires acknowledgement transmitting data frame with sub-field
Originator next higher layer
Originator
Recipient
Data (AR=1)
Recipient next higher layer
APSDE-DATA.request (AR=1)
Acknowldgement APSDE-DATA.indication APSDE-DATA.confirm
Figure Successful data transmission with acknowledgement
Comment #215
Copyright 2005 ZigBee Standards Organization. rights reserved.
ZigBee Specification
1.2.8.2.4
Retransmissions
device that sends frame with acknowledgement request sub-field shall assume that transmission successfully received shall hence perform retransmission procedure. device that sends frame with acknowledgement request sub-field shall wait most apscAckWaitDur

Other recent searches


ZHX1423 - ZHX1423   ZHX1423 Datasheet
WM8904-6201-FL32-M-REV1 - WM8904-6201-FL32-M-REV1   WM8904-6201-FL32-M-REV1 Datasheet
TCS450 - TCS450   TCS450 Datasheet
QL902M - QL902M   QL902M Datasheet
Q68000-A8000 - Q68000-A8000   Q68000-A8000 Datasheet
MPEG-2 - MPEG-2   MPEG-2 Datasheet
HT6240-002 - HT6240-002   HT6240-002 Datasheet

 

Privacy Policy | Disclaimer
© 2012 Datasheet Archive