Huawei SRAN12.1 CIoT-Huawei Workshop

SRAN 12.
1
eRAN12.1 Workshop
CIoT
Madrid- March 2017
Vodafone – Huawei SRAN12.1 Workshop
HUAWEI TECHNOLOGIES CO., LTD.

eRAN 12.1
Agenda CIoT General Overview
Deep Dive Selected CIoT Features
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2

Agenda
1 GENERAL OVERVIEW
CIoT

By 2020, LPWA to Represent 70% of Cellular IoT Connections
Market Connections in 2020 Requirements Technology

Segment (Billion)
 Camera
l >10Mbps 3G/4G
 Electronic billboards…
0.2B
 Smart Home l ~1Mbps GSM/GPRS/CDMA

 POS… 0.8B l Low power LTE MTC(R12, R13)
consumption
 Sensors, Meters l Small Packet (<100kbps) Zigbee, Bluetooth

 Asset Tracking
2B l Deep Coverage （20dB） WiFi, Sigfox, LoRa
 Smart Parking l Low power (10 Years)
 Smart agriculture … l Low cost (<$5) NB-IoT…
LPWA: Low Power Wide Area

4
LPWA = Low Power Wide Area
Low-Power Wide-Area Network is a type of
LPWA wireless telecommunication network designed to

allow long range communications at a low bit rate
among things (connected objects, such as
sensors)
Long Battery Life Deep Penetration Low Device Cost Mass Deployment
5
The Rise of CAT-1/eMTC, Sunset of 3G
Typical 3G IoT Cases Cat-1 is Better Option
B2C as Main Cases

Suitable Lower Power Lower
Data Rate Consumption E2E TCO
Wearable IoT Gateway

Backhaul 10Mbps PSM/eDRX All 4G
Cat-1 IODT test Done with Qualcomm MDM9x07 chipset in 2016H1
The Rise of Cat-1 Assists Sunset of 3G in 2020
6 6 Huawei Confidential
The Rise of NB-IoT, Sunset of 2G
Typical 2G IoT Cases NB-IoT/eMTC is Better Option
Same Lower Power Deep

Data Rate Consumption Coverage
POS Smart Vending

100k~1Mbps PSM/eDRX 15~20dB Gain
Meter Machine
The Rise of NB-IoT/eMTC Assists Sunset of 2G in 2025
7 7 Huawei Confidential
NB-IoT / eMTC are Future Oriented LPWA Technologies
4G ~10Mbps Cellular IoT

(Including Cat1)
Future Oriented
eMTC Cellular IoT ~1Mbps Cellular IoT
Technology
NB-IoT ~100kbps Cellular IoT(Full Capability LPWA)
8
Standardization of NB-IoT/eMTC Completed
2016.0 2016.05 2016.06 2016.09 2017.03

3
R14 kick off R14 frozen
R14
R13 Completed Positioning
RAN1 R13 Multicast
NB-IoT RAN2 RAN4(Performance) Non-Anchor PRB enhancements
RAN3 Mobility and service continuity
enhancement
New Power Class
R14
Positioning
R13 Completed
R13 Multicast
RAN1
eMTC RAN4(Performance) Mobility
RAN2
enhancements
RAN3
Higher data rates
VoLTE
9
Huawei NB-IoT Chipset Roadmap
Boudica v100(ES) Boudica v100 Boudica v100

5.3x5.3 BGA (Trial) (Commercial)
3GPP Rel-13 NB-IoT
20GPIOs
128 KB apps memory
Single Tone
Bands: 698~960MHz
Band 5/8/20/28
Boudica v200 (Planning)

30 GPIOs
256KB apps memory
Single Tone/Multi-tone
Bands: 698~960/1800/2100
Band: 450MHz
LiteOS
2016Q2 2016Q3 2016Q4 2017
10
Contents
CIoT Industry Insights
CIoT12.1 Solution Overview
11
Cellular IoT Architecture
IoT
Applications
Intelligent Intelligent Intelligent
Telemetric Smart Metering LTE-VDC Supply Chain Production Line Artificial aid
IoT Platform Unified IoT Platform
EPC
IoT Core Option 1 (Software Upgrade) New EPC Option 2
LTE NB-IoT MTC/eMTC LTE-V

Cellular IoT
Access 2016 2017-2018 2018 202X
Technologies Low Bandwidth
High Bandwidth and Low Power Consumption Ultra-reliable and Low Latency
12
CIoT12.1 Main Features Overview
Solution Feature Description Benefits UE chipset Release
2016Q3
NB-IoT Coverage Extension 20 dB higher coverage than LTE & GSM. Commercial
Theoretical 3dB higher coverage than 2-Antenna Receive

Enhanced NB- UL 4-Antenna Receive Diversity NA Commercial
Diversity.
IoT Coverage
Mitigating the interference with cell edges in densely
SFN populated urban areas and increasing the signal to NA Commercial
interference plus noise ratio (SINR) at cell edges
In areas with favorable coverage, multi-tone transmission
Enhanced NB- 2017
Multi-tone increases data rates and reduces the transmission delay and Commercial
IoT Capacity
power consumption for uplink data transmission.
NB-IoT Power
Idle Mode eDRX 10 years long lifetime for device battery 2016Q3 Commercial
Saving
NB-IoT RAN Sharing with Common Carrier NA Commercial

NB-IoT RAN
Sharing
NB-IoT RAN Sharing with Dedicated Carrier NA Commercial
eMTC Introduction 2016Q4 Commercial
eMTC Solution
Power Saving on eMTC 10 years long lifetime for device battery 2016Q4 Commercial
13
Huawei CIoT Roadmap
NB-IoT CIoT12.0
End of Sep End of Dec
For trial GA
CIoT12.1
End of Dec 2016 2017 Q2 GA
for trial
eMTC CIoT12.1
End of Dec 2016 2017 Q2 GA
for trial
14
Huawei CIoT Software Roadmap
CIoT12.0 CIoT12.1 CIoT13.x
NB-IoT NB-IoT NB-IoT

Basic Coverage Basic
 3GPP R13  4R Receive(900M)  3GPP R14
 Standalone/Guard Band/In Band Power Consumption Coverage
 Single-tone  eDRX enhancement  UL CoMP
Coverage Throughput/Capacity Throughput/Capacity
 Support Coverage Class 0/1/2  Multi-tone  Multi-carrier
 20dB Coverage Gain Other Service
 SFN  MOCN  Positioning(R14)
Power Consumption  Broadcast
 PSM/eDRX  Service Priority based Scheduling
Service phase II
 Service Priority based Scheduling
phase I eMTC eMTC
Coverage Enhancement Performance Enhancement
Extended DRX Positioning
Mobility Management
Congestion Control
Voice
15
Architecture for NB-IoT
C-SGN is a new logical entity and can be implemented
Application
Platform to support only the necessary functionality required for
CIoT use cases From 3GPP TR 23.720
MME/SGSN
Serving GW
PGW/GGSN
IOT Platform
HSS/PCRF
G/U/L/NB-IoT BTS
NB-IoT Data transmission option：

