Overview
ISO/IEC 30118-6:2021 defines the formal mapping between Open Connectivity Foundation (OCF) Resources and AllJoyn Interfaces to enable interoperable translation between two major IoT frameworks. The standard specifies device-type mappings (AllJoyn ↔ OCF), identifies equivalent OCF resources for mandatory and optional AllJoyn interfaces, and provides property-by-property mapping using OCF extensions to JSON Schema so implementations can programmatically translate payloads.
Key topics and technical requirements
- Resource ↔ Interface equivalency: Detailed correspondence between OCF resource types and AllJoyn interfaces, including device type conversions.
- Property-level mapping: Per-property definitions, type conversions and derived-model definitions expressed using OCF JSON Schema extensions.
- Mapping syntax and conventions: Rules for naming, value assignment, arrays, default/conditional mapping, loops, and method invocation to support deterministic translation.
- AllJoyn bridging requirements: Operational scenarios and requirements for a bridging function (use of introspection, stability/loss handling, exposing AllJoyn producers to OCF clients and vice versa).
- On-the-fly translation: Methods for translating between d‑bus (AllJoyn) payloads and OCF payloads with and without introspection.
- Security and CRUDN behavior: Considerations for secure mapping and the Create/Read/Update/Delete/Notify semantics for resource types.
- API and resource definitions: OpenAPI 2.0 definitions, example URIs, and detailed resource type definitions (e.g., AllJoynObject, SecureMode) to support implementation and testing.
Practical applications
ISO/IEC 30118-6 is targeted at professionals implementing IoT interoperability layers:
- Gateway and bridge developers needing programmatic mappings to translate between OCF clients and AllJoyn devices.
- IoT platform integrators who must unify device ecosystems that use different frameworks.
- Device manufacturers who want their devices accessible across OCF and AllJoyn-enabled systems without redesign.
- Test labs and QA teams validating semantic equivalence and protocol translation correctness.
- Standards and product architects designing interoperable consumer and industrial IoT solutions.
Benefits include reduced integration cost, consistent semantics across frameworks, automated translation using JSON Schema, and clearer security and behavior expectations for bridging components.
Related standards and keywords
- Related: other parts of the ISO/IEC 30118 series, OCF Specifications, AllJoyn (AllSeen Alliance) documentation, OpenAPI, JSON Schema, and d‑bus.
- SEO keywords: ISO/IEC 30118-6, OCF to AllJoyn mapping, IoT interoperability, resource to interface mapping, JSON Schema mapping, AllJoyn bridge, device type mapping, OpenAPI 2.0, d-bus translation.
Open preview (PDF)Information technology — Open Connectivity Foundation (OCF) Specification — Part 6: Resource to AllJoyn interface mapping specification
