Information technology – Open Connectivity Foundation (OCF) Specification — Part 11: Device to cloud services specification

This document defines functional extensions to the capabilities defined in ISO/IEC 30118-1 to meet the requirements of the OCF Cloud. This document specifies new Resource Types to enable the functionality and any extensions to the existing capabilities defined in ISO/IEC 30118-1.

Technologies de l'information — Specification de la Fondation pour la connectivité ouverte (Fondation OCF) — Partie 11: Spécification des services entre appareil et nuage

General Information

Status
Published
Publication Date
17-Oct-2021
Current Stage
6060 - International Standard published
Start Date
18-Oct-2021
Due Date
16-May-2022
Completion Date
18-Oct-2021
Ref Project
Standard
ISO/IEC 30118-11:2021 - Information technology – Open Connectivity Foundation (OCF) Specification
English language
37 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


INTERNATIONAL ISO/IEC
STANDARD 30118-11
First edition
2021-10
Information technology — Open
Connectivity Foundation (OCF)
Specification —
Part 11:
Device to cloud services specification
Technologies de l'information — Specification de la Fondation pour la
connectivité ouverte (Fondation OCF) —
Partie 11: Spécification des services entre appareil et nuage
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: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
© ISO/IEC 2021 – All rights reserved

Contents Page
Foreword . v
Introduction . vi
1 Scope . 1
2 Normative references . 1
3 Terms, definitions, and abbreviated terms . 2
3.1 Terms and definitions . 2
3.2 Symbols and abbreviated terms . 2
4 Document conventions and organization . 3
4.1 Conventions . 3
4.2 Notation . 3
5 Overview . 4
5.1 Introduction . 4
5.2 OCF Cloud architecture alignment with ISO IEC 17789 . 4
5.3 Architecture . 5
5.4 Interaction flow . 6
5.5 Cloud operational flow . 7
5.5.1 Introduction . 7
5.5.2 Pre-requisites and OCF Cloud user account creation . 7
5.5.3 Mediator registration with the OCF Cloud . 7
5.5.4 Device provisioning by the Mediator . 8
5.5.5 Device registration with the OCF Cloud . 8
5.5.6 Connection with the OCF Cloud . 8
5.5.7 Publishing links to the OCF Cloud RD . 8
5.5.8 Client to server communication through the OCF Cloud . 8
5.5.9 Refreshing connection with the OCF Cloud . 9
5.5.10 Closing connection with the OCF Cloud. 9
5.5.11 Deregistering from the OCF Cloud . 9
6 Resource model . 11
6.1 OCF Cloud Resource Directory . 11
6.1.1 Indirect discovery for lookup of Resources . 11
6.1.2 Resource Directory definition . 11
6.1.3 RD operational flows . 12
6.2 CoAPCloudConf Resource . 17
6.2.1 Introduction . 17
6.2.2 Resource definition . 17
6.2.3 Cloud status governing state machine . 18
6.2.4 Error handling . 20
7 Network and connectivity . 20
8 Functional interactions . 21
8.1 Onboarding, provisioning, and configuration . 21
8.1.1 Overview . 21
8.1.2 Use of Mediator . 21
8.1.3 Device connection to the OCF Cloud . 24
8.1.4 Device registration with the OCF Cloud . 24
8.2 Resource publication . 24
© ISO/IEC 2021 – All rights reserved iii

8.3 Client registration with the OCF Cloud . 25
8.4 Resource discovery . 25
8.5 Device deregistration from the OCF Cloud . 27
8.6 Device management . 27
8.6.1 Behaviours on Device maintenance state changes . 27
10 Security . 27
Annex A (normative) Swagger2.0 definitions . 28
A.1 List of Resource type definitions . 28
A.2 Resource directory resource . 28
A.2.1 Introduction . 28
A.2.2 Well-known URI. 28
A.2.3 Resource type . 28
A.2.4 OpenAPI 2.0 definition. 28
A.2.5 Property definition . 32
A.2.6 CRUDN behaviour . 33
A.3 CoAP Cloud configuration Resource . 33
A.3.1 Introduction . 33
A.3.2 Example URI. 33
A.3.3 Resource type . 33
A.3.4 OpenAPI 2.0 definition. 33
A.3.5 Property definition . 37
A.3.6 CRUDN behaviour . 37

iv © 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 Device to Cloud Services
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 v

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 Resourc
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.