There will also be better group management features, making it easier to create and manage conceptual groups of IoT devices, and detailing “how you add and remove devices and add security,” said Kesavan. The big news for developers in v2.0 is the support for Node.JS at the API level. Presumably, the Nest support would include some integration with Nest’s Weave IoT protocol, but Kesavan did not go into specifics. Specific device integration will also be provided for IoT device families like Nest, LIFX, and Hue. Presentation slide: Bridging other EcosystemsĮEBus, a European IoT spec for energy management in homes and smart buildings. There are also plans to integrate the UPnP AV data model directly to IoTivity to support audio and video. ![]() In the future, the OCF will translate IoTivity’s REST APIs to UPnP’s SOAP/XML representations, he added. “A UPnP device will essentially be discovered and seen as an OCF device.” “We’re doing a lot of work in protocol translations, exposing UPnP devices using a plugin mechanism,” said Kesavan. Much of v2.0 is about supporting legacy UPnP devices. Integrating IoT ecosystems is a more challenging problem. Presentation slide: IoTivity v2.0 Focus Areas IoTivity 2.0 will also support Samsung’s Linux-ready Artik embedded modules. “Zephyr and IoTivity have the same data model, but the APIs are not yet compatible,” said Kesavan. Arduino 101 runs the Arduino IDE on the Intel-developed, open source Zephyr OS, which itself runs on an Intel Curie module based on an Intel Quark SE chip. New hardware targets will include Intel’s Arduino 101 board. “We’re porting IoTivity to Windows so it can build upon Visual Studio 2013,” he said. The Windows integration will be more substantial. For iOS, the OCF is essentially doing what it did for Android: adding support in the “upper stack built on C++” rather than the lower C-based stack, in order to expose IoTivity to the iOS API, said Kesavan. Version 2.0 will expand that to Windows and iOS. IoTivity currently supports Linux, including specific Ubuntu and Android support, as well as Arduino. Joining the IoTivity Party: iOS, Windows, UPnP, and Arduino 101 He also explained how the OCF is exploring usage profiles beyond home automation in domains like automotive and industrial. Speaking shortly after the release of IoTivity 1.1, Kesavan told the ELC audience about plans to support new platforms and IoT ecosystems in v2.0. Kesavan is a seed contributor to the core IoTivity library, and currently serves as the Business Development Task Group chair for OCF. The Iotivity 2.0 talk (see full video below) was presented by Vijay Kesavan, a Senior Member of Technical Staff in the Communication and Devices Group at Intel Corp. Here, we examine another ELC 2016 talk about the specifics of those integrations, as well as other changes planned for the IoTivity 2.0 release due later this year. We also looked at how the OCF has evolved from the earlier Open Interconnect Consortium (OIC) and acquired the assets of the Universal Plug and Play (UPnP) Forum. In May, we reported on an Embedded Linux Conference talk by Open Connectivity Foundation (OCF) Executive Director Mike Richmond on the potential for interoperability between the OCF’s IoTivity IoT framework and the AllSeen Alliance’s AllJoyn spec. ![]() In an ELC talk in May, Vijay Kesavan of Intel’s Communication and Devices Group outlined plans to support new platforms and IoT ecosystems in IoTivity v2.0. Twitter Facebook LinkedIn Reddit Pinterest Email
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |