Muhammad Awais

[email protected]

Nokia, Ericsson and Intel have recently announced their combined support for a new standard called Narrow-Band Long-Term Evolution (NB-LTE), which they see as an ideal connectivity solution for the growing cellular Internet-of-Things market.

NB-LTE is an improved variant of existing 4th Generation LTE (Long-Term Evolution) mobile technology which has been optimised for low-power machine-to-machine and Internet-of-Things applications.

This new standard is NB-LTE is well suited for IoT applications – thanks to being a narrow-band cellular communications standard for applications that aren’t very data intensive – which offers low implementation cost, ease of use and good power.

NB-LTE networks operate with narrow-band 200kHz channels, meaning that existing spectrum allocations such as 2G can’t simply be re-allocated to support the new technology. However, NB-LTE can be used in shared spectrum alongside existing LTE networks.

This narrow-band approach is particularly valuable today as more and more stakeholders are using the RF spectrum, with more spectrum congestion and less unallocated space.

Nokia, Ericsson and Intel plan to work closely together to develop and bring to market infrastructure and technology that supports the uptake of the NB-LTE standard, as well as products that make use of it. These companies aim to support the building of an ecosystem around NB-LTE that accelerates its adoption, including its use in in IoT applications.

They believe that it makes sense to take advantage of the existing widespread deployment of cellular networks to support and drive IoT adoption … that the development of the NB-LTE standard helps achieve this at minimal cost through the re-use of existing infrastructure where appropriate, and that this development will bring benefits to consumers such as enhanced connectivity of devices at a lower cost.

Intel intends to support commercial rollout of the technology, providing a roadmap for their NB-LTE chipsets and product upgrades beginning in 2016 that will enable NB-LTE connectivity combined with slim form factors.

These products will add to Intel’s growing NB-LTE portfolio. Nokia and Ericsson will provide the technology needed for infrastructure upgrades, supporting an extension of existing LTE base stations and networks to NB-LTE technology.

Narrow-band LTE is intended to make it easier for mobile operators to support the huge numbers of small devices that IoT applications are expected to bring into existing 4G LTE networks, without network congestion.

Existing 4G networks are considered to be crucial to IoT development because they’ll be around for decades – hence the Long-Term Evolution name. Using this infrastructure provides a kind of future-proofing for IoT devices, which may easily have a longer useful lifespan than a smartphone.

On the other hand, existing, 2G and 3G networks may soon be decommissioned. Taking advantage of the existing global footprint of LTE cellular infrastructure ensures a global foundation for a vast range of new cellular IoT applications for consumer and industry users, and ensures that this will be a stable foundation.

But NB-LTE doesn’t have industry-wide support, and other companies such as Huawei are putting their weight behind the existing Narrowband Cellular IoT, or NB-CIoT, standard. NB-CIoT has already gained operator support from major players such as Vodafone and China Unicom.

However, the NB-LTE standard, unlike NB-CIoT, does not require any overlay network for compatibility with existing LTE networks and chipsets. This means that NB-LTE can be more easily deployed across existing LTE networks, compared to the competing NB-CIoT standard, and this is an important advantage.

The key difference is that the NB-LTE standard makes it much easier to re-use existing LTE infrastructure – both in terms of the network infrastructure and the chipsets in end-user devices. This leads to clear advantages for the NB-LTE standard in terms of cost and deployment time.

At a recent meeting, the 3rd Generation Partnership Project (3GPP) Radio Access Network (RAN) group has looked at these different proposals and decided on a common way forward, which is important since narrowband LTE specifications are likely to play a crucial role in the development of the cellular IoT sector.

What they have agreed on is a standard called Narrowband-IoT or NB-IoT. This is a new standard that is not exactly the same as either the NB-LTE proposal or the NB-CIoT proposal, but something which seems to include the benefits of both approaches, which all stakeholders can agree on as a common standard for future IoT-friendly LTE development.

This new standard reconciles the differences between the narrowband standards being promoted by different technology vendors, and provides for low device cost, low power consumption, and an optimised network architecture with IoT applications in mind that provides improved indoor coverage, low delay sensitivity and support for a massive number of low-throughput IoT devices on the network.

Overall the Narrow-Band Long-Term Evolution standard offers a glimpse into the future of M2M devices and the Internet of Things. However if you have a wireless M2M product idea or revision requirement – we can work together to meet your needs.

Here at the LX Group we have end-to-end experience and demonstrated results in the entire process of IoT product development, and we’re ready to help bring your existing or new product ideas to life. Getting started is easy – click here to contact us, or telephone 1800 810 124.

LX is an award-winning electronics design company based in Sydney, Australia. LX services include full turnkey design, electronics, hardware, software and firmware design. LX specialises in embedded systems and wireless technologies design.

Published by LX Pty Ltd for itself and the LX Group of companies, including LX Design House, LX Solutions and LX Consulting, LX Innovations.

Yaler is a simple, open and scalable relay service that enables secure outside access to Internet-connected embedded systems and IoT devices that are behind a firewall or router.

Firewalls and Network Address Translators (NATs) can cause connectivity issues when deploying Internet-connected embedded systems and IoT products in the real world, especially in corporate environments.

For example, say you want to access something like an Internet-connected temperature sensor connected to your private LAN from anywhere in the outside world.

Traditionally, this would require opening and forwarding ports at the router, which means extra hassle as well as extra security vulnerabilities, and this needs to be repeated for each additional IoT device you add to the network.

Yaler aims to solve this problem in a simple and easy-to-use manner while also maintaining security.

One common solution is to use port forwarding and to assign an external IP address for each device at the router level. However, this requires the end users of these devices to know how to configure port forwarding and to have administrative access to the network infrastructure, which isn’t always possible.

Yaler aims to solve this problem, making it easy to set up secure Web and SSH access to embedded devices and IoT systems from outside the local network, regardless of whether they’re behind a firewall, a NAT or a mobile network router, and without requiring configuration of the network infrastructure. Yaler provides this in the form of an easy-to-use cloud-based connectivity service.

