Difference between revisions of "Tech pages/IoT Interoperability"

Jump to navigation Jump to search
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
= Layout=
= Layout =
  [[Tech pages/IoT_systems|Main]] Main page
 
  [[Tech pages/IoT_XepsExplained|IoT_XepsExplained]] Description of xeps and their interaction
{{XmppIoTLayout}}
  [[Tech pages/IoT_Examples|IoT_Examples]] Mashup some examples from different industries, help finding new ones
  [[Tech pages/IoT_Support|IoT_Support]] Here we describe who support this and related work that can help you.
  [[Tech pages/IoT_Interoperability|IoT_Interoperability]] How we will keep everything truly interoperable
  [[Tech pages/IoT_XMPP_Process|IoT_XMPP_Process]] How is the process of the xep's and interoperability interfaces managed
  [[Tech pages/IoT_ConstrainedDevices|IoT_ConstrainedDevices]] Going in to the world of restricted devices we need special care.


== Overview ==
== Overview ==
Line 13: Line 8:
Some examples of interoperability  
Some examples of interoperability  


* ZigBee alliance, Defining all layers of the OSI stack for wireless sensor networks and adding "profiles" for smart energy
 
* Upnp and dlna working with specifications for printers, Tv sets to be interoperable 
* LonMark an initiative to standardize equipment connected to the lonworks communication system


The problem is that to finance these organizations they must take a member fee and the certification processes is very costly for companies. This also implies that they need to be more or less closed (you have t
The problem is that to finance these organizations they must take a member fee and the certification processes is very costly for companies. This also implies that they need to be more or less closed (you have t
Line 30: Line 23:
Creating interoperabilty is a crucial thing in the area of Internet of Things. Interoperability is needed on several layers and can either be forced in to specifications and required through certification processes.
Creating interoperabilty is a crucial thing in the area of Internet of Things. Interoperability is needed on several layers and can either be forced in to specifications and required through certification processes.


We are therefore planning for a special working group in the XSF organisation that votes on the changes in the interface specifications
We are therefore planning for a special working group in the XSF organisation that votes on the changes in the interface specifications.
 
This will involve a separate mailing list


== Interface specification Process ==
== Interface specification Process ==
Line 37: Line 32:
== Automatic test bed ==
== Automatic test bed ==


To be interoperable and to verify functions testing is cru
To be interoperable and to verify functions testing is crucial therefore we intend to setup an interoperable testbed with a interoperable bot that you can connect to and run an interoperable test.


== Other examples ==
== Other examples ==
In all technical protocols there are interoperability efforts unfortunately they often are to close to the physical protocol they are working with
* [http://zigbee.org/ ZigBee alliance] Defining all layers of the OSI stack for wireless sensor networks and adding "profiles" for smart energy
* [http://upnp.org Upnp Forum]
* [http://upnp.org dlna working group] Specifications for printers, Tv sets to be interoperable 
* LonMark an initiative to standardize equipment connected to the lonworks communication system
* BacNet


* Lonworks and the lonmark organisation
* The Zigbee smart energy 3.0 and ZigBee IP this is one of the closest to actually leave the physical layer
* The Zigbee smart energy 2.0 and ZigBee IP
*
15

edits

Navigation menu