ISO/IEC 30118-1:2021
(Main)Information technology — Open Connectivity Foundation (OCF) Specification — Part 1: Core specification
Information technology — Open Connectivity Foundation (OCF) Specification — Part 1: Core specification
The OCF Core specifications are divided into a set of documents: Core specification (this document): The Core specification document specifies the Framework, i.e., the OCF core architecture, interfaces, protocols and services to enable OCF profiles implementation for Internet of Things (IoT) usages and ecosystems. This document is mandatory for all Devices to implement. Core optional specification: The Core optional specification document specifies the Framework, i.e., the OCF core architecture, interfaces, protocols and services to enable OCF profiles implementation for Internet of Things (IoT) usages and ecosystems that can optionally be implemented by any Device. Core extension specification(s): The Core extension specification(s) document(s) specifies optional OCF Core functionality that are significant in scope (e.g., Wi-Fi easy setup, Cloud).
Technologies de l'information — Specification de la Fondation pour la connectivité ouverte (Fondation OCF) — Partie 1: Spécification du coeur
General Information
Relations
Buy Standard
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 30118-1
Second edition
2021-10
Information technology — Open
Connectivity Foundation (OCF)
Specification —
Part 1:
Core specification
Technologies de l'information — Specification de la Fondation pour la
connectivité ouverte (Fondation OCF) —
Partie 1: Spécification du coeur
Reference number
ISO/IEC 30118-1:2021(E)
© ISO/IEC 2021
---------------------- Page: 1 ----------------------
ISO/IEC 30118-1:2021(E)
COPYRIGHT PROTECTED DOCUMENT
© 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
---------------------- Page: 2 ----------------------
ISO/IEC 30118-1:2021(E)
Contents Page
Foreword . vii
Introduction . viii
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 3
3.1 Terms and definitions . 3
3.2 Symbols and abbreviated terms . 7
4 Document conventions and organization . 8
4.1 Conventions . 8
4.2 Notation . 8
4.3 Data types . 9
4.4 Resource notation syntax . 10
5 Architecture . 11
5.1 Overview . 11
5.2 Principle . 11
5.3 Functional block diagram. 12
5.4 Framework . 14
6 Identification and addressing . 14
6.1 Introduction . 14
6.2 Identification . 15
6.2.1 Device and Platform identification. 15
6.2.2 Resource identification and addressing . 15
6.3 Namespace: . 16
6.4 Network addressing . 16
7 Resource model . 17
7.1 Introduction . 17
7.2 Resource . 17
7.3 Property . 18
7.3.1 Introduction . 18
7.3.2 Common Properties . 19
7.4 Resource Type . 21
7.4.1 Introduction . 21
7.4.2 Resource Type Property . 21
7.4.3 Resource Type definition . 21
7.4.4 Multi-value "rt" Resource . 23
7.5 Device Type . 23
7.6 OCF Interface . 24
7.6.1 Introduction . 24
7.6.2 OCF Interface Property . 24
7.6.3 OCF Interface methods . 25
7.7 Resource representation . 42
7.8 Structure . 42
7.8.1 Introduction . 42
7.8.2 Resource relationships (Links) . 42
7.8.3 Collections . 48
© ISO/IEC 2021 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 30118-1:2021(E)
7.8.4 Atomic Measurement . 50
7.9 Query Parameters . 52
7.9.1 Introduction . 52
7.9.2 Use of multiple parameters within a query . 52
7.9.3 Application to multi-value "rt" Resources . 53
7.9.4 OCF Interface specific considerations for queries . 53
8 CRUDN . 54
8.1 Overview . 54
8.2 CREATE . 54
8.2.1 Overview . 54
8.2.2 CREATE request . 55
8.2.3 Processing by the Server . 55
8.2.4 CREATE response . 55
8.3 RETRIEVE . 56
8.3.1 Overview . 56
8.3.2 RETRIEVE request . 56
8.3.3 Processing by the Server . 56
8.3.4 RETRIEVE response . 56
8.4 UPDATE . 57
8.4.1 Overview . 57
8.4.2 UPDATE request . 57
8.4.3 Processing by the Server . 57
8.4.4 UPDATE response . 58
8.5 DELETE . 58
8.5.1 Overview . 58
8.5.2 DELETE request . 59
8.5.3 Processing by the Server . 59
8.5.4 DELETE response . 59
8.6 NOTIFY . 59
8.6.1 Overview . 59
8.6.2 NOTIFICATION response . 59
9 Network and connectivity . 60
9.1 Introduction . 60
9.2 Architecture . 60
9.3 IPv6 network layer requirements . 61
9.3.1 Introduction . 61
9.3.2 IPv6 node requirements . 62
10 OCF Endpoint . 62
10.1 OCF Endpoint definition . 62
10.2 OCF Endpoint information . 63
10.2.1 Introduction . 63
10.2.2 "ep" . 63
10.2.3 "pri" . 64
10.2.4 "lat" . 64
10.2.5 OCF Endpoint information in "eps" Parameter . 64
10.3 OCF Endpoint discovery . 65
10.3.1 Introduction . 65
10.3.2 Implicit discovery . 65
iv © ISO/IEC 2021 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 30118-1:2021(E)
10.3.3 Explicit discovery with "/oic/res" response . 65
11 Functional interactions . 67
11.1 Introduction . 67
11.2 Resource discovery . 68
11.2.1 Introduction . 68
11.2.2 Resource based discovery: mechanisms . 68
11.2.3 Resource based discovery: Finding information . 69
11.2.4 Resource discovery using "/oic/res" . 76
11.2.5 Multicast discovery using "/oic/res" . 77
11.3 Notification . 78
11.3.1 Overview . 78
11.3.2 Observe . 78
11.4 Introspection . 79
11.4.1 Overview . 79
11.4.2 Usage of Introspection . 83
11.5 Semantic Tags . 84
11.5.1 Introduction . 84
11.5.2 Semantic Tag definitions . 85
12 Messaging . 87
12.1 Introduction . 87
12.2 Mapping of CRUDN to CoAP . 87
12.2.1 Overview . 87
12.2.2 URIs . 88
12.2.3 CoAP method with request and response . 88
12.2.4 Content-Format negotiation . 89
12.2.5 OCF-Content-Format-Version information . 90
12.2.6 Content-Format policy . 91
12.2.7 CRUDN to CoAP response codes. 92
12.2.8 CoAP block transfer . 92
12.2.9 Generic requirements for CoAP multicast . 92
12.2.10 Setting timeout on response to a confirmable request . 93
12.3 Mapping of CRUDN to CoAP serialization over TCP . 93
12.3.1 Overview . 93
12.3.2 URIs . 93
12.3.3 CoAP method with request and response . 93
12.3.4 Content-Format negotiation . 93
12.3.5 OCF-Content-Format-Version information . 94
12.3.6 Content-Format policy . 94
12.3.7 CRUDN to CoAP response codes. 94
12.3.8 CoAP block transfer . 94
12.3.9 Keep alive (connection health) . 94
12.3.10 CoAP using a proxy . 94
12.4 Payload Encoding in CBOR . 94
13 Security . 95
Annex A (normative) Resource Type definitions . 96
A.1 List of Resource Type definitions . 96
A.2 Atomic Measurement links list representation . 96
A.2.1 Introduction . 96
© ISO/IEC 2021 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/IEC 30118-1:2021(E)
A.2.2 Example URI . 96
A.2.3 Resource type . 96
A.2.4 OpenAPI 2.0 definition . 96
A.2.5 Property definition . 102
A.2.6 CRUDN behaviour . 103
A.3 Collection . 103
A.3.1 Introduction . 103
A.3.2 Example URI . 103
A.3.3 Resource type . 104
A.3.4 OpenAPI 2.0 definition . 104
A.3.5 Property definition . 110
A.3.6 CRUDN behaviour . 112
A.4 Device . 112
A.4.1 Introduction . 112
A.4.2 Well-known URI . 112
A.4.3 Resource type . 112
A.4.4 OpenAPI 2.0 definition . 112
A.4.5 Property definition . 115
A.4.6 CRUDN behaviour . 116
A.5 Introspection Resource . 116
A.5.1 Introduction . 116
A.5.2 Well-known URI . 116
A.5.3 Resource type . 116
A.5.4 OpenAPI 2.0 definition . 116
A.5.5 Property definition . 118
A.5.6 CRUDN behaviour . 119
A.6 Platform . 119
A.6.1 Introduction . 119
A.6.2 Well-known URI . 119
A.6.3 Resource type . 119
A.6.4 OpenAPI 2.0 definition . 119
A.6.5 Property definition . 122
A.6.6 CRUDN behaviour . 123
A.7 Discoverable Resources . 123
A.7.1 Introduction . 123
A.7.2 Well-known URI . 123
A.7.3 Resource type . 123
A.7.4 OpenAPI 2.0 definition . 123
A.7.5 Property definition . 128
A.7.6 CRUDN behaviour . 129
Annex B (informative) OpenAPI 2.0 Schema Extension . 130
B.1 OpenAPI 2.0 Schema Reference . 130
B.2 OpenAPI 2.0 Introspection empty file . 130
Annex C (normative) Semantic Tag enumeration support . 131
C.1 Introduction . 131
C.2 "tag-pos-desc" supported enumeration . 131
Bibliography . 132
vi © ISO/IEC 2021 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC 30118-1:2021(E)
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 Core 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.
This second edition cancels and replaces the first edition (ISO/IEC 30118-1:2018), which has been technically
revised.
The main changes compared to the previous edition are as follows:
— simplification of specification so that it only includes the core functionality;
— additional resusable infrastructure components are now in the core optional specification;
— addition of semantic tags, sleepy devices based on long latency;
— improvements made on CoAP bindings, Error diagnostic payloads, discovery, reset of device and usage
of baseline interfaces;
— addition of clarifications throughout.
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
---------------------- Page: 7 ----------------------
ISO/IEC 30118-1:2021(E)
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, provid
...
INTERNATIONAL ISO/IEC
STANDARD 30118-1
Second edition
Information technology — Open
Connectivity Foundation (OCF)
Specification —
Part 1:
Core specification
PROOF/ÉPREUVE
Reference number
ISO/IEC 30118-1:2021(E)
©
ISO/IEC 2021
---------------------- Page: 1 ----------------------
ISO/IEC 30118-1:2021(E)
COPYRIGHT PROTECTED DOCUMENT
© 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 PROOF/ÉPREUVE © ISO/IEC 2021 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 30118-1:2021(E)
Contents Page
Foreword . vii
Introduction . viii
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 3
3.1 Terms and definitions . 3
3.2 Symbols and abbreviated terms . 7
4 Document conventions and organization . 8
4.1 Conventions . 8
4.2 Notation . 8
4.3 Data types . 9
4.4 Resource notation syntax . 10
5 Architecture . 11
5.1 Overview . 11
5.2 Principle . 11
5.3 Functional block diagram. 12
5.4 Framework . 14
6 Identification and addressing . 14
6.1 Introduction . 14
6.2 Identification . 15
6.2.1 Device and Platform identification. 15
6.2.2 Resource identification and addressing . 15
6.3 Namespace: . 16
6.4 Network addressing . 16
7 Resource model . 17
7.1 Introduction . 17
7.2 Resource . 17
7.3 Property . 18
7.3.1 Introduction . 18
7.3.2 Common Properties . 19
7.4 Resource Type . 21
7.4.1 Introduction . 21
7.4.2 Resource Type Property . 21
7.4.3 Resource Type definition . 21
7.4.4 Multi-value "rt" Resource . 23
7.5 Device Type . 23
7.6 OCF Interface . 24
7.6.1 Introduction . 24
7.6.2 OCF Interface Property . 24
7.6.3 OCF Interface methods . 25
7.7 Resource representation . 42
7.8 Structure . 42
7.8.1 Introduction . 42
7.8.2 Resource relationships (Links) . 42
7.8.3 Collections . 48
© ISO/IEC 2021 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 30118-1:2021(E)
7.8.4 Atomic Measurement . 50
7.9 Query Parameters . 52
7.9.1 Introduction . 52
7.9.2 Use of multiple parameters within a query . 52
7.9.3 Application to multi-value "rt" Resources . 53
7.9.4 OCF Interface specific considerations for queries . 53
8 CRUDN . 54
8.1 Overview . 54
8.2 CREATE . 54
8.2.1 Overview . 54
8.2.2 CREATE request . 55
8.2.3 Processing by the Server . 55
8.2.4 CREATE response . 55
8.3 RETRIEVE . 56
8.3.1 Overview . 56
8.3.2 RETRIEVE request . 56
8.3.3 Processing by the Server . 56
8.3.4 RETRIEVE response . 56
8.4 UPDATE . 57
8.4.1 Overview . 57
8.4.2 UPDATE request . 57
8.4.3 Processing by the Server . 57
8.4.4 UPDATE response . 58
8.5 DELETE . 58
8.5.1 Overview . 58
8.5.2 DELETE request . 59
8.5.3 Processing by the Server . 59
8.5.4 DELETE response . 59
8.6 NOTIFY . 59
8.6.1 Overview . 59
8.6.2 NOTIFICATION response . 59
9 Network and connectivity . 60
9.1 Introduction . 60
9.2 Architecture . 60
9.3 IPv6 network layer requirements . 61
9.3.1 Introduction . 61
9.3.2 IPv6 node requirements . 62
10 OCF Endpoint . 62
10.1 OCF Endpoint definition . 62
10.2 OCF Endpoint information . 63
10.2.1 Introduction . 63
10.2.2 "ep" . 63
10.2.3 "pri" . 64
10.2.4 "lat" . 64
10.2.5 OCF Endpoint information in "eps" Parameter . 64
10.3 OCF Endpoint discovery . 65
10.3.1 Introduction . 65
10.3.2 Implicit discovery . 65
iv © ISO/IEC 2021 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 30118-1:2021(E)
10.3.3 Explicit discovery with "/oic/res" response . 65
11 Functional interactions . 67
11.1 Introduction . 67
11.2 Resource discovery . 68
11.2.1 Introduction . 68
11.2.2 Resource based discovery: mechanisms . 68
11.2.3 Resource based discovery: Finding information . 69
11.2.4 Resource discovery using "/oic/res" . 76
11.2.5 Multicast discovery using "/oic/res" . 77
11.3 Notification . 78
11.3.1 Overview . 78
11.3.2 Observe . 78
11.4 Introspection . 79
11.4.1 Overview . 79
11.4.2 Usage of Introspection . 83
11.5 Semantic Tags . 84
11.5.1 Introduction . 84
11.5.2 Semantic Tag definitions . 85
12 Messaging . 87
12.1 Introduction . 87
12.2 Mapping of CRUDN to CoAP . 87
12.2.1 Overview . 87
12.2.2 URIs . 88
12.2.3 CoAP method with request and response . 88
12.2.4 Content-Format negotiation . 89
12.2.5 OCF-Content-Format-Version information . 90
12.2.6 Content-Format policy . 91
12.2.7 CRUDN to CoAP response codes. 92
12.2.8 CoAP block transfer . 92
12.2.9 Generic requirements for CoAP multicast . 92
12.2.10 Setting timeout on response to a confirmable request . 93
12.3 Mapping of CRUDN to CoAP serialization over TCP . 93
12.3.1 Overview . 93
12.3.2 URIs . 93
12.3.3 CoAP method with request and response . 93
12.3.4 Content-Format negotiation . 93
12.3.5 OCF-Content-Format-Version information . 94
12.3.6 Content-Format policy . 94
12.3.7 CRUDN to CoAP response codes. 94
12.3.8 CoAP block transfer . 94
12.3.9 Keep alive (connection health) . 94
12.3.10 CoAP using a proxy . 94
12.4 Payload Encoding in CBOR . 94
13 Security . 95
Annex A (normative) Resource Type definitions . 96
A.1 List of Resource Type definitions . 96
A.2 Atomic Measurement links list representation . 96
A.2.1 Introduction . 96
© ISO/IEC 2021 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/IEC 30118-1:2021(E)
A.2.2 Example URI . 96
A.2.3 Resource type . 96
A.2.4 OpenAPI 2.0 definition . 96
A.2.5 Property definition . 102
A.2.6 CRUDN behaviour . 103
A.3 Collection . 103
A.3.1 Introduction . 103
A.3.2 Example URI . 103
A.3.3 Resource type . 104
A.3.4 OpenAPI 2.0 definition . 104
A.3.5 Property definition . 110
A.3.6 CRUDN behaviour . 112
A.4 Device . 112
A.4.1 Introduction . 112
A.4.2 Well-known URI . 112
A.4.3 Resource type . 112
A.4.4 OpenAPI 2.0 definition . 112
A.4.5 Property definition . 115
A.4.6 CRUDN behaviour . 116
A.5 Introspection Resource . 116
A.5.1 Introduction . 116
A.5.2 Well-known URI . 116
A.5.3 Resource type . 116
A.5.4 OpenAPI 2.0 definition . 116
A.5.5 Property definition . 118
A.5.6 CRUDN behaviour . 119
A.6 Platform . 119
A.6.1 Introduction . 119
A.6.2 Well-known URI . 119
A.6.3 Resource type . 119
A.6.4 OpenAPI 2.0 definition . 119
A.6.5 Property definition . 122
A.6.6 CRUDN behaviour . 123
A.7 Discoverable Resources . 123
A.7.1 Introduction . 123
A.7.2 Well-known URI . 123
A.7.3 Resource type . 123
A.7.4 OpenAPI 2.0 definition . 123
A.7.5 Property definition . 128
A.7.6 CRUDN behaviour . 129
Annex B (informative) OpenAPI 2.0 Schema Extension . 130
B.1 OpenAPI 2.0 Schema Reference . 130
B.2 OpenAPI 2.0 Introspection empty file . 130
Annex C (normative) Semantic Tag enumeration support . 131
C.1 Introduction . 131
C.2 "tag-pos-desc" supported enumeration . 131
Bibliography . 132
vi © ISO/IEC 2021 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC 30118-1:2021(E)
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 Core 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.
This second edition cancels and replaces the first edition (ISO/IEC 30118-1:2018), which has been technically
revised.
The main changes compared to the previous edition are as follows:
— renaming of smarthome to generic applicable device specification;
— addition of new device types and classification of devices;
— addition of clarifications throughout.
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
---------------------- Page: 7 ----------------------
ISO/IEC 30118-1:2021(E)
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 con
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.