ISO/IEC 30118-17:2021

Information technology – Open Connectivity Foundation (OCF) Specification - Part 17: OCF resource to Zigbee cluster mapping specification

This document provides detailed mapping information between Zigbee defined Clusters and OCF defined Resources.

Technologies de l'information — Specification de la Fondation pour la connectivité ouverte (Fondation OCF) — Partie 17: Spécification du mapping entre ressources OCF et grappe Zigbee

General Information

• Status: Published
• Publication Date: 17-Oct-2021
• ICS: 35.200 - Interface and interconnection equipment
• Technical Committee: ISO/IEC JTC 1 - Information technology
• Drafting Committee: ISO/IEC JTC 1 - Information technology
• Current Stage: 6060 - International Standard published
• Start Date: 18-Oct-2021
• Due Date: 16-May-2022
• Completion Date: 18-Oct-2021

Overview

ISO/IEC 30118-17:2021 defines a formal mapping between Open Connectivity Foundation (OCF) resources and Zigbee clusters. The standard documents how Zigbee-defined clusters (Zigbee 3.0 / ZCL) can be exposed, translated and represented as OCF resources, enabling consistent interoperability between Zigbee devices and OCF-based applications, gateways and platforms.

Keywords: ISO/IEC 30118-17:2021, OCF resource to Zigbee cluster mapping, Zigbee to OCF mapping, IoT interworking.

Key topics and technical requirements

The document covers practical mapping rules and technical requirements, including:

• Mapping theory & approach

  • Interworking approach and translation principles for mapping Zigbee clusters to OCF resources.
  • Mapping syntax and notation conventions used in the standard.

• Property and value rules

  • Value assignment, property naming, ranges and array handling.
  • Default and conditional mappings, and rules for method invocation across protocols.

• Zigbee translation & gateway requirements

  • Operational scenarios for Zigbee bridging functions and specific requirements for Zigbee 3.0 servers.
  • Guidelines for exposing Zigbee servers to OCF clients and for creating virtual OCF servers that represent Zigbee devices.

• Device & resource equivalence

  • Device type mapping between Zigbee device types and OCF device types.
  • Detailed equivalence tables for common clusters (On/Off, Level Control, Color Control, Thermostat, Window Covering, Temperature Measurement, Occupancy Sensing, IAS Zone, etc.).

• Detailed mapping APIs

  • API-level derived models and property definitions for individual clusters to support consistent implementation and testing.

Applications and who should use this standard

ISO/IEC 30118-17:2021 is targeted at professionals implementing IoT interoperability between Zigbee ecosystems and OCF-based systems:

• Device manufacturers building Zigbee devices that need to interoperate with OCF ecosystems.
• Gateway and hub vendors implementing Zigbee-to-OCF bridging or virtual OCF server functionality.
• IoT platform and application developers who consume OCF resources mapped from Zigbee devices.
• System integrators and solution architects deploying smart home and building automation solutions.
• Test labs and certification bodies validating conformance of mappings and interworking.

Typical use cases include smart lighting, HVAC/thermostat integration, motorized window coverings, environmental sensors, occupancy and security sensor interoperability in unified smart home or building management platforms.

Related standards

• Zigbee 3.0 / Zigbee Cluster Library (ZCL)
• OCF core specifications (Open Connectivity Foundation)
• Other parts of the ISO/IEC 30118 series covering OCF mapping and interworking

This standard is essential for reducing integration complexity and ensuring predictable behavior when Zigbee devices are represented and controlled via OCF resource models.

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 30118-17
First edition
2021-10
Information technology — Open
Connectivity Foundation (OCF)
Specification —
Part 17:
OCF resource to Zigbee cluster
mapping specification
Technologies de l'information — Specification de la Fondation pour la
connectivité ouverte (Fondation OCF) —
Partie 17: Spécification du mapping entre ressources OCF et grappe
Zigbee
Reference number
© ISO/IEC 2021
© ISO/IEC 2021
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
ii
© ISO/IEC 2021 – All rights reserved