Furthermore, Yaler provides an infrastructure and service that allows your IoT devices to be accessed from the outside Internet with a simple public URL. This is accomplished by using a reverse HTTP protocol, where a service on the Internet acts as a public relay for these devices on the private network behind firewalls or NATs.

You can use almost any network-connected hardware that provides a TCP socket, with guides and tutorials provided by Yaler that make it easy to get started with popular platforms including the Arduino, Raspberry Pi, Intel Edison and BeagleBone. A single Yaler relay server instance can host many devices, such as Arduinos, SheevaPlug style devices, Android phones, or any other connected device with TCP socket connectivity.

Furthermore, remote access to local gateways enables the configuration and control of other devices on the network, even if these are embedded IoT devices that use alternative network stacks like Bluetooth Low Energy or 802.15.4/6LoWPAN. If they can be reached via their gateway from the TCP/IP network infrastructure, then Yaler can be configured to talk to these devices.

Libraries and examples are available for Yaler using the Arduino Ethernet shield, the Arduino Yún, Arduino with the Texas Instruments CC3000, and many other popular low-cost IoT development platforms. Yaler also makes it easy to implement a custom binding for any other device, based on the software examples they provide using C, C#, Java or Python.

The process to get started is simple – after the Yaler library, or YalerTunnel command-line tool, has been installed on the device – end users can just plug in their device and access it from outside the local network via the Yaler relay at a known, stable URL.

Once your devices are accessible and addressable from the Web using the Yaler relay, Yaler makes it fairly easy and straightforward to set up integration with other existing Web applications or third-party services that you use.

Yaler enables secure tunnelling of most TCP-based legacy and proprietary protocols, so for example you can use VNC to monitor a machine, or collect data stored in a local database, without compromising on security. The Yaler service supports SSL/TLS encryption, where an embedded device publishes over a secure connection to the Yaler relay, and a client can then access the data over HTTPS.

Remote access is simplified thanks to the YalerTunnel daemon, enabling remote SSH access to embedded Linux devices via the Yaler relay without the need for port forwarding. This enables you to securely access local embedded computers for administration, monitoring and remote operation.

You can conveniently debug, monitor, reboot or update a device such as a Raspberry Pi, Arduino Yún or any other Linux platform remotely, using standard tools at the command line.

Yaler is based around open-source technology, and it is free to use with a single HTTP relay domain associated with your Yaler account. All Yaler libraries and daemons are freely provided under the Simplified BSD open source license and dual-licensing is possible, to help integrate Yaler into your commercial needs.

This suits hobbyist users, and also makes it easy for enterprise users to get started evaluating the Yaler platform to see how it fits into their IoT needs. You can also move up to paid plans for enterprise users with demanding needs, providing features like a larger number of different domains, HTTPS support, premium support and high amounts of data transfer.

With tools such as Yaler – or many others from around the world – getting your Internet-of-Things product ideas to reality is much simpler than you can imagine. Here at the LX Group we have end-to-end experience and demonstrated results in the entire process, and we’re ready to help bring your existing or new product ideas to life. Getting started is easy – click here to contact us, or telephone 1800 810 124.

Published by LX Pty Ltd for itself and the LX Group of companies, including LX Design House, LX Solutions and LX Consulting, LX Innovations.

The new JN5169 series of wireless microcontrollers from NXP is a range of low-power, high-performance RF microcontroller devices aimed at home automation and remote control, smart energy management, smart lighting and similar Internet-of-Things applications, particularly in consumer products as well as industrial environments.

These system-on-chip devices incorporate an enhanced 32-bit RISC processor and a comprehensive set of analog and digital peripherals along with an IEEE 802.15.4-compliant 2.4 GHz radio transceiver supporting the JenNet-IP, RF4CE and ZigBee Pro wireless networking standards. The 802.15.4/ZigBee network stack includes support for the ZigBee Light Link, ZigBee Smart Energy and ZigBee Home Automation profiles.

The JN5169 platform is Thread and ZigBee 3.0 ready, and it features a new toolchain for software development that offers extensive debugging capabilities while also allowing a reduction of up to 15% in compiled code size.

This family of devices have the ability to connect with up to 250 other nodes in a wireless mesh network, allowing them to be used in a variety of different mesh network and Internet-of-Things applications, from home automation and consumer electronics through to large-scale industrial applications.

There’s three chips in the new family, with different memory configurations to suit a range of applications – such as up to 512 kB of embedded Flash memory, up to 32 kB of RAM and 4 kB of on-board EEPROM. With up to 512 kB of flash on board, there is enough memory available to enable wireless over-the-air firmware updates.

This makes it easy to keep devices up-to-date with new features and security updates without the cost of additional external flash and without the need to replace or remove hardware devices in the field as new software updates are released.

The JN5169 is equipped with hardware peripherals to support a wide range of applications, including an I2C interface, an SPI port which can operate as either master or slave, up to 8 ADC channels with a built-in battery voltage monitor, a temperature sensor and support for either a 100-switch keyboard matrix or a 20-key capacitive touch pad.

The device also incorporates up to 20 digital I/O pins, a 128-bit AES security processor and integrated support for an infrared remote control transmitter, allowing remote control of devices such as air conditioners that use an infrared remote control.

Power use is incredibly low – the JN5169 series offers a very low receive current of just 14 milliamps, or as low as 0.6 micro amps in sleep mode – helping to keep standby power consumption low in household products such as smart lighting and to enable extended operation from small batteries in portable, battery-powered applications.

Furthermore, with a programmable clock speed capability – the JN5169 series can minimise power consumption in power-sensitive, battery-powered applications. Despite these strong energy efficiency features, an on-chip +10dBm power amplifier provides the JN5169 series with a transmission range that is double that of NXP’s existing RF home automation solutions, while drawing just 20 milliamps of current in transmit mode.