• CP(Control plane based solution):Data over
NAS message , No need for DRB
Additional C-SGN element
• UP(User Plane based solution) :Similar to legacy
LTE system
Page16
NB-IoT: Flexible Deployment with Small Licensed Spectrum
UMTS/LTE
180k 180k
LTE LTE
180k 180k
GSM
180k
Standalone LTE Guard Band LTE In Band
17
NB-IoT: Flexible Deployment
G+NB IoT U+NB IoT LTE Guard-band： LTE In-band：
NB IoT 200KHz NB IoT NB IoT
200KHz 180KHz
Guard NB Interference
GSM UMTS
Band IoT LTE Guard Band
3.8M Emission
4.2M Mask Req
5M 500K
LTE
2.6M LTE 10M(Sharp RF Filter)
Standalone LTE Guard Band LTE In Band
Guard Band
Scenario
(1:1 Co-Site)
G+NB IoT 100K
0K
U+NB IoT
(Central Frequency Gap:2.6M)
LTE Guard-band To Spectrum Edge(Emission Mask Requirement): 100K
(LTE 10M Guard band) To Neighbor RB(Interference Requirement): 200K
LTE In-band
0 K(Occupied 1 RB from LTE)
(LTE Bandwidth≥5M)
Page18
For uplink data transmission, an eNodeB can allocate multiple subcarriers at a time to a multi-tone-capable UE to increase the single-UE peak uplink data rate.
NB-IoT: Uplink and Downlink Subcarrier

Downlink Uplink(Single-tone)
3.75KHz ST
Downlink: OFDMA with 15kHz Subcarrier Spacing is 15KHz ST

N *15KHz MT
chosen because it can fit In-Band scenario
….
f f f
Page19
Throughput: Single-Tone & Multi-Tone
NB-IoT PUSCH option：
• Single-tone ：UE uplink only support one 15kHz/3.75kHz channel at the same time, both
15KHz and 3.75KHz should be supported for Single-Tone UE
• Better coverage, capacity, and lower complexity
• Multi-tone ：UE uplink could only support combination of multiple 15kHz channel
• Better throughput and battery life time in good coverage
3.75KHz
Complexity Throughput
Coverage 15KHz
N *15KHz
….
f f f
Scheduled dynamic by eNodeB
Co-exist in the same NB-IoT cell
20 Note: 3.75KHz is under planning in later version.

Coverage: NB-IoT Born to Provide Better Coverage
PSD Gain Repetition Gain

=10log (Power A/Bandwidth A) /(Power B/Bandwidth B) =10log Repetition Times
Up to 9dB DL Gain
Up to 17dB Up to 12dB UL Gain
(DL 8 Times and UL
16 Times Repetition)
180 KHz 3.75 KHz
3dB Gain(vs 2R)

 GSM 1R 3dB Gain
 NB-IoT 2R/4R
21
Power Saving: PSM
Paging
UE Power
PSM
Up to 310hours Time
active timer Idle State
Tx Power Consumption 0.0135mWh

Transmit 120mA*
Rx Power Consumption 0.0036mWh
Paging Monitoring 50mA Idle Power Consumption 0.0050mWh
Idle State 1mA Once Communication 0.022mWh

PSM 0.005mA PSM Consumption/day 0.36mWh
Voltage Assumption: 3v Battery Life(2400mAh,3V) >>10Years
*50mA@MCL 144dBm
200byte/per report per day
22
Power Saving: eDRX
MME determine cycle according to UE service type(APN)

DRX Cycle: 1.28s eDRX Cycle: up to 2.92h
PTW
UE Power
Time
DRX DRX Cycle: 1.28s eDRX
PTW: Paging Transmission Window
Tx Power Consumption 0.0135mWh

Transmit 120mA*
Rx Power Consumption 0.0036mWh
Paging Monitoring 50mA
Idle Power Consumption 0.0050mWh
Idle State 1mA
Once Communication 0.022mWh
PSM 0.005mA
*eDRX Consumption/day 5.2258mWh
Voltage Assumption: 3v
Battery Life(4*2400mAh,3V) >10Years
*50mA@MCL 144dBm
200byte/per report per day
*eDRX Cycle 81.92s, PTW=3
23
Site: SingleRAN Support Upgrading Smoothly to NB-IoT
US700(Band12/13) RRU3269, RRU3203
APT700(Band28) RRU3262,RRU3268 RRU3268(V3&V6)
DD800(Band 20) RRU3220, RRU3222,

RRU3268(V3&V6), LRFUe
LRFUe, RRU3268
850M(Band 5) RRU3942, RRU3938 v3(Korea) RRU3908 v2, RRU3936 v3,RRU3804,

RRU3805,RRU3952
RRU3908 v2, MRFU v2, MRFU v2a

900M(Band 8)
RRU3936, RRU3938, RRU3953, MRFUe,RRU3926，
RRU3928, RRU3929,RRU3959,MRFUd
RRU3936, RRU3971, RRU3630, RRU3632, RRU3632B,

RRU3638,RRU3929, RRU3939, RRU3959, RRU3953
1800M(Band 3) MRFU V2,MRFU V2a,MRFUe,RRU3926,
RRU3928,RRU3935,RRU3938,MRFUd
SRAN12.0 SRAN12.1
24
eMTC: Deep Coverage and Power Saving for Vertical Industry
Repetition Idle Mode eDRX
MME determine eDRX & PTW cycle according to UE service type(APN)
high SINR DRX Cycle: 2.56s eDRX Cycle: up to 43.69mins
15dB Gain PTW

UE
No repetition Power
low SINR
Small repitition
DRX Cycle: 2.56s Time

Large repetitions DRX eDRX
15dB more gain can be got with large number In the idle state, the paging cycle is extended from 2.56s
of repetition. to the maximum of 43.69 mins
25
eRAN12.1 - CIoT
Agenda CIoT General Overview
Deep Dive Selected Features

Agenda eRAN12.1 – NB-IoT Selected features
MLBFD-12000103 LTE In-band Deployment Maintained
2.2
MLOFD-120201 NB-IoT Coverage Extension Maintained
MLOFD-120230 Multi-tone New
MLOFD-120220 Idle Mode eDRX Maintained

Physical Layer Structure: Frequency Domain
Uplink Downlink
• SC-FDMA: two types of subcarrier spacing • OFDMA
 3.75 kHz (Large power spectrum; good coverage; PRACH)  Occupies a bandwidth of 200 kHz. (A 10 kHz guard band is
 15 kHz (High rates; small delay; PUSCH) reserved on each side, and therefore the actual bandwidth is
• Two transmission modes 180 kHz. Occupies a bandwidth of 180 kHz in LTE in-band
 Single-tone (One UE uses one carrier for low-speed transmission) deployment, that is, occupies an RB)
 Multi-tone (One UE occupies multiple carriers for high-speed  Subcarrier spacing: 15 kHz
transmission. Only the 15-kHz subcarrier spacing is supported.)  Number of subcarriers: 12

NB-IOT Solution Introduction: LTE In-band Deployment
• In-band Deployment:
• One RB will be used for NB-IoT. In-band NB-IoT
will be compatible with LTE by “Puncture” NB-IoT
180K
• NB-IoT Uplink PRB index：
• As all potential NB-IoT in-band uplink PRB
collides with LTE PRACH,LTE PUCCH ,eMTC
PRACH，eMTC PUCCH or SRS, we suggest
LTE 10M system bandwidth
the system edge of PRB to decrease the
• NB-IoT Downlink PRB index
capacity loss (maximum continuous PUSCH
Bandwidth NB-IoT downlink available PRB eMTC coexist，NB-IoT
PRB) of LTE and PUCCH will automatically avail PRB
move forward one PRB. 10MHz 4,9,14,19,30,35,40,45 19,30
HISILICONTECHNOLOGIES
HUAWEI SEMICONDUCTOR
CO., LTD. Page 29
NB-IoT frequency planning: In-band Mode
LTE DC subcarrier
LTE PRB #24

LTE PRB #25
LTE PRB #48

LTE PRB #49
LTE PRB #18
LTE PRB #24
LTE PRB #25
LTE PRB #48

LTE PRB #49
LTE PRB #1
LTE PRB #0
NB-IoT
NB-IoT
LTE Guard-band LTE Guard-band LTE Guard-band LTE Guard-band
10MHz LTE 10MHz LTE
Uplink Downlink
NB-IoT Uplink PRB index: PRB #0 NB-IoT Downlink PRB index: PRB #19,#30
LTE PUCCH available LTE PRACH available NB-IoT PRB indices Middle 6 PRBs used eMTC SIB1 NB-IoT
LTE system Cell SRS available LTE system
PRB indices(Normal available PRB limited by the 100kHz channel by the LTE frequency hopping downlink PRB
bandwidth PRB indices bandwidth
CP) indices raster PBCH/PSS/SSS range indices
10M 0~9,40~49 10~15 7~42 10M 4,9,14,19,30,35,40,45 22~27 1~18,31~48 19,30
As all potential NB-IoT in-band uplink PRB collides with LTE PUCCH or NB-IoT Downlink interference to LTE downlink
SRS, we suggest PRB #0 to decrease the capacity loss(maximum As NB-IoT 15kHz downlink subcarrier orthogonalize with LTE
continuous PUSCH PRB) of LTE and PUCCH will automatically move 15kHz downlink subcarrier, there is no interference.
forward one PRB.
Page 30 HUAWEI TECHNOLOGIES CO., LTD.

Impact Analysis
 For in-band mode, NB-IoT will occupy PRB of LTE, and NB-IoT PRB is statically configured,
even if there are no traffic in NB-IoT cell at a moment, the RB cannot be used by LTE.
So the capacity of LTE will decrease due to RB loss:
LTE DL cell DL user UL cell UL user

Bandwidth throughput throughput throughput throughput
10M 2% 6% 2% 4%
 If there are multiple online UEs in the LTE cell, the average uplink and downlink experienced
rates are affected each time after an RB is reserved.
LTE Bandwidth Single UE Experienced Rate Loss
10M 8%~20%
 average uplink and downlink experienced rates evaluated based on:

• The inter-site distance is 500 meters.
• Each cell has 10 online UEs.
• The network load is about 20%.
• The ratio of large-sized packets to small-sized packets is 1:4.

User Guide
 Exclusive on other Features
 LOFD-070220 eMBMS Phase 1 based on Centralized MCE Architecture
 LOFD-080215 eMBMS Service Continuity
 LOFD-001005 UL 4-Antenna Receive Diversity
 LOFD-001003 DL 4x2 MIMO
 LOFD-001060 DL 4X4 MIMO
 LOFD-001031 Extended CP
 LOFD-081223 Extended Cell Access Radius Beyond 100km
 LOFD-081208 Inter-eNodeB SFN Based on Coordinated BBU
 LOFD-081209 Inter-eNodeB Adaptive SFN/SDMA Based on Coordinated BBU
 LOFD-081221 Super Combined Cell
 LOFD-001025 Adaptive Power Consumption
 LOFD-001039 RF Channel Intelligent Shutdown
 LOFD-001074 Intelligent Power-Off of Carriers in the Same Coverage of UMTS Network
 LOFD-001042 Intelligent Power-Off of Carriers in the Same Coverage
NB-IoT Power Configuration
In-band/Guard Band Standalone

 Power on NB-IoT = Power on LTE RB + ≥6dB  No Special Requirement on Power
Boosting  Default not less than In-band/Guard band.
 Power Requirement on NB-IoT:
LTE Power: 2*20W
LTE Bandwidth 10MHz
Power on LTE RB 0.4W per PA
Power on NB-IoT 1.6W per PA
NB-IoT carrier power 2*1.6W

2.2

1. NB-IOT Solution Introduction: Coverage Extension
 coverage levels : LTE Solution
• NB-IoT supports a maximum of three coverage levels: 0, 1, and 2 Average
Power=
• Under identical radio conditions, NB-IoT delivers 0 dB, 10 dB, and 180 KHz 200mW/180k
Hz
20 dB higher coverage, respectively, than LTE. 12 times
/10.8dB
 key technology ：
NB-IoT Solution
• Power Spectrum Density Boosting
Average
• Repetition Power=
15 KHz 200mW/15kHz
Coverage Level 0 Coverage Level 1 Coverage Level 2
HUAWEI TECHNOLOGIES CO., LTD. Page 35

2. Impact Analysis
 Positive Impact (Gain)
• This feature enables UEs to access NB-IoT networks in a wider coverage area, increases
UEs' access success rate and RRC connection setup success rate in coverage
enhancement areas, and reduces UEs' service drop rate.
• This feature also decreases RBLER and packet loss rate.
 Dependency on other Features

› Prerequisite feature: MLBFD-12000234 Basic Scheduling
 License
Feature ID Feature Name License Control Item NE Sales Unit
NB-IoT Coverage Extension

MLOFD-120201 NB-IoT Coverage Extension eNodeB per cell
(NB-IoT)

3. User Guide
• When to Use NB-IoT Coverage Extension
› NB-IoT terminals, for example, terminals used in wireless meter reading and intelligent parking services, may
be deployed indoors or underground and therefore have requirements on deep coverage. In such coverage
enhancement scenarios, this feature must be enabled.
• Required Information
› NB-IoT service application scenarios, network deployment modes, cell coverage radius, and power.
• Feature Activation/ Deactivation Process
› Purchase a required license
› Run the MOD CELLALGOSWITCH command to set the COVERAGE_EXTENSION_SWITCH option of the
NbCellAlgoSwitch parameter to ON/OFF.
• Parameter Adjustment
› Cell.CoverageLevelType: Indicates the coverage level for an NB-IoT cell. This parameter is set based on
actual application and coverage requirements.
» When operators require a 20 dB coverage enhancement, it is recommended that this parameter be set to
COVERAGE_LEVEL_0:1, COVERAGE_LEVEL_1:1, or COVERAGE_LEVEL_2:1.

4.Example: Verification
• Observation after Activation
Users can monitor the following counters on the U2000 to check whether NB-IoT Coverage Extension is enabled.
Values of the following counters may be incremented only after this feature is enabled.
Counter ID Counter Name Counter Description
Number of times NPUSCH scheduling sets the number of transmission
1526744763 L.NB.ChMeas.NPUSCH.Repetition.16
repetition times to 16 in an NB-IoT cell
Number of times NPDSCH scheduling sets the number of transmission
1526744680 L.NB.ChMeas.NPDSCH.Repetition.16
L.NB.ChMeas.NPDSCH.Repetition.128to25 Number of times NPDSCH scheduling sets the number of transmission
1526744683
6 repetition times to a value in the range of 128 to 256 in an NB-IoT cell

