New products, Conferences, Books, Papers, Internet of Things

Posts tagged ‘MQTT’

Libelium Sensors Connect with Cloud Platforms for the Internet of Things

diagrama_cloud_connection_cloud-500pxLibelium today added new integration options from leading Cloud technology providers in the latest stage of the build-out of its Waspmote wireless sensor platform ecosystem, to reduce time to market for Internet of Things solutions.

Demos showcasing Waspmote and Plug & Sense! nodes integrated with software platforms from Axeda, EsriThingWorx as well as the MQTT protocol will be rolled out at Dreamforce 2013 in San Francisco at Smart City Expo World Congress in Barcelona, Spain and at the Internet of Things & WSN Conference in Santa Clara, California. The new Cloud connector framework is based on a new managing system for Libelium’sMeshlium wireless sensor gateway, allowing easy configuration of any of these platforms. Existing Meshlium users are eligible for the upgrade.

Libelium has simplified the integration of leading Cloud software platforms to its Waspmote wireless sensor network platform, decreasing time to market for new IoT solutions. “Waspmote is a universal hardware platform for the Internet of Things because it is open and modular, and can integrate any sensor, using any communication protocol, and send retrieved data to any Cloud system for analysis or storage,” said David Gascón, CTO at Libelium. “Now we’re offering access to the best Cloud software platforms by streamlining the integration process, to connect the physical world to the virtual world and transform sensor data into information resources.” Waspmote Cloud Connector Software Ecosystem Additions – available separately.

More info here.

Meet Node-RED, an IBM project that fulfills the internet of things’ missing link

node-red-screenshotFrom GigaOm:

If you play around with enough connected devices or hang out with enough people thinking about what it means to have 200 connected gizmos in your home, eventually you get to a pretty big elephant in the room: How the heck are you going to connect all this stuff? To a hub? To the internet? To each other?

It’s one thing to set a program to automate your lights/thermostat/whatever to go to a specific setting when you hit a button/lock your door/exit your home’s Wi-Fi network, but it’s quite another to have a truly intuitive and contextual experience in a connected home if you have to manually program it using IFTTT or a series of apps. Imagine if instead of popping a couple Hue Light Bulbs into your bedroom lamp, you bought home 30 or 40 for your entire home. That’s a lot of adding and setting preferences.

If you take this out of the residential setting and into a factory or office it’s magnified and even more daunting because of a variety of potential administrative tasks and permissions required. Luckily, there are several people thinking about this problem. Mike Kuniavsky, a principal in the innovation services group at PARC, first introduced me to this concept back in February and will likely touch on this in a few weeks at our Mobilize conference next month. He likens it to a more organic way of programming.

The basic idea is to program the internet of things much like you play a Sims-style video game — you set things up to perform in a way you think will work and then see what happens. Instead of programming an action, you’re programming behaviors and trends in a device or class of devices. Then you put them together, give them a direction and they figure out how to get there.

Over at IBM, a few engineers are actually building something that might be helpful in implementing such systems. It’s called node-RED and it’s a way to interject a layer of behaviors for devices using a visual interface. It’s built on top of node.js and is available over on github.

The idea behind the node-RED effort came from playing around with connected devices, and the work it took to make things work together. The engineers behind the code — Nicholas O’Leary, Dave Conway-Jones and Andy Stanford-Clark — are also working with IBM’s MQTT messaging protocol. But with node-RED they aren’t focused on how devices talk to each other, but how they work together.

“The first version of node-RED was all about MQTT and how can we move messages between different topics and do it in a really lightweight way,” said O’Leary. But eventually it became more about a way to tell devices what you’d like them to do as opposed to having to tell each of them how to do it added Conway-Jones.

More info here.

IBM launches an appliance for the ‘Internet of things’

Preparing its customers to join the emerging ’Internet of things’, IBM has released a new appliance built to manage and route a voluminous amount of machine-to-machine small data messages

Using the MQTT (the Message Queuing Telemetry Transport) format, the IBM MessageSight appliance is capable of processing over 13 million messages per second, all of which could arrive from as many as 1 million end-nodes.

“It’s a huge breakthrough in scale,” said Mike Riegel, who is the IBM vice president of mobile and application integration middleware.

The IBM MessageSite was one of a number of new products and updates that the company announced as part of its Impact conference, being held this week in Las Vegas.

IBM designed this appliance, which will be available for customers on May 24, to specifically work with what is being called The Internet of things.

The Internet of things is not a network, but a new buzzphrase describing the growing use of network-connected embedded microprocessors, often connected to sensors or other data-gathering instruments. Because microprocessors are now so inexpensive and networks are so pervasive, such embedded systems could provide a wealth of data that organizations in most industries could use to monitor and improve operations.

For instance, a new car today may have dozens of microprocessors that run millions of lines of code, Riegel said. The car maker could ingest all the data these embedded systems produce, supplying their customers and themselves with pertinent information about how well the vehicle is operating.

By 2020, there might be as many as 22 billion embedded systems and other portable devices connected to the Internet, according to IMS Research. Collectively, these systems may produce more than 2.5 quintillion bytes of new data every day, estimated the IT research company.

More info here.

A Giant Step Forward for the IoT and Big Data

