Oct 5, 2016
Noted because of semantic interoperability between LWM2M and OIC.
seen from Brazil
seen from Canada
seen from Switzerland
seen from Vietnam
seen from United States
seen from Canada
seen from United States
seen from Japan
seen from Costa Rica
seen from Canada
seen from Malaysia
seen from India
seen from China
seen from China
seen from China
seen from China
seen from United States
seen from China
seen from China
seen from United States
Noted because of semantic interoperability between LWM2M and OIC.
Open Interconnect Consortium lanza nuevas herramientas para desarrolladores
Open Interconnect Consortium lanza nuevas herramientas para desarrolladores
La oferta actualizada de herramientas para desarrolladores incluye oneIoTa, que permite a los usuarios crear modelos simples para cualquier dispositivo IoT (utilizando RAML y JSON) en cuestión de minutos.
Los modelos son compatibles de forma instantánea con la arquitectura RESTful de Open Interconnect Consortium (OIC).
Dado que los modelos son constructivos (por ejemplo, se puede construir un…
View On WordPress
OIC and UPnP. Hopefully they paid less than $1500, as the usefulness of UPnP for new projects is about nil.
[T]he Open Interconnect Consortium is acquiring the assets of the Universal Plug and Play Forum, an organization formed about 15 years ago to standardize discovery and control of networked devices.
UPnP is used in about 3 billion devices and plays a key background role in wireless home networks, especially the routers that usually sit at the center of them. …
OIC will acquire "substantially all the assets of the UPnP Forum," the organizations said. In return, OIC will offer membership to everyone in the UPnP group.
A deal between standards groups could help make home IoT easier
A deal between standards groups could help make home IoT easier
The Internet of Things is moving to the forefront of home networking as the variety of devices that can go online rapidly expands.Reflecting this trend, the Open Interconnect Consortium is acquiring the assets of the Universal Plug and Play Forum, an organization formed about 15 years ago to standardize discovery and control of networked devices. Source: A deal between standards groups could help…
View On WordPress
» Specifications |
Download Giant PDF Specs and Wonder!
I don’t know if all the standards are strictly comparable, as they’re dealing with different areas of the IoT. Weird that AllJoyn isn’t mentioned.
Mentioned are:
Wireless IoT Forum - launched in April
oneM2M
Open Interconnect Consortium
Industrial Internet Consortium
HyperCat
The Open Interconnect Consortium, Inc., Statement of Founding Principles
http://openinterconnect.org/wp-content/uploads/2011/07/Statement-of-Founding-Principles.pdf
OPEN INTERCONNECT CONSORTIUM, INC. STATEMENT OF FOUNDING PRINCIPLES
The Open Interconnect Consortium, Inc. (the “Corporation”) and its Members wish to define and promote a single connectivity framework to enable communications and interoperability in support of the “Internet of Things” across multiple vertical markets, operating systems, platforms, modes of communication, transports and use cases and to encourage the development and distribution of products implementing such connectivity frameworks.
The above goal will be accomplished through the following activities and outputs: (((I bet you didn’t know that “principles” could have “outputs,” but a new world is dawning, etc)))
Specifications. Development and publication of Specifications (as defined more fully in the Intellectual Property Rights Policy of the Corporation), which define and promote communication and interoperability requirements for the “Internet of Things.”
Open Source Project. Cooperate with open source projects in the development of open source software in support of the Specifications.
Test Tools: Technical resources, such as software in binary and/or source code form, for validating compliance with Specifications and open source projects.
Testing Activities: “Plugfests” (((wow))) and other events and activities that provide opportunities for Members to test interoperability and validate compliance with Specifications and open source projects.
Whitepapers: Technical and non-technical documents which discuss various technical and business considerations, insights, and consumer requirements for the “Internet of Things.”
Ecosystem Development: Representing the Corporation and activities to attract industry membership and broad adoption.
Marketing and Public Relations: Representing the Corporation, generating awareness of the Corporation, and providing liaison to other standards development organizations.
Certification and Logo Program: Following publication of Specifications and open source projects, the Corporation will further develop a formal certification process, logo, trademark, and other marketing programs and collateral, the extent of which shall be determined by the Corporation, for promotion of Member products that comply with Specifications and open source projects.
The following sets forth the technical scope of any specifications that would be adopted by the Corporation:
Enabling devices, services and applications (“Products”) to discover, connect, communicate and interoperate through:
A framework that includes: 1 – STATEMENT OF FOUNDING PRINCIPLES PDX\107235\120825\TFH\14743894.2
Object models for devices, users, resources Discovery of and interaction between objects Associated security (authentication; encryption; privacy; access control) Device management (provisioning) Data management Mapping of the above onto multiple underlying technologies, but not the definition of those technologies (Bluetooth, Wi-Fi, IP, Zigbee, ZWave, etc...) Protocols, data formats and the mapping and adapting of both APIs Functions, input parameters, data structures, and services (including web services, web resources and software modules), to the extent that they are specifically described in detail For clarification, the following activities are expressly not included in scope of any specification that would be adopted by the Corporation: Any enabling technologies that may be necessary to make or use any product or portion thereof that complies with the Specification, but are not themselves expressly set forth in the Specification.
For example:
Semiconductor manufacturing and packaging technology Processor architecture/microarchitecture Processor instruction sets Compiler technology Basic operating system technology
The implementation of other published specifications developed by any other standards body but referred to in the body of the Specification, including but not limited to the following to the extent included in such other published specifications:
o Media codecs or their physical layer implementation
o Specific encryption, authentication, access control, and other security protocol standards’ specifications
o Physical layer (PHY) connectivity or interaction between devices
o User interface software
o Data formats
2 – STATEMENT OF FOUNDING PRINCIPLES PDX\107235\120825\TFH\14743894.2
Any portions of any product and any combinations thereof the purpose or function of which is not required for compliance with the Specification
Without limiting the foregoing, the scope of any specifications that would be adopted by the Corporation is limited to functionality within the blocks enclosed by the dotted-line boxes in the block diagram below, as such blocks are further defined below.
This drawing is a block diagram, and implementation of the behavior and algorithm descriptions contained within the dashed boxes may be physically distributed across system design.
In furtherance of these efforts, the Corporation and its Members seek to solicit the participation and comments of all interested parties on a fair, equitable and open basis. As part of these efforts, the Corporation may interface with other groups or bodies developing standards and specifications related to above.
3 – STATEMENT OF FOUNDING PRINCIPLES PDX\107235\120825\TFH\14743894.2
A statement from the Open Interconnect Consortium
*This is Cisco, GE, Intel and Samsung, basically: the IoT players who aren’t the Big Five Stacks.
*It’s interesting hear a Consortium talking in its own voice. Mostly they just consort.
http://openinterconnect.org/members/
WHY ARE WE DOING THIS?
We want to connect the next 25 billion devices for the Internet of Things. We want to provide secure and reliable device discovery and connectivity across multiple OSs and platforms. There are multiple proposals and forums driving different approaches... but no single solution addresses the majority of key requirements. We need industry consolidation around a common, interoperable approach. We need a broad industry consortium of companies to create a scalable solution.
View the Open Interconnect Consortium, Inc. STATEMENT OF FOUNDING PRINCIPLES
http://openinterconnect.org/wp-content/uploads/2011/07/Statement-of-Founding-Principles.pdf
WHAT ARE WE DOING?
We are defining the specification, certification & branding to deliver reliable interoperability -- a connectivity framework that abstracts complexity This standard will be an open specification that anyone can implement and is easy for developers to use It will include IP protection & branding for certified devices (via compliance testing) and service-level interoperability There will also be an Open Source implementation of the standard This Open Source implementation will be designed to enable application developers and device manufacturers to deliver interoperable products across Android, (((Google))) iOS, (((Apple))) Windows, (((Microsoft))) Linux, Tizen, and more. (((I guess that leaves Facebook and Amazon scratching their heads and forking Android code, but that seems to be the coming thing, even Microsoft does it.)))
WHO NEEDS THIS?
Consumers, Enterprise, Industrial, Automotive, Health, etc. who want smart devices to easily interconnect and communicate with appliances, embedded devices, etc. Developers of operating systems, platforms, and applications who want their products to interoperate seamlessly across many brands and ecosystems. End users who want consistent levels of security and identity across smart devices down to the smallest connected appliance
HOW WILL WE DELIVER IT?
Our goal is to define a comprehensive communications framework to enable emerging applications in all key vertical markets. The framework must enable multiple new modes of communication, such as Peer-to-Peer, Mesh & Bridging, Reporting & Control, etc. The framework should include a consistent implementation of identity, authentication and security across the modes of User ID, Enterprise / Industrial ID & Credentials. (((That’ll be interesting.))) It should include a sense of proximity for the Internet of Things and Wearable devices and include support for Onboarding and Provisioning. And the framework must support a “building block” architecture and provide an Open Source implementation