• Feature Evaluation
Users monitor the following KPIs to achieve activation benefits of the NB-IoT Coverage Extension feature.
› Packet loss rate
» Downlink packet loss rate: L.NB.Thrp.Pkts.DL.SRB.Loss/L.NB.Thrp.Pkts.DL.SRB.Tot
› RBLER
» Downlink RBLER: L.NB.Traffic.DL.SCH.ErrTB.Rbler/L.NB.Traffic.DL.SCH.TB
» Uplink RBLER: L.NB.Traffic.UL.SCH.ErrTB.Rbler/L.NB.Traffic.UL.SCH.TB
› Service drop rate
» L.NB.UECNTX.AbnormRel/(L.NB.UECNTX.NormRel + L.NB.UECNTX.AbnormRel)
› RRC setup success rate
» L.NB.RRC.ConnReq.Succ/L.NB.RRC.ConnReq.Att
› RACH access success rate
» L.NB.RA.ContResolution/L.NB.RA.Att

2.2

1. MLOFD-120230 Multi-tone
Uplink
15KHz ST
N *15KHz MT
….
f f
• For uplink data transmission, an eNodeB can allocate multiple subcarriers at a time to a
multi-tone-capable UE to increase the single-UE peak uplink data rate.
• Benefits: In areas with favorable coverage, multi-tone transmission increases data rates
and reduces the transmission delay and power consumption for uplink data transmission.

1. MLOFD-120230 Multi-tone
Uplink
15KHz ST
N *15KHz MT
….
f f
• For uplink data transmission, an eNodeB can allocate multiple subcarriers at a time to a
multi-tone-capable UE to increase the single-UE peak uplink data rate.
• Benefits: In areas with favorable coverage, multi-tone transmission increases data rates
and reduces the transmission delay and power consumption for uplink data transmission.

1. MLOFD-120230 Multi-tone Description
• 3GPP specifications stipulate that NB-IoT should support single-tone and multi-tone
transmission in the uplink.
• Single-tone transmission is mandatory for UEs, while multi-tone transmission is optional.
• There are three types of multi-tone transmission: 3-tone, 6-tone, and 12-tone, which mean
an eNodeB can allocate 3, 6, or 12 subcarriers (15 kHz each), respectively, at a time for
uplink data transmission.
• The eNodeB flexibly schedules multi-tone-capable UEs to reduce the data transmission
delay and UE power consumption.

1. MLOFD-120230 Multi-tone Requirements

1. MLOFD-120230 Multi-tone Configuration

1. MLOFD-120230 Multi-tone Activation Observation

2.2

1. NB-IOT Solution Introduction：eDRX
DRX Cycle: 2.56s eDRX Cycle: up to 2.92h
PTW：10.24s
DRX DRX Cycle: 2.56s eDRX Time
• In the idle state, the paging cycle is extended from 10.24s to the maximum of 2.92h
• In each paging timing window, a number of paging opportunities are kept to ensure the
success rate of paging.
• MME determine the eDRX cycle and PTW length according to UE service type(APN)

2. eDRX procedure 1. The eNodeB includes the HSFN in the MIB and in SIB1. An HSFN
lasts 10.24s, which is the unit of an eDRX cycle.
2. The UE obtains the HSFN and determines whether to use DRX or
eDRX based on its own capabilities. If a UE uses eDRX, it includes the
eDRX cycle length in an Attach Request/TAU Request message sent to
the MME.
3. If the MME accepts the eDRX request, it configures a different
eDRX cycle and the size of the PTW for the UE according to the
predefined policy, and includes the information in an Attach
Accept/TAU Accept message to the UE. If the MME rejects the eDRX
request, the UE uses the DRX paging mechanism.
4. The UE and MME stores the "Extended DRX Parameters" after
negotiation, and uses the stored parameter values as the eDRX cycle
later.
5. When a MME has a paging message for the UE, it calculates the
HSFN and paging hyperframe (PH) for the UE based on the
negotiated eDRX cycle.
6. The MME sends the paging message to the eNodeB before the
PH time for the UE arrives.
7. On receiving the paging message, the eNodeB uses the eDRX
cycle carried in the message to calculate the time of the HSFN
and PH. The eNodeB also calculates the PO for the UE based on the
configured paging cycle, and sends the paging message to the UE at the
calculated time.The UE calculates the paging message delivery time the
same way the eNodeB does, and monitors and receives the paging
message during this time.

3. eDRX requirements

4. eDRX: When to use it
• When Idle Mode eDRX is enabled, the UE periodically monitors the paging channel and can
receive MT services.
• In traditional power saving mode (PSM, EPC feature), however, the UE cannot receive
MT services unless it proactively accesses the network.
• It will take a long time generally for a UE to proactively access the network,
depending on the mobile-originated (MO) data reporting period and tracking area update
(TAU) period.
• Therefore, Idle Mode eDRX is suitable for machine-to-machine (M2M) services that
require short delays for downlink MT services (for example, tracking the locations of
children and elderly people).

5. Impact Analysis
 Positive Impact (Gain)
• As idle mode eDRX adopts long paging cycles, UEs can stay in deep sleep state for a long
period to save UE power.
 Negative Impacts
• Response delay is relatively large
• In SRAN12.0 the eNodeB had to be equipped for time synchronization with GPS, BeiDou,
IEEE 1588V2, GLONASS, or 1PPS+TOD clock
• SRAN12.1 supports eDRX in both time and frequency synchronization modes.
 license MLOFD-120220 Idle Mode eDRX Idle Mode eDRX (NB-IoT) eNodeB Per cell

6. eDRX requirements

7. User Guide
When to use idle mode eDRX
• Idle mode eDRX is recommended when UEs that support this feature need to receive MT services and the
core network also supports this feature.
Required information
• Number of UEs that support this feature, and capability of the MME to support this feature
• eDRX start time (HSFN 0) configured on the MME, which is set as the GPS start time
Feature activation
• Set [MO] CellAlgoSwitch[/MO][Para] NbCellAlgoSwitch[/Para][bitmap] IDLE_EDRX_SWITCH :1[/bitmap]
Feature deactivation
• Set [MO] CellAlgoSwitch[/MO][Para] NbCellAlgoSwitch[/Para][bitmap] IDLE_EDRX_SWITCH :0[/bitmap]

Feature evaluation
› After this feature is activated, on the IoT of Metrics (IoM) platform, query the power consumption reported by
UEs that support this feature to see whether UE power consumption is reduced significantly when other
conditions remain unchanged.
Performance monitoring
Use the following counters to monitor the delivery of paging messages.
• New counters introduced

Counter ID Counter Name Description
1526744781 L.NB.Paging.S1.Rx.eDRX Number of eDRX paging messages received over the S1 interface in an NB-IoT
cell
1526744780 L.NB.Paging.S1.Rx Number of paging messages received over the S1 interface in an NB-IoT cell
1526744690 L.NB.Paging.UU.Att Number of UEs paged over the Uu interface in an NB-IoT cell

eRAN12.1
eMTC Feature Introduction
www.huawei.com
HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential

eMTC Network Architecture
MME/SGSN
Serving GW
PGW/GGSN
IOT Platform Application
G/U/L(eMTC) BTS Platform
HSS/PCRF
Upgrade Legacy EPC

eMTC System Architecture

Coverage enhancement
• eNodeB determines initial number of

high SINR
transmission repetition based on UE ‘s RSRP
measurement and adjusts the number of low SINR
No repetition
transmission repetition by the actual SINR of