Contents Page
Foreword . vii
Introduction . viii
1 Scope . 1
2 Normative references . 1
3 Terms, definitions symbols and abbreviations . 2
3.1 Terms and definitions . 2
4 Document conventions and organization . 3
4.1 Conventions . 3
4.2 Notation . 3
5 Theory of operation . 4
5.1 Interworking approach . 4
5.2 Mapping syntax . 4
5.2.1 Introduction . 4
5.2.2 General . 4
5.2.3 Value assignment . 4
5.2.4 Property naming . 4
5.2.5 Range . 4
5.2.6 Arrays . 4
5.2.7 Default mapping . 5
5.2.8 Conditional mapping . 5
5.2.9 Method invocation . 5
6 Zigbee translation . 5
6.1 Operational scenarios . 5
6.2 Requirements specific to Zigbee bridging function . 6
6.2.1 Requirements specific to Zigbee . 6
6.2.2 Exposing Zigbee 3.0 servers to OCF clients . 6
6.2.3 Translation for well-defined set . 8
6.2.4 Exposing a Zigbee 3.0 server as a virtual OCF server . 8
7 Device type mapping . 14
7.1 Introduction . 14
7.2 Zigbee device types to OCF device types . 14
8 Resource to zigbee cluster equivalence . 14
8.1 Introduction . 14
8.2 Zigbee clusters to OCF resources . 14
8.2.1 Introduction . 14
8.2.2 On/off . 15
8.2.3 Level control . 15
8.2.4 Color control . 15
8.2.5 Thermostat . 16
8.2.6 Window covering . 16
8.2.7 Temperature measurement . 17
8.2.8 Occupancy sensing . 17
8.2.9 IAS zone . 17
9 Detailed mapping APIs . 18
9.1 Introduction . 18
© ISO/IEC 2021 – All rights reserved iii

9.2 Color control cluster - color space - control . 18
9.2.1 Derived model . 18
9.2.2 Property definition . 18
9.2.3 Derived model definition . 19
9.3 Color control cluster - color space - information . 19
9.3.1 Derived model . 19
9.3.2 Property definition . 19
9.3.3 Derived model definition . 20
9.4 Color control cluster - color temperature - information . 20
9.4.1 Derived model . 20
9.4.2 Property definition . 21
9.4.3 Derived model definition . 21
9.5 Color control cluster - color temperature - information . 22
9.5.1 Derived model . 22
9.5.2 Property definition . 22
9.5.3 Derived model definition . 22
9.6 Color control cluster - hue and saturation - control . 23
9.6.1 Derived model . 23
9.6.2 Property definition . 23
9.6.3 Derived model definition . 24
9.7 Color control cluster - hue and saturation - information . 25
9.7.1 Derived model . 25
9.7.2 Property definition . 25
9.7.3 Derived model definition . 25
9.8 IAS zone cluster - control . 26
9.8.1 Derived model . 26
9.8.2 Property definition . 26
9.8.3 Derived model definition . 26
9.9 IAS zone cluster - information . 27
9.9.1 Derived model . 27
9.9.2 Property definition . 27
9.9.3 Derived model definition . 31
9.10 Level control cluster - control . 34
9.10.1 Derived model . 34
9.10.2 Property definition . 34
9.10.3 Derived model definition . 35
9.11 Level control cluster - information . 35
9.11.1 Derived model . 35
9.11.2 Property definition . 35
9.11.3 Derived model definition . 36
9.12 Occupancy sensing cluster - information . 36
9.12.1 Derived model . 36
9.12.2 Property definition . 36
9.12.3 Derived model definition . 37
9.13 On/Off cluster - control . 37
9.13.1 Derived model . 37
9.13.2 Property definition . 37
9.13.3 Derived model definition . 38
iv © ISO/IEC 2021 – All rights reserved

