If you have IoT devices in the field, it’s really important to have good security on it. Not all hardware devices have for example a TPM chip (they are cheap). With Windows 10 IoT you can use this chip to have a safer device in the field. With Windows 10 IoT you have the following TPM ‘software’ options:
Discrete (L2C or SPL)
TPM Simulator-dev tool
With TPM you can secure your IoT Device with the following options:
Secure boot mechanism and the possibility to enable remote attestation with ‘Measured Boot’
Bitlocker, the same as on your Windows 10 device you can use Bitlocker on your IoT device. With Bitlocker you can protect your data with strong encryption and secure key storage.
Here in the Netherlands we are lucky to have Internet of Things networks available. We have a complete coverage of Sigfox from Aerea and hopefully this year coverage of LoRa from KPN. Off course we also have The Things Network (Lora based) community network in some cities.
All these ‘standards’ have great functionality for IoT sensors:
Long distance; several km’s
Low energy for sensors
Indoor coverage (not always)
Last week T-Mobile in the Netherlands announced an extra IoT network named NB-IoT (NarrowBand-IoT). This standard is based on the 3GPP (3rd Generation Partnership Project) telecommunications associations, like GMS, UMTS and LTE.
I don’t know if it is great again that an extra operator is creating a new IoT network or not, they all use different standards now.
We know that not every (new) sensor will support every standard that is on the market. So sensor makers must think before releasing with network(s) they will support. I think it would be much better if we had one standard for sensor communication. So we can focus to have the best and cheapest sensors. Yes, I know that completion is also good, but the competition would be better if they all use the same standard like with the telephone market.
I like the idea of the NB-IoT what T-Mobile has launched. It’s based on the current 3G and 4G networks and it’s easy (just software) to add this new IoT network. They will have directly whole covered in the Netherlands, but even better it’s simple to launch in every country. And that would be great for Asset management or other IoT propositions. No big investments in new hardware for T-Mobile and maintain extra hardware. During the launch of the new network T-Mobile showed also a new use case for IoT: Smart Paving Stone. They put a sensor in the paving stone at parking places in a city. The sensor can see if a car is on the parking spot and via an APP a other person can see where a space is available to park. Great use case, because we have a lot of paving stones here in the NL for parking spaces.
What do you think of the several IoT networks? Good or not?
When we work with Azure Stream Analytics, it’s sometimes difficult to do troubleshooting when there is a problem. These week I noticed (maybe it’s there already for a long time) the Diagnostic Diagram in the (new) Azure Portal in an Azure Stream Analytics Job. See below:
After selecting the diagram, you get a great overview what is happening in the Streaming Job. When you are troubleshooting it’s sometimes really difficult to see what is happing in the job:
After selecting a query for example, you see directly the query:
This is a great first step to do better diagnostics on an Azure Streaming Job. I like to see the following also:
Wondering if we starting and stopping the job will be much faster then now. It takes now a lot of time, starting, stopping, checking, starting and stopping
More debugging in the logs of Stream Analytics
Real-time logs in the Azure Portal of running Stream Analytics Jobs
In the next episode I will talk about the debugging to Azure Storage that is currently available.
Like you maybe know Windows 10 IoT has several versions available:
Windows 10 IoT Core
Windows 10 IoT Mobile Enterprise
Windows 10 IoT Enterprise
Windows 10 IoT Core
This free version has no shell, but supports Universal Windows Apps and Drivers. It can run on X86 and ARM devices like the Raspberry PI 2 and 3(only on Insider Build). It is at the moment lot used for proof of concept in my work. The devices are cheap and we don’t need any shell to run other apps on it. This version is really for the small factor devices.
Technical specs: 512MB RAM, 2GB storage
Windows 10 Mobile Enterprise
This version has a modern shell(like Windows Mobile 10), supports Universal Windows Apps and Drivers. It’s focused on mobile device, like handheld scanners, mobile device for credit card payment etc. It’s only supports ARM devices
Technical specs: 512MB RAM, 4GB storage
Windows 10 IoT Enterprise
This version has a full desktop shell. It can run also Win32 apps and Universal Apps. It’s only supporting X86 devices. It is focused on devices that need more capabilities and power of the device
Technical specs: 1GB RAM, 16GB storage
The great thing about these version, if you build an Universal App, it will run on all Windows 10 devices.
Last week I had a presentation at the Microsoft EBC in Brussel for IoT Partners. At this event around 150 people addend from 12 countries in Europe. In the keynote I presented our Smart Building solution as a partner showcase. Here is my presentation: