Your browser is not supported. Please update it.

6 March 2015

OIC and IIC announce collaboration, consolidation slowly comes to IoT

The initial land-grab for standards and working groups in the IoT seems to be over, as consolidation begins to set in and the hard work starts. The latest shift in the ecosystem sees the Open Interconnect Consortium (OIC) announce a strategic liaison agreement with the Industrial Interconnect Consortium (IIC), as the two organizations position themselves against the onslaught of AllSeen and the emergence of Thread.

With their walled gardens and veiled secrecy, it’s not actually that easy to see what the groups are working on. The Nest-backed Thread Group is set to unveil its 802.15.4 6LoWPAN protocol sometime in the summer, and as Google owns Nest and its smart thermostats, this will likely be Google’s IoT venture aside from Android.

Qualcomm’s AllSeen Alliance and its AllJoyn protocol meanwhile seems to have taken the lead in the industry, given that it is already shipping inside devices. AllJoyn is a device discovery and management platform, which hopes to be installed on all connected devices to link them together – with the AllJoyn Gateway Agent sitting at central points in the IoT networks.

The AllSeen Alliance, formed when Qualcomm open-sourced its AllJoyn project, has over 100 members, and already presides over a steady stream of AllJoyn-enabled products – including TVs from LG, audio equipment from Gramofon and Panasonic, and potentially any device that uses a Qualcomm Atheros networking chip thanks to the lightweight nature of the AllJoyn software stack.

The AllJoyn Gateway Agent, unveiled in January, is the next step up the device chain, and is intended to allow remote management and access for deployed AllJoyn devices. A set of APIs allow the platform to connect to devices on other networks, including Bluetooth, ZigBee, Z-Wave, REST, XMPP and MQTT. Currently, the Gateway Agent can be installed on Linux and OpenWRT WiFi routers, with the additional connectivity protocols added to the routers via the abovementioned APIs and physical adapters.

Meanwhile, the OIC, which was founded by Atmel, Broadcom, Dell, Intel, Samsung and Intel subsidiary Wind River, has slowly grown to over 50 members, will be putting its coding expertise to task on adapting findings sourced to from the IIC and its 141 members – founded by AT&T, Cisco, GE, IBM and Intel.

We spoke to Guy Martin, a senior strategist in Samsung’s open source group, and Kimberly Lewis, the marketing profile manager at Intel, who were both representing the OIC. Martin explained that the OIC doesn’t see the IIC as a rival because it is not pushing for standards. Due to this, Martin joked that it “could act as the adult in the room” when the OIC is discussing inclusions to the standard.

While we initially thought this new liaison was the beginning of a merging process, Martin said that this was not the case, as the IIC’s main role in the dynamic is currently gathering use cases and requirements from its industrial-leaning members – which the OIC then takes into consideration when developing its standard.

The standard can be summarized as a transport layer-agnostic communications layer, that handles the application level communications between devices. While its most direct rival, AllJoyn, has beaten it to market, Martin said that the OIC’s standard would be ready in the middle of 2015, with products featuring the code appearing in the second half. We asked and were told that the device releases and specifications were not being mandated by the OIC,

The OIC has already shown the pre-standard version its work through IoTivity, which is an open source implementation of the OIC’s project, sponsored by the OIC and governed by the Linux Foundation. Protected by an Apache 2.0 license, adopters are able to write the plugins required to communicate with all manner of devices – perhaps most interestingly with AllSeen ones.

The OIC standard’s core is written in C, and the IoTivity implementation of it is around 50kB in size. The additional wrappers are written in C++, and developers are able to write additional implementations of the standard if required – which could be particularly handy for those developers heavily invested in other languages and frameworks such as JavaScript.

We also received some clarification on Broadcom’s departure from the OIC last year. Martin and Lewis said that the Broadcom decision wasn’t unexpected internally, given that Broadcom’s IP business model is at odds with the OIC’s RAND licensing process.

In order to avoid the standard devolving into a perpetual IP battleground, new versions of the standard are subject to a 60-day waiting period in which members can voice their concerns about elements of the standard that might infringe on their own IP.

Members are allowed to opt out of the licensing agreement two times in a 5 year period, per the terms of their membership agreement. This means that it is possible that royalties will be paid for portions of the OIC codebase, but the OIC is able to rewrite sections that might cause complaint – in order to ensure that its standard remains free to use.

The business model for the OIC’s members is to ensure that all the players in the IoT space are competing on a consistent playing field. If you can guarantee that everyone has access to the OIC standard, it should prevent different companies from forging their own paths on the back of technology that might be abandoned at the expense of customers and businesses who invest in failed platforms.

As it is focusing on the application side of things, the OIC spec doesn’t need to concern itself with the protocols used to communicate between separate OIC devices. Whether the data is delivered by BLE, WiFi or ZigBee, the OIC implementation will treat it in the exact same way – forwarding down the most suitable chain in a network of devices that could be linked by dozens of protocols, as long as there was a gateway there to bridge the gaps at some point.

Decisions about branding and badging have yet to be made, but it seems sensible to create some sort of consumer-facing identify that might help persuade buyers in the showrooms. However, with the ability for the OIC’s framework to speak to AllJoyn devices, and vice versa (with platforms like Ubuntu’s Snappy Core also able to download the plugins to link devices), there might not be a need to form branded battle lines – as long as the devices just work.

Towards the end of MWC, enterprise software and data management biz SAP announced that it would be joining the IIC, with its HANA in-memory database.