9.14 On/off cluster - information . 39
9.14.1 Derived model . 39
9.14.2 Property definition . 39
9.14.3 Derived model definition . 39
9.15 Temperature measurement cluster - information . 40
9.15.1 Derived model . 40
9.15.2 Property definition . 40
9.15.3 Derived model definition . 40
9.16 Thermostat cluster - cool - control . 41
9.16.1 Derived model . 41
9.16.2 Property definition . 41
9.16.3 Derived model definition . 42
9.17 Thermostat cluster - current temperature - information . 42
9.17.1 Derived model . 42
9.17.2 Property definition . 43
9.17.3 Derived model definition . 43
9.18 Thermostat cluster - heat - control . 43
9.18.1 Derived model . 43
9.18.2 Property definition . 44
9.18.3 Derived model definition . 44
9.19 Window covering cluster - configuration - control . 45
9.19.1 Derived model . 45
9.19.2 Property definition . 45
9.19.3 Derived model definition . 46
9.20 Window covering cluster - configuration - information . 47
9.20.1 Derived model . 47
9.20.2 Property definition . 47
9.20.3 Derived model definition . 51
9.21 Window covering cluster - lift percentage - control . 53
9.21.1 Derived model . 53
9.21.2 Property definition . 53
9.21.3 Derived model definition . 53
9.22 Window covering cluster - lift percentage - information . 54
9.22.1 Derived model . 54
9.22.2 Property definition . 54
9.22.3 Derived model definition . 54
9.23 Window covering cluster - lift position - control . 55
9.23.1 Derived model . 55
9.23.2 Property definition . 55
9.23.3 Derived model definition . 55
9.24 Window covering cluster - lift position - information . 56
9.24.1 Derived model . 56
9.24.2 Property definition . 56
9.24.3 Derived model definition . 56
9.25 Window covering cluster - tilt percentage - control . 57
9.25.1 Derived model . 57
9.25.2 Property definition . 57
9.25.3 Derived model definition . 58
© ISO/IEC 2021 – All rights reserved v

9.26 Window covering cluster - tilt percentage - information . 58
9.26.1 Derived model . 58
9.26.2 Property definition . 58
9.26.3 Derived model definition . 59
9.27 Window covering cluster - tilt position - control . 59
9.27.1 Derived model . 59
9.27.2 Property definition . 59
9.27.3 Derived model definition . 60
9.28 Window covering cluster - tilt position - information . 60
9.28.1 Derived model . 60
9.28.2 Property definition . 60
9.28.3 Derived model definition . 61

vi © ISO/IEC 2021 – All rights reserved

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees established
by the respective organization to deal with particular fields of technical activity. ISO and IEC technical
committees collaborate in fields of mutual interest. Other international organizations, governmental and non-
governmental, in liaison with ISO and IEC, also take part in the work.
The procedures used to develop this document and those intended for its further maintenance are described in
the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of
document should be noted (see www.iso.org/directives or www.iec.ch/members_experts/refdocs).
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Details of any
patent rights identified during the development of the document will be in the Introduction and/or on the ISO list
of patent declarations received (see www.iso.org/patents) or the IEC list of patent declarations received
(see patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not constitute
an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see  www.iso.org/iso/foreword.html. In
the IEC, see www.iec.ch/understanding-standards.
This document was prepared by the Open Connectivity Foundation (OCF) (as OCF Resource to Zigbee Cluster
Mapping Specification, version 2.2.0) and drafted in accordance with its editorial rules. It was adopted, under
the JTC 1 PAS procedure, by Joint Technical Committee ISO/IEC JTC 1, Information technology.
A list of all parts in the ISO/IEC 30118 series can be found on the ISO and IEC websites.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html and www.iec.ch/national-
committees.
© ISO/IEC 2021 – All rights reserved vii

Introduction
This document, and all the other parts associated with this document, were developed in response to
worldwide demand for smart home focused Internet of Things (IoT) devices, such as appliances, door
locks, security cameras, sensors, and actuators; these to be modelled and securely controlled, locally
and remotely, over an IP network.
While some inter-device communication existed, no universal language had been developed for the
IoT. Device makers instead had to choose between disparate frameworks, limiting their market share,
or developing across multiple ecosystems, increasing their costs. The burden then falls on end users
to determine whether the products they want are compatible with the ecosystem they bought into, or
find ways to integrate their devices into their network, and try to solve interoperability issues on their
own.
In addition to the smart home, IoT deployments in commercial environments are hampered by a lack
of security. This issue can be avoided by having a secure IoT communication framework, which this
standard solves.
The goal of these documents is then to connect the next 25 billion devices for the IoT, providing secure
and reliable device discovery and connectivity across multiple OSs and platforms. There are multiple
proposals and forums driving different approaches, but no single solution addresses the majority of
key requirements. This document and the associated parts enable industry consolidation around a
common, secure, interoperable approach.
ISO/IEC 30118 consists of eighteen parts, under the general title Information technology — Open
Connectivity Foundation (OCF) Specification. The parts fall into logical groupings as described herein:
– Core framework
– Part 1: Core Specification
– Part 2: Security Specification
– Part 13: Onboarding Tool Specification
– Bridging framework and bridges
– Part 3: Bridging Specification
– Part 6: Resource to Alljoyn Interface Mapping Specification
– Part 8: OCF Resource to oneM2M Resource Mapping Specification
– Part 14: OCF Resource to BLE Mapping Specification
– Part 15: OCF Resource to EnOcean Mapping Specification
– Part 16: OCF Resource to UPlus Mapping Specification
– Part 17: OCF Resource to Zigbee Cluster Mapping Specification
– Part 18: OCF Resource to Z-Wave Mapping Specification
– Resource and Device models
– Part 4: Resource Type Specification
– Part 5: Device Specification
viii © ISO/IEC 2021 – All rights reserved

– Core framework extensions
– Part 7: Wi-Fi Easy Setup Specification
– Part 9: Core Optional Specification
– OCF Cloud
– Part 10: Cloud API for Cloud Services Specification
– Part 11: Device to Cloud Services Specification
– Part 12: Cloud Security Specification

© ISO/IEC 2021 – All rights reserved ix

INTERNATIONAL STANDARD ISO/IEC 30118-17:2021(E)

Information technology — Open Connectivity
Foundation (OCF) Specification —
Part 17:
OCF resource to Zigbee cluster mapping specification
1 Scope
This document provides detailed mapping information between Zigbee defined Clusters and OCF
defined Resources.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 30118-1 Information technology – Open Connectivity Foundation (OCF) Specification – Part 1:
Core specification
https://www.iso.org/standard/53238.html
Latest version available at: https://openconnectivity.org/specs/OCF_Core_Specification.pdf
ISO/IEC 30118-2 Information technology – Open Connectivity Foundation (OCF) Specification – Part 2:
Security specification
https://www.iso.org/standard/74239.html
Latest version available at: https://openconnectivity.org/specs/OCF_Security_Specification.pdf
ISO/IEC 30118-3 Information technology – Open Connectivity Foundation (OCF) Specification – Part 3:
Bridging specification
https://www.iso.org/standard/74240.html
Latest version available at: https://openconnectivity.org/specs/OCF_Bridging_Specification.pdf
ISO/IEC 30118-4 Information technology – Open Connectivity Foundation (OCF) Specification – Part 4:
Resource type specification
https://www.iso.org/standard/74241.html
Latest version available at: https://openconnectivity.org/specs/OCF_Resource_Type_Specification.pdf
ISO/IEC 30118-5 Information technology – Open Connectivity Foundation (OCF) Specification – Part 5:
Smart home device specification
https://www.iso.org/standard/74242.html
Latest version available at: https://openconnectivity.org/specs/OCF_Device_Specification.pdf
Derived Models for Interoperability between IoT Ecosystems, Stevens & Merriam, March 2016
https://www.iab.org/wp-content/IAB-uploads/2016/03/OCF-Derived-Models-for-Interoperability-
Between-IoT-Ecosystems_v2-examples.pdf
Zigbee, Zigbee Specification, August 2015
http://www.zigbee.org/zigbee-for-developers/zigbee-3-0/
© ISO/IEC 2021 – All rights reserved 1

Zigbee Cluster Library Specification, Version 1.0
http://www.zigbee.org/zigbee-for-developers/zigbee-3-0/
ZigBee Lighting & Occupancy Device, Version 1.0
http://www.zigbee.org/zigbee-for-developers/zigbee-3-0/
3 Terms, definitions symbols and abbreviations
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 30118-1,
ISO/IEC 30118-2, and ISO/IEC 30118-3 and the following apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
– ISO Online browsing platform: available at https://www.iso.org/obp
– IEC Electropedia: available at http://www.electropedia.org/
3.1.1
Zigbee Attribute
data entity which represents a physical quantity or state within Zigbee.
3.1.2
Zigbee Cluster
one or more Zigbee Attributes (3.1.1), commands, behaviours, and dependencies, which supports an
independent utility or application function.
3.1.3
Zigbee Server
cluster interface which is listed in the input cluster list of the simple descriptor on an endpoint.
3.1.4
Zigbee 3.0 Server
Zigbee Server (3.1.3) which is built on Zigbee 3.0 stack
3.1.5
Zigbee Client
cluster interface which is listed in the output cluster list of the simple descriptor on an endpoint.
3.1.6
Zigbee 3.0 Client
Zigbee Client (3.1.5) which is built on Zigbee 3.0 stack
3.1.7
Zigbee Device
unique device identifier and a set of mandatory and optional clusters to be implemented on a single
Zigbee endpoint.
3.1.8
Zigbee 3.0 Device
Zigbee Device (3.1.7) which is built on Zigbee 3.0 stack
2 © ISO/IEC 2021 – All rights reserved

4 Document conventions and organization
4.1 Conventions
In this document a number of terms, conditions, mechanisms, sequences, parameters, events, states,
or similar terms are printed with the first letter of each word in uppercase and the rest lowercase (e.g.,
Network Architecture). Any lowercase uses of these words have the normal technical English meaning.
In this document, to be consistent with the IETF usages for RESTful operations, the RESTful operation
words CRUDN, CREATE, RETRIVE, UPDATE, DELETE, and NOTIFY will have all letters capitalized.
Any lowercase uses of these words have the normal technical English meaning.
4.2 Notation
In this document, features are described as required, recommended, allowed or DEPRECATED as
follows:
Required (or shall or mandatory).
These basic features shall be implemented to comply with the Mapping Specification. The phrases
“shall not”, and “PROHIBITED” indicate behavior that is prohibited, i.e. that if performed means the
implementation is not in compliance.
Recommended (or should).
These features add functionality supported by the Mapping Specification and should be
implemented. Recommended features take advantage of the capabilities the Mapping Specification,
usually without imposing major increase of complexity. Notice that for compliance testing, if a
recommended feature is implemented, it shall meet the specified requirements to be in compliance
with these guidelines. Some recommended features could become requirements in the future. The
phrase “should not” indicates behavior that is permitted but not recommended.
Allowed (or allowed).
These features are neither required nor recommended by the Mapping Specification, but if the
feature is implemented, it shall meet the specified requirements to be in compliance with these
guidelines.
Conditionally allowed (CA)
The definition or behaviour depends on a condition. If the specified condition is met, then the
definition or behaviour is allowed, otherwise it is not allowed.
Conditionally required (CR)
The definition or behaviour depends on a condition. If the specified condition is met, then the
definition or behaviour is required. Otherwise the definition or behaviour is allowed as default
unless specifically defined as not allowed.
DEPRECATED
Although these features are still described in this document, they should not be implemented except
for backward compatibility. The occurrence of a deprecated feature during operation of an
implementation compliant with the current document has no effect on the implementation’s
operation and does not produce any error conditions. Backward compatibility may require that a
feature is implemented and functions as specified but it shall never be used by implementations
compliant with this document.
© ISO/IEC 2021 – All rights reserved 3

Strings that are to be taken literally are enclosed in “double quotes”.
Words that are emphasized are printed in italic.
5 Theory of operation
5.1 Interworking approach
The interworking between ZigBee Clusters and OCF defined Resources is modelled using the derived
model syntax described in Derived Models for Interoperability between IoT Ecosystems.
5.2 Mapping syntax
5.2.1 Introduction
Within the defined syntax for derived modelling used by this document there are two blocks that define
the actual Property-Property equivalence or mapping. These blocks are identified by the keywords "x-
to-ocf" and "x-from-ocf". Derived Models for Interoperability between IoT Ecosystems does not define
a rigid syntax for these blocks; they are free form string arrays that contain pseudo-coded mapping
logic.
Within this document we apply the rules in defined in clause 5.2 to these blocks to ensure consistency
and re-usability and extensibility of the mapping logic that is defined.
5.2.2 General
All statements are terminated with a carriage return.
5.2.3 Value assignment
The equals sign (=) is used to assign one value to another. The assignee is on the left of the operator;
the value being assigned on the right.
5.2.4 Property naming
All Property names are identical to the name used by the original model; for example, from the OCF
Temperature Resource the Property name "temperature" is used whereas when referred to the derived
ecosystem then the semantically equivalent Property name is used.
The name of the OCF defined Property is prepended by the ecosystem designator "ocf" to avoid
ambiguity (e.g. "ocf.step")
5.2.5 Range
The range on the OCF side is fixed.
5.2.6 Arrays
An array element is indicated by the use of square brackets "[]" with the index of the element contained
therein, e.g. range [1]. All arrays start at an index of 0.
4 © ISO/IEC 2021 – All rights reserved

5.2.7 Default mapping
There are cases where the specified mapping is not possible as one or more of the Properties being
mapped is optional in the source model. In all such instances a default mapping is provided. (e.g.
"transitiontime = 1")
5.2.8 Conditional mapping
When a mapping is dependent on the meeting of other conditions then the syntax:
If "condition", then "mapping".
is applied.
E.g. if onoff = false, then ocf.value = false
5.2.9 Method invocation
The invocation of a command from the derived ecosystem as part of the mapping from an OCF
Resource is indicated by the use if a double colon "::" delimiter between the applicable resource,
service, interface or other construct identifier and the command name. The command name always
includes trailing parentheses which would include any parameters should they be passed.
For example, when dealing with the "on()" command for Zigbee On/off Cluster this gives a complete
command invocation as: "zb.command.onoff::on()".
6 Zigbee translation
6.1 Operational scenarios
The overall goal is to make Bridged Zigbee 3.0 Servers appear to OCF Clients as if they were native
OCF Servers in the local network or cloud environment
The mapping between the OCF data models and Zigbee Clusters is specified in 9. Programmatic (i.e.
On-the-fly) data model translation is not supported.
Figure 1 shows an overview of a Zigbee 3.0 Bridge Platform and its general topology. It exposes Zigbee
3.0 Servers to OCF Clients. Each Bridged Zigbee 3.0 Server is represented as a Virtual OCF Server.
The Zigbee 3.0 Bridging Function supports Asymmetric bridging. The scope of this document is the
asymmetric bridging to expose the Zigbee Server to OCF. The asymmetric bridging to expose an OCF
Server to a Zigbee Client is out of scope.

Figure 1 – OCF Zigbee Bridge Platform and Components
© ISO/IEC 2021 – All rights reserved 5

6.2 Requirements specific to Zigbee bridging function
6.2.1 Requirements specific to Zigbee
This document refers to Zigbee 3.0 or higher. Zigbee 3.0 is built on Zigbee Pro 2015 or newer, which
enhances the IEEE 802.15.4 standard by adding a mesh network and security layers along with an
application framework. Low power support is not the scope of this document.
An OCF Zigbee Bridging Function shall act as a Zigbee Coordinator in network layer. A Zigbee
Coordinator is responsible for initiating and maintaining the devices on the network. An OCF Zigbee
Bridge Platform will act as Zigbee Client towards the Zigbee 3.0 Devices in the application layer. Users
can expect that a certified OCF Bridge Platform will be able to talk to Zigbee 3.0 Devices, without the
user having to buy some other device.
6.2.2 Exposing Zigbee 3.0 servers to OCF clients
The nature of how Zigbee Devices are structured may be different than how an OCF Device is
structured. The mapping of the structure of a Zigbee device on an OCF Device is given by Table 1.
A Zigbee Server cluster may map to one or more OCF Resources. If a specific Zigbee Server cluster
has specific commands, one or more OCF Resources corresponding to the specific command attributes
may be additionally needed.
A Zigbee Attribute of a Zigbee Server cluster typically maps to an OCF Resource Property. However,
in some special cases, multiple attributes are mapped to a single OCF Resource Property e.g.,
"CurrentX" and "CurrentY" of the Zigbee color control cluster map to the "csc" Property in the
"oic.r.colour.csc" (Colour Space Coordinates) Resource because of the difference in the data types,
i.e., "csc" is an array, but "CurrentX" and "CurrentY" map to a number.
Table 2 is a mapping example of this rule.
Table 1 – Translation Rule between Zigbee and OCF Data Models
From Zigbee mapping To OCF mapping
count count
Zigbee Device 1 OCF Device 1
Zigbee Cluster 1 OCF Resource n
Zigbee Attribute 1 OCF Resource Property 1
6 © ISO/IEC 2021 – All rights reserved

Table 2 – Zigbee to OCF Mapping Example (Color Temperature Light)
From Zigbee To OCF
Zigbee 3.0 0x010c OCF oic.d.light
Device (Color Temperature Light) Device (Light)
Zigbee 0x0006 OCF Resource(s) oic.r.switch.binary
Server Cluster (On/Off) (Binary Switch)
0x0300 oic.r.colour.hs
(Color Control Cluster) (Colour Hue and Saturation)
oic.r.colour.csc
(Colour Space Coordinates)
oic.r.colour.colourtemperature
(Colour Temperature)
Zigbee 0x0000 OCF Resource value (of Binary Switch Resource)
Property
Attribute (OnOff of On/Off Cluster)
0x0003 csc (of Colour Space Coordinates)
(CurrentX of Color Control
Cluster)
0x0004
(CurrentY of Color Control
Cluster)
If a Zigbee 3.0 Device, Zigbee Server Cluster, Zigbee Attribute are enlisted in the well-defined set, the
Bridging Function shall follow the requirements for translating it to an OCF Device, OCF Resource, or
OCF Resource Property (i.e. "deep translation").
A Zigbee 3.0 Server Device maps to a single OCF Device Type. The OCF Device Type is provided by
using the Device ID of the Zigbee 3.0 Server Device (The Device ID is allocated by the Zigbee Alliance
and has the same meaning of the OCF Device Type). The Zigbee 3.0 Bridging Function has a table
which includes the mapping information between the Zigbee Device ID and the OCF Device Type.
Based on the table, the Zigbee 3.0 Bridging Function finds the OCF Device Type according to the
Zigbee Device ID.
A Zigbee Device includes one or more Zigbee Server Clusters. If a Zigbee Cluster maps to multiple
OCF Resources, the Zigbee Cluster may be translated as a Resource with a Collection Resource Type.
The resource mapping between Zigbee Server Cluster and OCF Resources is defined in 9 for deep
translation. The Zigbee 3.0 Bridging Function has a table which includes the mapping information
between the identifier of Zigbee Cluster and OCF Resource Type(s). The Zigbee 3.0 Bridging Function
obtains the list of cluster identifiers after the Virtual Zigbee 3.0 Client and Zigbee 3.0 Server Device
are bound. Based on the table, the Zigbee 3.0 Bridging Function finds the OCF Resource Type(s)
according to the identifier of Zigbee Cluster.
Since a Bridging Function knows all relationships between OCF Resources and Zigbee Server Clusters,
the path component of URI can be free to choose. Maintaining relationship information and URI
definition is implementation specific.
If a Zigbee operation fails, the Bridging Function send an appropriate OCF error response to the OCF
Client. it constructs an appropriate OCF error message (e.g., diagnostic payload if using CoAP) from
the Zigbee enumerated status value and Zigbee enumerated status (if any), using the form " name>: ", with the taken from the Zigbee Status Code field and the
taken from the Zigbee enumerated status, and the error code for the OCF network
set to an appropriate value.
© ISO/IEC 2021 – All rights reserved 7

6.2.3 Translation for well-defined set
If a Zigbee 3.0 Device, Zigbee Server Cluster, Zigbee Attribute are enlisted in the well-defined set, the
Bridging Function shall follow the requirements for translating it to an OCF Device, OCF Resource, or
OCF Resource Property (i.e., "deep translation"). Table 3 is the list of Zigbee 3.0 devices and
mandatory Zigbee Server Clusters with corresponding OCF devices and mandatory OCF Resources.
Optional OCF Resources mapped with the specific Zigbee Server Clusters are enlisted in the well-
defined set.
Table 3 – Zigbee 3.0 Device & Cluster – OCF Device & Resource mapping
Zigbee 3.0 Zigbee 3.0 OCF OCF OCF
Device Name Mandatory Cluster Mandatory Resource Type Device Type (“rt”) Device Name
(Device ID)
On/off light On/off oic.r.switch.binary, oic.d.light Light
(0x0100)
Color Temperature On/off, oic.r.switch.binary, oic.d.light Light
Light Level Control,
(0x010c) Color Control
Extended Color Light On/off, oic.r.switch.binary, oic.d.light Light
(0x010d) Level Control,
Color Control
Dimmable Light On/off, oic.r.switch.binary, oic.d.light Light
(0x0101) Level Control
Color Dimmable Light On/off oic.r.switch.binary, oic.d.light Light
(0x0102) Level Control,
Color Control
Temperature Sensor Temperature oic.r.temperature oic.d.sensor Generic Sensor
(0x0302) Measurement
Thermostat Thermostat oic.r.temperature(2) oic.d.thermostat Thermostat
(0x0301)
Window Covering Window Covering oic.r.openlevel oic.d.blind Blind
Device
(0x0202)
Smart Plug On/off, oic.r.switch.binary, oic.d.smartplug Smart Plug
(0x0051) Metering
Mains Power Outlet On/off oic.r.switch.binary, oic.d.smartplug Smart Plug
(0x0009)
On/off output On/off oic.r.switch.binary, oic.d.smartplug Smart Plug
(0x0002
IAS Zone IAS Zone oic.r.ias.zone oic.d.sensor Generic Sensor
(0x0402)
Occupancy Sensor Occupancy Sensing oic.r.sensor.presence oic.d.sensor Generic Sensor
(0x0107 )
6.2.4 Exposing a Zigbee 3.0 server as a virtual OCF server
Table 4 shows how OCF Platform properties, as specified in ISO/IEC 30118-1, shall be derived,
typically from fields of Descriptor
...