Thursday, December 11, 2014

IoT Ecosystem Game

Internet of Things is changing the world. Not by what we do, but how we do things. This affects individuals, organizations and business ecosystems.

Until now, we have seen ecosystems dominated by a single companies. Let's take Apple as an example. In specific consumer product segments, Apple has ruled the whole value chain from hardware via software to markets and distribution channel. With the model Apple has succeeded to collect 80% of profits of smart phone industry, with only 18% market share.

IoT however is way too diverse for any single company to dominate. Applications vary from hen houses to connected cars, from thermostats to medical instruments. Just like technical architectures are changed from M2M verticals to horizontal layers of IoT, are businesses forced to co-operate with partners and competitors.

M2M vs IOT architecture.
Connected devices is nothing new, M2M has existed from 10 to 20 years already. However, M2M  tends to be like vertical silos, application specific end-to-end solution with limited expandability. IoT as opposite is more like Internet architecture in general, horizontal layers without predefined purpose for any specific function.

Changes in connectivity architectures reflects to ecosystems. A healthy IoT ecosystem has different players for different horizontal players, and preferably many of them. A good example of IoT ecosystem is build around ARM and IBM. ARM provides technology for Things and  IBM for Internet, making it Internet of Things.

ARM embed and IBM cloud offering are really a winning combo. ARM has the strongest ecosystem of silicon vendors. IBM with it's new cloud offering and partnership with Apple, ARM, Semtech, and many more has really gained reputation. This heterogeneous and loosely linked ecosystem has no single point of failure.

There is no ring to rule them all, and there is always room for new trials. That's the only way how the technology can go further in large scale, the law of natural selection applies in technolofy as well.

Just recently Intel announced a new IoT platform, partnering with Accenture, Capgemini, HCL, NTT Data, Tata Consultancy and Wipro. Basically, that's a single silicon vendor with bunch of consultants. Doesn't sounds like a healthy ecosystem. I expressed my thoughts  about the Intel Edison/Quark technology already a year ago. The technology is the basis of this new alliance, which really doesn't convince me.

Sunday, December 7, 2014

Node-RED for Home Automation

Node-RED is a great tool for creating graphical data stream integration and processing flows. Now Node-RED is even better suitable for home automation, as support for multiple different wireless sensors is added via Tellstick Duo.

Yesterday I started to prepare a demonstration for a local Node.js meetup in Helsinki. Node-RED is built a top of Node.js, thus it is natural topic for a presentation in the meet-up. Meanwhile preparing the demonstration, I ended up creating an input node into Node-RED for Tellstick Duo. It is now contributed to the project.

The node is available in npm and github with name node-red-contrib-tellstick.
More detailed information is available on my web site: http://ala-paavola.fi/Node-RED

Node-RED with tellstick input node.

Tellstick Duo is USB-connected 433MHz RF transmitter and receiver from Telldus Technologies in Sweden. It supports wide range of commercially available sensors and devices from different vendors.

Node-RED was initially created by IBM Emerging Technologies at IBM Hursley lab, Winchester UK. It was released as an open source project and is still actively maintained and supported by IBM. It's one of the key assets in IBM Bluemix portfolio.

Couple of weeks ago I met one of the initial creators of the software, Dave Conway-Jones (@ceejay). His answer to my question why did they released it as open source in the first place was something like: "We tough it's so cool that it would be a crime against humanity not to publish it to the whole world." Well, perhaps Dave didn't expressed it exactly like that, but that's how I feel it.

Node-RED is really gaining momentum at the moment. More and more manufacturers are including it in their products, Multitech Conduit IoT Gateway as an example.

More and more devices are supported by Node-RED, Philips Hue for example.
A friend of mine, a system operator, created a build health status indicator with help of Node-Red and Hue. He integrated Node-RED into their company continuous integration tool chain, and now everybody in the office see what's the status of the build. If someone breaks the build, server room neighbourhood is immediately glowing red...

Thursday, December 4, 2014

LoRa in constructed environment

Suddenly LoRa has became one of the hottest technologies in the Internet of Things domain. The number of new customer cases we see in our company is increasing on a daily basis. But where's the beef?

There are two main use cases where LoRa is strong:
- Wide area wireless sensor network (W-WSN)
- Factory (or any facility) area netwok (FAN)

In W-WSN applications, individual diameter of individual LoRa cells may vary from 2 to 20 kilometers. This makes it possible to collect data from many sensors into single gateway for upstream via wired or wireless connections (3G/4G data mode). This is the modem killer scenario explained in previous posting.

Factory area network with star-topology.

FAN is perhaps more common use case for LoRa. Facility can be anything including factory, refinery, warehouse, seaport, shopping center, or office block, and all other cases where mainstream technologies like WiFi, Bluetooth, Zigbee, and other 2.4 GHz RF can't do the job without unreasonable number of access points or complex multi-hop routing algorithms and routing node.

LoRa modulation has certain characteristics which make it suitable for difficult constructed environments like a factory.

Aa a rule of thumb: the lower the frequence the longer the distance, or better peneration. Reduction from 2.4 GHz to Sub-GHz frequencies alone gives significant improvement. The CSS modulation of LoRa makes it possible to detect signals 20dB below the noise floor, yet giving improvement over traditional narrow-band Sub-GHz radios.



Multipath propagation


Multipath fading is a common problem in constructed environment. Signal may travel via multiple different routes due to reflections from different surfaces. It's like echo on a railway station making it very difficult to understand announcements given by loudspeakers. In radio technology, multipath propagation may cause signal amplification or attenuation with short displacement of the receiver.


Up-chirp, increasing frequency sweep in time domain.

Different frequencies have different reflection signature. Chirp Spread Spectrum (CSS) uses frequency sweeps to carry information. During the sweep, some frequency may attenuate, whereas some other frequency may be amplified. All in all, detection of signal in receiver side is very reliable. Consider the railway station example. If audio frequency sweeps - chirps - are broadcasted from loudspeakers, human can easily recognize whether the individual sweep is going from low to high (up-chirp) or from high to low (down-chirp), even if significant echo takes place.

Frequency also affects signal penetration. Due to various reasons, certain frequencies may penetrate better than others. By spreading the signal to wider bandwidth, we increase the probability that some signal gets through. According to our experiments, LoRa has been the only commonly available IoT RF technology, which can deliver data from inside a closed metallic storage container to outside world.