Hi Tomcik,
Very welcome to IoTivity world. I can answer for few from your questions. IoTivity is also considering G/W kind of device. I expect next year it will be formalized. Current IoTivity Cloud Implementation is just relay the data instead of storing in cloud. But this is up to the cloud operator, We can adapt the cache or shadow concept on the cloud but it require additional extension as of now. Queuing on MQ needs to be answered from the IoTivity Cloud project person for more correctness. BR, Uze Choi From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Ondrej Tomcik Sent: Wednesday, November 30, 2016 3:00 PM To: iotivity-dev at lists.iotivity.org Subject: [dev] IoTivity in Kistler products Hello IoTivity developers. I would like to ask you for help. We are evaluating IoTivity platform for our test&measurement platform and I would like to ask you few questions which are not clear to me yet. We have for example measurement station which contains our sensors(can measure pressure, force, acceleration and torque). Some of them can host IoTivity directly and connect to cloud, but some of them not. ? Other IoT platforms provides ?gateway?. This gateway uses adapters(drivers) in which you can implement logic for data transformation. For example, 3rd party camera uploads xml with ocr information and picture to ftp server. I need to host this FTP server in an adapter and when device uploads the file, I parse this xml, transform to json and send this message to IoT platform in the name of that device. How should I handle these type of devices with IoTivity? I was not ablemto find something similar. IoTivity supports cloud deployment. Devices which wants to communicate with the cloud has to sign-up. After they are authorized, they can communicate with Cloud Interface. I found two examples. One is aircon_controlle and if I understand IoTivity correctly, it is both server and client, which can change it?s state (on/off). ? Is this state stored both locally and also on cloud side in resource dictionary? It is required for us to send many telementry messages from station sensors (and gateway) to cloud / from station sensors to station infield server. This messages has to be queued, in correct order and delivered. ? How is this done? Is Kafka used for this purpose? ? Is messaging done through Cloud Interface -> Message Queue -> Kafka? ? How are intermittent connections handled ? ? On the cloud side, we will have a microservice which will receive these messages and route it to correct microservice. Is it only client which will subscribe to the specific topic? ? Is it possible to allow subscribing only from internal network of cloud and publishing from sites? Sorry for many questions, but we have many requirements which as far as I see IoTivity can fulill. But I am not sure how exactly. Documentation has few gaps which I will try to update later. Thank you. Ondrej Tomcik Kistler Bratislava, s.r.o. ?ev?enkova 34, 851 01 Bratislava, Slovakia Direct +421232272604, Main Office +421 2 32 272 903, +421 2 32 272 910 <mailto:ondrej.tomcik at kistler.com> ondrej.tomcik at kistler.com, www.kistler.com <https://www.kistler.com/> Description: Description: C:\Users\Too\AppData\Roaming\Microsoft\KISTLER-Standard-Signature\image001.jpg Confidentiality Notice: This e-mail is privileged and confidential and for the use of the addressee only. Should you have received this e-mail in error please notify us by replying directly to the sender or by sending a message to info at kistler.com. Unauthorised dissemination, disclosure or copying of the contents of this e-mail, or any similar action, is prohibited. -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161130/2bd3de05/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13614 bytes Desc: ?????? ?? ????????. URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161130/2bd3de05/attachment.jpg>
