15
edits
Difference between revisions of "Tech pages/IoT systems"
Jump to navigation
Jump to search
no edit summary
| Line 3: | Line 3: | ||
* [[Tech pages/IoT_XepsExplained|IoT_XepsExplained]] Description of xeps and their interaction | * [[Tech pages/IoT_XepsExplained|IoT_XepsExplained]] Description of xeps and their interaction | ||
* [[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_Interoperability|IoT_Interoperability]] How we will keep everything truly interoperable | ||
* [[Tech pages/ | * [[Tech pages/IoT_XMPP_Process|IoT_XMPP_Process]] How is the process of the xep's and interoperability interfaces managed | ||
* [[Tech pages/ | * [[Tech pages/IoT_ConstrainedDevices|IoT_ConstrainedDevices]] Going in to the world of restricted devices we need special care. | ||
= Introduction = | = Introduction = | ||
| Line 14: | Line 16: | ||
On the M2M machine to machine area nothnig like XMPP has ever excisted we have seen several "If you all do like me" [[lonworks]][[KNX]][[zigbee]][[z-wave]] What they all have in common is that they all have gateways to IP | On the M2M machine to machine area nothnig like XMPP has ever excisted we have seen several "If you all do like me" [[lonworks]][[KNX]][[zigbee]][[z-wave]] What they all have in common is that they all have gateways to IP | ||
The | The evolvement of wifi and initiatives as ipso-alliance and IPv6 together brings the revolution of connected devices and M2M. | ||
The big problem is that they are all trapped in business silos covered by clouds with exploding number of different API's making it very hard to create interoperable inventive services without creating your own hardware. | |||
== Goals == | == Goals == | ||
| Line 28: | Line 31: | ||
== XMPP strengths == | == XMPP strengths == | ||
* Proven technology | * Proven technology | ||
* | * Security | ||
* | * Efficient | ||
== XMPP weaknesses == | == XMPP weaknesses == | ||
* Provisioning, things that cant answer friend requests. | * Provisioning, things that cant answer friend requests. | ||
* | |||
== Overall sources and links == | |||
= Xeps in experimental= | |||
[[http://xmpp.org/extensions/xep-0322.html|xep-0322]] | |||
[[http://xmpp.org/extensions/xep-0323.html|xep-0323]] | |||
[[http://xmpp.org/extensions/xep-0324.html|xep-0324]] | |||
= Protoxeps = | |||
[[http://xmpp.org/extensions/inbox/sensor-network-concentrators.html|sensor-network-concentrators]] | |||
[[http://xmpp.org/extensions/inbox/sensor-network-control.html|sensor-network-control]] | |||
= Latest working material = | |||
[[https://github.com/joachimlindborg/XMPP-IoT|XMPP-IoT]] | |||
[[https://github.com/joachimlindborg/XMPP-Exi|XMPP-Exi]] | |||
= Authors = | = Authors = | ||
Email: peter.waher@clayster.com | Email: peter.waher@clayster.com | ||