APS IB
1.4 The ZigBee device profile
1.4.2 Device Profile overview
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54
— End Device Bind Request Processing
— Bind and Unbind Command Processing
— Network Management
1.4.2.1 Device and service discovery overview The following capabilities exist for device and service discovery:
— Device Discovery – Provides the ability for a device to determine the identity of other devices on the PAN. Device Discovery is supported for both the 64 bit IEEE address and the 16 bit Network address. Device Discovery messages can be used in one of two ways:
— Broadcast addressed – All devices on the network shall respond according to the Logical Device Type and match criteria. ZigBee End Devices shall respond with just their address. Zig-Bee Coordinators and ZigZig-Bee Routers with associated devices shall respond with their address as the first entry followed by the addresses of their associated devices depending on the type of request. The responding devices shall employ APS acknowledged service on the unicast responses.
— Unicast addressed – Only the specified device responds. ZigBee End Devices shall respond with just their address. ZigBee Coordinator or Routers shall reply with their address and the addresses of each of their associated devices
For ZigBee Version 1.0, Device Discovery is a distributed operation where individual devices or their immediate parent devices respond to discovery requests. To enable future upgrades to a centralized or agent based discovery method, a "device address of interest" field has been added and the broadcast addressed discovery commands may be optionally unicast for ZigBee releases after Version 1.0.37
— Service Discovery – Provides the ability for a device to determine services offered by other devices on the PAN.
— Service Discovery messages can be used in one of two ways:
— Broadcast addressed –Due to the volume of information that could be returned, only the individual device shall respond which match criteria established in the request unless that device is a ZigBee Coordinator or ZigBee Router with sleeping associated device. In that case, the ZigBee Coordinator or ZigBee Router shall cache the Service Discovery infor-mation for the sleeping associated devices and respond on their behalf if the sleeping device matches criteria in the request. The responding devices shall also employ APS acknowledged service on the unicast responses.
— Unicast addressed – Only the specified device shall respond. In the case of a ZigBee Coor-dinator or ZigBee Router, these devices shall cache the Service Discovery information for sleeping associated devices and respond on their behalf.
— Service Discovery is supported with the following query types:
— Active Endpoint – This command permits an enquiring device to determine the active endpoints. An active endpoint is one with an application supporting a single profile, described by a Simple Descriptor. The command may be broadcast or unicast addressed.
— Match Simple Descriptor – This command permits enquiring devices to supply a Profile ID and, optionally, lists of input and/or output Cluster IDs and ask for a return of the iden-tity of an endpoint on the destination device which match the supplied criteria. This com-mand may be broadcast or unicast addressed. For broadcast addressed requests, the responding device shall employ APS acknowledged service on the unicast responses.
37CCB Comment #171
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54
— Simple Descriptor – This commands permits an enquiring device to return the Simple Descriptor for the supplied endpoint. This command shall be unicast addressed.
— Node Descriptor - This commands permits an enquiring device to return the Node Descriptor from the specified device. This command shall be unicast addressed.
— Power Descriptor - This commands permits an enquiring device to return the Power Descriptor from the specified device. This command shall be unicast addressed.
— Complex Descriptor – This optional command permits an enquiring device to return the Complex Descriptor from the specified device. This command shall be unicast addressed.
— User Descriptor - This optional command permits an enquiring device to return the User Descriptor from the specified device. This command shall be unicast addressed.
For ZigBee Version 1.0, Service Discovery is a distributed operation where individual devices or their immediate parent devices respond to discovery requests. To enable future upgrades to a centralized or agent based discovery method, a "device address of interest" field has been added and the broadcast addressed discovery commands may be optionally unicast for ZigBee releases after Version 1.0.38 1.4.2.2 End device bind overview
The following capabilities exist for end device bind:
— End Device Bind
— Provides the ability for an application to support “simple binding” where user intervention is employed to identify command/control device pairs. Typical usage would be where a user is asked to push buttons on two devices for installation purposes.
— Provides the ability for an application to support a simplified method of binding where user intervention is employed to identify command/control device pairs. Typical usage would be where a user is asked to push buttons on two devices for installation purposes. Using this mech-anism a second time allows the user to remove the binding table entry39
1.4.2.3 Bind and unbind overview
The following capabilities exist for directly configuring binding table entries:40
— Bind
— Provides the ability for creation of a Binding Table entry that map control messages to their intended destination.
— Unbind
— Provides the ability to remove Binding Table entries.
1.4.2.4 Network management overview The following capabilities exist for network management:
Network management:
— Provides the ability to retrieve management information from the devices including:
— Network discovery results
38CCB Comment #171 39CCB Comment #123, 236 40CCB Comment #236
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54
— Link quality to neighbor nodes
— Routing table contents
— Binding table contents
— Provides the ability to set management information controls including:
— Network disassociate
1.4.2.5 Device Descriptions for the Device Profile
The ZigBee Device Profile utilizes a single Device Description. Each cluster specified as Mandatory shall be present in all ZigBee devices. The response behavior to some messages is logical device type specific.
The support for Optional clusters is not dependent on the logical device type.
1.4.2.6 Service Type usage
The ZigBee Device Profile shall employ the Message (MSG) Service Type. See clause 1.3 for details.
1.4.2.7 Configuration and roles
The Device Profile assumes a client/server topology. A device making Device Discovery, Service Discovery, Binding or Network Management requests does so via a client role. A device which services these requests and responds does so via a server role. The client and server roles are non-exclusive in that a given device may supply both client and server roles.
The Device Profile describes devices in one of two configurations:
— Client – A client issues requests via Device Profile messages. Based on processing of those requests at the server, the client receives responses to the issued requests
— Server – A server is the target of requests via Device Profile messages processes those requests and issues responses.
1.4.2.8 Cluster ID format within the Device Profile
The following Cluster ID format shall be used within the Device Profile:
Figure 29 Cluster ID Format for the Device Profile