4G/LTE - NB IoT
NB-LTE stands for Narrow Band LTE. For the high level description of NB-LTE and some comparative view of other technology, refer to LTE-M/Category M/M1/M2 page. Early July in 2016 (around Jul 10), the first version of 3GPP TS documents on NB IoT were posted and I started working on note based on these documents. It is very early stages for now and these notes will keep being updated and still some of high level description based on TR 45.820 (Ref ) remain in some notes. (I see pretty big differences between the official TS and TR 45.820 in terms of the details).
Followings are some of high level topics in this page
Followings are the list of the topics (pages) that I am working on now... usually my approach is to study on physical/MAC layers first and then RRC messages and then everything in between. I am writing these pages based on the assumption that readers are familiar with basic concepts used in legacy (normal) LTE. So I don't describe much on the basic concepts in these pages. If LTE-NB is your first experience of LTE and come across any concept/terminologies you are not familiar, I would recommend you to refer to pages for legacy (normal) LTE (Try "Search" menu at the top)
Questions before Study
When I first heard of a variation of LTE (NB-LTE) with using only 200 Khz (1 RB), I thought like this : "OK, I think I can understand the motivation is 200 Khz. It is same as basic channel bandwidth of GSM. So if we use this in LTE, we may be able to use GSM/GPRS spectrum for NB-LTE. Also, even the smallest bandwidth of the current LTE (1.4 Mhz) might be too much for such a super low throughput application like IoT. OK, so far so good. Then a question popped up in my mind.
OK.. I think 200 Khz (more accurately 180 Khz) is to utilize 1RB of legacy LTE as it is. Also, it is not difficult think of how we utilize this single RB because data transmission and reception in the single RB is possible even in legacy LTE. However, there are somethings that cannot be reduced to single RB bandwidth in legacy LTE. So you may have following questions.
I would not give you answers to any of these questions in this page. It is just my way of studying anything new. Coming up with my own question before jumping into textbook or specification documents.
The first impression that I got while I was reading Release 13 LTE-NB specification is that it is almost a new design except a few very fundamental factors/parameters.
Followings are some of parameters that remains same in LTE-NB comparing to normal (legacy) LTE
Followings are some of parameters that are different from legacy LTE. I would just put down a high level descriptions of the difference here. For the details, I would recommend you to each separate pages that I listed at the top.
In short, there is no changes at all in Downlink and small changes in Uplink as follows.
As you know, LTE is originally designed to provide very high data rate. So it might sound ironic that we are trying to provide very low throughput service like IoT. However, as far as I experienced.. in engineering there is no such a thing like ironic.. engineers are always to try to come up with a solution when there is need. Even though LTE is originally designed for high throughput, there has been continuous effort for low throughput (low cost) solution for the past couple of years. This is why you start seeing UE Category running backward. Most of initial LTE implementation was implemented as Category 3 and kept incrementing the numbers. However, we started seeing backward numbers like Category 1 and Category 0. However, all of exisiting LTE categories still keep the lowest boundary of LTE specification as follows :
However, the industry realized that there would be limitation to make LTE perfectaly suitable for IoT / MTC crieteria (super simple, untra cheap, extremly low energy consumption). Finally the industry tried to break at least one of the LTE boundary. It is to break frequency domain boundary and decide to make it narrower.
Then the question is how narrow it should be. Probably the most practical answer they found seems to be the bandwidth of 1RB because 1 RB is the minimum scheduling unit of current (legacy) LTE in frequency domain. They might have tried to pick narrower bandwidth (e.g, 6 subcarriers etc). However, in this case it would require too much redesign from the legacy LTE.
The industry decided to time domain boundary as it is, meaning that we can use the most of time domain design of the legacy LTE as it is.
With 1RB Bandwidth selected, we can utilize(deploy) this system in various situation as illustrated below.
Inband Mode : In this mode, we can deploy LTE NB within a legacy LTE if you just reserve only 1 RB anywhere in the legacy LTE band.
Guardband Mode : As you know, every LTE band has at least 100 Khz guardband on each end of the band. It means that you can easily have around 200 Khz space between any two non-contiguous band even if they are sitting in the closest possible locations. Guardband mode is to deply LTE-NB in the space that are reserved for the guardband of legacy LTE band.
Standalone Mod : In previous two modes, LTE-NB coexists with an existing legacy LTE band. But we can think of another case where it is deployed completely independent from any legacy LTE. In an extreme case, we may deploy it in completely free space in the spectrum. However, in practical sense this mode of operation is intended to reserve (free up) a GSM channel and deploy LTE-NB in that space.
 3GPP RP-151621
 3GPP TR 45.820 V13.1.0 (2015-11) : Cellular system support for ultra-low complexity and low throughput Internet of Things (CIoT) (Release 13)
 3GPP TS 36.211 V13.2.0 (2016-06) E-UTRA Physical channels and modulation
 3GPP TS 36.331 V13.2.0 (2016-06) : E-UTRA RRC Protocol Specification