This is 40% lower than similar products currently on the market, according to NXP. Antenna diversity is also supported, maximising wireless performance and range while minimising energy use. NXP is also offering a series of new reference designs for network-connected smart lighting solutions based around the JN5169, including white, tuneable white and RGBW colour-programmable Internet-of-Things lighting solutions.

These smart lighting reference designs are complemented by a range of other reference designs from NXP such as wireless switches, wall panel controls, smart plugs, IoT sensors and gateways, along with cloud services for controlling them that will be offered by NXP’s partners, making up a complete Internet-of-Things ecosystem.

Along with the use of the highly integrated JN5819 system-on-chip, these reference designs incorporate innovations such as the use of oscillator crystals rated for 85 degrees C rather than more expensive crystals specified for operation up to 125 degrees C.

Innovative hardware and software techniques incorporated in the JN5819 family allow the clock to be stable in high-temperature environments where these cheaper crystals are used. Design innovations such as these mean that NXP’s JN5169-based smart lighting reference designs have a reduction in total hardware cost of up to 25% compared to similar products on the market.

The JN5169 series also offers innovative solutions to the problem of setting up and commissioning IoT products in a user-friendly and secure way. These devices support near-field communications for device commissioning, making it easy and intuitive to provision new devices and set them up on the network with just a tap on an NFC-enabled smartphone or other device.

Using NFC connectivity for device commissioning is convenient and it also offers security benefits, allowing devices to be easily yet securely paired without broadcasting network details over the air.

This new JN5169 chipset from NXP will offer a new dimension in wireless home automation, and here at the LX Group we’re ready to bring your products to life. Getting started is easy – click here to contact us, or telephone 1800 810 124.

Published by LX Pty Ltd for itself and the LX Group of companies, including LX Design House, LX Solutions and LX Consulting, LX Innovations.

The almost-exponential rise of Internet-of-Things platforms has led many observers and marketplace participants to consider if there are too many disparate or incompatible systems being released, and thus are starting to consider an open-source IoT platform as an option to allow for third-parties to integrate their own products into these new platforms.

Therefore the launch of IoTivity – a new open-source software framework and standards project is of great interest to the IoT community. IoTivity aims to enable seamless device-to-device interoperability to address the needs of the growing Internet of Things industry.

This means promoting and certifying open standards among IoT device manufacturers, allowing billions of IoT consumer products from a wide variety of vendors to be compatible and interoperable with each other.

After launching last year with promises of tackling the problem of device-to-device discovery and communication between consumer IoT products from different vendors, the Open Interconnect Consortium (OIC) has recently launched the initial version of their IoTivity standard and its open-source reference implementation. IoTivity is sponsored by the OIC and hosted by the Linux Foundation.

The project will be governed by an independent steering group that liaises with the OIC, whose project charter is to develop and maintain an open-source implementation that meets OIC’s specifications and passes their certification process – which everyone can work off as an open-source reference platform.

IoTivity aims to be a way for connected IoT products to share information on what they are and what they can do, enabling interoperability of devices from different manufacturers. For example, a smart IoT lamp that supports IoTivity may be able to tell an IoTivity-enabled TV that it is a lamp and it can turn on and off, and dim or change colours, in response to messages over the network.

The TV might therefore be able to use this information to automatically dim the lights when it is turned on. Devices can use this information to provide notifications or communicate information via “output” devices, to control other devices, or to use information collected from sensors and “input” devices.

IoTivity is intended to play a middleware role, somewhere in between the network or radio hardware in a device and the higher-level user applications that control a device. It’s designed to work smoothly and interconnect IoT products and devices in a way that “just works” for consumers – and without adding a lot of extra burden to software development for device manufacturers.

Consisting of both a standard that will be implemented in the firmware and software of IoT devices, and a testing and certification process that allows consumers to choose devices with confidence that their IoT products from different vendors can work together.

In the next few months the OIC aims to finalise and release a version 1.0 standard specification, and at the same time as this official release of the specification the IoTivity project will release a full open-source codebase which is a reference implementation of that specification (rather than the preview release previously available).

The founders of the OIC believe that an industry-standard specification, a reference software implementation, and a commitment to open-source are necessary to drive true interoperability across the growing IoT industry.

With this in mind, the IoTivity software framework is open-source under the Apache 2.0 license. The founders also believe that true innovation can happen most effectively when multiple parties come together to develop the source code in an open way, under an open-source governance process, which is why the Linux Foundation is involved.

Interested developers can get started learning about IoTivity today, by downloading and exploring the current IoTivity preview release. IoTivity is open to everyone, and OIC membership is not a requirement to participate in this open-source project. However, interested companies and developers working with IoTivity and interoperable IoT solutions are encouraged by the OIC to consider if membership in the consortium is right for them.

The IoTivity framework consists of four key components – including device and resource discovery, where IoTivity supports multiple discovery mechanisms for devices and resources both in proximity and remotely, and data transmission – where IoTivity supports interoperable information exchange and control between devices based on a messaging and streaming model.

IoTivity’s data management component supports the collection, storage and analytics of data from various resources across the IoT network, and IoTivity device management aims to provide a one-stop-shop that supports the configuration, provisioning and diagnostics of IoT devices on the network.

This allows a vast number of sensors and “things” to be easily configured, set up on the network and connected to each other, in a way that is easy for all users including home consumers.

The IoTivity framework APIs expose the framework to developers, and are available in several languages and for multiple operating systems. These APIs are based on a resource-based, RESTful architecture model, and API references are available for each release along with additional information on the IoTivity website and Wiki.

IoTivity aims to operate across all operating systems and network protocols, eventually, with current APIs, examples and support documentation available for Ubuntu Linux, the Arduino platform and the Linux-based Tizen operating system for consumer appliances.

Over the next few months, the IoTivity will offer great promise for an open-source Internet-of-Things – and success will be predicated on the amount of industry take-up. However IoTivity is only one of many platforms that you can harness for IoT product success.

