Search Results for: upnp+/wp-content/uploads/2016/04/iot
Site Map
The Thread Group and Open Connectivity Foundation Create Liaison Agreement to Increase Application Connectivity and Choice in Connected Home
Collaboration will help Thread Group and Open Connectivity Foundation members easily design and build products that leverage both technologies
SAN RAMON, Calif. – July 27, 2016 – Today the Thread Group and the Open Connectivity Foundation (OCF) announced that the two alliances will work together in their mission to advance the adoption of connected home products. The Thread Group and OCF share many member companies who will benefit from this liaison agreement, and both groups are committed to driving improved cross-application interoperability and device connectivity in the connected home.
Specifications
OCF SPECIFICATION 2.2.7
Single file download with all specification files in this release (dated November 16, 2023; 44 MB).
Download the OCF 2.2.4 Specification Overview.
Individual files included in above single .zip package:
-
Core Framework
This specifies the mandatory OCF core architecture, core features, resource framework, and protocols to enable OCF implementations for the Internet of Things (IoT). The OCF architecture is based on the Resource Orientated REST architectural style. Additional functional interactions (CRUDN, Messaging, Discovery, Monitoring, and Maintenance) are specified. Other OCF specifications use the models and procedures defined in this document.
Download the OCF Core Specification. -
Core Optional Framework
This specifies optional capabilities of the OCF core architecture that may be realized by OCF implementations for the Internet of Things (IoT). This includes how scenes, rules, and alerts can be realized on an OCF Device.
Download the OCF Core Optional Specification. -
Security
The Security specification defines security objectives, philosophy, resources and mechanism that impacts OCF base layers of the OCF Core specification. The Security specification includes device identity, authentication, provisioning, establishing network credentials, authorization and access control within the OCF Resource-oriented architecture. Security topics also include confidentiality, message integrity, resource persistence protections, and securing exchanges between local and remote devices or hosts.
Download the OCF Security specification. -
Bridging
The Bridging specification specifies a framework for translation between devices in OCF and non-OCF ecosystems. It specifies general requirements for resource discovery, message translation, security, and handling of multiple bridges.
Download the OCF Bridging Specification. -
Resource Type
The Resource Type specification specifies a base resource schema for all OCF resources and a set of resources that are built on this base schema that may be exposed by OCF Devices. The Resource specification uses OpenAPI 2.0 as a specification language for the APIs exposed by the resources and the payload definitions for the resource representations. These resources enable modeling of key Use Cases including: Device Control, Notification, Environment Sensing and Control, Energy Management, and Energy Saving.
Download the OCF Resource Type Specification. -
Device
The Device specification defines how a Device is represented in OCF, and a list of known OCF device types. For the Device Types defined, the document specifies which resources are mandatory to be implemented, noting that all OCF defined resources may optionally be exposed by an OCF Device.
Download the OCF Device Specification. -
Easy Setup
This specification defines functional extensions to the capabilities defined in the OCF Core Specification to meet the requirements Easy Setup of either Wi-Fi on an OCF Device, or eSIM connectivity on an OCF Device. This specification specifies new Resource Types to enable the functionality and any extensions to the existing capabilities defined in the OCF Core Specification.
Download the OCF Easy Setup Specification. -
Device to Cloud Services
This specification defines functional extensions to the capabilities defined in the OCF Core Specification to meet the requirements of a Device connected to an OCF Cloud. This specification specifies new Resource Types to enable the functionality and any extensions to the existing capabilities defined in the OCF Core Specification.
Download the OCF Device to Cloud Services Specification. -
Resource to AllJoyn Interface Mapping
The OCF Resource to AllJoyn Interface Mapping specification provides detailed mapping information to provide equivalency between AllJoyn defined Interfaces and OCF defined Resources. The specification provides mapping for Device Types (AllJoyn to/from OCF), identifies equivalent OCF Resources for both mandatory and optional AllJoyn interfaces and for each interface defines the detailed Property by Property mapping using OCF defined extensions to JSON schema to programmatically define mappings.
Download the OCF Resource to AllJoyn Interface Mapping Specification. -
Resource to BLE Mapping
This document provides detailed mapping information between BLE (Bluetooth Low Energy) and OCF defined Resources.
Download the OCF Resource to BLE Mapping Specification. -
Resource to LWM2M Mapping
The OCF Resource to LWM2M Mapping specification provides detailed mapping information to provide equivalency between LWM2M defined Objects and OCF defined Resources. A LWM2M Bridge is an Asymmetric Client Bridge, therefore this document identifies equivalent OCF Resources for specific LWM2M Objects, and defines the detailed Property by Property mapping using OCF defined extensions to JSON schema to programmatically define the mappings.
Download the OCF Resource to LWM2M Mapping specification.
-
Resource to Matter Cluster Mapping
The OCF Resource to Matter Cluster Mapping specification provides detailed mapping information to provide equivalency between Matter defined Objects and OCF defined Resources. The overall goal is to represent Bridged Matter Servers to OCF Clients as if they were native OCF Servers in the local network or cloud environment.
Download the OCF Resource to Matter Cluster Mapping specification.
-
Resource Type OMA Optional
This document specifies optional OMA resource types that can be used in an OCF Device.
Download the OCF Resource Type OMA Optional Specification. -
Resource to OneM2M Module Class Mapping
The OCF Resource to OneM2M Module Class Mapping specification provides detailed mapping information to provide equivalency between oneM2M defined Module Classes and OCF defined Resources. A oneM2M Bridge is Asymmetric Client Bridge, therefore this document provides unidirectional mapping for Device Types, identifies equivalent OCF Resources for specific oneM2M Module Classes, and defines the detailed Property by Property mapping using OCF defined extensions to JSON schema to programmatically define the mappings.
Download the OCF Resource to OneM2M Module Class Mapping Specification. -
Resource to UPlus Mapping
This document provides detailed mapping information between UPlus (U+) and OCF defined Resources.
Download the OCF Resource to UPlus Mapping Specification. -
Resource to Zigbee Cluster Mapping
This document provides detailed mapping information between Zigbee defined Clusters and OCF defined Resources.
Download the OCF Resource to Zigbee Cluster Mapping Specification -
Resource to Z-Wave Mapping
This document provides detailed mapping information between Z-Wave and OCF defined Resources.
Download the OCF Resource to Z-Wave Mapping Specification -
Resource to EnOcean Mapping
This document provides detailed mapping information between EnOcean and OCF defined Resources.
Download the OCF Resource to Z-Wave Mapping Specification -
Onboarding Tool
Download the OCF Onboarding Tool Specification
-
Cloud Security
Download the OCF Cloud Security Specification
-
OCF Cloud API for Cloud Services
The OCF Cloud API for Cloud Services provides well-defined APIs exist for device information retrieval (and update) and event subscription between two OCF Cloud instances. The APIs are designed to be agnostic of the data models; hence all existing and future data models published by OCF can be used. The data models describe payloads for the RESTful verbs and when originating from outside of a cloud (for example, when retrieving an end device's information), are passed through unaltered.
Download the OCF Cloud API for Cloud Services Specification.
Reference Documents
-
OCF Certificate Policy
This Certificate Policy comprises the policy framework for the PKI and is consistent with the Internet X.509 PKI Certificate Policy and Certification Practices Framework [RFC 3647]. It governs the operations of the PKI components by all individuals and entities within the PKI (collectively, “PKI Participants”). It provides the minimum requirements that PKI Participants are required to meet when issuing and managing Certification Authorities (CAs), digital certificates, and private keys. In addition, it informs potential Relying Parties about what they need to know prior to relying on issued certificates.
Download the OCF Certificate Policy.
Draft specifications
Specifications in IPR review may be found on the Draft Specifications page here.
Specification Archive
OCF 2.2.6
OCF 2.2.6 Specifications - single file download (English) (20 MB)
OCF 2.2.5
OCF 2.2.5 Specifications - single file download (English) (20 MB)
OCF 2.2.4
OCF 2.2.4 Specifications - single file download (English) (30 MB)
OCF 2.2.3
OCF 2.2.3 Specifications - single file download (English) (20 MB)
OCF 2.2.2
OCF 2.2.2 Specifications - single file download (English) (18 MB)
Download the OCF 2.2.2 Specification Overview presentation here.
OCF 2.2.1
OCF 2.2.1 Specifications - single file download (English) (18 MB)
OCF 2.2.0
OCF 2.2.0 Specifications - single file download (English) (17.5 MB)
OCF 2.1.1
OCF 2.1.1 Specification Introduction and Overview deck
OCF 2.1.1 Specifications - single file download (English) (14.5 MB)
OCF Core Specification (2.1.1)
OCF Core Optional Specification (2.1.1)
OCF Security Specification (2.1.1)
OCF Resource Type Specification (2.1.1)
OCF Device Specification (2.1.1)
OCF Bridging Specification (2.1.1)
OCF Wi-Fi Easy Setup Specification (Core Specification Extension) (2.1.1)
OCF Device to Cloud Services Specification (2.1.1)
OCF Resource to AllJoyn Interface Mapping Specification (2.1.1)
OCF Resource to BLE Mapping Specification (2.1.1)
OCF Resource to OneM2M Module Class Mapping Specification (2.1.1)
OCF Resource to Zigbee Cluster Mapping Specification (2.1.1)
OCF Resource to Z-Wave Mapping Specification (2.1.1)
OCF Onboarding Tool Specification (2.1.1)
OCF Cloud Security Specification (2.1.1)
OCF 2.1.0
OCF 2.1.0 Specification Introduction and Overview deck
OCF 2.1.0 Specifications - single file download (English) (14.5 MB).
OCF Core Specification (2.1.0, English, Simplified Chinese)
OCF Core Optional Specification (2.1.0)
OCF Security Specification (2.1.0)
OCF Resource Type Specification (2.1.0)
OCF Device Specification (2.1.0)
OCF Bridging Specification (2.1.0)
OCF Wi-Fi Easy Setup Specification (Core Specification Extension) (2.1.0)
OCF Device to Cloud Services Specification (2.1.0)
OCF Resource to AllJoyn Interface Mapping Specification (2.1.0)
OCF Resource to BLE Mapping Specification (2.1.0)
OCF Resource to OneM2M Module Class Mapping Specification (2.1.0)
OCF Resource to Zigbee Cluster Mapping Specification (2.1.0)
OCF Resource to Z-Wave Mapping Specification (2.1.0)
OCF Onboarding Tool Specification (2.1.0)
OCF Cloud Security Specification (2.1.0)
OCF 2.0.5
OCF 2.0.5 Specification Introduction and Overview deck
OCF 2.0.5 Specifications - single file download (English) (12.8 MB).
OCF Core Specification (2.0.5)
OCF Core Optional Specification (2.0.5)
OCF Security Specification (2.0.5)
OCF Resource Type Specification (2.0.5)
OCF Device Specification (2.0.5)
OCF Bridging Specification (2.0.5)
OCF Wi-Fi Easy Setup Specification (Core Specification Extension) (2.0.5)
OCF Device to Cloud Services Specification (2.0.5)
OCF Resource to AllJoyn Interface Mapping Specification (2.0.5)
OCF Resource to OneM2M Module Class Mapping Specification (2.0.5)
OCF Resource to Zigbee Cluster Mapping Specification (2.0.5)
OCF Onboarding Tool Specification (2.0.5)
OCF Cloud Security Specification (2.0.5)
OCF 2.0.4
OCF 2.0.4 Specification Introduction and Overview deck
OCF 2.0.4 Specifications - single file download (English) (10.6 MB).
OCF Core Specification (2.0.4)
OCF Security Specification (2.0.4)
OCF Resource Type Specification (2.0.4)
OCF Device Specification (2.0.4)
OCF Bridging Specification (2.0.4)
OCF Wi-Fi Easy Setup Specification (Core Specification Extension) (2.0.4)
OCF Cloud Specification (Core Specification Extension) (2.0.4)
OCF Resource to AllJoyn Interface Mapping Specification (2.0.4)
OCF Resource to OneM2M Module Class Mapping Specification (2.0.4)
OCF 2.0.3
OCF 2.0.3 Specification Introduction and Overview deck
OCF 2.0.3 Specifications - single file download (English) (10.6 MB).
OCF Core Specification (2.0.3)
OCF Security Specification (2.0.3)
OCF Resource Type Specification (2.0.3)
OCF Device Specification (2.0.3)
OCF Wi-Fi Easy Setup Specification (Core Specification Extension) (2.0.3)
OCF Cloud Specification (Core Specification Extension) (2.0.3)
OCF Resource to AllJoyn Interface Mapping Specification (2.0.3)
OCF Resource to OneM2M Module Class Mapping Specification (2.0.3)
OCF 2.0.2
OCF 2.0.2 Specification Introduction and Overview deck
OCF 2.0.2 Specifications - single file download (English) (10.6 MB).
OCF Core Specification (2.0.2)
OCF Security Specification (2.0.2)
OCF Resource Type Specification (2.0.2)
OCF Device Specification (2.0.2)
OCF Wi-Fi Easy Setup Specification (Core Specification Extension) (2.0.2)
OCF Cloud Specification (Core Specification Extension) (2.0.2)
OCF Resource to AllJoyn Interface Mapping Specification (2.0.2)
OCF Resource to OneM2M Module Class Mapping Specification (2.0.2)
OCF 2.0.1
OCF 2.0.1 Specification Introduction and Overview deck
OCF 2.0.1 Specifications - single file download (English) (10.6 MB).
OCF Core Specification (2.0.1)
OCF Security Specification (2.0.1)
OCF Resource Type Specification (2.0.1)
OCF Device Specification (2.0.1)
OCF Wi-Fi Easy Setup Specification (Core Specification Extension) (2.0.1)
OCF Cloud Specification (Core Specification Extension) (2.0.1)
OCF 2.0
OCF 2.0 Specification Introduction and Overview Presentation
OCF 2.0 Specifications - single file download (English) (15 MB).
OCF Core Specification (2.0)
OCF Security Specification (2.0)
OCF Resource Type Specification (2.0)
OCF Device Specification (2.0)
OCF Wi-Fi Easy Setup Specification (Core Specification Extension) (2.0)
OCF Cloud Specification (Core Specification Extension) (2.0)
OCF 1.3
OCF 1.3 Specification Introduction and Overview Presentation
OCF 1.3 Specifications - single file download (English, Korean) (15 MB).
OCF Core Specification (1.3), (1.3.1)
OCF Security Specification (1.3), (1.3.1)
OCF Bridging Specification (1.3)
OCF Resource Type Specification (1.3.1)
OCF Device Specification (1.3)
OCF Wi-Fi Easy Setup Specification (Core Specification Extension) (1.3), (1.3.1)
OCF 1.0
Read the OCF 1.0 Specification Introduction and Overview (English, Japanese) for more background.
OCF 1.0 Specifications (English, Korean) (dated June 28, 2017; 13.5 MB).
OIC 1.1
OIC Core Specifications ( 1.1.2, 1.1.1, 1.1.0)
OIC Security Specifications ( 1.1.1, 1.1.0)
Certification
Please visit the members-only website for more plugfest event details and access to the certification-related documents.
IoTivity Open Source Code
Visit the IoTivity web page for the open source code: https://www.iotivity.org/
Exclusions
None.
Supplemental Spec Resources
Published Specification Legal Disclaimer
Copyright © 2016-2019 Open Connectivity Foundation, Inc. All rights reserved.
The OCF logo is a trademark and/or service mark of Open Connectivity Foundation, Inc. in the United States or other countries. Other names and brands may be claimed as the property of others.
USE OF THE INFORMATION CONTAINED HEREIN SHALL BE GOVERNED SOLELY BY THE TERMS AND CONDITIONS OF THE OPEN CONNECTIVITY FOUNDATION, INC. INTELLECTUAL PROPERTY RIGHTS POLICY. THE DOCUMENT AND INFORMATION CONTAINED HEREIN IS NOT, IN ITSELF, A LICENSE, EITHER EXPRESSLY OR IMPLIEDLY, TO ANY INTELLECTUAL PROPERTY OWNED OR CONTROLLED BY ANY MEMBER OF THE OPEN CONNECTIVITY FOUNDATION, INC. OR OF ANY OTHER AUTHORS OR DEVELOPERS OF THIS SPECIFICATION OR OTHER DOCUMENT. THE INFORMATION CONTAINED HEREIN IS PROVIDED ON AN "AS IS" BASIS, AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE OPEN CONNECTIVITY FOUNDATION, INC., AS WELL AS THE AUTHORS AND DEVELOPERS OF THIS SPECIFICATION OR OTHER DOCUMENT HEREBY DISCLAIM ALL OTHER WARRANTIES AND CONDITIONS, EITHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES, DUTIES OR CONDITIONS OF MERCHANTABILITY, OF FITNESS FOR A PARTICULAR PURPOSE, OF ACCURACY OR COMPLETENESS, OF RESULTS, OF WORKMANLIKE EFFORT, OF LACK OF VIRUSES, OF LACK OF NEGLIGENCE OR NON-INFRINGEMENT.
Necessary IP Declarations – UDA 2.0
Capitalized terms are defined in the UPnP Forum Membership Agreement.
Pursuant to the requirements of section 3.8(a) and 3.8(f) of the UPnP Forum Membership Agreement, the following Members have made the indicated declarations related to Necessary IP that is not the Member’s Member Input that is incorporated in the above named Approved DCP Framework and their willingness to license such Necessary IP.
By providing this information, the UPnP Forum makes no representation regarding the accuracy or validity of this information nor its relevance to the UPnP Forum, DCPs, Proposed or Approved DCP Frameworks, test configuration files, Reference Implementations, Reference Implementation test logs, or to UPnP Compliant Devices. Consistent with Section 3.6(a)(D) of the UPnP Forum Membership Agreement, no Member, including Steering Committee representatives and working committee chairs, has undertaken on behalf of the UPnP Forum or its Members, any patent search with respect to the Proposed or Approved DCP Frameworks, Proposed DCPs, Standardized DCPs, Reference Implementations and associated test configuration files.
Members that now discover they have or acquire Necessary IP that is included in this Approved DCP Framework have a disclosure obligation under Section 3.8(f) and must submit its Declaration through the forms linked below.
UPnP Patent Disclosure Guidelines
Questions or concerns regarding the disclosure processes and guidelines may be referred to the Legal Inquiry Taskforce using this online form.
Declarations
Member: Cisco Systems
Proposed DCP or DCP Framework: UPnP Device Architecture Annex C Cloud
Signatory Name: Wouter van der Beek
Title: mr
Address 1: Four Stoney Croft Rise
Address 2:
City: Chandlers Ford
State: Hampshire
Country: United Kingdom
Postal Code: 0
Email: [email protected]
Date and Time stamp: 5/22/2014 01:46 AM
Patent License Option: (ii) RAND terms and conditions
Member: Intel Corporation
Proposed DCP or DCP Framework: UPnP Device Architecture 2.0
Signatory Name: Scott Lofgren
Title: systems Engineer
Address 1: 1900 Prairie City Raod
Address 2:
City: Folsom
State: California
Country: USA
Postal Code: 95630
Email: [email protected]
Date and Time stamp: 6/19/2014 09:53 AM
Patent License Option: (ii) RAND terms and conditions
Member: Intel Corporation
Proposed DCP or DCP Framework: UPnP Device Architecture Annex C Cloud
Signatory Name: Scott Lofgren
Title: Systems Eng.
Address 1: 1900 prairie city road
Address 2:
City: Folsom
State: California
Country: USA
Postal Code: 95630
Email: [email protected]
Date and Time stamp: 6/4/2014 01:43 AM
Patent License Option: (ii) RAND terms and conditions
Contributors
The UPnP Forum in no way guarantees the accuracy or completeness of this contributor list and in no way implies any rights for or support from those members listed. Members contributing to this DCP Framework, but not included in the list below should notify the Forum Administrator.
AllegroSoft
Cable Labs Inc
Canon
Cisco Systems
Clayster
Comarch
Conexant
Epson
GoPro (Woodman Labs Inc.)
HP
Intel
Microsoft
Nokia
Philips
Siemens
Sony
TP Vision
Necessary IP Declarations
Pursuant to the requirements of section 3.8(a) and 3.8(f) of the former UPnP Forum Membership Agreement, former Members made declarations related to Necessary IP that is not the Member's Member Input that is incorporated in the below listed Standardized DCP or Approved DCP Framework and their willingness to license such Necessary IP. Declarations for each Standardized DCP or Approved DCP Framework can be viewed by clicking the corresponding links below.
By providing this information, the former UPnP Forum makes no representation regarding the accuracy or validity of this information nor its relevance to UPnP Forum, DCPs, Proposed or Approved DCP Frameworks, test configuration files, Reference Implementations, Reference Implementation test logs, or to UPnP Compliant Devices. Consistent with Section 3.6(a)(D) of the former UPnP Forum Membership Agreement, no former Member, including Steering Committee representatives and working committee chairs, has undertaken on behalf of the UPnP Forum or its Members, any patent search with respect to the Proposed or Approved DCP Frameworks, Proposed DCPs, Standardized DCPs, Reference Implementations and associated test configuration files.
Standardized DCP | Publication Date |
---|---|
CloudProxy:1 | 2015 |
ContentDirectory:4 Service Revision Dated 30 June 2015 | 2015 |
IoT Management and Control DataModel:1 Dated May 15 (previously named SensorDataModel:1) |
2015 |
IoT Management and Control DataModel:1 Dated Feb 1 (previously named SensorDataModel:1) |
2015 |
IoT Management and Control DataModel:1 Dated Nov 1 (previously named SensorDataModel:1) |
2014 |
MultiScreen:1 | 2014 |
MultiScreen:2 | 2014 |
FriendlyInfoUpdate:1 | 2014 |
MediaServer:4 and MediaRenderer:3 (Rev. 31 March 2013) | 2013 |
IoT Management and Control: 1 (previously named SensorManagement:1) |
2013 |
DataStore:1 | 2013 |
EnergyManagement:1 | 2013 |
Telephony:2 | 2012 |
DeviceManagement:2 | 2012 |
RemoteAccess:2 | 2011 |
MediaServer:4 and MediaRenderer:3 | 2011 |
Telephony:1 | 2011 |
DeviceProtection:1 | 2011 |
IGD:2 | 2010 |
DeviceManagement:1 | 2010 |
RemoteAccess:1 | 2009 |
ContentSync:1 | 2009 |
SolarProtectionBlind:1 | 2008 |
MediaServer:3 | 2008 |
MediaRenderer:2 | 2008 |
QoS:3 Services | 2008 |
LowPowerDevice:1/LowPowerProxy:1 | 2007 |
Approved DCP Framework | Publication Date |
---|---|
UDA 2.0 | 2014 |
UDA 1.1 Annex A | 2011 |
UDA 1.1 | 2008 |
UDA 1.0 | 2008 |
UDA 1.0 | 2006 |
Inquiries
Questions or concerns regarding the disclosure processes and guidelines may be referred to [email protected]