ISO/IEC 30118-9:2021 PDF

Information technology – Open Connectivity Foundation (OCF) Specification — Part 9: Core optional specification

Первая страница стандарта ISO/IEC 30118-9:2021

Открыть превью (PDF)

Название (английский):

ISO/IEC 30118-9:2021

Information technology – Open Connectivity Foundation (OCF) Specification — Part 9: Core optional specification

Статус документа:: Действующий
Формат:: Электронный (PDF)
Количество страниц:: 100
Дата публикации:: 18 октября 2021 г.
Издание:: ISO/IEC IS 30118 edition 1 version 1
ICS:: 35.200

Язык документа:

ruen

Срок поставки:17 раб. дн. (перевод)

Цена:1 500 €

Описание (английский):

The OCF Core specifications are divided into a series of documents: Core specification: 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 (this document): 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).

Технические детали

Технический комитет: ISO/IEC JTC 1 - Information technology
SKU: ISO/IEC 30118-9:2021

Abstract

Overview

ISO/IEC 30118-9:2021 - "Information technology - Open Connectivity Foundation (OCF) Specification - Part 9: Core optional specification" defines optional OCF core architecture components that devices may implement to provide richer Internet of Things (IoT) behavior. Published as part of the ISO/IEC 30118 series, this document complements the mandatory Core Specification (Part 1) and the Security Specification (Part 2) by specifying optional resource types, interfaces, protocols and services for enhanced interoperability in smart home and commercial IoT ecosystems.

Key topics and technical requirements

OCF framework and interfaces: describes optional core capabilities that fit within the OCF core architecture and can be implemented by any Device.
Resource types and RESTful model: defines optional Resource Types (detailed in Annex A) and uses RESTful CRUDN operations (CREATE, RETRIEVE, UPDATE, DELETE, NOTIFY) and JSON-derived data types for payloads and interaction.
Functional interactions: covers onboarding, provisioning and configuration; device management; scenes and scene collections; rules (condition-action logic); icons; alerts; and maintenance.
Rule engine elements: defines Rule, Rule Input, Rule Expression, Rule Action and Rule Result semantics for autonomous device decision logic.
Scene and alert models: standardized Scene, Scene Member and Scene Collection structures for grouping device states; Alert and Alert Collection types for reporting issues.
Normative behavior classification: features are classified as Required, Recommended, Allowed, Deprecated, Conditionally Allowed/Required - implementations must follow the specified semantics for compliance.
References and interoperability: normative cross-references to ISO/IEC 30118-1/-2, relevant IETF RFCs (e.g., RFC 3339 timestamps), OpenAPI and IANA registries ensure consistent API and metadata treatment.

Practical applications and who uses it

Device manufacturers add optional capabilities (scenes, autonomous rules, alerts, software update metadata) to increase product value and interoperability across OCF ecosystems.
Platform vendors and gateway developers implement optional resource types to support richer automation, local control and management features.
IoT solution architects and integrators use the specification to design systems that require standardized scene management, rules engines, or device maintenance reporting.
Test labs and certification bodies apply the document to validate optional OCF features in conformance testing.

Related standards (select)

ISO/IEC 30118-1: Core specification (mandatory)
ISO/IEC 30118-2: Security specification
Relevant IETF RFCs cited for timestamps, ABNF and syslog (e.g., RFC 3339)

By implementing ISO/IEC 30118-9:2021 optional features, organizations can accelerate secure, interoperable IoT deployments-improving automation, remote/local management and cross-vendor compatibility for smart home and commercial IoT solutions.

Overview

Key topics and technical requirements

OCF framework and interfaces: describes optional core capabilities that fit within the OCF core architecture and can be implemented by any Device.
Resource types and RESTful model: defines optional Resource Types (detailed in Annex A) and uses RESTful CRUDN operations (CREATE, RETRIEVE, UPDATE, DELETE, NOTIFY) and JSON-derived data types for payloads and interaction.
Functional interactions: covers onboarding, provisioning and configuration; device management; scenes and scene collections; rules (condition-action logic); icons; alerts; and maintenance.
Rule engine elements: defines Rule, Rule Input, Rule Expression, Rule Action and Rule Result semantics for autonomous device decision logic.
Scene and alert models: standardized Scene, Scene Member and Scene Collection structures for grouping device states; Alert and Alert Collection types for reporting issues.
Normative behavior classification: features are classified as Required, Recommended, Allowed, Deprecated, Conditionally Allowed/Required - implementations must follow the specified semantics for compliance.
References and interoperability: normative cross-references to ISO/IEC 30118-1/-2, relevant IETF RFCs (e.g., RFC 3339 timestamps), OpenAPI and IANA registries ensure consistent API and metadata treatment.

Practical applications and who uses it

Device manufacturers add optional capabilities (scenes, autonomous rules, alerts, software update metadata) to increase product value and interoperability across OCF ecosystems.
Platform vendors and gateway developers implement optional resource types to support richer automation, local control and management features.
IoT solution architects and integrators use the specification to design systems that require standardized scene management, rules engines, or device maintenance reporting.
Test labs and certification bodies apply the document to validate optional OCF features in conformance testing.

Related standards (select)

ISO/IEC 30118-1: Core specification (mandatory)
ISO/IEC 30118-2: Security specification
Relevant IETF RFCs cited for timestamps, ABNF and syslog (e.g., RFC 3339)

ISO/IEC 30118-9:2021 PDF

Технические детали

Abstract

Overview

Key topics and technical requirements

Practical applications and who uses it

Related standards (select)

Похожие стандарты

Abstract

Overview

Key topics and technical requirements

Practical applications and who uses it

Related standards (select)

Похожие стандарты

Information technology. Open Connectivity Foundation (OCF) Specification - Core specification

Information technology — Open Connectivity Foundation (OCF) Specification — Part 2: Security specification

Systems and software engineering — Software life cycle processes

Asset management — Vocabulary, overview and principles

Asset management — Asset management system — Requirements

Information technology — Radio frequency identification device conformance test methods — Part 2: Test method…

Information technology — Multimedia framework (MPEG-21) — Part 22: User Description

Milk — Determination of the lactoperoxidase activity — Photometric method (Reference method)