To meet your IoT goals, the LX Group team can help you take your Internet-of-Things idea from the whiteboard to the white box. Getting started is easy – click here to contact us, or telephone 1800 810 124.

Published by LX Pty Ltd for itself and the LX Group of companies, including LX Design House, LX Solutions and LX Consulting, LX Innovations.

Not only here in Australia but in parts of the USA and other countries, cellular providers are closing down their 2G GSM network to reallocate spectrum to their faster UMTS 3G and LTE wireless networks.

This shutdown will have a great effect on existing cellular M2M applications as a large percentage were designed around inexpensive GPRS modules – or before UMTs was available. Soon all these devices will be rendered inoperable and will need to be redesigned or replaced with radio hardware that can access the newer cellular networks.

There are many chipsets and modules to choose from, and one new example is the Colibri LTE Platform from Sequans Communications – a chipset solution for mobile LTE (commonly marketed as 4G LTE) cellular connectivity, specifically aimed at Internet-of-Things and M2M applications.

Colibri LTE is a part of the Sequans Streamlite LTE family of chipset products for 4G connectivity in IoT applications, designed for use in devices such as embedded Internet-connected sensors requiring wireless cellular connectivity, tablets, mobile routers or other portable devices.

Their LTE chipset is designed to support Category 4 LTE user equipment, providing a downlink rate up to 150 Mbps and an uplink rate up to 50 Mbps, providing plenty of bandwidth for current and future applications.

The Colibri platform comprises dedicated ICs for the RF platform and the baseband processor, an integrated IoT applications processor in the baseband IC that runs Sequans’ carrier-proven LTE protocol stack, an IMS (IP Multimedia Subsystem) client, and a comprehensive software package for over-the-air device management and packet routing.

Colibri have designed their products with optimisations for IoT and M2M applications in mind – providing low power consumption and high performance at a relatively low cost. This enables an affordable connectivity for mass-market IoT and M2M products.

Furthermore, the high-level integration and highly efficient architecture provide a strong balance of features and performance while achieving very low price points for cost-sensitive M2M and IoT applications.

Colibri’s software suite is based on more than a decade of proven field experience. It is running in major 4G deployments around the world and is one of the most mature solutions in the global 4G ecosystem. It includes the entire LTE Release 10 software stack along with the drivers and host applications required for a complete 4G system.

There is much more than just data – as Colibri supports VoLTE (Voice over LTE) and Wi-Fi SoftAP as well as Active Interference Rejection (AIR) technology – which is an innovative and powerful interference mitigation algorithm implemented on all Sequans LTE platforms.

AIR has been tested and proven at both the system and link levels and has been shown to significantly improve user experience and increase network capacity, especially near the cell edge where signal is weak.

For designers of embedded devices in IoT and M2M applications, the Colibri EZ-Link LTE hardware modules offer complete, single-mode LTE solutions based on the Colibri chipset and platform, simplifying integration and shortening the time to market for the development of hardware devices and products with cellular connectivity.

These modules are ideal for adding LTE connectivity to embedded devices and the ever-expanding array of new types of IoT products now going wireless for the first time. EZLink LTE modules come pre-tested, pre-integrated and pre-certified for easy drop-in integration into your design, with IoT-friendly interfaces, LP-DDR SDRAM, embedded boot Flash and power management included.

These compact hardware modules, available in either the M.2 PC card form factor or an ultra-small surface-mountable LGA form factor, are based on the Colibri LTE chipset platform and include all the other elements necessary for a complete LTE modem system – allowing for a simplified, cost-effective, all-in-one solution for adding LTE connectivity to numerous types of IoT, M2M, consumer electronics and mobile computing devices.

These modules incorporate the Colibri LTE platform along with all the other elements required for a complete LTE modem system, including an LTE-optimised transceiver, a complete dual-band RF front-end for LTE bands 4 and 13, and key peripheral interfaces, all in a single compact package.

Voice and data are supported – including Voice over LTE, Wi-Fi SoftAP, and all major operating systems such as Windows, Android, ChromeOS, Linux and MacOS. Interfacing with hardware is easy thanks to support for a wide variety of hardware interfaces – including USB 2.0, HSIC, SDIO, SPI and high-speed UART.

According to Sequans, the availability of these powerful and compact yet low-cost chipset solutions for 4G LTE, already certified for use with Verizon Wireless in the United States, the world’s leading LTE network, will accelerate adoption of single-mode LTE across the whole spectrum of IoT and M2M applications.

Game-changing efficiencies built into the Colibri platform mean that the costs of embedded LTE modules are now at or below 3G costs for the first time, making the move from 3G to the high bandwidth of 4G/LTE connectivity very attractive in a range of embedded mobile, M2M and IoT applications where the appropriate Telco network infrastructure exists.

Colibri is just one of many UMTS and LTE wireless options available for your new or existing Internet of Things application, and here at the LX Group our team can help you move past the 2G shutdown and enable longevity for your products. Getting started is easy – click here to contact us, or telephone 1800 810 124.

Published by LX Pty Ltd for itself and the LX Group of companies, including LX Design House, LX Solutions and LX Consulting, LX Innovations.

The exponential growth of the Internet-of-Things marketplace is encouraged by new platforms to host prospective products and data – and new player to the scene is Cloudplugs – an end-to-end platform that provides cloud computing services for Internet-of-Things applications – with features including a trigger management engine, geolocation engine, database and storage engine and a billing engine.

Their new SmartPlug Apps cloud-based IDE allows the development of CloudPlugs IoT applications from the cloud, along with cloud-based automation that enables the remote deployment, configuration, update and management of devices.

IoT applications can be developed in JavaScript using the SmartPlug cloud based IDE, or with your favourite JavaScript development tool, anywhere, any time, on any browser. Whether you are a home user, an appliance manufacturer or a service provider, the CloudPlugs cloud service allows you to develop, deploy and manage as many as thousands of Internet-connected devices quickly without the need to develop and manage your own IT infrastructure to support them.