Large repetitions
UE
Simulated gains
› UE with high SINR: no repetitions and 25
small number of repetitions 20
SNR Gain（dB）
› UE with low SINR: large number of 15
Theoretical simulation data, not
repetitions
10 product capacity
5
0
0 500 1000 1500 2000 2500
number of repetition

UE Low Cost
Cat 1 UE Cat 0 UE Cat-M UE
Max 1000 bits 1.4MHz BB,
Max 1000 bits Max BW 20MHz 20 MHz
for unicast Peak rate reduction TBS RF
Max 2216 bits
for broadcast Max UL TBS 5160 1000 1000
Rel-12 MTC
A single receive RF 10296 (unicast) 1000(unicast)

Max DL TBS 1000
2216 (broadcast) 2216 (broadcast)
Rel-13
eMTC
HD-FDD (optional)
1ms switching time Receive
2 1 1
antennas
Bandwidth reduction
1.4MHz RF & BB Support(optiona Support(optiona
bandwidth l) l)
HD-FDD Support(optional)
UL Tx power reduction 1ms swiching 1ms swiching
(optional) time time
23dBm->20dBm
UL max Tx 20(optional)
23 dBm 23 dBm
power dBm
Cost 100% 50% 25%

Idle Mode eDRX
DRX Cycle: 2.56s eDRX Cycle: up to 43.69mins

PTW
DRX DRX Cycle: 2.56s eDRX Time
• In the idle state, the paging cycle is extended from 2.56s to the maximum of 43.69 mins
• In each paging timing window, a number of paging opportunities are kept to ensure the success
rate of paging.
• MME may determine the eDRX cycle and PTW length according to UE service type(APN), or IMSI
segment.

Impact Analysis
• Positive Impact (Gain)

› Coverage enhanced：15dB compare to LTE
› Increase the terminal battery life
› Low UE cost: 25% of Cat1
• Negative Impacts
› eMTC UE and LTE UE shared the user number specifications of cell, LTE UE number will
decrease when eMTC UE access network.
› The available PRB and peak rate of LTE UE will decrease when eMTC UE access
network.

User Guide 1
 Dependency on Hardware/NEs/ Transimission

 Macro/ LampSite(DBS3900LTE)/ BTS3911E
 LMPT、UMPT
 LBBPd、UBBPd
 EPC needs to support R13 protocol(eDRX, Coverage level paging, EPC is not
required to upgrade if these features are not necessary)
 R13 CatM1 UE
 Dependency on other Features
 NA

User Guide 1
 eMTC feature is not supported if following feature is enabled

 LOFD-001007 High Speed Mobility
 LOFD-001008 Ultra High Speed Mobility
 LOFD-070220 eMBMS Phase 1 based on Centralized MCE Architecture
 LOFD-081221 Super Combined Cell
 LOFD-081223 Extended Cell Access Radius Beyond 100km

User Guide2
 License (Per Cell)
 MLOFD-121280 eMTC Introduction
 Activate Feature
 Turn on eMTC Switch
Set [MO] CellEmtcAlgo[/MO][Para] EmtcAlgoSwitch[/Para][bitmap]EMTC_SWITCH:1[/bitmap]
 Deactivate Feature
 Turn off eMTC Switch
Set [MO] CellEmtcAlgo[/MO][Para] EmtcAlgoSwitch[/Para][bitmap]EMTC_SWITCH:0[/bitmap]

User Guide3
 License (Per Cell)
 MLOFD-121282 Power Saving on eMTC.
• Activate Feature
 Turn on eDRX Switch
Set [MO] CellEmtcAlgo[/MO][Para] EmtcAlgoSwitch[/Para][bitmap]IDLE_EDRX_SWITCH:1[/bitmap]
Deactivate Feature
 Turn off eDRX Switch
Set [MO] CellEmtcAlgo[/MO][Para] EmtcAlgoSwitch[/Para][bitmap]IDLE_EDRX_SWITCH:0[/bitmap]

Example: Verification
 Observation after Activation
 MLOFD-121280 eMTC Introduction package
 New counters introduced

Counter ID Counter Name Description
1526745796
L.Traffic.User.eMTC.Avg Average number of eMTC users in a cell
1526745797
L.Traffic.User.MTC.Avg.CoverageLevelA Average number of modeA eMTC users in a cell
1526745798
L.Traffic.User.MTC.Max Maximum number of eMTC users in a cell
1526745799
L.Traffic.User.MTC.Max.CoverageLevelA Maximum number of modeA eMTC users in a cell
1526745800
L.Traffic.User.MTC.Max.CoverageLevelB Maximum number of modeB eMTC users in a cell

Example: Verification
 MLOFD-121282 Power Saving on eMTC
 New counters introduced
Counter Name Description
L.Paging.eMTC.S1.Rx.eDRX eDRX paging times of eMTC User in S1 interface of a cell

Contents
• eMTC Introduction
• Power Saving on eMTC

eMTC Introduction

Contents
1. Overview
2. Principles/Mechanism
3. Network Impact
4. Engineering Guidelines
5. Activation Observation and Verification
6. Reference Documents

Feature Overview
2017 Q2
2014
eRAN12.1 eMTC
•Cat M1 UE access and data transmission
•Coverage enhancement
•eDRX in Idle Mode
•EAB access control
•Congestion control on delay-tolerant RRC connection

Feature Overview – Benefits and Application Scenarios
 Introduction: The Internet of Things (IoT) is an important part of the information technology of the future. Technically, IoT is
expected to enable people-thing and thing-thing interconnections by combining communication technologies and
networks. To adapt to the needs of IoT services, the Enhanced Machine Type Communications (eMTC) technology is
introduced by 3GPP Release 13 based on the LTE evolution. eMTC has the following characteristics: wide coverage (15 dB
coverage enhancement compared with LTE), low cost, low power consumption, and massive connections.
 Benefits:
 Enhances coverage by 15 dB compared with traditional LTE coverage.
 Decreases UE costs and operator deployment costs.
 Decreases UE power consumption and prolongs the UE battery lifespan.
 Scenarios:
 eMTC is applicable to services, such as wearables' child/VIP tracking, health monitoring, vehicle guards, smart
logistics, smart elevators, and electronic billboards.

Contents
1. Overview
3. Network Impact

Feature Description – Basic Principles
eMTC Low Costs Cat 1 UE Cat 0 UE Cat M1 UE
Max. bandwidth 20 MHz 20 MHz 1.4 MHz
Peak rate reduction Max. UL TBS 5160 1000 1000
Cat M1 UE
Single antenna 10296 (unicast) 1000 (unicast)
Max. DL TBS 1000
(eMTC)
2216 (broadcast) 2216 (broadcast)
HD-FDD (optional)
Cat 0 UE
1 ms switching interval
(MTC)
Number of Antennas 2 1 1
Bandwidth reduced to 1.4

MHz
Supported Supported (optional) Supported (optional)
UL transmit power HD-FDD
(optional) 1 ms switching interval 1 ms switching interval
reduction (optional)
23 dBm to 20 dBm
Note: LTE UEs used for IoT services include the lowest-cost Cat 1 UE
introduced in Release 8, Cat 0 UE (no manufacturer has developed this type Maximum UL Transmit
23 dBm 23 dBm 20 dBm (optional)
of UE) introduced in Release 12, Cat M1 UE (Qualcomm and Altair developed Power
commercial chips in 2016 Q4, HiSilicon has not) introduced in Release 13.
Costs 100% 50% 25%

