Internet of Everything

  • 1.  Collecting data in IoT networks

    Posted Sep 11, 2017 16:27
    I am interested to learn what companies with IoE and IoT use to monitor the IoT network and make sense of the (big) data that is collected in the IoT networks?

    ------------------------------
    Mark Desar
    ESRI
    ------------------------------


  • 2.  RE: Collecting data in IoT networks

    Posted Sep 12, 2017 06:31
    Marc, indeed a very interesting question, with no easy answers. As far as I can see/understand it, there will only be "partial" monitoring, i.e. the IP connectivity required for IoT will be monitored by the various CSPs. Connectivity within buildings/houses may be monitored depending on the used systems, by the users themselves. Applications may be monitored by the application providers.  The type of data collected could go a lot further that the basic data, needed to monitor/provide the service. Which makes it very tricky, also the regulation and security and privacy of this data.  Maybe what is now IoE should be defined far more precisely, in a set of value added services that can then be further detailed.

    ------------------------------
    Anton Van der Burgt
    Xelas software
    ------------------------------



  • 3.  RE: Collecting data in IoT networks

    TM Forum Member
    Posted Sep 13, 2017 02:52
    Hi Mark,

    What you will find, many companies are focusing on just making IoT/IoE devices function. Data collection is immature and a low priority objective. There are no direct tools, data is often gathered as a man-in-the-middle.

    Consider giving an IP address to a simple coffee maker. It really isn't an IoT/IoE device yet, but you can remotely start brewing the coffee. After it's prepared to make the coffee.

    Without going into the kitchen, there are dozens of methods that could be used to start the coffee maker on the local network. API, port, CLI, VPN, tunnel, etc... Depends on the complexity and access you have to the coffee maker.

    Remotely connecting to your home network, you could also find a way to start the coffee brewing. But it's still not an IoT/IoE device.

    When the device contacts a central hub, somewhere on the internet, now it's an IoT/IoE device. And it doesn't do anything until you install an app of visit the central hub's website. Which provides a button to start brewing the coffee in your home coffee maker.

    In most cases, the app and website would make a call that cascades an instruction to your coffee maker. When viewing all the calls, to every other coffee maker, this would be the big data.

    The manufacturer could also notify the hub when you manually start the coffee making process. Providing more data, showing preference over the app, website, or directly using the button.

    While the coffee maker may even use NTP to keep the clock accurate. In many cases, IoT/IoE does not change the basic functionality of a device.

    ------------------------------
    Brian LaVallee
    INVITE Communications Co. Ltd
    ------------------------------



  • 4.  RE: Collecting data in IoT networks

    TM Forum Member
    Posted Sep 14, 2017 10:29
    Hi Brian,

    Your quote "When the device contacts a central hub, somewhere on the internet, now it's an IoT/IoE device" is what my submission is all about. I would like to get rid of the central hub and make that coffee maker a resource on the internet which can be accessed (with credentials) without the central hub app.

    My proposal at a very high level involves tiny hub at the local router which publishes the devices on its LAN to a "DNS++" along with the  path to reach it. Application developers can query "DNS++" and send messages to the device along with the necessary credentials.

    The "DNS++" and Credential Management can be implemented as a blockchain to avoid central authority.

    ------------------------------
    Santhosh Sathiyaseelan
    Verizon Communications
    ------------------------------



  • 5.  RE: Collecting data in IoT networks

    TM Forum Member
    Posted Sep 15, 2017 04:02
    Sorry Mark, this is a but off-topic.

    Hi Santhosh,

    There are many possible approaches that could be explored.

    - Centralized Hub
    - Decentralized Hub
    - Direct Access
    - Indirect Access
    - Announced
    - Discovered

    With each approach, there are numerous pros and cons.

    While you may have considered the benefits for the methods you've considered. I see a number of potential flaws you may or may not have considered.

    The device manufacturer has to provide the 'tiny hub' you mentioned. Some early implementations use this method, an example is the Phillips Hue Lighting Bridge. But this method can easily lead to a dozen devices that require power and network connectivity for every IoT/IoE device.

    The Hue bridge is actually an auxiliary controller, connecting lights to the LAN to my apps and the central hub. It has already had to be replaced with a later model to support newer features.

    The DSN++ approach 'may' require direct access to the LAN environment, 'maybe' even the IoE/IoT device. I've seen a few attempts to decentralize DNS, but none that really took off. I assume your method would operate like dynamic DNS, mapping the name to network to the IoT/IoE device.

    While this may be an extreme example, the Bitcoin blockchain has already exceeded 100GB. The manufacturers of my refrigerator, washing machine, or coffee maker are NOT going to provide a lot of storage or memory. There are cost considerations.

    Remember, a blockchain is always growing. And I am not going to be very happy when I can't get my morning coffee, all because my coffee maker is out of memory.

    ------------------------------
    Brian LaVallee
    INVITE Communications Co. Ltd
    ------------------------------



  • 6.  RE: Collecting data in IoT networks

    TM Forum Member
    Posted Sep 18, 2017 09:49
    Thank you for your response Brian.
    There are some gaps between my thinking & your understanding of it :).
    My apologies for not articulating it clearly.

    1) The device manufacturer does not provide the HUB, The router manufacturer/ISP does that.
         The hub is somewhat similar to Samsung SmartThings/ Wink etc but the key difference is that it's
         not connected to a central proprietary server. Instead they update the "DNS++" and provide protocol
         traslations from IP to Zigbee,ZWave etc. as applicable. Its primary function is to act as a conduit to
         the IoT device from the outside world.

    2) The blockchain is not on the device, but on the global network as blockchain's should be.
         It is where the DNS++ "resides". It is also used for the device ACL's.

    Your coffeemaker & washing machine will work as is :)

    ------------------------------
    Santhosh Sathiyaseelan
    Verizon Communications
    ------------------------------



  • 7.  RE: Collecting data in IoT networks

    Posted Sep 21, 2017 15:53
    Mark, 

    I am interested in your question. It seems the amount and types of data vary depending on the use case of the device. Early and some current IoT solutions didn't understand the importance of collecting the right data and providing the capability to make better business decisions from analyzing the data.

    The discussion has addressed IoT devices where bandwidth doesn't seem to be an issue. Devices such as a coffee maker, Nest thermostats, etc. can transmit much data without power concerns. Does your question pertain only to these types of devices or also devices that may be low power or mission critical where you need fast response times and thus a edge computing solutions (gateway) as well as cloud storage?

    ------------------------------
    Phillip Simulis
    Simtelligent
    ------------------------------