CloudPlugs offers the SmartPlug agent as the backbone of their IoT platform, which they claim is the most powerful and secure agent available for IoT devices. It is a secure, robust and lightweight yet powerful software agent with full lifecycle management capabilities for IoT gateways and other devices – enabling secure and efficient communications with the CloudPlugs IoT platform through their PlugNet protocol.

The platform supports local communications through multiple interfaces and protocols simultaneously, enabling devices with different physical interfaces and protocols to communicate. Devices and gateways powered by SmartPlug can easily exchange data with and control other devices, and scripts can be developed in the cloud and deployed to thousands of SmartPlugs with one click.

CloudPlugs offers maximum flexibility by delivering its end-to-end IoT connectivity platform as a subscription service as well as for in-house deployments. There is no limit on the number of prototype virtual devices that you can create and test in CloudPlugs, even with a free account.

The free account allows you to get started with free evaluation or hobbyist use of CloudPlugs, with up to 10 physical devices, up to 100Mb of storage and 100Mb of bandwidth per month. This is designed to allow individuals or small businesses to use the CloudPlugs platform to manage IoT devices as well as providing a free evaluation platform for larger users.

Moving up to a paid business subscription allows you to use as many devices as you want, with as much storage and bandwidth as your devices need, and a pay-as-you-use elastic pricing model which scales as your IoT business grows – where you’re only paying for the bandwidth and resources you’re actually using.

You can also choose a white-label CloudPlugs deployment in order to deliver IoT services, devices and management dashboards to customers under your own brand, along with in-house deployment on your own servers if desired for security or compliance reasons.

CloudPlugs uses a flexible and powerful MQTT-based publish-and-subscribe architecture, where things and applications subscribe to channels to publish their information and to read or issue control commands. Channels are data structures that allow things and applications to publish and to read data. Things or applications publish data into channels, or subscribe to channels to read data.

Channels can be created manually through the platform, or created dynamically. This dynamic management of channels means that they will automatically disappear if all the data published to that channel is deleted and will be created on-the-fly as data gets published to a newly specified channel by devices, removing the need for manual and inflexible configuration of channels.

Your devices and applications communicate with each other by subscribing to the same channels through MQTT, REST, WebSockets or the PlugNet protocol. Devices or “things” that use MQTT can connect and exchange data with other things that use the MQTT or WebSockets protocols, and if you’ve already developed existing products or devices that communicate using MQTT then it’s easy to get started connecting them to the CloudPlugs platform by modifying the MQTT logic to communicate to the CloudPlugs backend service.

To get started connecting your IoT things to the CloudPlugs platform, you need a CloudPlugs account – along with an appropriate hardware platform such as an Android device, an Arduino, Raspberry Pi, Libelium Waspmote or many others. Next you’ll need a software library that will be integrated with your controller firmware, and these are supplied for free download from CloudPlugs to cover a range of supported devices.

A wide range of different hardware and software platforms can easily and quickly be connected to the CloudPlugs platform using a lightweight REST API, which allows for almost any contemporary or future hardware platform to be integrated into the system.

CloudPlugs libraries are designed to give developers maximum flexibility and choice for the development and integration of applications to monitor and manage their IoT devices, and libraries are available that enable the development of software for integration with CloudPlugs using a range of different programming languages and environments – including Node.js, JavaScript, C, PHP, Android, Arduino and Objective-C.

These supported platforms cover a wide range of applications, including networking, development on embedded platforms such as the Arduino, Raspberry Pi and BeagleBone, and the Objective-C development of iOS apps.

Getting started with Cloudplugs can be easily achieved – for any purpose from initial experimenting with the Internet-of-Things to a full system. Here at the LX Group we’re ready to partner with you to meet your Internet-of-Things product goals, and can work with your ideas and more to bring them to reality. Getting started is easy – click here to contact us, or telephone 1800 810 124.

Published by LX Pty Ltd for itself and the LX Group of companies, including LX Design House, LX Solutions and LX Consulting, LX Innovations.

As smartphone use becomes prevalent in today’s society, they can not only be used for voice and data communication – later models equipped with Bluetooth LE (Low Energy) can also receive messages over a short range from new Bluetooth LE-equipped devices known as Beacons.

As always Google is on the forefront of Beacon technology, and their new beacon platform enables contextual experiences for users through mobile interactions with Bluetooth Low Energy (BLE) beacons. These beacons are simple, low-power devices which send one-way BLE signals that can be read by nearby Bluetooth-enabled devices.

Beacons can be deployed in fixed places such as businesses, museums, and bus stops, and also on movable objects such as vehicles. Deploying BLE beacons in your venue or attaching them to physical assets that you manage is a good way to give users a location-aware experience via their mobile devices, with contextual and timely information for users which is relevant to their local environment.

Google’s beacon platform consists of several components, starting with the beacon hardware. Lightweight and power-efficient BLE beacons transmit Bluetooth beacon frames, such as Eddystone frames, at a defined interval.

The Proximity Beacon API can be used to register any beacon that supports Eddystone, the iBeacon specification or the AltBeacon specification, so you’ve got a wide range of compatible hardware choices.

The next key component is Google’s Eddystone, an open beacon format that can communicate with Android and iOS devices, aimed at improving interoperable BLE beacon-based applications and services. Eddystone is designed with transparency and robustness in mind, building upon lessons learned from working with industry partners in existing deployments, as well as the wider beacon user community, and it’s released under the Apache 2.0 open-source license.

The Eddystone protocol specification defines a BLE message format for proximity beacon messages, and it describes several different frame types that may be used individually or in combination to create beacons that can be used for a variety of applications.

Different frame types can typically be interleaved by a single beacon, for example 100 transmissions of an Eddystone UID frame for location identification followed by one Eddystone TLM telemetry frame for a health status check, then a repeat of that cycle.

