IOT

iot@xmpp.org

138 discussions

XMPP-based approach for IoT platform Commissioning and Network Management

by CONZON DAVIDE

Hi all, during the last 30 months I have been involved in a project called IMPReSS ( http://impressproject.eu/ ) co-funded by both European Commission, through 7th programme framework, and Brazilian government, through the CNPq minister. The aim of the project, which is on the eve of the final review, is to provide a Systems Development Platform which enables rapid and cost effective development of complex systems involving Internet of Things and Services and at the same time facilitates the interplay with users and external systems. Leveraging XMPP protocol, the project developed a Network Management infrastructure and Commissioning and Configuration infrastructure for IoT platforms. The latter supports the configuration and mashup of the different components of the IoT platform, while the Network Management infrastructure provides instruments for network monitoring and setup. This infrastructure leverages many features provided by XMPP protocol: - every device is uniquely identified through a Jabber Identifier (JID); - the presence mechanism is used to know in real-time the status of the devices; - XEP-0030 (Service Discovery) is used to discover the entities and their feautres; - XEP-0050 (AdHoc Command) and XEP-0060 (Publish-Subscribe) are used to model the device capabilities in term of data generated and services provided; - XEP-0248 (PubSubCollection Nodes) is used to organize the publish-subscribe nodes, modeling the devices and their features,in a hierarchical structure. which can be used in the discovery mechanism As a next step, we are aiming at making this solution to converge toward XMPP-IoT extensions specifications, with a particular interest and focus on XEP-0324: Internet of Things - Provisioning, which will allow us to improve furtherly our commissioning infrastructure to help people with non-programming skills to quickly and easily develop IoT application based on general purpose IoT middlewares and platforms. This XMPP infrastructure has received good feedback and interest at ICIN 2016 conference on ‘Innovations in Clouds, Internet and Networks’( http://www.icin.co.uk/ ) where has been presented. If you are interested in extended information, you can find the presented paper at the following link: https://www.researchgate.net/publication/299445607_XMPP-based_Network_Manag… and relevant slides here: https://www.researchgate.net/publication/299594851_Slides_XMPP-based_Networ… Hope you can find this approach interesting for you. Please, if you have any comments, questions or you are interested in cooperating on this do not hesitate to contact me. BR, Davide Conzon -- Davide Conzon Istituto Superiore Mario Boella (ISMB) via P.C. Boggio, 61 - 10138 Torino (ITALY) tel. (+39) 011.2276.710 Informativa - Art. 13 D.lgs. 196/03 ========================== Il trattamento dei dati ha la finalità di permettere lo svolgimento delle attività di ricerca, formazione e studio, oltre agli ulteriori servizi messi a disposizione dall’Istituto Superiore Mario Boella I dati saranno trattati con modalità manuali, informatiche e/o telematiche; non verranno per nessuna ragione comunicati ad altri soggetti ed Enti senza previa autorizzazione. Potranno venire a conoscenza dei Vostri dati il responsabile del trattamento e le categorie di soggetti incaricati del trattamento. In ogni momento potrà rivolgersi al nostro servizio Privacy per conoscere i suoi dati e farli integrare, modificare o cancellare per violazione di legge, od opporsi al loro trattamento e/o per esercitare gli altri diritti previsti dall’art. 7 del D.lgs 196/03. Titolare del trattamento è la società Istituto Superiore Mario Boella con sede in Via P. Carlo Boggio n. 61- 10138 Torino. All information and attachments are reserved and an Istituto Superiore Mario Boella intellectual property, if you receive this message for error please delete it and contact info at ismb.it.

8 years, 5 months

Global IoTday 9th of april

by Joachim Lindborg

Hi all next saturday it's global IoT day http://iotday.org I will again have a session in Stockholm where we will do some hacking, talk about IoT compare protocols and technologies and of course use xmpp-iot. *The idea is to use XEP323 and XEP 325 with basic read and write between IoT devices* *http://http://www.xmpp-iot.org/tutorials/ <http://www.xmpp-iot.org/tutorials/>* *http://www.xmpp.org/extensions/xep-0323.html#readmomentary <http://www.xmpp.org/extensions/xep-0323.html#readmomentary>* *http://www.xmpp.org/extensions/xep-0325.html#sect-idp1718128 <http://www.xmpp.org/extensions/xep-0325.html#sect-idp1718128>* *We will talk between JID's subscribed to each outer so devices need to accept subscription requests either from anybody or if you prefer specific servers. * *We will also use one chat room for discussions * *We will use another chat room for devices to have anonymous direct messaging. So no groupchat talks in that room only direct messaging between nicknames, otherwise it would easily be totally swamped.* So I would like all of you, that have a device or two, to hook them up and publish a JID and we try to do an "around the world federated IoT hack with the best open 'IoT Silo' killing standard, XMPP. If you have any other suggestion on usage, pubsub, adhoc, testcases, servers, etc etc lets talk about it and see where we get. *Regards* Joachim Lindborg CTO, systems architect Sustainable Innovation SUST.se Barnhusgatan 3 111 23 Stockholm Email: Joachim.lindborg(a)sust.se linkedin: http://www.linkedin.com/in/joachimlindborg Tel +46 706-442270

8 years, 5 months

CFP: 3rd EAI International Conference on IoT Technologies for HealthCare - HealthyIoT 2016

by Aida Causevic

**************************************************************************************** Please accept our apologies if you receive multiple copies of this announcement due to cross posting. **************************************************************************************** Dear Colleagues, Please find below information related to the 3rd EAI International Conference on IoT Technologies for HealthCare to be held in Västerås, Sweden. Kindly consider submitting your work to this conference. We have also opened call for workshop proposals. More details can be found at: CALL FOR CONFERENCE PAPERS:http://healthyiot.org/2016/show/cf-papers CALL FOR WORKSHOP PROPOSALS: http://healthyiot.org/2016/show/cf-workshops Scope HealthyIoT 2016 is the third one of an international scientific event series dedicated to Internet of Things and Healthcare. The Internet of Things, as a set of existing and emerging technologies, notions and services, can provide many solutions to delivery of electronic healthcare, patient care and medical data management. HealthyIoT aims to bring together technology experts, researchers, industry and international authorities contributing towards the assessment, development and deployment of healthcare solutions based on IoT technologies, standards and procedures. Topics * Wearable Sensor Systems * Medical and Sensor Data Stream Processing * Signal Processing and Analysis * Machine Learning for Signal Processing * Emerging eHealth IoT Applications * Network Communications for Health Sensor Data * Quantified Self Devices & Technologies * Processing of Quantified Self Data * Cloud Technologies for Healthcare * Intelligent Data Processing and Predictive Algorithms in eHealth * Smart Homes and Smart Caring Environments * Telemedicine Applications * The Smartphone as a HealthyThing * Wellness and Health Management Applications * Data Mining of Health Data on the Cloud * Medical and Sensor Data Stream Processing * Security, Safety and Privacy in eHealth and IoT * Interoperability and Standardization Issues in IoT and Healthcare * Network Communications for Health Monitoring * Mobile Sensing and Smartphone Sensing * Wireless Sensor and Actuator Networks * Sensor Network Operating Systems and Resource Management **************************************************************************************** Important dates Full Paper Submission deadline May 10, 2016 Notification deadline June 10, 2016 Camera-ready deadline July 30, 2016 Conference October 18-19, 2016 Västerås, Sweden Best regards, Aida Čaušević PhD, Postdoctoral researcher Mälardalen University School of Innovation, Design and Engineering Box 883, SE-721 23 Västerås, Sweden Phone: +46 21 101 613, Cell: +46 739 607 316 URL: http://www.es.mdh.se/staff/188-Aida_Causevic

8 years, 7 months

IoT Gateway

by Peter Waher

Hello For those interested in XMPP & IoT, this project might be of interest: https://github.com/PeterWaher/IoTGateway In this project I'll add support for the IoT XEPs (and more), and might be useful if you want to learn about or experiment with these. The project is in its inception phase. Best regards, Peter Waher

8 years, 8 months

Re: [IOT] IANA application

by Peter Waher

Hello Peter, Joachim and Dave (& others). Thanks for the input. > tror du beh?ver uppdatera adresser etc i > https://www.iana.org/assignments/uri-schemes/prov/iotdisco det l?r v?l inte > komma fram post till valparaiso? och din mail fungerar ju inte heller. Regarding address in application: Yes, it points to my old address in Chile. I learnt that I was to move back after sending the application. A request to update the contact information has been sent. Let’s see how long that takes… > jag reagerade p? att version skall vara numeric med decimalpunkt men m?nga > k?r ju major.minor.patch https://wiki.eclipse.org/Version_Numbering vilket > eg blir string? You could also report the version number as two or more parameters. The point here is to make searching more simple. For instance, you want 1.10 to be greater than 1.2, which it is if numeric, but not if a string. This makes it possible to search for temperature sensors of brand X, model Y with a version number greater than Z. You could add a patch parameter (or build parameter) to include more detailed information if you want. > I find this slightly unfortunate, because XEP-0053 reads: > > The XMPP Registrar shall be responsible for interacting with the > IANA on behalf of the XMPP Standards Foundation. If an XMPP > Extension Protocol specification requires interaction with the IANA, > that fact shall be noted by the document author(s) and discussed on > the Standards mailing list along with normal discussion of the XEP. > The XMPP Registrar shall collaborate with the author(s) to submit an > appropriate request to the IANA. > > I suppose it could be argued that this registration has been made on > behalf of ISO/IEC/IEEE working group 21451-1-4 (not the XSF), or even on > behalf of no organization. Correct. The work on this was part of the IEEE WG. I also mailed the iot list (and others) for comments, but received them a bit late. > What exactly is the relationship between this URI scheme and XEP-0347? XEP-0347 proposed a method (in §3.9) where metadata could be encoded as a string, and then encoded as a QR-code (as an example). In the IEEE WG, they did not like the fact that the string was not encoded as a URI. So, we created another encoding based on similar principles, but that has a URI scheme and valid URI syntax. This encoding is better, and the URI scheme is registered. The idea is to update XEP-0347 to reflect this change. It also makes it easier to integrate into software scanning QR codes to know what the code is supposed to mean. > Yes, Peter Waher's postal and email address, as listed, doesn't work > anymore, does it? Nope. > I'm a little confused by the registration, which seems to be several pages > longer than it should be anyway and hasn't been, as far as I can tell, > formally reviewed by anyone. So it doesn't surprise me at all that odd > things like version numbers (which have no place in protocols) have ended > up in there. Yes, it was reviewed by several people. IANA does not publish things that have not been reviewed. > Also, for future reference, it'd be helpful to keep to English on these > lists, despite Google Translate's help in giving me some idea of what's > discussed. I often do this error myself, believing I’m responding to a person directly, when I’m actually responding to the entire list. Best regards, Peter Waher

8 years, 10 months

Re: [IOT] IOT Digest, Vol 37, Issue 2

by Peter Waher

Hello Peter Yes, this was registered in August: http://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml https://www.iana.org/assignments/uri-schemes/prov/iotdisco http://www.iana.org/assignments/uri-schemes/prov/iotdisco.pdf I will also update XEP-0347 (§3.9) to reflect this new URI scheme for encoding conceptual identities of things. Best regards, Peter Waher > ---------------------------------------------------------------------- > > Date: Wed, 11 Nov 2015 19:55:37 -0700 > From: Peter Saint-Andre <peter(a)andyet.net> > To: XMPP in the Internet of Things <iot(a)xmpp.org> > Subject: Re: [IOT] IANA application > Message-ID: <5643FFA9.7030801(a)andyet.net> > Content-Type: text/plain; charset=windows-1252; format=flowed > > Was this ever done? > > Sorry, this message was stuck in the queue. > > On 7/10/15 10:41 AM, Peter Waher wrote: > > Hello > > > > During the work in other standards groups, there has been some interest > > in the discovery model presented in XEP-0347. This has lead to the > > desire to update the IoT-discovery encoding described in the XEP > > somewhat and formalize it into a URI scheme. I?ve therefore prepared an > > application to IANA for a provisional URI scheme. The idea is to send it > > by the end of next week. So, if you have time, and an interest, you?re > > welcome to return any comments, suggestions or questions to me by then, > > so I have a chance to update the application before mailing it. The idea > > is to update XEP-0347 after the approval of such a provisional URI scheme. > > > > Best regards, > > > > Peter Waher

8 years, 10 months

IANA application

by Peter Waher

Hello During the work in other standards groups, there has been some interest in the discovery model presented in XEP-0347. This has lead to the desire to update the IoT-discovery encoding described in the XEP somewhat and formalize it into a URI scheme. I've therefore prepared an application to IANA for a provisional URI scheme. The idea is to send it by the end of next week. So, if you have time, and an interest, you're welcome to return any comments, suggestions or questions to me by then, so I have a chance to update the application before mailing it. The idea is to update XEP-0347 after the approval of such a provisional URI scheme. Best regards, Peter Waher

8 years, 10 months

COAP as Streaming Source

by Sadaf Khan

Hi i am working on coap protocol for an Iot Application .I' ve made this as a Spark-Streaming Source. i simply 've made a resource and add it to my server as a observable resource. then i start observing it through myclient, It fetches the data perfectly but also gives the following exception. 15/10/14 13:49:48 ERROR BlockGenerator: Error in block pushing thread java.io.NotSerializableException: org.eclipse.californium.core.CoapObserveRelation Serialization stack: - object not serializable (class: org.eclipse.californium.core.CoapObserveRelation, value: org.eclipse.californium.core.CoapObserveRelation@25d5cb65) at org.apache.spark.serializer.SerializationDebugger$.improveException(SerializationDebugger.scala:40) at org.apache.spark.serializer.JavaSerializationStream.writeObject(JavaSerializer.scala:47) at org.apache.spark.serializer.SerializationStream.writeAll(Serializer.scala:153) at org.apache.spark.storage.BlockManager.dataSerializeStream(BlockManager.scala:1189) at org.apache.spark.storage.BlockManager.dataSerialize(BlockManager.scala:1198) at org.apache.spark.storage.BlockManager.doPut(BlockManager.scala:850) at org.apache.spark.storage.BlockManager.putIterator(BlockManager.scala:637) at org.apache.spark.streaming.receiver.BlockManagerBasedBlockHandler.storeBlock(ReceivedBlockHandler.scala:77) at org.apache.spark.streaming.receiver.ReceiverSupervisorImpl.pushAndReportBlock(ReceiverSupervisorImpl.scala:141) at org.apache.spark.streaming.receiver.ReceiverSupervisorImpl.pushArrayBuffer(ReceiverSupervisorImpl.scala:112) at org.apache.spark.streaming.receiver.ReceiverSupervisorImpl$$anon$2.onPushBlock(ReceiverSupervisorImpl.scala:97) at org.apache.spark.streaming.receiver.BlockGenerator.pushBlock(BlockGenerator.scala:198) at org.apache.spark.streaming.receiver.BlockGenerator.org $apache$spark$streaming$receiver$BlockGenerator$$keepPushingBlocks(BlockGenerator.scala:171) at org.apache.spark.streaming.receiver.BlockGenerator$$anon$1.run(BlockGenerator.scala:89) can anyone have idea about this.? This is my custom receiver for making my client to stream it. class customReceiver(test:String) extends Receiver[CoapObserveRelation](StorageLevel.MEMORY_AND_DISK_2) with Logging{ @volatile private var stopped = false override def onStart() { val client = new CoapClient("coap://localhost/temp") var response=client.observe(new CoapHandler() { override def onLoad(response: CoapResponse) { } override def onError() { System.err.println("Failed") } }) response.proactiveCancel(); store(response) } } Any help is much awaited and appreciated :) Thanks