RB Resources of eMTC
The baseband and RF bandwidth of the eMTC UE is 1.4 MHz, so 3GPP specifies that one narrowband is composed of 6 non-overlapping
PRBs.
The system bandwidth is divided into several narrowbands. eMTC UE scheduling is limited by narrowbands. Cross-narrowband
scheduling is not allowed.
Note: The eMTC feature can now be deployed on the eNodeB only when the LTE bandwidth is 5 MHz or larger.

Coverage Level
Coverage enhancement (CE) levels are introduced in 3GPP specifications to adapt to the coverage depth and capacity performance
requirements of eMTC UEs.
• Four CE levels (0 to 3) are specified in idle mode, enhancing LTE coverage by 0, 5, 10, and 15 dB, respectively. eMTC UEs in idle mode
can choose a coverage level according to the measured RSRP. You can set parameters to specify the RSRP thresholds corresponding to
different CE levels.
• Two CE modes (A and B) are available for eMTC UEs in connected mode. CE levels for eMTC UEs in idle mode can map onto CE modes
for eMTC UEs in connected mode.
CE Mode A CE Mode B
CE levels in idle mode CE Level 0, CE Level 1 CE Level 2, CE Level 3
Transmission repetitions No repetition or a few repetitions (≤ 32) Many repetitions (≤ 2048)
UL Power Control Supported Not supported (always transmitting at the

maximum power)
CSI/CQI Supported Not supported
SRS Supported Not supported

eMTC DL Physical Layer Structure
• eMTC UEs do not receive signals from the downlink PDCCH, PCFICH, or PHICH. eMTC UEs and LTE UEs share other physical channels.
• eMTC has introduced the MPDCCH to send PDSCH and PUSCH scheduling indicators and common message indicators for eMTC UEs,
such as paging, RAR response, and UL ACK.
• eMTC UEs and LTE UEs share MIB messages. MIB messages are sent in subframe 0 and subframe 9 of each system frame with
transmission repetitions supported.
• eMTC has a new set of SIB messages, which are sent independently from LTE SIB messages.
Legacy for LTE

PDCCH
PCFICH
PHICH

eMTC UL Physical Layer Structure
• eMTC does not share PRACH resources with LTE and support CMD, FMD, and TMD. Huawei products use the TMD mode.
• eMTC does not share PUCCH resources with LTE. The PUCCH of eMTC supports cross-subframe frequency hopping rather than intra-subframe
frequency hopping.
• eMTC does not share PUSCH resources with LTE.

eMTC Random Access Procedure
• The PRACH preamble time-frequency

resources of eMTC UEs and common UEs
use the time division multiplexing (TDM) mode.
• During the non-contention-based RA

procedure, the eNodeB selects access
preambles for UEs from the dedicated
preamble group according to the eMTC UE
mode. If no response is received, the
contention-based RA procedure is performed.
• During the contention-based RA

procedure, the UE selects the preamble for
the corresponding coverage level to
initiate random access based on the RSRP
measurement result and the RSRP
threshold sent by the eNodeB.

eMTC Paging Procedure
An extended paging mechanism is introduced to reduce the power

consumption of eMTC UEs and save air interface resources.
1. The eNodeB sends information (the serving cell where the UE is

located, coverage level, recommended cell list and eNodeB list)
to the MME in the UE Context Release Complete message.
2. The MME sends the preceding information to the correct

eNodeB the next time it pages the eMTC UE.
3. Upon receiving the paging message, the eNodeB determines the

paging extension policy based on the number of current paging
times and planned number of paging times carried in the
message.
4. The eMTC UE is paged in the cell of its previous location,

recommended cells, and tracking area list (TAL) in descending
order.

eMTC Scheduling
• eMTC supports only cross-subframe scheduling, see the figure below.

• The MPDCCH is used to schedule the PDSCH of subframe (n + k), where n represents the end subframe of the
MPDCCH and k is greater than or equal to 2. The PDSCH to be scheduled is in at least the second valid downlink
subframe after the MPDCCH ends.
• The sequence of scheduling downlink PDSCHs starts from the last subframe of repetition times, which is the same
as that for LTE.
• The PDSCH HARQ feedback is performed in the same way as that for LTE.
• The DCI of the MPDCCH performs the PUSCH HARQ feedback, at least four TTIs after the end subframe of the
PUSCH.

eMTC Scheduling Policy
eMTC and LTE Dynamic Resource Sharing
› You can set the EmtcDlRbTargetRatio and EmtcUlRbTargetRatio parameters to specify the proportions of RB resources that LTE UEs and eMTC
UEs can use. If the cell PRB resource load is high, the eNodeB allocates resources to LTE UEs and eMTC UEs according to the specified proportions.
› If the cell resource load is low, the eNodeB schedules PRB resources to LTE UEs and eMTC UEs as required.
› eMTC UEs occupy RB resources for a long time, because eMTC supports the cross-subframe scheduling and repetition techniques. To prevent LTE
control information and high-priority services such as VoIP from being blocked for a long time, you can set DlLteRvsNbNum and UlLteRvsNbNum to
reserve RB resources for LTE UEs, ensuring LTE service performance when LTE and eMTC share a cell.
1 – Target proportion of RB Target proportion of RB

resources that eMTC UEs can resources that eMTC UEs Case 1: When both LTE and eMTC loads are high, bandwidth can be shared
use can use according to the specified target proportion of RB resources.
RB resources
reserved for LTE Case 2: When eMTC load is high but LTE load is low, eMTC UEs can occupy most
UEs bandwidth.
All system bandwidth occupied by LTE UEs Case 3: When LTE load is high but eMTC load is low, LTE UEs can occupy all the
bandwidth.
LTE PRB resources eMTC PRB resources
5 MHz 10 MHz 15 MHz 20 MHz
Number of system NBs 4 8 12 16
Maximum number of NBs that eMTC UEs can use 2 6 10 14

eMTC Coverage Enhancement
• The repetition technique allows the eNodeB to schedule the same data in the same resource block of consecutive subframes, and
allows the receive end to use the HARQ mode to obtain combination gains, reducing retransmission times and improving edge
coverage.
• The repetition technique applies to the following channels: PBCH, PRACH, PDSCH, MPDCCH, PUSCH, and PUCCH.
• Division of coverage levels: Coverage enhancement can be divided into different coverage levels based on different repetition times and modulation modes,
to balance capacity and coverage.
• In good-coverage areas, UE transmit power can be reduced, and the number of uplink/downlink data transmission repetitions can be reduced to the
minimum, even to 0.
• In poor-coverage areas, UT transmit power needs to be increased, and multiple uplink/downlink data transmission repetitions are required to ensure that
coverage requirements can be met.
1
CE Level 0 (LTE coverage area) CE Level 1 (LTE + 5 dB) CE Level 2 (LTE + 10 dB) CE Level 3 (LTE + 15 dB)

