The Makeup of an M2M Network Architecture

January 20, 2014
M2M is built up of 3 main components: data producers, data aggregators and controllers M2M fascinates me. If I had to guess why it probably has to do with the communication and network nature of it – it is at the same time similar and different than VoIP. With Google just acquiring Nest, I just had to write my own piece about M2M – something I wanted to do for a while anyway. Before I start with my own ramblings about how I see the M2M networks, I'd like to share two great posts I've read this week about it, and a book I really enjoyed:
  • Dr Richard Windsor about the Nest acquisition, with a simple statement: "The world is not becoming less siloed but more."
  • Robert X. Cringely predicting the Internet of Crap – why vulnerabilities will make us throw away and replace all of our current networking equipment and devices
  • Rainbows End by Vernor Vinge. Go read it now. I'll wait. It has everything and anything you need to know about where we're headed with M2M
- Machine to Machine (M2M). Internet of Things (IoT). Internet of Everything (IoE). They are all one and the same. Probably coined by different vendors just to show they are thought leaders in this domain. They throw number into the air – everything between 10 billion to a trillion devices. Pick a number and a year, and you have yourself a prediction. When this brave new world arrives, what will connect all of these devices? How will the network architecture look like?

Here's what I think: There are 3 types of jobs that need to be done: you either produce data, aggregate and process data or make decisions. And you can do more than a single task.
  • Producing data – this is the work done by sensors. They can be connected wirelessly or by other means to "something" that collects that information and is capable of sending it elsewhere. I think this is what we're seeing today: be in Nest, or these new wristbands that are popping everywhere. We have our hacker's platforms for these toys: Arduino and Raspberry Pi. Consider them first generation and wait to see them shrink and improve.
  • Aggregators – these are the machines than and up gobbling data from sensors and processing it. They can filter information, aggregate it, and make calculations on top of it. It is where Big Data and analytics will find a cozy home – a place where ridiculously huge amounts of data need to be collected.
  • Decision makers – all that data is collected for a reason, and that reason may be to show a fancy visual on a dashboard in your smartphone; or to drive a decision – lower the temperature on that Nest thermostat as an example.
This model is different than the one of VoIP, where everyone is both a client and a server. It is also different than the one of the web, where you are either a client (web browser) or a server. It seems to me like a hybrid of sorts between the two – which is exactly where you'll find something like WebRTC. But more on that – in a later post.

You may also like

RTC@Scale 2024 – an event summary

RTC@Scale is Facebook’s virtual WebRTC event, covering current and future topics. Here’s the summary for RTC@Scale 2024 so you can pick and choose the relevant ones for you.

Read More