Andy Stanford-Clark, an IBM Master Inventor who lives in the United Kingdom, jokes that his goal was “world domination” in 1999 when he and Arlen Nipper of Eurotech invented a protocol aimed at greatly improving machine-to-machine communications. This was at the time when another British technology pioneer, Kevin Ashton, coined the term “Internet of Things” to describe how the Internet could be connected to the physical world via a vast network of sensors. Sanford-Clark believed that his protocol, now called MQ Telemetry Transport, or MQTT for short, would enable organizations to quickly and affordably gather, integrate and make use of all of that sensor data. It would be an essential underlying technology for the Internet of Things.

Fast forward to today. OASIS, one of the leading technology standards bodies governing the evolution of the Internet, has just announced that it will accept MQTT as an industry standard protocol. This move paves the way for the technology to be used widely for applications ranging from power distribution and public safety to retailing, smart phones and auto communication systems. MQTT now has the potential to have the same kind of impact on the world as HTTP, which is a key part of every Internet address for computers and Web sites. Proponents of the Internet of Things believe there could be up to 50 billion sensors hooked up by the year 2020–turning the promise of Big Data into a reality. “The vision of billions and trillions of connected devices can now come true,” says Stanford-Clark. “The implications are huge. We can solve the energy crisis and improve agriculture, transportation and healthcare. It will make getting things done easier, cheaper and more efficient.”

More info here.

Choosing Your Messaging Protocol: AMQP, MQTT, or STOMP

MQTT_HeaderOne of the most common questions I’m asked to cover when I discuss software architecture topics is the difference between the various application messaging protocols that exist today—issues like how and why the protocols came about, and which one should be used in a particular application.

Their question is valid.

Today, application architects need to use a messaging broker to speed and scale their applications, particularly in the cloud. Even once you select your messaging middleware application, application developers need to then select the protocol. Understanding the subtle differences between them can be difficult.

Today, we will consider three of the most common and popular TCP/IP-based messaging protocols, and provide a quick summary on the advantages of each: AMQPMQTT and STOMP. Before we go on, I should also point out that all three of these protocols are supported in RabbitMQ version 3.0—something we will use as an example and come back to later.

More info here.

Work begins to standardize ‘internet-of-things’ protocol

OASIS has announced a new technical committee is being formed to formalize a standard protocol for machine-to-device-to-sensor-to-refrigerator-to-other-machine-somewhere-else-on-the-network interactions, otherwise known as the “internet of things.’

The protocol, “MQ [Messaging Queue] Telemetry Transport,” or MQTT, is described on the MQTT.org site as a “machine-to-machine (M2M)/Internet of Things connectivity protocol.” The protocol, designed as an “extremely lightweight publish/subscribe messaging transport,” is intended to facilitate “connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium.” Examples include “sensors communicating to a broker via satellite link, over occasional dial-up connections with healthcare providers, and in a range of home automation and small device scenarios.”

MQTT is also well-suited for mobile applications, proponents say, due to “its small size, low power usage, minimized data packets, and efficient distribution of information to one or many receivers.”

Having a universally accepted and adopted M2M protocol will help get new devices and systems to market faster, since they often are built using many variations of hardware and software platforms, device types, and networks, OASIS notes.

MQTT was invented by Dr Andy Stanford-Clark of IBM, and Arlen Nipper of Arcom (now Eurotech), back in 1999. It also has been called the “SCADA protocol,” the “MQ Integrator SCADA Device Protocol” (MQIsdp), the “WebSphere MQTT” (WMQTT).

OASIS’ MQTT Technical Committee will work with MQTT as its base document to “define an open publish/subscribe protocol for telemetry messaging designed to be open, simple, lightweight, and suited for use in constrained networks and multi-platform environments.”  OASIS has scheduled the first, in-person  meeting to be held in Boston on Monday, 25 March 2013, to be hosted by IBM.  A working specification will be completed by March 2014, OASIS says.

The MQTT TC is intended to complement previous work by the OASIS AMQP Technical Committee, which released a specification that provides for transaction and publish & subscribe messaging between autonomous businesses, departments and applications using an open protocol for enterprise middleware. The MQTT specification adds a means “by which sensors, control systems, embedded systems and mobile devices can publish and subscribe low-level, technically-orientated data,” OASIS says. “There is natural affinity to bridge MQTT with AMQP, so as to connect telemetry with enterprise applications.”

More info here.

Facebook’s Updated iPhone App Aids Internet of Things

Buried in the details of last week’s update to Facebook’s now-native iOS app was a small bit of technology that could have potentially big impact on the future of the Internet of Things.

The technology is called Message Queuing Telemetry Transport (MQTT), an IBM-developed protocol for real-time messaging over networks with low power and bandwidth. MQTT is now under the hood within Facebook’s iOS app’s messaging features, part of Facebook’s efforts to pull in the features from its native Messenger app.

“We use MQTT to update notifications, messages, and bookmarks. At application startup, we walk the dependency graph and ensure that our MQTT service has started before we start listening for new notifications. Even as we add new features, our modular system ensures that our application setup happens in the right place, at the right time,” wrote Facebook engineer Jonathan Dann on the company’s engineering blog last week.

More info here.