eMTC Congestion Control
RRC Access Control of Delay-Tolerant UEs
EAB Access Control
• When the EPC is overloaded, it sends an overload message, instructing the eNodeB to
• The extended access barring (EAB) mechanism uses an additional set of
reject the connection requests sent by delay-tolerant UEs and release connected UEs to
control parameters for MTC/eMTC UEs to control the access of these
relieve network congestion.
UEs without adding AC levels of traditional UEs. This mechanism does
• When the eNodeB rejects the access of or releases a delay-tolerant UE, it notifies the UE
not affect the access of traditional UEs.
of the cause value and wait time. The UE can initiate another access after the wait time
• SIB14 is added to notify EAB parameters to restrict the access of
expires.
MTC/eMTC UEs.

Contents
1. Overview
3. Network Impact

Network Impact Analysis
• Positive Impact (Benefits)

› Enhances coverage by 15 dB compared with traditional LTE coverage.
› Reduces deployment cost in vertical industries, because low-cost UEs (Cat M1 UEs) are used
for IoT services.
• Negative Impact
› Decreases LTE single-user peak rate, cell throughput rate, and user throughput rate. This is
because the eMTC feature occupies some PRB resources, reducing the PRB resources
available for LTE users.

Contents
1. Overview
3. Network Impact

Engineering Guidelines (1)
 Version Mapping
› The eNodeB and U2000 support this feature in the 17B version.
 Hardware/NE/Transmission Dependency
› Macro/LampSite (DBS3900 LTE)/BTS3911E
› LMPT, UMPT, LBBPd, and UBBPd
› The EPC must support 3GPP Release 13.
› Cat M1 UEs of Release 13 are required.
 Mutually Exclusive/Prerequisite/Impacted Features
 Prerequisite feature
None
 Mutually exclusive features
Feature ID Feature/Function Name

LOFD-070220 eMBMS Phase 1 based on Centralized MCE Architecture
LOFD-001007 High Speed Mobility
LOFD-001008 Ultra High Speed Mobility
LOFD-081221 Super Combined Cell
LOFD-081223 Extended Cell Access Radius Beyond 100 km
N/A Manual RB masking
N/A Enhanced MBSFN symbol power saving
N/A Mute RE switch
N/A Two RRU combination

• License Management

MLOFD-121280 eMTC Introduction eMTC Introduction(FDD) eNodeB per cell
N/A eNodeB hardware license eMTC BHCA(FDD) eNodeB per 100 BHCA
 When to Use
› Deploy this feature when the operator wishes to offer eMTC services. The system bandwidth of LTE cells must be higher than
or equal to 5 MHz.
› None
 Feature Activation
› Run the MOD CELLEMTCALGO command with EMTC_SWITCH(EmtcSwt) selected for the eMTC Algorithm Switch
parameter.
• Feature Deactivation
› Run the MOD CELLEMTCALGO command with EMTC_SWITCH(EmtcSwt) deselected for the eMTC Algorithm Switch
parameter.

Contents
1. Overview
3. Network Impact

Activation Observation and Verification
 Feature Evaluation
› Users can monitor the values of the following counters to check whether this feature is enabled. This feature is enabled if the counter
values are not 0.

1526745796 L.Traffic.User.eMTC.Avg Average number of eMTC UEs in a cell
1526745798 L.Traffic.User.eMTC.Max Maximum number of eMTC UEs in a cell
› After you activate this feature, create a Uu-interface tracing task, and check whether MIB carries the "schedulinginfoSIB1-BR" field. If
MIB carries "schedulinginfoSIB1-BR" and the field value is not 0, this feature is enabled successfully.

Power Saving on eMTC

Contents
1. Overview
3. Network Impact

Feature Overview – Benefits and Application Scenarios
 Introduction: 3GPP specifications define the eDRX in idle mode function. This function prolongs the paging cycle from the traditional 2.56s to the maximum 43.69
min, reduces the number of periodic paging channel monitoring times for UEs in idle mode. With this function, UEs can stay in the deep-sleep state while
maintaining low power consumption.
 Benefits: Compared with the traditional paging DRX function, this feature prolongs the UE sleep period and reduces power consumption.
 Application scenarios:
 IoT application scenarios where the operator wishes to reduce power consumption, for example, Smart Meter, sewer monitoring, care of the old and kids.
 UEs supporting eDRX in idle mode have accessed the cell.

Contents
1. Overview
3. Network Impact

Paging of eDRX in Idle Mode
• Hyper-SFN (also called H-SFN, or hyper frame) is introduced for eDRX, because eDRX paging cycle is quite long. 1 H-SFN equals 1024 SFNs, that is, 10.24s. An eDRX cycle is
measured in the unit of a hyper frame. Its value range is {10.24s *2^i}, where i equals a number from 1 to 8. The maximum eDRX cycle is 43.69 min.
• The eNodeB broadcasts an H-SFN in system information to the UE. When an eDRX paging occurs, the eNodeB calculates the UE paging time using the algorithm illustrated in
the figure (see 3GPP TS 36.304) and then sends a paging message to the UE. The UE calculates paging monitoring time using the same algorithm to receive the paging
message.
• Due to a long eDRX paging cycle, the MME cannot forward the paging message upon reception to the eNodeB for processing (limited cache, long response time). Instead, the
MME waits and sends the message only when the UE paging cycle arrives. To estimate the UE paging time, the MME needs to use the same H-SFN as that used by the eNodeB.
(The MME, eNodeB, and UE must be synchronous in H-SFN.)
• PTW specifies the time for the eDRX UE to monitor a paging message. The MME configures the PTW size for the UE. The UE is wakened up in the PTW and monitors the paging
message according to the common paging mode until it receives the paging message or the PTW ends. The network side can resend the paging message in the PTW,
increasing the paging success rate. The message is retransmitted by the EPC, rather than by the eNodeB.
 The paging time window (PTW) length is an integer multiple of 1.28s, and its
maximum length is 20.48s (16 x 1.28s). The eNodeB calculates the PTW start
and end positions based the eDRX cycle (TeDRX, H) and PTW length.
 UE_ID_H indicates the HASH ID calculated using an S-TMSI and the CRC-32
algorithm. eDRX supports S-TMSI-based paging instead of IMSI-based
paging.

Negotiation and Paging of eDRX in Idle Mode
• The eNodeB broadcasts an H-SFN in SIB1 to the UE.
• When the UE wishes to use eDRX, it sends an Attach Request or TAU Request
message carrying the eDRX cycle to the MME.
• If the MME accepts the request from the UE, it configures different eDRX cycles and
PTW sizes according to the local strategy and then sends the information in an Attach
Accept or TAU Accept message to the UE. If the MME rejects the request from the UE,
the UE uses the traditional paging DRX mechanism.
• The S-GW informs the MME when receiving data. The MME calculates the H-SFN and
paging frame (PF) for the UE to receive the paging message based on the eDRX cycle.
The MME sends the paging message to the eNodeB before the PF time for the UE
arrives.
• On receiving the paging message, the eNodeB uses the eDRX cycle carried in the
message to calculate the time of the H-SFN and PF. The eNodeB also calculates the PO
for the UE based on the configured paging cycle, and sends the paging message to the
UE at the calculated time.
• The UE uses the same method to calculate when the paging message is sent and
monitors the message at the calculated time. In this way, it can obtain the paging
message from the eNodeB.

