The Internet of Things (IoT, for short) is a concept that has been around for over 15 years, and with the advent of cheap devices and plenty of bandwidth, has started to gain some traction. So what is it? There are a lot of definitions out there, covering a lot of area (and even more marketing hype) but there needs to be a good way of stating what it is.
So here is my definition:
The Internet of Things is a way of looking at how mundane devices can communicate with each other.
Yes, it's short, probably a lot shorter than you would expect. But at the heart of it, it is things communicating with other things. So maybe a few more definitions are in order
A Device can be anything that generates, processes, or consumes data.
Communication is the act of sending and receiving of information
So far it sounds a lot like the regular internet. You've got devices communicating back and forth, and you've got information flowing around between devices (in this case computers and servers). We need that final word - Mundane.
Mundane - average, ordinary, not standing out in any way.
So we're not talking about connecting a tablet to eBay. We're talking about connecting your front door to the security system, your mailbox sending a text message, or your toaster to the breadbox. Some of these can already be done, and if you follow the news, you are seeing more products out every day that communicate back and forth.
But there is something lacking, and that is the ability of any device being able to communicate with any other device (within reason, of course - some conversations just don't make sense). I've got the capability the tie my mailbox into the security system, and from there send me a text message whenever it is opened, but I can't just take that mailbox sensor and tag it directly from a browser. I've got to go through an intermediary or two before I can get to the information. Now this in itself isn't a problem, since there are times when you want this sort of aggregation to take place. But in my case, since this information is local to my house, why should it go from the mailbox, to a centralized panel, to a server someplace in California, to a text message aggregator, and then finally I get that buzz on my phone when the postman does a delivery?
Each device also has its idiosyncrasies for setting them up and communicating with them. A WiFi camera will use 802.11x to communicate, while a 2Gig system uses a different set of frequencies and protocols to get things done. Even the same class of devices on the same network may not communicate in the same way, meaning you cannot just get a device and add it to your security system, but have to get a specific type of sensor, sometimes with proprietary protocols that prevent it from working with other devices.
So let me add another definition:
Open - the systems use non-proprietary methods of communications using commonly available protocols, and the communications medium is transparent as to function and capabilities.
So, a camera will look like a camera, and behave the same, at least at this level. This isn't to say that a camera manufacturer can't add more functionality that can only be gotten to in their own special way - just that if you are a device, you have to play nicely.
So what am I doing here? Well, I can't leave well enough alone. I don't do the hardware side, so developing devices isn't really my thing. I'm an architect and developer, and I see a lack in the overall area. There has been some mentions of a Web of Things, but it is also a bit nebulous. So I'm not planning on creating the next widget to make my toaster talk to the breadbox. Instead I'm exploring how I can make it easier for things to talk to each other.
In later posts I'll continue this discussion with myself. There's a lot of stuff out there that I can look at, and maybe someone or something has already solved my problem. But I'm guessing not, since my toaster still doesn’t recognize me and toast things the way I want them to.