What we know and Pycom plans
The following is a mashup of information collected online over the last few months, from reliable sources as well as directly from the conversations we’ve had with the various mobile network operators. Many of those conversations are still under wraps (yeah, NDAs and all that) but we have been able to give you a summary of what we think’s happening with LTE-M.
There is SO much going on with LTE-M and it’s everywhere in the world!
THE BASICS: What is LTE-M?
BI Intelligence on communications technologies used shows cellular as the second most used technology for IoT. The progression from 2G/3G/4G for IoT is the migration to LTE-M (NB-IoT or CAT-M1). It is said that NB-IoT will deliver the LPWA component of 5G.
LTE-M is based on 3GPP standard release 13 released ratified in June 2016. It presents a new Category M1 device optimised for the IoT able to address the LPWA connectivity for cellular communications.
Manufacturers of LTE-M products will benefit from CAT-M1 chipsets and module such as the Monarch from Sequans which are optimised for IoT yet giving a reduction of complexity and cost over existing LTE Cat 4/1 modules, also known as 4G.
Similar to other LPWAN networking technologies, products using LTE-M will have longer battery life of up to 10 years when using additional features such as Power Saving Mode and eDRX.
LTE-M can increase signal coverage area by up to seven times, or 20 decibels (dB), compared to existing GSM technology.
In addition, LTE-M gives users extended coverage compared to LTE for IoT devices including good coverage underground and deep inside buildings.
WHAT’S THE DIFFERENCE BETWEEN NB-IOT AND CAT-M1?
There are two different standards under 3GPP Release 13 – NB-IoT and CAT-M1. The key differences are that Cat M-1 has a higher peak data rate as well as time-to-market, while NB-IoT has greater flexibility in spectrum available and modes of operation.
Last year, our partners Sequans wrote a really neat article on LTE-M from an application point of view with a great visualisation of the various cellular networking technologies.
Excerpt from the article here:
Cat M1 defines a 1.4 MHz channel size and throughput of about 375 kbps uplink and 300 kbps downlink; Cat NB1 defines a very small channel size of 200 kHz and 10s of kbps of throughput. While certain applications, such as an IoT temperature sensor, will require only the smallest amount of throughput as available with Cat NB1, other applications, such a health or fitness wearable, transmitting a little more data, will need the higher throughput of Cat M1.
Connected mobility is determined by the ability of a technology to do handover between cells. Cat M1 supports handover (except in the coverage enhancement mode), but Cat NB1 does not. If your application is mobile, such as a health or fitness band or other wearable, Cat M1 is needed; if stationary, as in the case of an industrial sensor, then Cat NB1 will do.
For data transmissions above a certain level (hundreds of bytes) Cat NB1 will consume more power than Cat M1. The higher Cat M1 throughput allows devices to get to sleep faster between transmissions, thus saving power. This means that Cat NB1 is the best technology for simple sensor and metering applications, transmitting in short bursts, but that Cat M1 is the best fit for applications needing to transmit more than a few hundred bytes of data.
Can your application tolerate latency? With Cat M1 latency is similar to the latency in a typical Cat 1 deployment, approximately 10-15 milliseconds, but with Cat NB1, latency is greater and can range from 1.4 seconds to as much as 10 seconds in some deployment scenarios. For sensor and metering applications this is not an issue and Cat NB1 is suitable, but for latency intolerant applications such as warning or alarm systems, Cat M1 is needed.
Cat M1 supports VoLTE while Cat NB1 does not. Certain IoT applications benefit from VoLTE capability, including alarm panels and personal safety devices, indicating Cat M1 is required.
Take a look at the full article here: http://www.sequans.com/narrowband-lte-which-apps-need-cat-m1-and-which-need-cat-nb1/
HOW DO WE GET TO LTE-M?
Enabling LTE-M on Cellular Mobile Networks.
In 80% of cases it’s a question of updating the 4G base stations most of which are supplied by Huawei or Ericsson.
This does mean that, without a base station / hardware update by the network operators, the LTE-M service will be limited to where there is current 4G services available. Here’s the current penetration of 4G.
WHAT LTE-M NETWORKS ARE IN PLACE TODAY?
Network Roll Out Summary
Ultimately we believe that all network operators will offer both NB-IoT and CAT-M1, but it may be a few years before pan-region networks exist.
There’s been a tendency to roll out NB-IoT in Europe whereas the North America based operators have opted for CAT-M1. As is often the case, the LTE-M networks (apart from the head-to-head competition of who rolls out first and fastest between Verizon and AT&T in North America), we have seen a slight delay in the roll out plans of the various networks. However, once the green light is given for a roll out, it is a matter for switching the LTE / 4G networks via a software upgrade and so the roll out can happen relatively quickly.
There seems to be plans amongst a lot of operators in Europe for networks to be switched on and rolled out by end of 2017 with a view to full commercial deployment starting 2018. Yet, many trials and controlled device roll outs are taking place all over Europe.
Pycom is in talks with 8 operators around the world but due to confidentiality agreements we are not at liberty to give exact details of the plans for each network operator. However, below is an overview of the information in the public domain related to the various operators we know are rolling out. It’s their official plans and also what Pycom is planning.
‘No discussions yet’ doesn’t mean we will not engage with a certain operator. In true Pycom form, we have no exclusivity agreements and so it is more likely a statement of ‘we haven’t been able to engage yet but we most likely will in the future’.
Please note: The roll out plans are continuously updated by the Mobile network operators and it is worth following their news in your region as the below may very quickly become out of date.
Roll out Start
|AT&T||North America||CAT-M1||Testing in San Francisco and is believed to have nationwide North America coverage by end of 2017. Plan to extend network into Mexico by end of 2017.
Our understanding is that Data Plans start at $1.50 per month/device, Volume discounts and discounts for multi-year commitments available.
|Pycom is in talks and aims to add devices to the AT&T network in North America over the course of Q3-Q4 2017.|
|China Mobile||China||NB-IoT||200 site NB-IoT trial completed with ZTE in April 2017.||No discussions yet|
|China Telecom||NB-IoT||Plans to launch NB-IoT services commercially at the end of June 2017.||No discussions yet|
|China Unicom||China||NB-IoT||1000s commercial NB-IoT networks in more than 100 cities during 2017.||No discussions yet|
|NB-IoT||Has rolled out NarrowBand-IoT (NB-IoT) Network across eight countries in Europe Germany, the Netherlands, Greece, Poland, Hungary, Austria, Slovakia, Croatia.
DT is offering customers in Germany a simple device connectivity package called “NB-IoT Access” as well as a more comprehensive deal — under the “NB-IoT and Cloud of Things” banner — that includes device and data management.
|No discussions yet.|
|KPN||Netherlands||CAT-M1||Successful trails in the Netherlands (Q4 2016). Claim to go nationwide by end of 2017||Pycom is in talks to certify for network access. We aim to make it happen Q3-Q4 2017.|
|M1||Singapore||NB-IoT||NB-IoT trial with Nokia completed.||No discussions yet|
|NTT DOCOMO||Japan||NB-IoT||NB-IoT Trials conducted last year. No update on plans for roll-out and deployments at this point.||No discussions yet|
|Orange||France, Belgium||NB-IoT||LTE-M network roll out in France and Belgium completed by end of 2017. Full “Go Live” is expected early 2018.||Pycom is in talks to certify for network access. We aim to make it happen Q3-Q4 2017.|
|Singtel||Singapore||NB-IoT||Launched Assured+ in March 2017. Currently NB-IoT trial with Ericsson.
The network supposedly already supports CAT-M1.
Assured+ will connect devices across existing 3G/4G networks, NB-IoT and LTE Cat-M.
|Pycom is in talks to certify for network access over the course of Q3 and Q4 2017.
|Sprint||North America||CAT-M1||Testing in progress and services go live middle of 2018.||No discussions yet|
|NB-IoT (North America)||Full NB-IoT coverage in the Netherlands as of June 2017.
North America: Already deployed CAT-M1 and will be deploying NB-IoT throughout 2017 and 2018. Launched in Las Vegas already.
|Pycom is in talks in Europe and in the US to certify for network access.
|Telecom Italia||Italy||NTA||NTA||No discussions yet|
|Telefonica||Global||NB-IoT and CAT-M1||Is to deploy NB-IoT and CAT-M1 in Europe and South America||Pycom is in talks to certify for network access.
|Telenor||Nordics||NB-IoT||NB-IoT Rolling our as of late 2017. Dates not defined yet.||Pycom is in talks to certify for network access.
|Telstra||Australia||CAT-M1||Have concluded trials with Ericsson.
Starting 2H 2017. Telstra is set to support their operation across its expansive 4G network which covers over 98% of the Australian population
|No discussions yet Pycom intends to certify for network access.|
|Telus||Australia||CAT-M1||Committed to 5G but starting CAT-M1 roll out activities in the second half of 2017.||Initial contact. Pycom intends to certify for network access.|
|Verizon||North America||CAT-M1||CAT-M1 network switch on as of March 2017, already covering several North America cities claiming to cover 2.4 million square miles already.
Data Plans: $2/month/ device. Customized options available for bulk activations and volume purchases.
|Pycom is in talks and aims to add portfolio to ThingSpace platform and make sure there is good network access. We hope to make it reality Q3-Q4 2017.
|NB-IoT||Spain – Switch on in January 2017)
Ireland – switch-on started ready in summer 2017
Netherlands – started, ready in summer 2017
Germany – starting Q4 2017
Australia – Melbourne NB-IoT network trials concluded May 2016.
|Pycom is in talks to certify for network access. We will most likely be able to offer access to available networks by Q3 2017.|
THE MONARCH CHIP
The Cellular Chip used in FiPy, GPy and G01.
The official version: “Monarch is the Telco industry’s most highly integrated Cat M1/NB1 (NB-IoT) chip, whereby baseband, RF transceiver, power management, and RAM memory are integrated into a single, tiny 6.5 x 8.5 mm package. Monarch is fully compliant with the 3GPP’s Release 13 definitions for narrowband LTE (LTE-M and NB-IoT). In addition, Monarch supports advanced features such as programmable RF filtering for global band support in a single SKU, and proprietary dynamic power management technology for ultra low power consumption and operating life of 10+ years.”
By now, the Monarch chip, while still brand new, has been integrated and tested with many of the world’s mobile operators already which should significantly lighten and shorten the testing and certifications load for Pycom’s portfolio.
PYCOM PLANS FOR NETWORK CERTIFICATION
Working with 8 operators to enable and certify the FiPy, GPy and G01 on their networks…and more to come.
Network certification can be costly (sometimes as much as €50k) and so we have to pace ourselves a bit. In addition, it is worth observing the roll out schedules for each of the network operators to try and tie in with network availability….we’re sure you’d agree that there’s no point certifying on a network that is far from rolled out. Below is a breakdown of our certification phases.
Please note that the date and roll outs are fluid still and therefore things may change. In addition, other network operators will be added to the list as we engage and understand more about their roll-out plans.
Phase I – Q2 – Q3 2017
Phase II – Q3 – Q4 2017
Phase II – Q4 2017 – Q1 2018
ONBOARDING & NETWORK OPERATOR IOT PLATFORMS
Pycom is in talks with some of the above network operators about providing Nano SIM cards to customers. This is purely to make sure that the SIM/connectivity purchase and network on-boarding is facilitated making the process easy for our developers. As always with us, there’s no obligation to run with our provision and each developer can go and choose other SIM/connectivity solutions if they wish. This gives everyone complete freedom to work with a network of choice.
We’re working as quickly as we can to get the SIM/Connectivity Reseller framework up and running on our Webshop and hope to be able to offer the first ones in October/November 2017. It is not anticipated however that Pycom will be able to provide Network / Connectivity support. We’re just not staffed for it at present but we will provide contact details for each of the operators we work with to ensure support is available.
As we mature the Pybytes Middleware, we will include mobile network and connectivity data there too, so that users can have one free and common platform for device management.