The final key component of the beacon platform is the Proximity Beacon API, which allows you to administer data associated with the beacons that your application uses. The Proximity Beacon API allows you to manage your beacons, register and update beacons, add “attachments” to beacons via the cloud, and monitor the status and health of beacons by monitoring parameters such as battery level.

To make it easy to learn about the Proximity Beacon API and to get started using it, Google provides proximity beacon sample apps for both iOS and Android mobile platforms.

The Proximity Beacon API allows you to manage data associated with your BLE beacons using a REST interface. The Proximity Beacon API allows you to register beacons to the cloud, with beacon attachments hosted on Google’s servers.

After you register a beacon with the Proximity Beacon API you can associate attachments that are stored in the cloud, which means you can manage and update the information associated with each beacon even after the beacons are deployed.

The Proximity Beacon API, in combination with Eddystone’s telemetry broadcast type, helps you to manage your beacons and ensure that your beacon fleet is behaving as it should. Eddystone-TLM frames allow your beacons to report their status to client devices.

For most beacons, these frames are transmitted at regular intervals throughout the device lifetime. You can use the diagnostics and monitoring tools in the Proximity Beacon API to get health statistics from the beacon network and to identify any erroneous behaviours, such as a beacon with a low battery, allowing you to allocate maintenance where it’s needed with beacons in the field, ensuring that your users have a consistently great experience.

You can use attachments to provide data which is specific to one or more beacons, enabling your apps to react to the user’s location. Since attachments are stored in the cloud, the Proximity Beacon API provides a scalable, low-latency way to manage and update the data associated with your deployed beacons, ensuring that your users always see the latest available data and eliminating the need to manually re-provision beacons.

After attachments have been added to beacons using the Proximity Beacon API, you can retrieve them in your app using the Nearby Messages API.

Using Google’s Nearby API, you can extend the functionality of Eddystone and the Google Beacon Platform, allowing your iOS or Android app to detect nearby beacons and execute their attachments, giving users a rich and interactive proximity-based experience.

Users’ devices can use Bluetooth beacons as a signal to improve other location-based tools, such as the Place Picker, which assists users in selecting nearby locations of interest such as local businesses. With the Nearby API, you can build apps that detect beacons and retrieve messages that you wish to associate with each beacon and process within your app.

Examples could include showing the bus schedule when a user is waiting at a bus stop or providing ticket availability at a theatre kiosk. When you’ve added an attachment to your beacon using the Proximity Beacon API, the Nearby Messages API allows your mobile app to retrieve the attached message or content when the user’s device detects the beacon.

Here at the LX Group we’re ready to partner with you to realise your Beacon requirements, Internet-of-Things ideas and more to bring them to reality. Getting started is easy – click here to contact us, or telephone 1800 810 124.

Published by LX Pty Ltd for itself and the LX Group of companies, including LX Design House, LX Solutions and LX Consulting, LX Innovations.

The exponential increase of chipsets aimed at the Internet-of-Things market has offers a huge variety of new IP-based products to choose from, which may cause the appearance that older standards such as ZigBee are waning in popularity. However, nothing could be further from the truth, and one example is the new Kinetis KW2x microcontroller family from Freescale Semiconductor.

The Kinetis KW2x is a series of wireless system-on-chip devices aimed at meeting the increased processing and memory requirements associated with applications that use advanced 802.15.4/ZigBee stacks and communications standards in modern Internet-of-Things applications, such as ZigBee Smart Energy 2.0 and the ZigBee Internet Protocol specification, today and into the future.

These devices integrate a 50 MHz ARM Cortex-M4 processor with an 802.15.4-compliant 2.4 GHz RF transceiver on a single chip, providing a low-power, compact, single-chip integrated solution for 802.15.4/ZigBee wireless mesh network applications in home automation, healthcare, smart energy and consumer electronics.

The KW2x family expands on the successful Kinetis microcontroller portfolio based on the ARM Cortex-M4 core, with the software protocol stacks, development tools and IDE all compatible with the existing family of Kinetis MCUs and the ZigBee protocol seamlessly integrated into Kinetis software development tools – allowing you to rapidly get started programming and creating wireless mesh networks for your embedded and IoT applications.

Specifications are rich, as the Kinetis KW2x family integrates a class-leading 2.4 GHz RF transceiver, a Cortex-M4 core and a robust feature set for a powerful, secure and low-power IEEE 802.15.4 wireless solution all integrated on a single die.

These wireless MCUs offer up to 512 KB of flash, 64 KB of RAM and up to 64 KB of FlexMemory. Dual PAN support allows this platform to simultaneously participate in two ZigBee networks, making it useful in complex ZigBee installations or in router or gateway applications.

The KW2x family supports the ZigBee IP network stack, the RF4CE standard, and the ZigBee Home Automation, ZigBee Smart Energy 1.x and ZigBee Smart Energy 2.0 ZigBee application profiles, enabling a broad range of applications.

Along with reducing product size and reducing bill-of-materials cost with a highly integrated solution – the KW2x product line offers strong power efficiency and long battery life in portable, battery-powered Internet of Things applications.

The radio subsystem supports the 2.4 GHz ISM band as well as the 2.36-2.4 GHz MBAN (medical body-area network) band, and offers high power efficiency for its transmit power, along with fast antenna diversity, transmit power up to +8 dBm and a receiver sensitivity of -102 dBm, offering very long communication range. The microcontroller provides enough memory to run complicated protocol stacks on a single IC while also providing plenty of space for user application code.

According to Freescale, this family of devices provides greater processing performance and larger flash and RAM options compared to other similar devices on the market, helping smart IoT appliances and consumer automation products avoid obsolescence as 802.15.4/ZigBee specifications evolve, with the ability to meet future standards and new ZigBee application profiles via firmware updates on the same hardware.

The Kinetis KW2x wireless MCU family provides plenty of Flash and RAM, allowing engineers to quickly upgrade products with new features, including over-the-air remote firmware updates, without the need for costly and relatively difficult replacements of the hardware in users’ homes and other installations.

For applications that require more flexibility, the KW2x platform optionally provides 64 kB of “FlexMemory”, that allows users to configure part of the on-chip flash memory as additional flash memory or enhanced EEPROM. This means users can choose how that memory is allocated between program and data storage, for example if extra EEPROM space is desired for storing configuration data.

The KW2x family offers reduced power consumption and an increased RF link budget, along with antenna diversity which improves reliability of the radio link, particularly in environments where multi-path interference is a problem.

The IEEE 802.15.4 2.4GHz transceiver is designed to reduce transmission power where appropriate, and run in a low-power mode when commanded, helping to achieve strong power efficiency. These devices include hardware assisted dual personal area network support, which means that a single device can communicate wirelessly on two different ZigBee networks, simultaneously using two different PAN IDs.

This makes these chipsets attractive for gateway or router applications in home or building automation networks, connecting together different smart energy or home automation networks without the need for multiple radios.

Security has not been forgotten – as Freescale have integrated advanced security features usually found in higher-end processors, providing security and cryptographic functions including key generation, secure memory and tamper detect functionality.

Secure Flash protects the code and data from unauthorised access or modification, while tamper detection can identify events and asynchronously erase secure RAM, generating an interrupt so the application firmware can take additional actions, including a system reset.

A dedicated cryptographic acceleration unit supports a set of specialised operations to improve the throughput of encryption and decryption operations as well as message digest functions. These features address the growing attention and the need for strong security in embedded SCADA and automation systems as well as connected Internet-of-Things consumer products in the home.

As leaders in Zigbee-based product development, we’re ready to work together with you to develop new product designs, or reviewing and upgrade any existing versions with you for your success. Getting started is easy – click here to contact us, or telephone 1800 810 124.

Published by LX Pty Ltd for itself and the LX Group of companies, including LX Design House, LX Solutions and LX Consulting, LX Innovations.

The Experiential Living Lab for the Internet of Things (ELLIOT) project is a European research project that aims to develop an experiential platform for Internet of Things research, where users and the public are directly involved in co-creating, exploring and experimenting with new ideas, technologies, potential market opportunities and concepts related to IoT applications and services – particularly where UX and user interaction design is concerned.

The ELLIOT program is designed to support research into the potential impact of the IoT and other emerging information technologies in the context of what the ELLIOT consortium calls the “Open User Centred Innovation” paradigm and the “Living Lab” approach.

Established by a consortium of European universities, institutions and private industries – ELLIOT is a three-year research program built around four main aims – firstly, to study and develop a set of “KSB” (Knowledge, Social and Business) Experience Models integrating social, technical, economic, legal and ethical dimensions related to the use of emerging IoT technologies and services into a single, holistic meta model.

Secondly, the project aims to design and develop an “Experiential Platform” where these KSB Experience Models will be implemented to allow people to explore and experience socially-enabled IoT technology and other information technology including the validation of this technology and evaluation of its impact. This experiential platform will operate as a knowledge and experience-gathering testbed environment in the context of the IoT.

Thirdly, the project aims to explore the potential of collaborative UI design techniques and tools such as serious gaming, participative requirements engineering and requirements validation in the context of the IoT.

Finally, one of the core objectives of the ELLIOT research program is to experiment within a series of “Living Labs”, each composed of a physical space, a information space architecture and a social community of users of that space. The project is expected to facilitate increased adoption of IoT technologies in Europe and to enhance the potential of collaborative industry, academic and public-sector innovation for the discovery of novel IoT applications, services and business opportunities which bridge the gap between these emerging technologies, industry stakeholders and the public.

The ELLIOT project’s “experiential” approach has been explored and its technology platform experimented with in different use-cases belonging to six different sectors, namely Wellbeing, Logistics, Environment, Retail, Remote Medical Assistance, and Energy-Efficient Offices, in order to validate the capacity for users and the public to co-create innovative and useful IoT-based services in these domains.

Starting from these use-cases, it is expected that the ELLIOT project will contribute to a new, user-centric approach to novel product and service development with IoT technologies, while also being applicable to IT products and services more generally, through the use of this “Experiential Platform” and the progressive extension of the use of this platform into other use-cases and industrial sectors.

The engagement of users in the research and innovation process behind new products and services is attracting more attention in technology design today, across many industrial sectors. This is especially true in business domains where users and citizens have a crucial role in the adoption of new services that they collaboratively create on top of new information and communication technologies.

This is particularly relevant when it comes to the Internet of Things, finding use-cases for IoT technologies, along with researching the markets for new IoT products and services. Examples of business domains that ELLIOT has identified as important, where the project aims to contribute valuable research, include “eHealth”, “eInclusion”, “eManufacturing”, “eParticipation” and ICT for Environment as well as ICT for Energy.

To explore, to experiment with, and validate the experiential research and innovation approach that ELLIOT applies, several scenarios have been conducted in different “Living Labs”, each implementing different kinds of IoT experiences. These Living Labs are composed of a physical space such as a building, a civil architecture, a laboratory, an urban or rural zone, equipped with advanced ICT infrastructure for communication and collaboration such as wired networks, wireless terrestrial networks or wireless satellite networks.

The need for this user-participative approach is increasingly being recognised, and the “Living Lab” model is becoming more popular. A “Living Lab” is an open innovation environment in a real-life setting in which experiential research and innovation is supported by the availability of a technology platform for designing innovative applications and services.

The European Network of Living Labs comprises 274 diverse and mature “Living Labs” covering a wide range of application domains. Most of them are already operational in different domains spanning from eHealth to Energy Optimisation and Efficiency, from Intelligent Mobility to Inclusion of the elderly and disadvantaged people and Rural Development.

The project also aims to identify, experiment with and explore IoT-oriented user co-creation tools and techniques. Co-creation, as it’s defined by ELLIOT, in an IoT-oriented environment is akin to the co-creation processes of software development which is very common, for example, in the open-source software development community.

