CAT-M & NB-IoT Design and Conformance Test Evolution of MTC/CIoT in 3GPP CIoT RAN Clean sheet...
Transcript of CAT-M & NB-IoT Design and Conformance Test Evolution of MTC/CIoT in 3GPP CIoT RAN Clean sheet...
CAT-M & NB-IoT Design and Conformance Test20170614
JianHuaWu 吳建樺[email protected]
What’s IOT?
Internet of Things物聯網
Page
Diverse IoT Applications
Healthcare
Agriculture
Asset tracking
Smart Energy
Connected cities
Manufacturing
Connected
cars
Weareables
Long battery life
Low device cost
Low deployment cost
Extended coverage
Support for a massive number
of devices.
3
Page
Diverse IoT Applications
Healthcare
Agriculture
Asset tracking
Smart Energy
Connected cities
Manufacturing
Connected
cars
Weareables
Range
ZigBee
BT LE
NFC
WiFi Cellular
LPWAN
Data rate / Power consumption
4
Page
3GPP for IOT
R8
LTE Cat 1
R12
LTE Cat 0
R12
PSM
(Power Saving mode)
R13
e-DRXR13
CAT-M1 / Nbiot / EC-GSM
5
Page
LTE Cat 1 >> Cat 0 >> Cat M1
• Reduced device bandwidth of 1.4MHz in
downlink and uplink
• Reduced maximum transmit power of 20dBm
• Provide an LTE coverage improvement –
corresponding to 15dB for FDD
• Enhance the DRX cycle
6
Page
Evolution of MTC/CIoT in 3GPP
CIoT RAN Clean sheet proposal
• NB-LTE (Ericsson, Nokia, MTK, AT&T,
Sprint, others)
CIoT GERAN Clean sheet proposals
• NB-M2M (Neul-Huawei, u-blox, Ericsson, Samsung)
• NB-OFDMA (Qualcomm)
• C-UNB (derivative of SIGFOX)
• NB-CSS (Semtech, derivative of LoRa)
• NB-CIoT (NB-M2M + NB-OFDMA) (Qualcomm, Neul-Huawei, u-blox others)
GSM Evolution proposals
• NB-GSM
• EC-GSM (Ericsson others)
TR 45.820
LTE Evolution proposal
• LTE-M 1.4MHz BW
GERAN
selection
process
RAN #69 selection process
September 2015
NB-CIoT
EC-GSM
Likely to move forward
• LTE-M 1.4MHz
• EC-GSM
TR 36.888
Output for R13 standardization
• LTE-M 1.4MHz
• EC-GSM
• NB-CIoT
• NB-LTE
RAN #70 selection process
December 2015
Clean sheet proposal work
item for further refinement
• NB-CIoT
• NB-LTERP-151621
R13 spec June 2016, expect merged OFDMA
DL and two separate UL TBC
Almost certain for Rel-13
7
Page
IOT in 3GPP
9
Page
Wide Diversity of Communication RequirementsOne transport technology does not fit all use cases
Technology
LTE Cat-NB1
LTE Cat-M1
LTE Cat-1Cars
Fleet
track
Asset
management
Street
lighting
Water
meteringPets
Agriculture
Pulse meterBlood
presure
Smart
home
Wearables
Survelliance
Trash canes
Devices per
Application
Industry
Automation
Telematics
~ 10s kbps
~ 100s kbps
~ Few Mbps
Billboards
Requirements
~ $8/module
< $5/module
~
$15/module
10
Marketing Status
Page
Marketing Status
https://gsacom.com/paper/commercial-volte-networks-
3gpp-technology-iot-networks/
• We have counted 4 commercial NBIoT
networks, with several more veryclose to
commercial launch; a further 40 networks in 29
countries trialling,demonstrating or planning to
deploy NB-IoT (plus commitments to
development by multi-country operator groups)
• 2 commercial LTE-M networks (Verizon USA
and AT&T USA) and 12 other networks in 10
countries trialling, demonstrating or planning to
deploy LTE-M.
12
Page
Marketing Status
13
Low device costLow deployment cost
14
LTE Cat-NB1 LTE Cat-M1
Page
Low Device Cost – Reduce Complexity
https://resources.ext.nokia.com/asset/200178 15
Page
Typical 5MHz LTE5MHz with 25 x 180kHz
LTE 180kHz PRB(Physical Resource Block)
NB-IoT200kHz from 1 x 180kHz
180kHz from 12x15kHz
subcarriers (OFDMA downlink)
NB-IoT in-band
with LTE
NB-IoT LTE guard
band
NB-IoT in 200kHz GSM
spectrum no guard
NB-IoT in 200kHz GSM
spectrum with guard
TBC NB-IoT excluded
from central 6 PRB
25x180k=
4.5MHz
Cat M and NB-IoT
16
Deployment options
Page
Typical 5MHz LTE5MHz with 25 x 180kHz
LTE 180kHz PRB(Physical Resource Block)
Cat M1.4MHz with 6 x 180kHz
NB-IoT200kHz from 1 x 180kHz
180kHz from 12x15kHz
subcarriers (OFDMA downlink)
Cat M in-band
with LTENB-IoT in-band
with LTE
NB-IoT LTE guard
band
NB-IoT in 200kHz GSM
spectrum no guard
NB-IoT in 200kHz GSM
spectrum with guard
TBC NB-IoT excluded
from central 6 PRB
6x 180k=
1.08MHz
25x180k=
4.5MHz
Cat M and NB-IoT
17
Deployment options
PSM and eDRX
LTE Cat-NB1 LTE Cat-M1
Page
PSM Flow
19
UE NAS State Registered
(normal)
Registered
(normal)
Registered
(no cell)
RRC State Connected Idle Null
T3412
T3324Power on / Attach
Tracking Area update
PSM modepaging
Page
Power Saving Mode
– It is a specially kind of UE status that can minimize the energy consumption that is
supposed to be even lower than normal idle mode energy consumption.
– This is newly added feature in Release 12 and is specified in 3GPP 24.301-5.3.11
Power saving mode and 23.682-4.5.4 UE Power Saving Mode.
– Similar to power-off, but the UE remains registered with the network
– No need to re-attach or re-establish PDN connections.
– A UE in PSM is not immediately reachable for mobile terminating services.
20
Page
T3412 & T3324 3gpp 24.301
T3412
T3324
21
Page
PSM Power Consumption
• The maximum duration of
PSM (T3412) is 12.1 days.
• PSM mode can be cancelled
anytime by the device by
sending a TAU to the
network that does not
include the PSM timers.
22
Page
eDRX - Extended/Enhanced DRX – idle mode
3gpp 24.008, section 10.5.5.32Nokia_LTE_Evolution_for_IoT_Connectivity_White_Paper_EN.pdf
Page
eDRX - Extended/Enhanced DRX – connected mode
© Keysight Technologies 2016 24
3gpp 36.213
Page
Power Saving Mode and eDRXRel-12 Power Saving Mode (PSM) Rel-13 Enhanced DRX (eDRX)
CO
NN
EC
TE
D
TA
U
T3412
T3324
PSM
Paging
OcassionsUE unreachable
- T3324 determines for how long the UE will
monitor paging beforing entering in PSM
- While in PSM, UE is not reachable by the
Network and all circuitry is turned off
- UE exits PSM when T3412 expires (TAU) or with
a Mobile Originated transfer
CONNECTED eDRX
Before Rel-13
- DRX cycles extended from 2.56 seconds:
• To 9.22 seconds in NB-IoT
• To 10.24 seconds in Cat-M
2.56s 9.22s
IDLE eDRX
- New Paging Time Window which allows longer
paging cycles:
• 3 hours in NB-IoT
• 44mis in Cat M
CO
NN
EC
TE
D
Paging Time Window
UE monitoring control
channel
25
Coverage Enhancement
26
LTE Cat-NB1 LTE Cat-M1
Page
NB-IoT: Key parameters
Frequency rangeNB-IoT (LTE) FDD Bands:
1, 2, 3, 5, 8, 11, 12, 13, 17, 18, 19, 20, 25, 26, 28, 66, 70
Duplex Mode FDD Half Duplex type B
MIMO No MIMO support
Bandwidth 180 kHz (1PRB)
Multiple AccessDownlink: OFDMA
Uplink: SC-FDMA
Modulation Schemes
Downlink: QPSK
Uplink: Single Tone: π/4-QPSK, π/2-BPSK
Multi Tone: QPSK
Coverage 164 dB (+20dB GPRS)
Data Rate ~25 kbps in DL and ~64 kbps in UL (multi-tone UE)
Latency < 10 seconds
Low Power eDRX, Power Saving Mode
HARQ (1 process only)
UL Power Control (Open Loop only)
RSRP, RSRQ Reporting
CSI Reporting
Carrier Aggregation
IMS
eMBMS
Support for other features:
Handovers in CONNECTED
$
27
Page
NB-IoT: Coverage Levels
Path LossP
ow
er
Level
Receiv
ed
NRSRP Thres 1
NRSRP Thres 2
NORMAL ROBUST EXTENDED
NPRACH Resources (48 sc)
• Up to 3 different Coverage Levels signaled
via SIB2-NB
• (Normal, Robust, Extreme)
• (CE Level : 0 ,1, 2)
• ( MCL : 144 db ,154 db , 164 db)
• The coverage level selected determines the
NPRACH resources to use:
• Subset of subcarriers, PRACH
Repetitions, Max number of attempts,
etc…
• UE derives the Coverage Level based on
NRSRP measured
o NPRACH resources to be used are
determined by the Coverage Level
28
Page
NB-IoT: Random Access Procedure
NB-IoT Device
NB-IoT
eNodeB
Random Access Preamble
Random Access Response
Scheduled Transmission
(msg3)
Contention Resolution
1st Higher Layer Protocol Interaction
CP
Tcp TSEQ
1st Repetition 2nd Repetition 3rd Repetition
Pseudo Random Hopping
Preambles can be repeated up to 128 times
Preamble repetition :
1, 2, 4, 8, 16, 32, 64, or 128 timesPreamble symbol group
29
Page
NB-IoT: Repetitions
GPRS
Extended
Coverage
– Technique consisting on repeating the same transmission several times:
• Achieve extra coverage (up to 20 dB compared to GPRS)
• Each Repetition is self-decodable
• Scrambling code is changed for each transmission to help combination
• Repetitions are ACK-ed just once
– For NB-IoT all channels can use Repetitions to extend coverage
Time: in Sub-frames (1ms)
DCI Ack
NPDCCH NPDSCH
NPUSCH
Format 2Repetitions = 2 Repetitions = 4
Example: Repetitions used in NB-IoT in NPDCCH and NPDSCH channels
30
Page
Uplink Frame Structure
• Single-Tone (MANDATORY):
To provide capacity in signal-strength-limited
scenarios and more dense capacity
o Number of subcarriers: 1
o Subcarrier spacing: 15 kHz or 3.75 kHz (via Random
Access)
o Slot duration: 0.5 ms (15 kHz) or 2 ms (3.75 kHz)
• Multi-Tone (OPTIONAL capability):
To provide higher data rates for devices in normal
coverage
o Number of subcarriers: 3, 6 or 12 signalled via DCI
o Subcarrier spacing: 15 kHz
o Slot duration = 0.5 m
∆f = 15 kHz
Total available
12 subcarriers
Total available
48 subcarriers
∆f = 3.75 kHz
256 Ts160 Ts
or
144 Ts2048 Ts 8192 Ts
1 slot = 2 ms
1 OFDM Symb = 8448 Ts (275us)
Guard period
2304Ts
(75us)
1 slot = 0.5 ms
1 OFDM Symb = 2208 Ts for symb#0 (71.88us)
1 OFDM Symb = 2192 Ts for symb#1..6 (71.35us)
Same as LTE
7 OFDM symbols 7 OFDM symbols
Can co-exist with LTE
NB-IoT: Uplink Frame Structuresubcarrier spacing
31
Page
NB-IoT Uplink Resource Unit Summary
32
Physical
Channel
𝚫f Resource Unit Mod
Scheme𝑵𝐬𝐲𝐦𝐛𝐔𝐋
𝑵𝐬𝐜𝐑𝐔 𝑵𝐬𝐥𝐨𝐭𝒔
𝐔𝐋 Slot
length
RU
length
NPUSCH
format 1
(UL-SCH)
3.75kHz 1 16 2ms 32ms 𝜋
2BPSK, 𝜋
4QPSK
7
15kHz
1 16
0.5ms
8ms
3 8 4ms
QPSK6 4 2ms
12 2 1ms
NPUSCH
format 2
(UCI)
3.75kHz 1 4 2ms 8ms𝜋
2BPSK
15kHz 1 4 0.5ms 2ms
Page
NB-IoT Uplink Resource Unit (RU)
33
Page
NB-IoT: Downlink Frame Structure
New Downlink channels
• NPBCH (physical broadcast channel)
• NPDSCH (physical downlink shared channel)
• NPDCCH (physical downlink control channel)
Downlink Frame Structure
• Same numerology as LTE (co-existence with LTE)
• Bandwitdh: 180 kHz = 12 subcarriers separated 15 kHz
o Equivalent to 1 LTE PRB
• Durations:
o 1 Frame = 10 subframes (1024 SFN)
o 1 subframe = 2 slots (1ms)
o 1 slot = 0.5ms (7 OFDM symbols)
o 1 Hyperframe = 1024 x 1024 radio frames (~
3hours)
New Downlink signals
• NPSS/NSSS (primary and secondary synchronization channels)
• NRS (cell reference signals)
subframes
1 2 3 4 5 6 7 8 90
1 Radio Frame = 10ms
subcarr
iers
time (ms)
0
12
0.5 1
slot 0 slot 1
12 subcarriers
(180KHz)
1 LTE PRB
34
Page
Each physical channel occupies the whole PRB;
Only one channel per subframe
LTE
Channels are time and frequency multiplexed;
Multiple channels per subframe
0 1 2 3 4 5 6 7 8 9
NB-IoTP
RB
(fre
qu
ency)
Subframes
(time)
1 P
RB
Subframes
(time)
SSS
PSS CRSPBCH
PDCCH PDSCH
PCFICH
PHICH
NB-IoT: Downlink Frame Structure
35
Page
NB-IoT: NPDCCH
NPDCCH (Narrowband physical downlink control channel)
• It carries Downlink Control Information (DCI). Three DCI types defined:
o N0: Used to schedule Uplink transmissions
o N1: Used to schedule Downlink transmissions
o N2: Used to schedule Paging or Direct Indication
• It fully occupies one downlink subframe (Repetitions may be used to
improve coverage)
• Resource elements are mapped around NRS
o In the case of in-band also around LTE CRS and starting at l symbol
to skip LTE PDCCH (as signaled by higher layers )
• Two Control Channel Elements (NCCE) in every NPDCCH
• Aggregation Level 1 uses only one NCCE
• Aggregation Level 2 uses both NCCE for more robust transmissions
R0
R0
R0
R0
R0
R0
R0
R0 R1
R1
R1
R1 R1
R1
R1
R1
NCCE0
NCCE1
subcarr
iers
NPDCCHStartl
R0
R0
R0
R0
R0
R0
R0
R0 R1
R1
R1
R1 R1
R1
R1
R1
NCCE0
NCCE1
NPDCCHStartl
Two Antenna ports
In-Band
Two Antenna ports
Standalone
0 1 2 3 4 5 6 7 8 9
Example where same NPDCCH is Repeated 4 times
subframe#
R=1 R=2 R=3 R=4
36
Page
NB-IoT: NPDSCH
NPDSCH (Narrowband physical downlink shared channel)
• It carries user data and broadcast information not transmitted on
NPBCH (i.e. SIBs-NB, paging or dedicated RRC).
• For the case of user data:
o QPSK only
o Single HARQ process
o TBS ≤ 680 bits
o A single TBS can be mapped to multiple consecutive downlink
subframes (NSF) signaled in DCI N1:
For example, TBS = 680 requires at least 3 subframes
o Up to 2048 Repetitions used to reach larger coverage
o Downlink scheduling signalled via DCI Format N1:
Modulation and coding scheme
Scheduling delay
DCI Repetition number
NPDSCH Repetition
Resource Assignment
HARQ-ACK Resource Index
TS 36.213 Table 16.4.1.5.1-1
NPDSCH Transport Block Size Table
TS 36.213 Table 16.4.1.3-1
Number of subframes for NPDSCH
NSF = 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9
n+5
1 2 3 4
subframe#
NPDSCH
37
Page 39
Page
Names
– eMTC
– Cat M
– Cat M1
– LTE-BL/CE (Bandwdth reduced Low complexity / Coverage Enhancement ) (36.300)
40
Page
CAT M Traits (1/3)
– LTE-M1 operate only in 1.4 Mhz (6 RB) bandwidth.
– LTE-M1 operate in Half Duplex mode
– LTE-M1 use the limited (reduced) max transmission power.
– LTE-M1 would mainly operate with legacy LTE using wider system bandwidth (e.g, 10 Mhz, 20Mhz system bandwidth).
– LTE-M1 divide the legacy LTE system bandwidth into multiple sections of 1.4 Mhz and use any one of those
sections (theoretically, LTE-M1 can use different 1.4Mhz section within the system bandwidth at every subframe)
– LTE-M1 does not use PCFICH, PHICH, PDCCH which is required to be spreaded across the whole system bandwidth of
legacy LTE.
41
Page
CAT M Traits (2/3)
– LTE-M1 use specially designed control channel called MPDCCH.
– In LTE-M1, MPDCCH and the corresponding PDSCH (i.e, the PDSCH scheduled by the MPDCCH) is not in the same
subframe. This is called 'Cross-subframe scheduling'.
– LTE-M1 use specially designed DCI formats (6-0A,6-0B,6-1A,6-1B,6-2)
– LTE-M1 can transmit PBCH, PRACH, M-PDCCH, PDSCH, PUCCH, PUSCH in repeating fashion. (This is to make
these channels decodable even when the signal quality/power is very poor as in the harsh condition like basement. As
a result, this kind of repeating transmission would make the effect of increasing cell radius and signal penetration)
42
Page
CAT M Traits (3/3)
– LTE-M1 support only the limited number of transmission mode : TM 1,2,6,9 which can operate in single layer.
– LTE-M1 utilize a new physical channel format that transmit SIB/RAR/Paging in repetitive mode without using control channel
– All the resource allocation information (subframe, TBS, Subband Index) for SIB1 decoding is determined by a MIB parameter
(No Control Channel is used for this)
– All the resource allocation information (subframe, TBS, Subband Index) for SIB2 decoding is determined by several SIB1
parameters (No Control Channel is used for this)
– LTE-M1 support the extended Paging (DRX) Cycle
43
Page
What’s common between LTE and LTE-M
– PSS (Primary Synchronization Signal) is common to both legacy LTE and LTE M1
– SSS (Secondary Synchronization Signal) is common to both legacy LTE and LTE M1
– CRS (Cell Specific Reference Signal) is common to both legacy LTE and LTE M1
44
Page
CAT M: CE mode and CE level
• Difference :
• Each of the level differs mostly in RACH and Paging process
• RACH configuration and resources (e.g, frequency, time, preamble) associated
with each of the RACH configuration
• Frequency resources used for RACH transmission
• Repetition Number for RACH Preamble
• Who decide the mode? Who decide the level?
• Operation mode is determined by eNB (informed to UE via RRC message)
• the Level within each Mode is determined by UE. (based on the reference signal
power (RSRP) it measure and inform it to eNB by PRACH resource (frequency,
time, preamble) it uses.)
RRC Connection Setup
45
Page
3gpp R1-156979
46
Page
SIB1 Repetition
47
Page 48
•When PDSCH is scheduled by DCI format 6-1A
• the number of MCS field is 4, it means the maximum MCS is 15
•When PDSCH is scheduled by DCI format 6-2
• the number of MCS field is 3, it means the maximum MCS is 7
•When PDSCH is scheduled by DCI format 6-1B
• the number of MCS field is 4 and I_MCS = I_TBS
Page
Uplink TBS Determination
CEModeB UE is not expected to
receive a DCI format 6-0B indicating
I_MCS >= 10.
CEModeA
49
Which application need NBIOT / CAT M?
50
LTE Cat-NB1 LTE Cat-M1
Page
Mobility Support in CE mode A Not support
Latency Better Worse
VoLTE Support No support
51
Keysight NBIOT/CAT M solution
Page
NB-IoT Product Development workflow
Battery drain
analyser
AcceptanceVerificationR&D
Design
Simulate
Protocol
L2/L3
Develop
L1/PHY
Develop
RF
Develop
Integrate
System &
perf-
ormance
verify
RF
Design
Verify
Protocol
Verify
Operator acceptance
GCF/PTCRB
Lab IOT
Field trials
Pre-cert Certification
CTIA/CE/FCC regs
OTA test
UXM integrated
test setVSA/VSG
System Vue
Anite A9000 protocol development,
conformance and operator
acceptance
Anite Propsim
channel emulator
T4000S RF & RRM
Conformance and Regulatory
System
Keysight covering the whole RF NB-IoT development cycle
Leading in GCF RF-NB-IoT validations
First to validate RF NB-IoT and CAT-M
test cases together
53
Page
Thank you
54