Time Synchronization of eDRX in Idle Mode
• As stipulated in section 4.5.13.3 of 3GPP TS 23.682 (Release 13), the H-SFN for the eNodeB and that for the MME must be synchronous, and the
synchronization precision equals the traditional DRX cycle (about 1s to 2s). To achieve synchronization, the eNodeB and MME must configure the
same eDRX H-SFN start time (H-SFN = 0) and they separately calculate the H-SFN of the current time. No signaling interworking is involved.
• eNodeB implementation of the current version:
1. eNodeB Using Time Synchronization

› The GPS, BeiDou, 1588v2, 1588v2atr, GLONASS time sources are supported. The operator needs to deploy corresponding time equipment.
› The eNodeB and MME need to use the GPS time-scale, with the eDRX H-SFN start time always set to the GPS start time.]
2. eNodeB Using Frequency Synchronization

› The operator needs to deploy the NTP time server. It is recommended that time synchronization be performed between the eNodeB and NTP server (including the U2000)
every two hours.
› The eNodeB and MME need to configure the same eDRX H-SFN start time, and the MME supports sending a paging message to the eNodeB in advance, to ensure the UE
can be paged within the PTW.
• Interconnection with the EPC

› The EPC can use the GPS and UTC time-scales to calculate the H-SFN and SFN.
› If the eNodeB uses time synchronization, the EPC can configure the eDRX H-SFN start time as the GPS start time.
› If the eNodeB uses time synchronization, the EPC can send a paging message to the eNodeB in advance.

Contents
1. Overview
3. Network Impact

Network Impact Analysis
• Positive Impact (Benefits)

› The eDRX paging cycle for a UE in idle mode is long, and the UE stays in the deep-sleep state for a
long time while maintaining low power consumption.
• Negative Impact
› None

Contents
1. Overview
3. Network Impact

 Version Mapping
› The eNodeB and U2000 support this feature in the 17B version.
 Hardware/NE/Transmission Dependency
› The UE supports the eDRX in Idle Mode feature.
› The MME supports the eDRX in Idle Mode feature, the GPS time-scale, and can configure the eDRX start time as the GPS start
time.
› Time synchronization equipment (GPS, BeiDou, 1588v2, 1588v2atr, or GLONASS) must be deployed on the eNodeB.
 Mutually Exclusive/Prerequisite/Impacted Features

 None
 License Management
MLOFD-121282 Power Saving on eMTC Power Saving on eMTC(FDD) eNodeB per cell

 When to Use
› Enable this feature to ensure eDRX UE power saving when all of the following conditions are met:
- The operator wishes to reduce the power consumption of eMTC UEs.
- There are eMTC UEs supporting eDRX in Idle Mode in the target area.
- The EPC supports the eDRX function.
› Collect the number of eDRX UEs in the target area and the eDRX supporting capability of the MME, then decide whether to
deploy this feature.
› Collect the eDRX start time (H-SFN = 0) configured by the MME. Check whether the time is consistent with the eDRX H-SFN
start time configured by the eNodeB.
 Feature Activation
› Run the MOD CELLEMTCALGO command with IDLE_EDRX_SWITCH(IdleEdrxSwt) selected for the eMTC Algorithm Switch
parameter.
• Feature Deactivation
› Run the MOD CELLEMTCALGO command with IDLE_EDRX_SWITCH(IdleEdrxSwt) deselected for the eMTC Algorithm
Switch parameter.

Contents
1. Overview
3. Network Impact

Activation Observation and Verification
 Feature Evaluation
› When this feature is activated, users can observe the following counter to monitor the sending of eDRX paging messages.
1526746005 L.Paging.eMTC.S1.Rx.eDRX Number of received eDRX paging messages over the S1

interface for eMTC UEs in a cell
• Troubleshooting
› If a time synchronization-related alarm is reported, time synchronization fails. For details, see section "Troubleshooting" in
Synchronization Feature Parameter Description.

Thank You
THANK YOU
www.huawei.com
Copyright©2013 Huawei Technologies Co., Ltd. All Rights Reserved.

The information contained in this document is for reference purpose only, and is subject to change or withdrawal according to specific customer
requirements and conditions.
Page 107

Huawei SRAN12.1 CIoT-Huawei Workshop

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Huawei SRAN12.1 CIoT-Huawei Workshop

Enviado por

Direitos autorais:

Formatos disponíveis

SRAN 12.

Vodafone – Huawei SRAN12.1 Workshop

HUAWEI TECHNOLOGIES CO., LTD.

Deep Dive Selected CIoT Features

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

Market Connections in 2020 Requirements Technology

 Smart Home l ~1Mbps GSM/GPRS/CDMA

 Sensors, Meters l Small Packet (<100kbps) Zigbee, Bluetooth

LPWA: Low Power Wide Area

Low-Power Wide-Area Network is a type of

LPWA wireless telecommunication network designed to

Typical 3G IoT Cases Cat-1 is Better Option

B2C as Main Cases

Wearable IoT Gateway

Cat-1 IODT test Done with Qualcomm MDM9x07 chipset in 2016H1

The Rise of Cat-1 Assists Sunset of 3G in 2020

Typical 2G IoT Cases NB-IoT/eMTC is Better Option

Same Lower Power Deep

POS Smart Vending

The Rise of NB-IoT/eMTC Assists Sunset of 2G in 2025

4G ~10Mbps Cellular IoT

NB-IoT ~100kbps Cellular IoT(Full Capability LPWA)

2016.0 2016.05 2016.06 2016.09 2017.03

Boudica v100(ES) Boudica v100 Boudica v100

Boudica v200 (Planning)

2016Q2 2016Q3 2016Q4 2017

CIoT Industry Insights

CIoT12.1 Solution Overview

IoT Platform Unified IoT Platform

LTE NB-IoT MTC/eMTC LTE-V

Theoretical 3dB higher coverage than 2-Antenna Receive

NB-IoT RAN Sharing with Common Carrier NA Commercial

eMTC Introduction 2016Q4 Commercial

NB-IoT NB-IoT NB-IoT

NB-IoT Data transmission option：

Standalone LTE Guard Band LTE In Band

Standalone LTE Guard Band LTE In Band

NB-IoT: Uplink and Downlink Subcarrier

Downlink: OFDMA with 15kHz Subcarrier Spacing is 15KHz ST

Scheduled dynamic by eNodeB

Co-exist in the same NB-IoT cell

20 Note: 3.75KHz is under planning in later version.

PSD Gain Repetition Gain

3dB Gain(vs 2R)

Tx Power Consumption 0.0135mWh

Idle State 1mA Once Communication 0.022mWh

MME determine cycle according to UE service type(APN)

Tx Power Consumption 0.0135mWh

US700(Band12/13) RRU3269, RRU3203

APT700(Band28) RRU3262,RRU3268 RRU3268(V3&V6)

DD800(Band 20) RRU3220, RRU3222,

850M(Band 5) RRU3942, RRU3938 v3(Korea) RRU3908 v2, RRU3936 v3,RRU3804,

RRU3908 v2, MRFU v2, MRFU v2a

RRU3936, RRU3971, RRU3630, RRU3632, RRU3632B,

Repetition Idle Mode eDRX

MME determine eDRX & PTW cycle according to UE service type(APN)

high SINR DRX Cycle: 2.56s eDRX Cycle: up to 43.69mins

15dB Gain PTW

DRX Cycle: 2.56s Time

Deep Dive Selected Features

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 26

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 27

transmission. Only the 15-kHz subcarrier spacing is supported.)  Number of subcarriers: 12