SEOUL, KOREA (Sep 19, 2018) — HDC and OCF signed a memorandum of understanding in support of joint marketing, and applying OCF standards to apartment houses, on Sep 19th at Yongsan headquarters, in Seoul, Korea.
Search Results for: upnp+/wp-content/uploads/2016/03/OCF-UPnP-Certification-Testing-and-Licensing-Application.pdf/page/26/member-announcements/hyundai-development-company-hdc-and-open-connectivity-foundation-ocf-signed-mou-to-apply-ocf-on-hdc-apartment-houses-for-the-first-in-the-world
Hyundai Development Company (HDC) and Open Connectivity Foundation (OCF) signed MOU to apply OCF on HDC Apartment Houses for the first in the World
UPnP Certification
How To Certify A UPnP Device
- Gain UPnP Certification rights by doing one of the following:
- Become an OCF Member, and pay the applicable annual membership fee (e.g. $2,000 USD for Gold Membership), and sign the UPnP Certification Testing and Licensing Agreement.
- Become a Non-Member Licensee by signing the UPnP Certification Testing and Licensing Agreement, Application Form, and paying the $5,000 USD annual fee.
- Access the certification test tool via the UPnP Certification Site.
- Run the test tool at your own facility or at a 3rd party test house.
- Submit the test logs, along with Web-based device registration form, to the Test Reviewer.
Note: Your company must submit a device registration form for each device. Visit the UPnP Certification Site for additional information. - Once you have submitted the test logs and device registration forms, the Test Reviewer reviews the test logs and contacts you with testing results.
Note: The review may require up to five (5) working days; however, two working days is our goal. - If the device passes, your company receives a certificate of conformity for that particular device. The certificate authorizes your company to use the certification mark on the certified device and in associated marketing material, according to the Implementer Membership Addendum and the Logo Usage Guidelines document and FAQ, which are accessible via the UPnP Certification Site.
If the device fails, your company is notified of the failure and reason, no certificate is issued, and your company may not market the device as UPnP-certified. Your company is welcome to alter the device and retest.
UPnP Certification FAQs
If you are associated with an OCF member company, or a Non-Member Licensee, and would like further information about the UPnP certification process, you can register for an account on the UPnP Certification Management System and read more about the process by clicking on “UPnP.”
UPnP General Compliance FAQ's
UPnP+ Certification
Read about the UPnP+ initiative here. Note that the UPnP+ certification process follows the same certification process as standard UPnP products.
The goal of UPnP+-certified products is to certify a more reliable, secure, and diverse family of products. Benefits included in UPnP+ certification include:
- Interoperability
- Security
- Evolving standards (e.g., HTML5, IPv6)
- Cloud-based features
- New services
In support of this effort, OCF has updated the UPnP Certification Test Tool (UCTT) for enhanced testing and expanded its testing program to improve the quality of open source implementations.
The following are the requirements for UPnP+ certification compared to UPnP certification for all UPnP certified devices.
Specification |
UPnP Certification |
UPnP+ Certification |
UDA |
|
|
IPv6 Annex |
|
|
UDA Cloud Annex |
|
|
The following are the requirements for UPnP+ certification compared to UPnP certification for floating services. These services can be added to other device types.
Service |
UPnP Certification |
UPnP+ Certification |
DeviceProtection |
|
|
FriendlyInfoUpdate |
|
|
EnergyManagement |
|
|
BasicManagementService |
|
|
ConfigurationManagementService |
|
|
SoftwareManagementService |
|
|
QOS |
|
|
QOS |
|
|
UPnP Pre-certification
The UPnP Test Vendors (UTVs) are OCF members and provide pre-certification testing services on behalf of Members looking to obtain UPnP® certification. See above for the UPnP certification process.
Notes for UPnP Licensees:
-
-
- Although UTVs can perform testing on your behalf, it is your responsibility to submit passing test logs and the product details using the online Device Registration form to achieve UPnP® Certification.
- Test results generated by UTVs may be shared with OCF and will be treated confidentially.
-
UPnP Test Vendors
Vendor name | Contact information |
---|---|
Allion Labs, Inc | http://www.allion.com/ [email protected] Tel: +886-2-2655-7877 |
CESI Technology Co., Ltd | http://www.adtc.org.cn [email protected] [email protected] [email protected] Tel: +86-10-67831802 ext 30 |
If you are a UTV and not listed above but would like to request to be added, please contact the OCF UPnP Certification Administrator at [email protected]. OCF membership is required.
Pre-Certification UPnP Cloud Interoperability Testing
The below listed UPnP Test Vendors provide pre-certification testing services specifically for the Cloud on behalf of Members looking to obtain UPnP® or UPnP+® Certification. The process for certifying devices can be found here.
Notes for UPnP Licensees:
- Although these UPnP Test Vendors can perform testing on your behalf, it is your responsibility to submit passing test logs and the product details using the online Device Registration form to achieve UPnP® or UPnP+® Certification.
- Test results generated by UPnP Test Vendors may be shared with OCF and will be treated confidentially.
Independent Cloud Interoperability Service Vendors:
Vendor name | Contact information |
---|---|
ConnectingYourThings (CYT) | http://www.cytiot.com/ [email protected]: +1 650-466-7011 |
Comarch Technologies | http://technologies.comarch.com
Email: [email protected] |
If you are a Cloud Interoperability Service Vendor and not listed above but would like to request to be added, please contact the OCF UPnP Certification Administrator at [email protected]. As noted above, OCF membership is required.
Disclaimer of Non-endorsement: This page contains links to other sites which the Open Connectivity Foundation (OCF) provides for informational and convenience purposes only. OCF does not control or monitor these sites, nor does their inclusion mean that OCF recommends or endorses these sites, the organizations or companies that run the sites or anything contained within the sites. OCF in no manner endorses, sponsors, recommends, certifies or approves these Independent Certification Vendors and/or their products or offerings.
Have a question that
wasn’t addressed above?
UPnP Standards & Architecture
About UPnP
Effective January 1, 2016, UPnP Forum assigned their assets to the Open Connectivity Foundation (OCF). UPnP Forum was originally formed in October 1999 as an industry initiative who gained more than 1000 leading companies in computing, printing and networking; consumer electronics; home appliances, automation, control and security; and mobile products.
UPnP technology allows devices to connect seamlessly and to simplify network implementation in the home and corporate environments. Toward this end, UPnP Forum members worked together to define and publish UPnP device control protocols built upon open, Internet-based communication standards.
The UPnP architecture offers pervasive peer-to-peer network connectivity of PCs of all form factors, intelligent appliances, and wireless devices. The UPnP architecture is a distributed, open networking architecture that leverages TCP/IP and the Web to enable seamless proximity networking in addition to control and data transfer among networked devices in the home, office, and everywhere in between.
Broad in Scope
UPnP technology targets home networks, proximity networks and networks in small businesses and commercial buildings. It enables data communication between any two devices under the command of any control device on the network. UPnP technology is independent of any particular operating system, programming language, or network technology.
Zero Configuration and Automatic Discovery
The UPnP architecture supports zero-configuration and automatic discovery whereby a device can:
- Dynamically join a network
- Obtain an IP address
- Announce its name
- Convey its capabilities upon request
- Learn about the presence and capabilities of other devices
- Leave a network smoothly and automatically without leaving any unwanted state information behind
DHCP and DNS servers are optional and are used only if they are available on the network.
Technology Benefits
- Media and device independence. UPnP technology can run on any network technology including Wi-Fi, coax, phone line, power line, Ethernet and 1394.
- Platform independence. Vendors can use any operating system and any programming language to build UPnP products.
- Internet-based technologies. UPnP technology is built upon IP, TCP, UDP, HTTP, and XML, among others.
- UI Control. UPnP architecture enables vendor control over device user interface and interaction using the browser.
- Programmatic control. UPnP architecture enables conventional application programmatic control.
- Common base protocols. Vendors agree on base protocol sets on a per-device basis.
- Extendable. Each UPnP product can have value-added services layered on top of the basic device architecture by the individual manufacturers.
Standardized Device Control Protocols
Like the creation of Internet standards, the UPnP initiative involves a multi-vendor collaboration for establishing standard Device Control Protocols (DCPs). Similar to Internet-based communication, these are based on protocols that are:
Declarative
Expressed in XML
Communicated via HTTP
See below for more information on UPnP technology.
Download all of the UPnP specifications here.
Interested in Certifying Devices?
Visit here for more information on how to qualify for access to the official UPnP certification test tool and to submit devices for UPnP certification.
Standards: Device Control Protocols
These are the specifications, produced by specific UPnP Task Groups, which have been standardized. The standardization process includes obtaining three sample implementations of the Device Control Protocol (DCP) to pass the UPnP Certification Test Tool, circulating the specification for a mandatory OCF member review and comment period, and obtaining the approval of the UPnP Work Group and OCF Board to become a Standardized DCP. Standardized DCPs are available to the public.
Device Categories
Audio/Video
- MediaServer:4 and MediaRenderer:3
- MediaServer:3
- MediaServer:2 and MediaRenderer:2
- MediaServer:1 and MediaRenderer:1
Basic
Cloud
Device Management
Home Automation
IoT Management and Control
MultiScreen
Networking
Printer
Remote Access
Remoting
Scanner
Sensor Management - RENAMED to IoT Management and Control
Telephony
Add-on Services
Referenced Specifications
The following specification is referenced in UPnP Device Architecture Version 1.0 and is provided here because it is no longer available from its original source.
UUIDs and GUIDs
This specification defines the format of UUIDs (Universally Unique IDentifier), also known as GUIDs (Globally Unique IDentifier).
A UUID is 128 bits long, and if generated according to the one of the mechanisms in this document, is either guaranteed to be different from all other UUIDs/GUIDs generated until 3400 A.D. or extremely likely to be different (depending on the mechanism chosen).
UUIDs were originally used in the Network Computing System and later in the Open Software Foundation's Distributed Computing Environment. (February 1997)
THE ABOVE APPROVED UPNP SPECIFICATIONS WERE COMPLETED PRIOR TO THE COMBINATION OF UPNP INTO THE OPEN CONNECTIVITY FOUNDATION. ALL LICENSES, INTELLECTUAL PROPERTY RIGHTS, AND OTHER RIGHTS, RESPONSIBILITIES, OBLIGATIONS, STANDARDS, AND PROTOCOLS ASSOCIATED WITH THESE APPROVED SPECIFICATIONS ARE SUBJECT TO THE UPNP BYLAWS AND FORUM MEMBERSHIP AGREEMENT.
Legal Disclaimer
NOTHING CONTAINED IN THESE DOCUMENTS SHALL BE DEEMED AS GRANTING YOU ANY KIND OF LICENSE IN ITS CONTENT, EITHER EXPRESSLY OR IMPLIEDLY, OR TO ANY INTELLECTUAL PROPERTY OWNED OR CONTROLLED BY ANY OF THE AUTHORS OR DEVELOPERS OF THESE DOCUMENTS. THE INFORMATION CONTAINED HEREIN IS PROVIDED ON AN "AS IS" BASIS, AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE AUTHORS AND DEVELOPERS OF THESE SPECIFICATIONS HEREBY DISCLAIM ALL OTHER WARRANTIES AND CONDITIONS, EITHER EXPRESS OR IMPLIED, STATUTORY OR AT COMMON LAW, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. OPEN CONNECTIVITY FOUNDATION, INC. FURTHER DISCLAIMS ANY AND ALL WARRANTIES OF NON-INFRINGEMENT, ACCURACY OR LACK OF VIRUSES.
The OCF Logo, UPnP Word Mark and UPnP Logo are trademarks of Open Connectivity Foundation, Inc. in the United States or other countries. *Other names and brands may be claimed as the property of others.
Copyright © 2016-2020 Open Connectivity Foundation, Inc. All rights reserved.
Copying or other form of reproduction and/or distribution of these works are strictly prohibited.
Architectural Documents
Here are the fundamental documents that anchor the UPnP architecture. Device architecture and template guidelines provide a blueprint for the UPnP Task Groups. When a Task Group is finished with its device and services specifications, the checklist provides a thorough accounting of milestones required to propose a specification for standardization.
PORTIONS OF THIS APPROVED SPECIFICATION WERE COMPLETED PRIOR TO THE COMBINATION OF UPNP INTO THE OPEN CONNECTIVITY FOUNDATION. FOR PORTIONS OF THE SPECIFICATION THAT WERE PUBLISHED ON OR PRIOR TO FEBRUARY 20, 2015 THE FOLLOWING APPLIES: ALL LICENSES, INTELLECTUAL PROPERTY RIGHTS, AND OTHER RIGHTS, RESPONSIBILITIES, OBLIGATIONS, STANDARDS, AND PROTOCOLS ASSOCIATED WITH PORTIONS OF THIS APPROVED SPECIFICATION THAT WERE PUBLISHED ON OR PRIOR TO FEBRUARY 20, 2015 ARE SUBJECT TO THE UPNP BYLAWS AND FORUM MEMBERSHIP AGREEMENT.
UPnP Device Architecture version 2.0
Document Revision Date: April 17, 2020
This latest revision adds the following text to section 4.1.1:
The subscription request containing a delivery URL not on the same network segment as the fully qualified event subscription URL shall not be accepted. For private networks this means that the delivery URL provided will adhere to the following IP ranges:
-
- 10.0.0.0 - 10.255.255.255 (10/8 prefix)
- 172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
- 192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
The UPnP Device Architecture (formerly known as the DCP Framework) contained herein defines the protocols for communication between controllers, or control points, and devices.
The UPnP Device Architecture (UDA) V2.0 is the basis for UPnP+ which enhances the UPnP experience so that any device can securely interact anywhere. Here is a summary of the changes between the UDA V1.1 and the new UDA V2.0:
- Annex A (IPv6) has been updated to be compliant with the latest IETF recommendations.
- Annex C (UPnP Cloud Architecture) has been added.
- Support for Control Point identification.
- Subscription support for individual state variables.
- A clarification was made that UDA 2.0 control points shall be backwards compatible with UDA 1.x devices.
- Version mapping clarification.
- Initial bye-bye clarification.
- M-search responses clarification.
- Various language editorial changes for consistency.
An archive of previously published versions of the UPnP Device Architecture is available for historical reference.
IP Declarations from last UDA 2.0 revision published February 20, 2015
UPnP Vendor's Implementation Guide
This document contains clarifications to v1.0 of the UPnP Device Architecture that are likely to be of specific interest to vendors implementing control points and/or devices.
Legal Disclaimer
NOTHING CONTAINED IN THESE DOCUMENTS SHALL BE DEEMED AS GRANTING YOU ANY KIND OF LICENSE IN ITS CONTENT, EITHER EXPRESSLY OR IMPLIEDLY, OR TO ANY INTELLECTUAL PROPERTY OWNED OR CONTROLLED BY ANY OF THE AUTHORS OR DEVELOPERS OF THESE DOCUMENTS. THE INFORMATION CONTAINED HEREIN IS PROVIDED ON AN "AS IS" BASIS, AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE AUTHORS AND DEVELOPERS OF THESE SPECIFICATIONS HEREBY DISCLAIM ALL OTHER WARRANTIES AND CONDITIONS, EITHER EXPRESS OR IMPLIED, STATUTORY OR AT COMMON LAW, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. OPEN INTERCONNECT CONSORTIUM, INC. FURTHER DISCLAIMS ANY AND ALL WARRANTIES OF NON-INFRINGEMENT, ACCURACY OR LACK OF VIRUSES.
The OCF Logo, UPnP Word Mark and UPnP Logo are trademarks of Open Connectivity Foundation, Inc. in the United States or other countries. *Other names and brands may be claimed as the property of others.
Copyright © 2016-2020 Open Connectivity Foundation, Inc. All rights reserved.
Copying or other form of reproduction and/or distribution of these works are strictly prohibited.
UPnP+ Initiative
UPnP+ Certification is now available. Read here for more details.
For Training and Resources on UPnP+ implementation please see below.
Evolution
- Full integration of IPv6 with seamless backwards compatibility to IPv4
- Improved interoperability baseline incorporating the latest specifications, including AV, Device Protection, and Energy Management
Revolution
- Discovery of cloud services and content as well as secure sharing of devices across the Internet
- Data-based definition of new devices
- Expandable protocol bridging using REST based methodologies
- Features that drive UPnP devices to the core of the Internet of Things
- Enabling Social Media interactions
The UPnP+ certification program uses new and existing UPnP device control protocols (DCPs) and UPnP architecture enhancements to provide UPnP protocols focused on delivering new technical capabilities enhancing functionality and increase customer satisfaction in today’s ever-changing market of always-on connectivity. UPnP+ technology is an evolution of previous UPnP capabilities that will assist devices trying to integrate new paradigms like mobile connected computing, cloud-based service delivery, smartphone content sharing, and the Internet of Things.
Key areas UPnP+ addresses include:
- Interoperability
- Security
- Evolving standards (HTML5, IPv6, etc.)
- Cloud-based features
- New services
UPnP+ supports a wide range of functions, ensuring future connectivity and makes new services possible, in areas such as health and fitness, energy management, security and sustainability. UPnP+ allows devices from different manufacturers to work together seamlessly, based on a single underlying technology, which is backwards-compatible with existing products and easy to deploy.
UPnP Device Architecture
The UPnP Device Architecture V2.0 (UDA 2.0) is the basis for UPnP+ certification enhancing the UPnP experiences towards the cloud and in a secure way. The UDA 2.0 is backwards compatible with UDA 1.x devices, enables additional features including IPv6, cloud based sharing, event subscriptions to individual state variables, and includes a number of clarifications. Access the UDA 2.0 here.
UPnP+ Training and Resources
- Why You Should Upgrade to UPnP+ (February 17, 2015)
YouTube recording | Presentation slides only - UPnP+ demo at IBC (September 2014) - YouTube video
- Leveraging UPnP+: The Next Generation of Universal Interoperability (April 2015)
Full Whitepaper | Short Marketing Brief - UPnP+ Certification Overview and Requirements Matrix
- UPnP Internet of Things Overview
- UPnP AV Tutorial
- UPnP Device Architecture Tutorial
- Cloud Demo Source Code
- UPnP+ Implementation Guide (Coming Soon!)
UPnP+ Certification Requirements
View UPnP+ Certification Information and the Requirements Matrix. The process to certify a UPnP+ product is the same as standard UPnP products.
If you have any questions, feel free to contact us!
UPnP+ Certification Requirements
In order to improve UPnP technology implementations and encourage the use of the latest version of UPnP specifications, UPnP Forum has created the UPnP+ certification level. UPnP+ certified products will be more reliable, more secure and will have increased functionality.
The benefits include improved features and performance in:
- Interoperability
- Security
- Evolving standards (HTML5, IPv6, etc.)
- Cloud-based features
- New services
In support of this effort, OCF has updated the UPnP Certification Test Tool (UCTT) for enhanced testing and expanded its testing program to improve the quality of open source implementations.
The following are the requirements for UPnP+ certification compared to UPnP certification for all UPnP certified devices.
Specification | UPnP Certification | UPnP+ Certification |
UDA |
|
|
IPv6 Annex |
|
|
UDA Cloud Annex |
|
|
The following are the requirements for UPnP+ certification compared to UPnP certification for floating services. These services can be added to other device types.
Service | UPnP Certification | UPnP+ Certification |
DeviceProtection |
|
|
FriendlyInfoUpdate |
|
|
EnergyManagement |
|
|
BasicManagementService |
|
|
ConfigurationManagementService |
|
|
SoftwareManagementService |
|
|
QOS |
|
|
QOS |
|
|
The following are the requirements for UPnP+ certification compared to UPnP certification for individual Device Control Protocols. If a particular DCP is used, the UPnP+ requirements for that device must be met for UPnP+ certification. DCPs not listed in this table have no additional requirements for UPnP+ certification.
Specification | UPnP Certification | UPnP+ Certification |
IGD |
|
|
AV |
|
|
MediaServer |
|
|
MediaRenderer |
|
|
UPnP IoT
Who should implement UPnP IoT?
For vendors that already implement UPnP in their devices, we provide a way to discover and manage IoT devices. Read below for more about the UPnP IoT Management and Control Device Control Protocols (DCPs). Bridges between OCF and UPnP have been built and an open source implementation should be available in the coming months.
For vendors that do not implement UPnP, it is recommended that you use OCF directly because of its native RESTful architecture that is very scalable. View the OCF resources here.
UPnP IoT Management and Control
UPnP+ Cloud is built on mature technology (UPnP, Internet Protocols, XMPP...) that caters to tomorrow’s connectivity requirements, removing boundaries and enabling full device and network compatibility. UPnP+ provides a solid, future-proof basis for integration of Cloud content and services. One important and fast-growing user requirement is accessing devices from remote locations, often using a mobile device. Home connectivity from outside the home (or workplace) allows for the development of new integrated capabilities, use cases and business models. Security is a vital element in the design of such applications, UPnP Cloud standards have this ‘built in’, along with access control configurability.
UPnP+ Cloud allows you to connect any number of home devices, mobile devices and cloud services across the Internet in “rooms.” You can control and synchronize any UPnP activities with just the people you want. None of your devices are actually shared until you specify with whom and under what conditions. It’s simple and secure sharing with the people you want on your terms. To access the Cloud DCPs and Implementation Guides, click here.
The strategy in creating UPnP+ uses new and existing UPnP device control protocols (DCPs) and UPnP architecture enhancements in order to provide UPnP protocols specifically for IoT applications. UPnP core technology provides a base for IoT, creating bridges to both wide-area networks and non-IP devices. There are already published UPnP DCPs for lights, thermostats, automatic blinds and security cameras, and UPnP has defined dozens of data models to support new IoT devices, specifically those with constrained resources.
The UPnP bridging concept allows different local networks to interact. This includes existing device network protocols such as Bluetooth or Zigbee. Entirely new domains, introduced as a result of the rise of the Internet of Things and Cloud computing, which couldn’t previously have been accommodated within UPnP are now enabled with UPnP+ IOT extensions.
Beyond physical bridging, the UPnP device data modelling approach allows devices from different ecosystem to agree on a common messaging format. Translations to this format ensures common operation between any ecosystems. UPnP has developed a tool to allow theses device data models to be crowd-sourced. UPnP scales at the rate of the Internet of Things.
In summary, UPnP IoT:
- Builds upon UPnP core technology that already provides a base for IoT (billions of devices deployed!)
- Uses commonly used web technologies to create secure communication between devices
- Bridges local UPnP networks together through the Internet
- Supports simple, data-based device descriptions to include resource constrained devices
- Enables existing UPnP specifications & devices to be Cloud-capable
- Provides a path for low-risk, rapid implementation of UPnP Cloud solutions
- Enables device and service discovery through the Cloud
- Combines UPnP and XMPP ecosystems to enable new IoT possibilities
Resources:
- UPnP IoT Management and Control Device Control Protocols (DCPs)
- UPnP: The Discovery & Service Layer For The Internet of Things (April 2015)
Full Whitepaper | Short Marketing Brief - Why You Should Upgrade to UPnP+ (February 17, 2015)
YouTube recording | Presentation slides only - UPnP+ demo at IBC (September 2014) - YouTube video
- UPnP Internet of Things Overview December 2014
- UPnP Internet of Things Overview (July 2014)
- Bringing UPnP to the Cloud and IOT (May 2014)
- UPnP+ Cloud demo video
- UDA V2.0 with Cloud Annex
UPnP FAQ
Learn More Here
Any more questions?
Have a question that isn’t answered above? Please contact us and we’ll do our best to answer. Your inputs, recommendations, and questions are important to us.
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.