Transferring the experience of the open-source software movement into an IoT-oriented “user co-creation” process through practices such as gamification and “serious gaming” is another approach that ELLIOT is investigating with the potential to enhance IoT-relevant collaborative development capabilities and to accelerate take-up and adoption of these practices.

We look forward to the results and news from the ELLIOT program, however here at the LX Group we’re always working on current and new IoT-based products for a wide range of clients. If your organisation is considering new product design, or reviewing an existing version – your next step is to contact the team at the LX Group where we not only share your passion for embedded hardware and the Internet-of-Things – our team of solutions architects, engineers and specialists is ready to partner with you for your success in the IoT marketplace. Getting started is easy – click here to contact us, or telephone 1800 810 124.

Published by LX Pty Ltd for itself and the LX Group of companies, including LX Design House, LX Solutions and LX Consulting, LX Innovations.

Here at the LX Group we’re always interested in new Internet-of-Things platforms, and the latest discovery by our team is a new entrant called Zetta. This is a new open-source Internet-of-Things platform that is built on Node.js, and designed for creating IoT servers and networked applications that run across multiple distributed devices, computers and the cloud.

Zetta aims to create an “API-First” Internet-of-Things platform – where any connected physical device and every Internet-connected “Thing” is exposed as an API, with REST APIs, WebSockets and reactive programming combined into a platform that is well suited for assembling many devices into data-intensive, real-time sensor networks or other Web-connected IoT applications.

Unlike other IoT platforms, Zetta servers can run in the cloud, on PCs, or on many different types of embedded hardware platforms and single-board computers such as a BeagleBone or Raspberry Pi.

With Zetta you can link these devices together, with each other and with cloud platforms such as Heroku, to create geo-distributed networks with an architecture that is optimised for data-intensive, real-time Big Data and streaming applications.

Furthermore, Zetta allows you to observe and react to device behaviour using code and using visualisation tools so that you gain actionable insights and take insightful actions based on physical data from IoT devices. You can also stream data into machine analytics platforms like Splunk.

And although you can run Zetta on lightweight hardware off the cloud, the platform allows you to assemble smartphone apps, device apps and cloud apps together into large, complex and adaptive “systems of systems” that operate at scale in the physical world of home automation, smart transportation, wearable computing and more.

Zetta also supports lightweight embedded microcontroller hardware such as the Arduino and Particle Core. Zetta communicates with these types of devices and exposes every device in the network, including these small devices, through a REST API both locally and in the cloud.

In a typical Zetta deployment a Zetta server will run on a hardware hub such as a BeagleBone Black, Intel Edison, or Raspberry Pi. This hardware hub device connects to other devices, and hosts the Zetta server itself which coordinates interactions with devices and generates HTTP APIs that an API consumer can interact with.

A typical Zetta deployment is built around a hub-and-spoke model, where the spokes are constrained devices and the hub devices have more computing power. For example, Zetta will run on a device such as a Raspberry Pi which is the hub, and this hub may be connected to “spoke” devices such as an Arduino.

End-node devices can be connected using Zetta even when these devices are low-cost, power efficient microcontrollers that don’t have the processing or memory capacity to run Zetta directly. As Zetta is built in pure JavaScript on node.js, and while the hub device needs to support node.js – the endpoint hardware devices do not.

Zetta software servers have the capability to run on the end-node hardware device if this device has the capacity, on a nearby hub device such as a BeagleBone or Intel Edison, or in the cloud – and these Zetta servers are the same wherever they run.

As well as the Zetta server running on the hub hardware, another Zetta server lives in the cloud, using the exact same node package as the hub server – and the Zetta server on the hardware hub will connect to the server in the cloud. Zetta will then expose an API to any consumers at the cloud endpoint.

When the “spoke” device communicates with the hub, there are Zetta drivers that mediate between different protocols. For example, a Zetta driver could talk serial between the hub and the spoke device, and mediate that serial protocol into a Web API.

These drivers are responsible for interacting with the device on the physical level, providing device models that are then taken and used to generate HTTP and Javascript APIs for use in Zetta, and Zetta will mediate from HTTP to the particular protocols used for hardware devices.

There are existing drivers published for a wealth of different hardware and interoperability applications, such as serial device connectivity for any platform, connectivity with consumer devices such as the Phillips Hue and the Belkin Wemo, serial SMS text message connectivity using inexpensive SIMCOM SIM800 GPRS modules, connectivity with the Google Glass and the Pinoccio mesh network platform – to name but a few.

Along with device drivers, Zetta “Scouts” are another key component of the Zetta server, and these serve as a discovery mechanism for determining what devices are on the network and whether any devices require system resources to speak a specific protocol.

Scouts will search for devices using a particular protocol, and report this information back to Zetta. Scouts can also use information such as a MAC address to fingerprint devices, identifying whether or not Zetta has interacted with the device before, and ensuring any relevant data such as security credentials are seamlessly provided by the server when interacting with that device again.

If the Zetta hub device has connectivity directly to the Internet (with its own external IP address) then Zetta will communicate directly with cloud services such as Heroku via simple HTTP APIs and WebSockets. If the hub is behind a router, then the z2z protocol is used.

Zetta servers allow for establishing a secure tunnelled link between two servers, which helps take care of network configurations and mechanisms such as firewalls that can traditionally make setup and provisioning difficult for Internet-connected IoT cloud services.

As Zetta can run on a wide range of inexpensive hardware, it can certainly be considered as as low-cost entrant to the Internet-of-Things platform market.

If this is of interest to you, your next step is to contact the team at the LX Group where we not only share your passion for embedded hardware and the Internet-of-Things – our team of solutions architects, engineers and specialists is ready to partner with you for your success in the IoT marketplace. Getting started is easy – click here to contact us, or telephone 1800 810 124.

Published by LX Pty Ltd for itself and the LX Group of companies, including LX Design House, LX Solutions and LX Consulting, LX Innovations.