Breaking News

Namedropping: The Many Names of Internet of Things

Page 1 / 2 Next >
View Comments: Newest First | Oldest First | Threaded View
User Rank
Mammoth solutions for small problems
prabhakar_deosthali   1/22/2015 3:48:19 AM
If all the billions of those tiny IoT sensors are connected all the time to internet, the netwrok traffic which can get created will be collassal and the network bandwidth requirements and the associated  cloud computing capability will grow out of proportion and all this mammoth effort for what?  Not for such important things as weather simulation and forecasting, or astronomy reasearch , but just for some data collection of wearable sensors or some sensors reporting the fridge inventory and such small things!


It is like tommorrows facebook or Whatsapp service where 90% of the data is of not much importance! 

User Rank
IoT - [It's not] The Name [that matters]
spike_johan   1/21/2015 5:29:21 PM
Entertaining article - thanks, but I feel as if it were somewhat misleading.

First, IPv6 was conceived  - as I recall - not to provide the addressing scheme for the coming IoT but rather as an end all/be all answer to the limitations of IPv4.

Second, the IoT - to my way of thinking - was not just another dreamed up name to speak to the evolution of the internet as imagined through the lense of IPv6 but rather was to speak to the upcoming (100's of billions) of things in the form of [mostly commercial/industrial] sensors that would take their places - in some yet to be determined fashion - on the internet.

Third, these things - these, sensors things - do not (if taken in a commercial/industrial setting) necessarily fit the same communication paradigm as those smart computing devices utilizing TCP/IP. I refer to daCosta saying that most sensors will/could use mostly unidirectional 'chirps'.

You didn't speak to the following but I would like to finish my argument and say in conclusion:

Fourth, these 'chirping', mostly unintelligent sensor devices will not have (aka not need) the requisite memory or processing power to carry the IP protocol stack or need to/want to participate in processing packets where the addresses are 128 bits.

And fifth, it seems myopically illogical to architect the [industrial/commercial side] of the IoT based on IPv6 just because it is easier to envision everything - industrial sensors and all - on the same flavor of internet.

I mean think about it in the following context. An agro-business with thousands of moisture sensors. Sporadic chirps consisting of a few bits (the size of the data payload) of moisture information; this as related to a data header size that might be a 100 times larger.

Packets on the network where the data headers consistently have sizes something like two orders of magnitude larger than the data payload? That's not good engineering.

Like Us on Facebook
EE Times on Twitter
EE Times Twitter Feed