Today, everyone must go through arduous certification and testing programs to create certifiable platforms that are both secure and contain working code. To address this complicated process, the OCF certification program continues to evolve and improve. One of the ways in which it continues to grow involves the testing and certification of modules for inclusion in devices whether they are a server or client. An OCF-capable module is not a complete end-product. However, it is designed to meet all the OCF certification requirements and functionality that can be included as part of an end-product. In this case, the modules we are referring to are sensors and actuators. As a result, the OCF recently began the process of certifying sensors and actuators to address the market demand for lower cost devices in the network.
While sensors can read, actuators can both read and write in the network using the OCF protocol. For example, a sensor will let you know when your door opens and closes by quickly beeping. An actuator will allow a carbon dioxide monitor to both sense and alert you of dangerous air levels. To certify a module within the OCF Certification Program, there are several rounds of thorough testing that need to be completed in order to ensure the module is secure and the code is working. The modules can be submitted for certification as either a sensor or an actuator. By certifying sensor and actuator modules, there is no need for the creation of new resources. A simple easy-to-use generic resource table can be used. Once the module has completed the original certification procedure successfully, it can then be used as the basis for derived certification of an end product. For a product based on the certified module, certification testing needs to be based on a minimum of three runs. If used in another design, the applicant must have express permission from the initial developer or designer to use the new design, and attestation also applies in these types of situations.
A module is certified using a table of generic device types and resource types. When a module is used in a final product, it will be tested as the OCF Defined Device Type and Resource Type(s). By certifying these modules, OCF is accelerating product certifications with pre-certified sensors and actuators, helping vendors reduce cost and associated time to market. If the module is reused in another design or implementation, it does not need to be retested. However, bear in mind that module certification would not be allowed to be used for a product if there were changes to the hardware, software, security mechanism, or operating system. The cost reduction and faster time to market that come out of module certification are increasingly important to the speedy evolution of the IoT as this helps manufacturers create secure, reliable devices that are ready for deployment with less operation expenditure.
The OCF is continually working to improve the process for certification of modules and thus devices. By offering module certification, the efforts of the OCF are helping device manufacturers and vendors decrease development cost and time-to-market of their IoT devices and appliances.
The Open Connectively Foundation and its members are ensuring that the interoperability needed for the Internet of Things exists, in order to create seamless, amazing experiences for end users. The OCF Certification Program includes conformance testing to ensure robust and secure connectivity, and to help manufacturers create products that interoperate with other OCF-Certified IoT devices regardless of their form factors, operating systems, service providers, or transports.
To view the latest OCF product listings, visit the OCF Announced Certified Product Registry. To learn more about the benefits of OCF certified benefits, steps for OCF certification and more, visit the OCF Certification page.