8 years, 11 months

Re: [IOT] [Standards] Blocking messages from unsubscribed users

by Joachim Lindborg

In the case of IoT i use it a lot devices only look at subscription requests from unsubscribe do users. And I also have component that takes care of devices blocking all messages from non subscribed Don't know if I need a xep for it or if its implementation specific for IoT I would like to be able to turn it on as default for myself receiving only subscription requests just as I have setup Skype måndag 12 oktober 2015 skrev Steffen Larsen <zooldk(a)gmail.com>: > Hi Matthew, > > Good call. The scenario I have used blocked commands was in a setup where > I actually needed configuration instead (setup once). > So for me and the scenarios I have, the ad-hoc command config would be > great!. > > The only problem I see, is that every server would vary a lot.. and have > different policies. > > /Steffen > > On 12 Oct 2015, at 23:28, Matthew Wild <mwild1(a)gmail.com <javascript:;>> > wrote: > > > > It seems a few people are requesting this. I'd like to understand the > use-cases. > > > > For example, if this is something you want to be the default > > behaviour, isn't it better as a deployment configuration? No protocol > > needed. > > > > A per-user configuration would also be possible using ad-hoc commands. > > Again, no extra XEPs needed. > > > > Just throwing things out there, I'd like to understand exactly what > people want. > > > > Regards, > > Matthew > > -- *Regards* Joachim Lindborg CTO, systems architect Sustainable Innovation SUST.se Barnhusgatan 3 111 23 Stockholm Email: Joachim.lindborg(a)sust.se linkedin: http://www.linkedin.com/in/joachimlindborg Tel +46 706-442270

8 years, 11 months

How to make Coap as Streaming Source

by Sadaf Khan

Hi, I am working on COAP-IOT protocol. i want to embed it as a streaming source in my application. Is it possible to do this via spark streaming. ?? Thanks in anticipation.

8 years, 11 months

← Newer
1
2
3
4
5
6
7
8
...
14
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

IOT