IoTivity | |
Author: | Open Connectivity Foundation |
Latest Release Version: | 2.0 |
Latest Release Date: | 2018 |
Programming Language: | C, C++, Java (programming language) |
License: | Apache License 2.0 |
The IoTivity is an open source framework created to standardize inter-device connections for the IoT.[1] Any individual or company can contribute to the project, and this may influence OCF standards indirectly. However, being a member of the OCF can benefit from patent cross-licensing protection.
The IoTivity architectural goal is to create a new standard by which billions of wired and wireless devices will connect to each other and to the Internet.[2]
In October 2016 they announced AllJoyn merger into Iotivity.[3] The group hoped that devices running either AllJoyn or Iotivity would be interoperable and backward compatible.
On October 10, 2016, the AllSeen Alliance merged with the Open Connectivity Foundation (OCF) under the OCF name and bylaws. OCF then sponsored both the IoTivity and AllJoyn open source projects. The merged groups announced that they will collaborate on future OCF specifications, as well as the IoTivity and AllJoyn open source projects, and current devices running on either AllJoyn or IoTivity will be interoperable and backward-compatible. The expanded OCF board of directors included: Electrolux, Arçelik A.S., ARRIS International plc, CableLabs, Canon, Cisco, GE Digital, Haier, Intel, LG Electronics, Microsoft, Qualcomm, Samsung, and Technicolor SA.[4]
The release is 2.0 was announced in September, 2018.[5] Previously, there was a 1.3.1 release[6] for the IoTivity Framework. Within the merging process with AllJoyn, the software license changed to Apache 2.0 Licence which makes it easier to other open source projects to include IoTivity and AllJoyn in more projects.
The system uses the Constrained Application Protocol (CoAP) as its application layer which can uses several underlying physical layers as long as the network layer is Internet Protocol.[7] Examples include: Wi-Fi, Ethernet, Bluetooth low energy, Thread, and Z-Wave.
Legacy protocols are also supported by a protocol plugin manager [8] including: